Integrate Prisma Cloud with GitHub
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 Prisma Cloud with GitHub
Prisma Cloud supports OAuth 2.0 as an authentication mechanism.
GitHub users can log into Prisma Cloud Console using GitHub as an OAuth 2.0 provider.
Prisma Cloud supports the authorization code flow only.
A CA certificate configured in
Manage > Authentication > System certificates > Certificate-based authentication to Console
is not supported in GitHub.Configure Github as an OAuth provider
Create an OAuth App in your GitHub organization so that users in the organization can log into Prisma Cloud using GitHub as an OAuth 2.0 provider.
- Log into GitHub as the organization owner.
- Go toSettings > Developer Settings > OAuth Apps, and clickNew OAuth App(orRegister an applicationif this is your first app).
- InApplication name, enterPrisma Cloud.
- InHomepage URL, enter the URL for Prisma Cloud Console in the format https://<CONSOLE>:<PORT>.
- InAuthorization callback URL, enter https://<CONSOLE>:<PORT>/api/v1/authenticate/callback/oauth.
- ClickRegister application.
- Copy theClient IDandClient Secret, and set them aside setting up the integration with Prisma Cloud.
Integrate Prisma Cloud with GitHub
Set up the integration so that GitHub users from your organization can log into Prisma Cloud.
- Log into Prisma Cloud Console.
- Go toManage > Authentication > Identity Providers > OAuth 2.0.
- SetIntegrate Oauth 2.0 users and groups with Prisma CloudtoEnabled.
- SetIdentity providertoGitHub.
- SetClient IDandClient secretto the values you copied from GitHub.
- SetAuth URLtohttps://github.com/login/oauth/authorize.
- SetToken URLtohttps://github.com/login/oauth/access_token.
- ClickSave.
Prisma Cloud to GitHub user identity mappings
Create a Prisma Cloud user for each GitHub user that should have access to Prisma Cloud.
After the user is authenticated, Prisma Cloud uses the access token to query GitHub for the user’s information (user name, email).
The user information returned from GitHub is compared against the information in the Prisma Cloud Console database to determine if the user is authorized.
If so, a JWT token is returned.
- Go toManage > Authentication > Users.
- ClickAdd User.
- SetUsernameto the GitHub user name.
- SetAuth methodtoOAuth.
- Select a role for the user.
- ClickSave.
- Test logging into Prisma Cloud Console.
- Logout of Prisma Cloud.
- On the login page, selectOAuth, and then clickLogin.
- Authorize the Prisma Cloud OAuth App to sign you in.
Prisma Cloud group to GitHub organization mappings
Use groups to streamline how Prisma Cloud roles are assigned to users.
When you use groups to assign roles, you don’t have to create individual Prisma Cloud accounts for each user.
Groups can be associated and authenticated with by multiple identity providers.
- Go toManage > Authentication > Groups.
- ClickAdd Group.
- InName, enter the GitHub organization.
- InAuthentication method, selectExternal Providers.
- InAuthentication Providers, selectOAuth group.
- Select a role for the members of the organization.
- ClickSave.
- Test logging into Prisma Cloud Console.
- Logout of Prisma Cloud.
- On the login page, selectOAuth, and then clickLogin.
- Authorize the Prisma Cloud OAuth App to sign you in.