VMware Tanzu Application Service (TAS) Defender
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)
VMware Tanzu Application Service (TAS) Defender
You can deploy a dedicated Defender on the Diego cells (Hosts) in your environment. The Prisma Cloud tile installs a TAS Defender on every Diego cell in the TAS environment, including Diego cells that run in Isolation Segments.
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 buildpack-based apps.
- Runtime protection (process, networking, and file system).
Defender is deployed as BOSH Director addon.
Addons are BOSH release jobs that run on each Diego cell host.
Defender runs as a service under the root user.
The Defender service is monitored by the Bosh agent, with the help of Monit.
Note that the Defender service isn’t a Garden container.
Console lets you deploy Defender to multiple TAS environments.
In Console, Defenders report which Cloud Controller they report to.
Currently, TAS Defender doesn’t support blocking for runtime rules, vulnerability rules, and compliance rules.
The block action stops the entire container.
The app lifecycle is controlled by the Tanzu Application Service framework, so Prisma Cloud cannot effectively block running apps.
TAS Defender, however, does support the prevent action.

TAS Defender currently doesn’t support custom compliance checks.
Install the TAS Defender
Go to the Tanzu Ops Manager Installation Dashboard to install TAS Defender.
If you’re upgrading from a release earlier than 20.09, you must first uninstall any previous versions of TAS Defender. In version 20.09, the tile has been rearchitected.
The old tile created a dedicated VM in the TAS environment with a Defender installed, and supported blobstore scanning only.
The new tile installs Defender on every Diego cell in the TAS environment, with expanded support for app scanning, host scanning, and runtime defense.
Prerequisites:
- Prisma Cloud Compute Console has already been installed somewhere in your environment.
- In Prisma Cloud Console, go toManage > System > Utilities, and download the TAS tile.
- In the Ops Manager Installation Dashboard, clickImport a Product, and select the tile you downloaded.
- Retrieve the install command from Prisma Cloud Console. It’s used to configure the tile.
- Go toManage > Defenders > Deploy > Single Defender.
- Choose the DNS name or IP address the TAS Defender will use to connect to Console. If a suitable option is not available, go toManage > Defenders > Names, and add a DNS name or IP address to the SAN table.
- Set the Defender type toTAS Defender.
- Copy the install command and set it aside.
- Go to the Tanzu Ops Manager Installation Dashboard.
- Add the Prisma Cloud tile to your staging area. Click the+button next to the version of the tile you want to install.
- Click the newly addedPrisma Cloud for TAStile.
- Configure the tile.
- InPrisma Cloud Component Configuration, paste the install command you copied from Prisma Cloud Console. Provide a name for this specific TAS Foundation, then clickSave.By default Prisma Cloud performs strict validation of your Cloud Controller’s (CC) TLS certificate. If you’re using self-signed certificates, this check will fail. To add your custom certificates to trusted cert list, you need to add the custom CA’s cert on the VM where the Prisma Cloud tile runs. For more information, see the article on trusted certificates.To skip strict validation of your Cloud Controller’s (CC) TLS certificate, enableSkip Cloud Controller TLS validation. Strict validation verifies the name, signer, and validity date of the CC’s certificate. Even with strict validation disabled, the sesssion is still encrypted. Skip strict validation when:
- You’re using self-signed certificates.certificates.
- You’re using certificates signed by a CA that isn’t in your cert store..
- When there’s a mismatch between the address you’re using to connect to the CC and the common name (CN) or subject alternative name (SAN) in the CC’s certificate.
- InCredentials, select your preferred authentication method: Basic Authentication or Certificate-based Authentication:For Basic Authentication, enter your Prisma Cloud Console credentials, then clickSave.For certificate-based Authentication, paste the certificate and private key used for authentication in PEM format, then clickSave.Notes:
- Your role must be Defender Manager or higher.
- For Certificate-based Authentication, the root CA used to sign the certificate used for authentication must be entered underManage > Authentication > System Certificates > Certificate-based authentication to Console.
- Install the Prisma Cloud tile. Return to the Ops Manager Installation Dashboard, clickReview Pending Changes, select bothPrisma Cloud for TASandTanzu Application Service, then clickApply changes.Tanzu Application Service must be staged when installing the Prisma Cloud tile.In order to deploy a new Defender after the Prisma Cloud tile is installed (e.g. if new Diego cells or isolation segments have been installed in the TAS environment),Apply changeson Ops Manager is required.
- After the changes are applied, validate that Prisma Cloud Defenders are running in your environment.
- Log into Prisma Cloud Console.
- Go toManage > Defenders > Manage > Defenders.In the table of deployed Defenders, you should see a Defender of typeTanzu Application Service, one per Diego cell, including Diego cells that run in the Isolation Segments of your TAS environment.Prisma Cloud reports the agentID in the Host field. To correlate an agentID to a Diego cell IP address, and determine exactly which host runs a Defender, login to an Diego cell, and inspect /var/vcap/instance/dns/records.json. This file shows how the agentID maps to a host IP address.If a TAS Defender disconnects from Console for more than one day, all data it collected is purged from Console. The Defender is also removed from the table inManage > Defenders > Manage. The period of time that data from a disconneted Defender is retained (by default, one day) can be configured inManage > Defenders > Manage > Defenders > Advanced Settings.
Utilizing collections with TAS metadata fields
Prisma Cloud automatically collects metadata fields such as Foundation, Organization Name, Application Name and ID, and Space Name and ID.
To utilize these fields, you’ll have to
manually create
appropriate collections that can then be used for filtering and aggregation.Resource type | Supported Labels |
---|---|
Host | tas-foundation |
Containers (running applications) | tas-application-id, tas-application-name, tas-space-id, tas-space-name, tas-org-id, tas-org-name, tas-foundation |
Droplets | tas-application-id, tas-application-name, tas-space-id, tas-space-name, tas-org-id, tas-org-name, tas-foundation |