OSS license management
Table of Contents
Self.Hosted 22.06 (EoL)
Expand all | Collapse all
-
- Getting started
- System Requirements
- Prisma Cloud container images
- Onebox
- Kubernetes
- OpenShift v4
- Console on Fargate
- Amazon ECS
- Alibaba Cloud Container Service for Kubernetes (ACK)
- Azure Kubernetes Service (AKS)
- Amazon Elastic Kubernetes Service (EKS)
- Google Kubernetes Engine (GKE)
- Google Kubernetes Engine (GKE) Autopilot
- IBM Kubernetes Service (IKS)
- Windows
- Defender types
- Cluster Context
-
- Install a single Container Defender
- Automatically Install Container Defender in a Cluster
- App-Embedded Defender
- App-Embedded Defender for Fargate
- Default setting for App-Embedded Defender file system protection
- VMware Tanzu Application Service (TAS) Defender
- Serverless Defender
- Serverless Defender as a Lambda layer
- Auto-defend serverless functions
- Install a single Host Defender
- Auto-defend hosts
- Deploy Prisma Cloud Defender from the GCP Marketplace
- Decommission Defenders
- Redeploy Defenders
- Uninstall Defenders
-
- Rule ordering and pattern matching
- Backup and restore
- Custom feeds
- Configuring Prisma Cloud proxy settings
- Prisma Cloud Compute certificates
- Configure Agentless Scanning
- Agentless Scanning Modes
- 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
- Credentials store
- Cloud accounts
-
- Prisma Cloud vulnerability feed
- Vulnerability Explorer
- Vulnerability management rules
- Search CVEs
- Scan reports
- Scanning procedure
- Customize image scanning
- Configure Registry Scans
-
- Scan Images in Sonatype Nexus Registry
- Scan images in Alibaba Cloud Container Registry
- Scan images in Amazon EC2 Container Registry (ECR)
- Scan images in Azure Container Registry (ACR)
- Scan images in Docker Registry v2 (including Docker Hub)
- 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 Artifactory Docker Registry
- Scan images in OpenShift integrated Docker registry
- Trigger registry scans with Webhooks
- Base images
- Configure VM image scanning
- Configure code repository scanning
- Agentless scanning
- Malware scanning
- Vulnerability risk tree
- Vulnerabilities Detection
- CVSS scoring
- Windows container image scanning
- Serverless function 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
- Cloud discovery
- OSS license management
- API
End-of-Life (EoL)
OSS license management
Prisma Cloud can detect licenses for package dependencies in code repositories.
It can scan code repos hosted by service providers (currently GitHub only).
It can also scan build folders constructed by CI build jobs.
A license policy defines the criticality of a license.
For example, you might specify consider any package with a GPL license as a critical issue.
Depending on your license policy, Prisma Cloud can raise alerts and block builds.
Create a license compliance policy
Compliance policies consist of one or more rules.
Prisma Cloud ships with a default rule named
Default - alert all components
.
This rule ships with alerts disabled, so the policy is effectively disabled.
As a starting point, consider cloning this rule, and reconfiguring it for your own purposes.
Set a threshold, and declare licenses you consider critical.
Rule order is important, so be sure your custom rule sits above the default rule.- Open Console.
- Go toDefend > Compliance > Code repositories.
- Choose the target of your policy.If your policy targets GitHub, go to theRepositoriestab.If your policy targets your CI pipeline, go to theCItab.
- ClickAdd rule.
- Specify a rule name.
- InScope, select one or more collections to apply your policy to specific repos.Use the defaultAllcollection to apply it to all repos.
- Set the rule thresholds.
- Specify the severity of each license of interest.Each field offers SPDX license identifiers as suggestions. Pattern-matching expressions are supported (e.g., GPL-*).
Scan with twistcli
To scan a folder with twistcli, use the following command:
twistcli coderepo scan [FOLDER_PATH] --details
Contents of the repo are assessed according to the policy in
Defend > Compliance > Code repositories > CI
.
Scan results are published in Monitor > Compliance > Code repositories > CI
For CI only, a status column indicates if twistcli passed or failed the build according to the defined policy.
Review scan results.
Go to
Monitor > Compliance > Code repositories
.
Each row in the results table has a meter which shows the number of compliance issues at each severity level.
Click on a row to drill into the details of the scan report.