Document:Prisma Cloud Compute Edition Administrator’s Guide

Helm charts

Filter

Welcome
- Releases
- Getting started
- Product architecture
- Support lifecycle
- Upcoming support lifecycle changes for Prisma Cloud Compute Edition and modules
- Licensing
- Prisma Cloud Enterprise Edition vs Compute Edition
- Utilities and plugins
Install
- Getting started
- System requirements
- Prisma Cloud container images
- Onebox
- Kubernetes
- OpenShift
- OpenShift
- VMware Tanzu Kubernetes Grid (TKG)
- Docker Swarm
- Amazon ECS
- Windows
- Defender types
- Install Defender
Upgrade
- Upgrade Prisma Cloud
- Upgrade Onebox
- Kubernetes
- OpenShift
- Helm charts
- Docker Swarm
- Amazon ECS
- Manually upgrade single Container Defenders
- Manually upgrade Defender DaemonSets
- Manually upgrade Defender DaemonSets (Helm)
- Manually upgrade Docker Swarm Defenders
Technology overviews
- Prisma Cloud Advanced Threat Protection
- App-specific network intelligence
- Container Runtimes
- Radar
- Serverless Radar
- Prisma Cloud Rules Guide - Docker
- Defender architecture
- Telemetry
Configure
- Rule ordering and pattern matching
- Disaster recovery
- Custom feeds
- Configuring Prisma Cloud’s proxy settings
- Custom certs for Console access
- 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
- Logon settings
- Reconfigure Prisma Cloud
- Subject Alternative Names
Authentication
- Logging into Prisma Cloud
- 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
- Use custom certificates for authorization
- Credentials store
Vulnerability management
- Vulnerability Explorer
- Vulnerability management rules
- Search CVEs
- Scan reports
- Customize image scanning
- Configure registry scans
- Registry scanning
- Base images
- Configure VM image scanning
- Configure code repository scanning
- Malware scanning
- Vulnerability risk tree
- Detect vulnerabilities in unpackaged software
- CVSS scoring
- Google Cloud Container Builder
- Windows container image scanning
- Serverless function scanning
- VMware Tanzu blobstore scanning
Compliance
- Compliance Explorer
- Manage compliance
- CIS Benchmarks
- Prisma Cloud Labs compliance checks
- Serverless functions compliance checks
- Windows compliance checks
- Custom compliance checks
- Trusted images
- Host scanning
- VM image scanning
- Detect secrets
- Cloud discovery
Runtime defense
- Runtime defense
- Runtime defense for processes
- Runtime defense for networking
- Runtime defense for file systems
- Runtime defense for hosts
- Custom runtime rules
- Blocked containers
- Import and export individual rules
- Discrete blocking
- Runtime defense for AWS Fargate
- Incident Explorer
- Incident types
Access control
- Role-based access control for Docker Engine
- Admission control with Open Policy Agent
Continuous integration
- Jenkins plugin
- Jenkins Freestyle project
- Jenkins Maven project
- Jenkins Pipeline project
- Run Jenkins in a container
- Jenkins pipeline on Kubernetes
- CloudBees Core pipeline on Kubernetes
- CI plugin policy
WAAS
- Web-Application and API Security (WAAS)
- Deploying WAAS
- Firewall Settings
- API Protection
- DoS protection
- Bot Protection
- WAAS Access Controls
- Advanced Settings
- WAAS Analytics
Firewalls
- Cloud Native Network Firewall (CNNF)
Secrets
- Secrets manager
- Integrate with secrets stores
- Secrets Stores
- Inject secrets into containers
- Injecting secrets: end-to-end example
Alerts
- Alert mechanism
- AWS Security Hub
- Cortex XSOAR alerts
- Email alerts
- Google Cloud Pub/Sub
- Google Cloud Security Command Center
- IBM Cloud Security Advisor
- JIRA Alerts
- PagerDuty alerts
- ServiceNow alerts
- ServiceNow alerts
- Slack Alerts
- Webhook alerts
Audit
- Event viewer
- Host activity
- Administrative activity audit trail
- Annotate audit event records
- Delete audit logs
- Syslog and stdout integration
- Log rotation
- Throttling audits
- Prometheus
- Kubernetes auditing
Tools
- twistcli
- Scan images with twistcli
- Install Console with twistcli
- Update the Intelligence Stream in offline environments
Deployment patterns
- Projects
- Migration options for scale projects
- Best practices for DNS and certificate management
- Caps
- Migrating to a SaaS Console
- Performance planning
API
- Stability guide
- Access the API
- Set up a fresh Console
- Automate Defender install
- Manage compliance policies with the API
- 20.12 porting guide
Howto
- Configure an AWS Classic Load Balancer for ECS
- Configure Prisma Cloud to use Nginx Ingress Controller in Kubernetes
- Configure the load balancer type for AWS EKS
- Deploy Defenders outside an OpenShift Cluster
- Configure Prisma Cloud Console’s listening ports
- Provision tenant projects in OpenShift
- Configure Prisma Cloud to use Istio Ingress Gateway
- Disable automatic learning
- Performing a rolling upgrade of Defenders
- Debug data

Helm charts

If you installed Prisma Cloud into your Kubernetes or OpenShift cluster with Helm charts, you can upgrade with the helm upgrade command.

First upgrade Console. Console will then automatically upgrade all deployed Defenders for you.

If you’ve disabled Defender auto-upgrade or if Console fails to upgrade one or more Defenders, manually upgrade your Defenders.

You must manaully upgrade App-Embedded Defenders.

Upgrading Console

Generate an updated Helm chart for Console, and then upgrade to it.

Download the latest recommended release.

Create an updated Console Helm chart.

$ <PLATFORM>/twistcli console export kubernetes \
  --service-type LoadBalancer \
  --helm

Install the updated chart.

$ helm upgrade twistlock-console \
  --namespace twistlock \
  --recreate-pods \
 ./twistlock-console-helm.tar.gz

Go to Manage > Defenders > Manage
and validate that Console has upgraded your Defenders.

Document:Prisma Cloud Compute Edition Administrator’s Guide

Helm charts

Table of Contents

Helm charts

Upgrading Console

Most Popular

Recommended For You

Document:Prisma Cloud Compute Edition Administrator’s Guide

Helm charts

Table of Contents

Helm charts

Upgrading Console

Most Popular

Recommended For You

Recommended Videos