VMware Tanzu Application Service (TAS) Defender
Table of Contents
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
VMware Tanzu Application Service (TAS) Defender
Prisma Cloud deploys the Defender on the VMware Tanzu Application Service (TAS) as add-on software, which works similarly to a Daemon set in Kubernetes.
This approach co-locates the Defender on every Diego cell VM.
The "Prisma Cloud for TAS" tile in the Tanzu Ops Manager allows you to configure the Defender across your TAS environment.
When you deploy full coverage Defenders for TAS, they perform blobstore scanning alongside compliance, vulnerability, and runtime protection.
If you have a large-scale environment, you can choose to deploy blobstore scanning Defenders as dedicated VMs that focus exclusively on scanning your blobstores.
Tanzu Application Service (TAS) Defender supports the following functions:
- Vulnerability scanning for running apps.
- Vulnerability and compliance scanning for the underlying Diego cell hosts.
- Blobstore scanning for Linux droplets.
- Runtime protection: Linux TAS Defenders support runtime protection for process, networking, and file system. Windows TAS Defenders support runtime protection for process.
The Prisma Cloud Console lets you deploy Defender to multiple TAS environments.
TAS Defender supports the prevent action because it doesn’t require controlling the app lifecycle.
The TAS Defenders don’t support the block action for runtime rules, vulnerability rules, and compliance rules because the Defenders cannot block running apps.
The TAS framework controls the app lifecycle, including stopping the containers as required by the block action.
Install the TAS Defender
Prerequisites:
- Prisma Cloud Compute Console has already been installed somewhere in your environment.
- Get the Prisma Cloud tile.
- Log in to the Prisma Cloud console.
- SelectManage > Defender > Deployed Defenders.
- ClickManual deploy.
- Select theOrchestratordeployment method.
- UnderOrchestrator type, select one of the following options:
- Tanzu Application Service Defender - Linux
- Tanzu Application Service Defender - Windows
- On the sidebar, click theDownloadbutton to get the TAS tile.Alternatively, you can download theVMWare Tanzu tilefrom underManage > System > Utilities.
- Import the Prisma Cloud tile.
- Go to theTanzu Ops Manager > Installation Dashboard.
- Click theImport a Productbutton.
- Select the downloaded tile.
- On the left sidebar, the Prisma Cloud for TAS appears.
- Click theplus signbeside the version number to stage the tile.
- Click the tile that was added.
- Configure the Defenders.
- Return to the Prisma Cloud Console.
- UnderThe name that Defender will use to connect to this Console, select the IP address or URL that your TAS environment can reach.
- Provide any needed Defender communication port.
- If you selected theTanzu Application Service Defender - Windowsas theOrchestrator type, enable or disableRuntime protection.
- Provide the Central Console address that the Defender can access. This is only needed if you follow a Project deployment pattern (Manage > Projects).
- Enable theAssign globally unique names to Hostsin theAdvanced Settingsas needed.
- Copy the installation scripts from the sidebar. You can deploy Prisma Cloud Defenders on Linux and Windows.
- Configure the Prisma Cloud tile.
- Return to the Tanzu Ops Manager.
- UnderAssign AZs and Networks, select theTAS networkand selectSave.
- UnderPrisma Cloud Component Configuration, paste the installation scripts for the operating systems you are using.If you don’t provide an installation script, Tanzu doesn’t deploy Defenders for that operating system.Enter aFoundationname (optional). If you don’t enter a Foundation name, you will not be able to usetas-foundationlabel inManage > Collections.SelectSave.
- UnderPrisma Cloud Proxy configuration, configure your Proxy as needed if you are using Linux.SelectSave.The Defender on Windows doesn’t support a proxy.
- UnderCredentials, provide your Prisma Cloud credentials for Linux and Windows. SelectSave. You can use certificates for authentication if you only use Linux. Provide your username and password credentials instead to authenticate the Defender if you use Windows Defenders by themselves or together with Linux Defenders.
- UnderResource configuration, you can add dedicated Linux VMs to serve exclusively as Linux blobstore scanners. SelectSave.
- Go back to theInstallation Dashboard.
- Click Review Pending Changes.
- Select the following products.
- Prisma Cloud for TAS
- VMWare Tanzu Application Service
- Every TAS Isolation segment in your environment.
- Apply the changes and wait for the tile to become active.It can take an hour or longer for the changes to apply and your deployment to complete.
- Verify the deployment on Prisma Cloud underManage > Defenders.After the deployment is complete, the deployed Defenders will appear in the table. TheHostcolumn showsAgent IDof the defended Linux Diego cells andVM CIDof the defended Windows Diego cells.You can search and filter your TAS Defenders based on the hostnames.
- To fetch theAgent IDof your Diego cells:
- Log into a Diego cell.
- The /var/vcap/instance/dns/records.json file shows how theAgent IDmaps to a host IP address.
Deploy Blobstore Scanners for TAS
Prisma Cloud for TAS can perform blobstore scanning on Linux VMs.
Defenders deployed as dedicated blobstore scanners still scan the host where they run for vulnerabilities, compliance issues, and runtime protection.
Prisma Cloud periodically discovers and scans the droplets in your blobstores for vulnerabilities using pattern matching.
- Go to theTanzu Ops Manager > Installation Dashboard.
- Click thePrisma Cloud for TAStile.
- UnderPrisma Cloud Component Configuration, paste the Linux installation script. If you don’t provide an installation script, Tanzu doesn’t deploy Defenders.If you are deploying only TAS Linux blobstore scanners you can unselect theInstall TAS Defender on all Linux Diego cells in the clustercheckbox.SelectSave.
- Go toResource Configuration.Specify the number of instances of blobstore scanners you want in your environment.
- Select theVM TYPE.
- Select thePERSISTENT DISK TYPE.
- Provide any load balancing configuration needed.
- Select whether an internet connection is allowed by the Blobstore scanner VM.SelectSave.
- UnderAssign AZs and Networks, select the TAS network and specify the preferred AZs for placing the blobstore scanners.SelectSave.
- Return to theInstallation Dashboard.
- ClickReview Pending Changes, and selectPrisma Cloud for TAS.Apply the changes. Wait for Tanzu to finish deploying the Defenders. This process can take a long time.
- Configure Prisma Cloud to scan a blobstore.