Integrate with PingFederate 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 PingFederate 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, users can log into the Console with their federated credentials.
This article provides detailed steps for federating your Prisma Cloud Console with your PingFederate v8.4 Identity Provider (IdP).
The Prisma Cloud/PingFederate SAML federation flow works as follows:
- Users browse to Prisma Cloud Console.
- Their browsers are redirected to the PingFederate SAML 2.0 endpoint.
- They enter their credentials to authenticate. Multi-factor authentication can be enforced at this step.
- A PingFederate 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.
Prisma Cloud Console is integrated with PingFederate as a federated SAML Service Provider.
The steps to set up the integration are:
Configure PingFederate
- Logon to PingFederate
- Go toIdP Configuration > SP Connection > Connection Type, and selectBrowser SSO.
- Go toIdP Configuration > SP Connection > Connection Options, and selectBrowser SSO Profiles SAML 2.0.
- Skip theImport Metadatatab.
- Go toIdP Configuration > SP Connection > General Info.
- InPartner’s Entity ID, entertwistlock.By default, the Partner’s Entity ID is "twistlock". When configuring the SAML Audience in the Prisma Cloud Console, the default value is "twistlock". If you choose a different value here, be sure to set the same value in your Console.
- InConnection Name, enterPrisma Cloud Console.
- ClickAdd.
- InBrowser SSO > SAML Profiles, select bothIDP-INITIATED SSOandSP-INITIATED SSO.
- Go toAssertion Creationand setSAML_SUBJECTtoSAML 1.1 nameid-format.In this example you mapped the user’s email address to the SAML_SUBJECT attribute which matches the user’s Prisma Cloud account. If you are using group-to-Prisma Cloud-role associations, addgroupsto the list of attributes to be returned in the SAML token.
- InIdP Configuration > SP Connection > Browser SSO > Protocol Settings > Assertion Consumer Service URL, specify an assertion consumer URL.
- UnderBinding, selectPOST.
- UnderEndpoint URL, enterhttps://<FQDN_OF_YOUR_TWISTLOCK_CONSOLE>:8083/api/v1/authenticate.
- InIdP Configuration > SP Connection > Browser SSO > Protocol Settings > Signature Policy, leave both values unchecked.
- InIdP Configuration > SP Connection > Browser SSO > Protocol Settings, review the protocol settings.
- ClickDone.
- Copy the PingFederate SAML token signing X.509 certificate as Base64 inServer Configuration. This certificate will be imported into Prisma Cloud Console.
Configure Prisma Cloud Console
Configure Prisma Cloud Console.
- Login to the Prisma Cloud Console as an administrator.
- Go toManage > Authentication > Identity Providers > SAML.
- SetIntegrate SAML users and groups with Prisma CloudtoEnabled.
- SetIdentity ProvidertoPing.
- InIdentity provider single sign-on URL, enter your PingFederate IdP endpoint.
- InIdentity provider issuer, enter your PingFederate Entity ID.
- InAudience, entertwistlock(default) or the value you set for Partner’s Entity ID in PingFederate.
- InX.509 certificate, paste your PingFederate X.509Signing Certificate Base64.
- ClickSave.
User account name matching
User account name matching.
- Go toManage > Authentication > Users.
- ClickAdd user.
- Create a new user:
- InUsername, enter the value returned within the SAML_SUBJECT attribute IdP user’s email address.
- InRole, select the appropriate role.
- SetCreate user in local Prisma Cloud account databasetoOff.
- ClickSave.
- Test login into the Prisma Cloud Console via PingFederate SAML federation.Leave your existing session logged onto the Prisma Cloud Console in case you encounter issues. Open a new incognito browser window and go tohttps://<CONSOLE>:8083.
Group name matching
Group name matching.
- Go toManage > Authentication > Groups.
- Click the+Add Groupbutton.
- 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.
- ClickSave
- Test login into the Prisma Cloud Console via PingFederate SAML federation.Leave your existing session logged onto the Prisma Cloud Console in case you encounter issues. Open a new incognito browser window and go tohttps://<CONSOLE>:8083.