Integrate Google G Suite 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 Google G Suite 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 Console with their federated credentials.
This article provides detailed steps for federating your Prisma Cloud Console with Google G Suite.
The Prisma Cloud/G Suite SAML federation flow works as follows:
- Users browse to Prisma Cloud Console.
- Their browsers are redirected to the G Suite 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.
Setting up Google G Suite
Prisma Cloud supports SAML integration with Google G Suite.
- Log into your G Suite admin console.
- Click onApps.
- Click onSAML apps.
- Click the+button at the bottom to add a new app.
- ClickSETUP MY OWN CUSTOM APPat the bottom of the dialog.
- Copy theSSO URLandEntity ID, and download the certificate. You will need these later for setting up the integration in Prisma Cloud Console. ClickNEXT.
- Enter anApplication Name, such asPrisma Cloud, then clickNEXT.
- In the Service Provider Details dialog, enter the following details, then clickNEXT.
- InACS URL, enter:https://<CONSOLE_IPADDR | CONSOLE_HOSTNAME>:8083/api/v1/authenticate.
- InEntity ID, enter:twistlock.
- EnableSigned Response.
- ClickFINISH, thenOK.
- Turn the application to on. Select eitherONfor everyone orON for some organizations.
Setting up Prisma Cloud
Set up Prisma Cloud for G Suite integration.
- Log into Console, then go toManage > Authentication > Identity Providers > SAML.
- SetIntegrate SAML users and groups with Prisma CloudtoEnabled.
- SetIdentity providertoG Suite.
- Set up the following parameters:
- Paste the SSO URL, Entity ID, and certificate that you copied during the G Suite set up into theIdentity Provider single sign-on URL,Identity provider issuer, andX.509 certificatefields.
- SetAudienceto match the application Entity ID configured in G Suite. Entertwistlock.
- ClickSave.
- Go toManage > Authentication > Users, and clickAdd user.
- In theUsernamefield, enter the G Suite email address the user you want to add. Select a role, then clickSave. Be sureCreate user in local Prisma Cloud account databaseisOff.
- Log out of Console.You will be redirected into G Suite and you might need to enter your credentials. After that, you will be redirected back into Prisma Cloud and authenticated as a user.