Integrate with Okta via SAML 2.0 federation
Table of Contents
Self.Hosted 31.xx
Expand all | Collapse all
-
- Getting started
- System Requirements
- Cluster Context
-
- Prisma Cloud Container Images
- Kubernetes
- Deploy the Prisma Cloud Console on Amazon ECS
- Console on Fargate
- Onebox
- Alibaba Cloud Container Service for Kubernetes (ACK)
- Azure Container Service (ACS) with Kubernetes
- Azure Kubernetes Service (AKS)
- Amazon Elastic Kubernetes Service (EKS)
- IBM Kubernetes Service (IKS)
- OpenShift v4
-
- Defender Types
- Manage your Defenders
- Redeploy Defenders
- Uninstall Defenders
-
- Deploy Orchestrator Defenders on Amazon ECS
- Automatically Install Container Defender in a Cluster
- Deploy Prisma Cloud Defender from the GCP Marketplace
- Deploy Defenders as DaemonSets
- VMware Tanzu Application Service (TAS) Defender
- Deploy Defender on Google Kubernetes Engine (GKE)
- Google Kubernetes Engine (GKE) Autopilot
- Deploy Defender on OpenShift v4
-
- Agentless Scanning Modes
-
- Onboard AWS Accounts for Agentless Scanning
- Onboard Azure Accounts for Agentless Scanning
- Configure Agentless Scanning for Azure
- Onboard GCP Accounts for Agentless Scanning
- Configure Agentless Scanning for GCP
- Onboard Oracle Cloud Infrastructure (OCI) Accounts for Agentless Scanning
- Configure Agentless Scanning for Oracle Cloud Infrastructure (OCI)
- Agentless Scanning Results
-
- Rule ordering and pattern matching
- Backup and Restore
- Custom feeds
- Configuring Prisma Cloud proxy settings
- Prisma Cloud Compute certificates
- Configure scanning
- User certificate validity period
- Enable HTTP access to Console
- Set different paths for Defender and Console (with DaemonSets)
- Authenticate to Console with Certificates
- Configure custom certs from a predefined directory
- Customize terminal output
- Collections
- Tags
- Logon settings
- Reconfigure Prisma Cloud
- Subject Alternative Names
- WildFire Settings
- Log Scrubbing
- Clustered-DB
- Permissions by feature
-
- Logging into Prisma Cloud
- Integrating with an IdP
- Integrate with Active Directory
- Integrate with OpenLDAP
- Integrate Prisma Cloud with Open ID Connect
- Integrate with Okta via SAML 2.0 federation
- Integrate Google G Suite via SAML 2.0 federation
- Integrate with Azure Active Directory via SAML 2.0 federation
- Integrate with PingFederate via SAML 2.0 federation
- Integrate with Windows Server 2016 & 2012r2 Active Directory Federation Services (ADFS) via SAML 2.0 federation
- Integrate Prisma Cloud with GitHub
- Integrate Prisma Cloud with OpenShift
- Non-default UPN suffixes
- Compute user roles
- Assign roles
-
- Prisma Cloud Vulnerability Feed
- Scanning Procedure
- Vulnerability Management Policies
- Vulnerability Scan Reports
- Scan Images for Custom Vulnerabilities
- Base images
- Vulnerability Explorer
- CVSS scoring
- CVE Viewer
-
- Configure Registry Scans
- Scan Images in Alibaba Cloud Container Registry
- Scan Images in Amazon Elastic Container Registry (ECR)
- Scan images in Azure Container Registry (ACR)
- Scan Images in Docker Registry v2 (including Docker Hub)
- Scan Images in GitLab Container Registry
- Scan images in Google Artifact Registry
- Scan Images in Google Container Registry (GCR)
- Scan Images in Harbor Registry
- Scan Images in IBM Cloud Container Registry
- Scan Images in JFrog Artifactory Docker Registry
- Scan Images in Sonatype Nexus Registry
- Scan images in OpenShift integrated Docker registry
- Scan Images in CoreOS Quay Registry
- Trigger Registry Scans with Webhooks
- Configure VM image scanning
- Configure code repository scanning
- Malware scanning
- Windows container image scanning
- Serverless Functions Scanning
- VMware Tanzu Blobstore Scanning
- Scan App-Embedded workloads
- Troubleshoot Vulnerability Detection
-
- Compliance Explorer
- Enforce compliance checks
- CIS Benchmarks
- Prisma Cloud Labs compliance checks
- Serverless functions compliance checks
- Windows compliance checks
- DISA STIG compliance checks
- Custom compliance checks
- Trusted images
- Host scanning
- VM image scanning
- App-Embedded scanning
- Detect secrets
- OSS license management
-
- Alert Mechanism
- AWS Security Hub
- Cortex XDR alerts
- Cortex XSOAR alerts
- Email alerts
- Google Cloud Pub/Sub
- Google Cloud Security Command Center
- IBM Cloud Security Advisor
- JIRA Alerts
- PagerDuty alerts
- ServiceNow alerts for Security Incident Response
- ServiceNow alerts for Vulnerability Response
- Slack Alerts
- Splunk Alerts
- Webhook alerts
- API
Integrate with Okta via SAML 2.0 federation
Many organizations use SAML to authenticate users for web services.
Prisma Cloud supports the SAML 2.0 federation protocol to access the Prisma Cloud Console.
When SAML support is enabled, administrators can log into Console with their federated credentials.
This article provides detailed steps for federating your Prisma Cloud Console with Okta.
The Prisma Cloud/Okta SAML federation flow works as follows:
- Users browse to Prisma Cloud Console.
- Their browsers are redirected to the Okta SAML 2.0 endpoint.
- They enter their credentials to authenticate. Multi-factor authentication can be enforced at this step.
- A SAML token is returned to Prisma Cloud Console.
- Prisma Cloud Console validates the SAML token’s signature and associates the user to their Prisma Cloud account via user identity mapping or group membership.
Integrating Prisma Cloud with SAML consists of setting up your IdP, then configuring Prisma Cloud to integrate with it.
Setting up Prisma Cloud in Okta
Set up Prisma Cloud in Okta.
- Log into the Okta admin dashboard.
- On the right, clickAdd Applications.
- On the left, clickCreate new app.
- SelectSAML 2.0, and then clickCreate.
- In theApp namefield, enterPrisma Cloud Console, then clickNext.
- In the SAML Settings dialog:
- In theSingle Sign On URLfield, enterhttps://<CONSOLE_ADDR>:8083/api/v1/authenticate.Note that if you have changed the default port you use for the HTTPS listener, you’d need to adjust the URL here accordingly. Additionally, this URL must be visible from the Okta environment, so if you’re in a virtual network or behind a load balancer, it must be configured to forward traffic to this port and it’s address is what should be used here.
- SelectUse this for Recipient URL and Destination URL.
- In the field forAudience Restriction, entertwistlock(all lowercase).
- ExpandAdvanced Settings.
- Verify thatResponseis set toSigned.
- Verify thatAssertion Signatureis set toSigned.
- (Optional) Add a group.Setting up groups is optional. If you set up group attribute statements, then permission to access Prisma Cloud is assessed at the group level. If you don’t set up group attribute statements, them permission to access Prisma Cloud is assessed at the user level.
- Scroll down to theGROUP ATTRIBUTE STATEMENTSsection.
- In theNamefield, entergroups.
- In filter drop down menu, selectRegexand enter a regular expression that captures all the groups defined in Okta that you want to use for access control rules in Prisma Cloud.In this example, the regular expression.*(t|T)wistlock.*is used to include all groups prepended with either Prisma Cloud or twistlock. You should enter your own desired group name here. If you have just one group, such as YourGroup, then just enterYourGroup. Regular expressions are not required. If you have multiple groups, you can use a regular expressions, such as(group1|group2|group3).
- ClickNext, and then clickFinish.You are directed to a summary page for your new app.
- Click on thePeopletab, and add users to the Prisma Cloud app.
- Click on theGroupstab, and add groups to the Prisma Cloud app.
- Click on theSign Ontab and clickView setup instructions.The following values are used to configure Prisma Cloud Console, so copy them and set them aside.
- Identity Provider Single Sign-On URL
- Identity Provider Issuer
- X.509 Certificate
Configuring Console
Configure Prisma Cloud Console.
- Open Console, and login as admin.
- Go toManage > Authentication > Identity Providers > SAML.
- SetIntegrate SAML users and groups with Prisma CloudtoEnabled.
- SetIdentity providertoOkta.
- Copy the following values from Okta and paste them into their corresponding fields in Console:
- Identity Provider Single Sign-On URL
- Identity Provider Issuer
- X.509 Certificate
- InAudience, entertwistlock.
- ClickSave.
Granting access by group
Grant access to Prisma Cloud Console by group.
Each group must be assigned a role.
- Open Console.
- Define a SAML group.
- Go toManage > Authentication > Groups.
- ClickAdd group.
- In theNamefield, enter a group name.The group name must exactly match the group name in the SAML IdP. Console does not verify if that the value entered matches a group name in the SAML IdP.
- Select theSAML groupcheckbox.
- Select a role.
- Select a project(s) - Optional.
- ClickSave.
Granting access by user
Grant access to Prisma Cloud Console by user.
Each user must be assigned a role.
- Open Console.
- Define a SAML user.
- Go toManage > Authentication > Users.
- ClickAdd user.
- In theUsernamefield, enter a user name.The username must exactly match the username in the SAML IdP. Console does not verify if that the value entered matches a user name in the SAML IdP.
- SelectSAMLas the Auth method
- Select a role.
- (Optional) Select a project(s).
- ClickSave.