CI plugin policy
Table of Contents
Prisma Cloud Enterprise Edition
Expand all | Collapse all
-
- Getting started
- System Requirements
- Cluster Context
-
- 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
- Deploy Defender with Declarative Object Management
-
- Agentless Scanning Modes
-
- Onboard AWS Accounts for Agentless Scanning
- Configure Agentless Scanning for AWS
- 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
- Customize terminal output
- Collections
- Tags
- WildFire Settings
- Log Scrubbing
- Permissions by feature
-
- 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
- Malware Scanning
- 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
CI plugin policy
Prisma Cloud lets you centrally define your CI policy in Console.
These policies establish security gates at build-time.
Use policies to pass or fail builds, and surface security issues early during the development process.
There are two types of policies you can use to target your CI tool: vulnerability policies and compliance policies.
CI rules have the same parameters as the rules for registries and deployed components, letting you evenly enforce policy in all phases of the app lifecycle.
Prisma Cloud offers the following components for integrating with CI tools:
- A native Jenkins plugin.
- A stand-alone, statically compiled binary, called twistcli, that can be integrated with any CI tool.
Vulnerability policy
For more information about the parameters in vulnerability management rules, see here.
Vulnerability rules that target the build tool can allow specific vulnerabilities by creating an exception and setting the effect to 'ignore'.
Block them by creating an exception and setting the effect to 'fail'.
For example, you could create a vulnerability rule that explicitly allows CVE-2018-1234 to suppress warnings in the scan results.
Rules take effect as soon as they are saved.
Create CI Policy for Vulnerabilities
Vulnerability CI policies let you raise alerts or fail builds when images/functions scanned in the CI process have vulnerabilities.
- Open Console.
- Go toDefend > Vulnerabilities > {Images | Functions} > CI.
- SelectAdd rule.
- Enter aRule nameand configure the rule.
- SelectSave.
- View the scan report underMonitor > Vulnerabilities > {Images | Functions} > CI.
Compliance policy
The compliance checks in Prisma Cloud are based on the Center for Internet Security (CIS) Docker Benchmarks.
We also provide numerous checks from our lab.
You can also implement your own checks using custom checks.
Compliance rules that target the CI tool can permit specific compliance issues by setting the action to 'ignore'.
Rules take effect as soon as they are saved.
Create CI Policy for Compliance
Compliance CI policies let you monitor, audit, and enforce security and configuration settings for your CI images and functions.
- Open Console.
- Go toDefend > Compliance > {Containers and images | Functions} > CI.
- SelectAdd rule.
- Enter aRule nameand configure the rule to enforce compliance checks.
- SelectSave.
- View the scan report underMonitor > Compliance > {Images | Functions} > CI.
Alert Profiles
To surface critical compliance and vulnerabilities events, you can create alert profiles for forwarding the alerts to various integrations.