> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/endpoint-security/endpoint-protection/caas-workloads-1.md).

# TAS Workloads

Protect VMware TAS environments with Cortex Cloud endpoint security.

The Tanzu Application Service (TAS) Tile is a `.pivotal` installation package generated by Cortex Cloud and imported into VMware Tanzu Ops Manager, the TAS control plane. When applied, each Linux Diego Cell, the VMs that host TAS applications, receives the Cortex XDR agent.

Once deployed, each Diego Cell registers as a separate endpoint in the Cortex Cloud console, providing the following protection for the Diego Cell and the applications running on it:

* Malware prevention and exploit protection
* Behavioral threat protection
* EDR event collection
* Vulnerability assessment for Diego cells and the application containers they host

{% hint style="info" %}
Each Diego Cell running the Cortex XDR agent consumes one EP Cloud license.
{% endhint %}

Some Cortex Cloud capabilities and endpoint actions are not available or behave differently on TAS endpoints. For details, see [Supported capabilities and actions on TAS endpoints](#supported-capabilities-and-actions-on-tas-endpoints).

## Tanzu Application Service Tile installer

The Cortex XDR agent supports VMware Tanzu Application Service (TAS/Cloud Foundry) on Linux Diego Cells only.

#### Prerequisites

Before you deploy the Cortex XDR agent to a TAS environment, verify the following:

<table><thead><tr><th width="250.25">Prerequisite</th><th>Details</th></tr></thead><tbody><tr><td>Supported Environment</td><td>VMware Tanzu Application Service (TAS) 6.x or 10.x<br>Linux Diego Cells only</td></tr><tr><td>License</td><td>Cortex XSIAM Enterprise or Premium, Cortex Cloud, or Cortex XDR</td></tr><tr><td>Cortex XDR agent version</td><td>Cortex XDR agent version 9.4 or later</td></tr><tr><td>Required permissions</td><td>Instance Administrator</td></tr><tr><td>Tanzu platform access</td><td>Access to Tanzu Ops Manager</td></tr></tbody></table>

### Create the Tanzu Application Service Tile via API

Call [create distributions](https://cortex-docs.paloaltonetworks.com/cortex-cloud-api/cortex-platform/endpoint-management.md#post-public_api-v1-distributions-get_versions) in the [Cortex Cloud API reference guide](https://cortex-docs.paloaltonetworks.com/cortex-cloud-api/get-started-with-cortex-apis.md) to generate the Tile.

Set the following required fields in the request body:

* `name`: a name for the installer
* `package_type`: `"tas"`
* `platform`: `"Linux"`
* `agent_version`: the Cortex XDR agent version to embed in the Tile

Optional fields include:

* `proxy` - list of proxy servers
* `endpoint_tags` - list of tags applied to Diego Cells provisioned from this installer

### Create the Tanzu Application Service Tile in Cortex Cloud

1. In Cortex XDR, navigate to **Inventory** → **Endpoints** → **Agent Installations**, and click **Create**.
2. Select **Tanzu Application Service Tile** as the **Package Type** and click **Next**.
3. Under **Define parameters**, configure the following:
   * **Platform**: Linux.
   * **Version**: Select the Cortex XDR agent version to embed in the Tile.
   * **Proxy** (optional): Enter the proxy servers the agent should use to reach the Cortex backend.
4. Click **Next**.
5. Under **Add metadata**, configure the following:
   * **Name**: Enter a name for the installer.
   * **Description** (optional): Enter a description.
   * **Endpoint tags** (optional): Select or type tags to apply to Diego Cells provisioned from this Tile.
6. Click **Create**. When the installer is ready, a new Agent Installation instance appears in the list. Right-click it and download the generated `.pivotal` Tile, then deploy it in Tanzu Ops Manager.

### Deploy the TAS Tile in Tanzu Ops Manager

After you download the `.pivotal` Tile from Cortex XDR, provide it to your Tanzu platform operator to import and apply in VMware Tanzu Ops Manager. For import and lifecycle procedures, see the [VMware Tanzu Ops Manager documentation](https://docs.vmware.com/en/VMware-Tanzu-Operations-Manager/index.html).

Once applied, each Diego Cell receives the Cortex XDR Linux agent with the relevant policies and modules, and registers automatically with your Cortex XDR tenant.

### Manage TAS endpoints in Cortex Cloud

Once registered, each Diego Cell appears in the Cortex Cloud management console as an endpoint with:

* **Endpoint type:** Server
* **Installation type:** Tanzu Tile
* **Auto-upgrade status:** Not Supported

### Supported capabilities and actions on TAS endpoints

The following Cortex Cloud endpoint actions are supported on TAS endpoints:

* Initiate malware scan / Stop malware scan
* Quarantine / Unquarantine file
* Live Terminal, on the Diego Cell host
* Remote Script Execution, on the Diego Cell host
* Initiate heartbeat
* Retrieve support file
* Run forensics triage / hunt

{% hint style="info" %}
**Note**

* To prevent conflicts with the Tanzu container runtime, some Linux protection modules run in report-only mode on TAS endpoints, so prevention and alerting for those modules can differ from standard Linux endpoints.
* Analytics events from TAS endpoints are excluded from the analytics pipeline.
  {% endhint %}

### Investigate TAS alerts and vulnerabilities

Each Diego Cell registers as its own endpoint in the Cortex XDR console. When the agent detects malicious activity on a Diego Cell, Cortex XDR raises an issue that includes TAS evidence, such as the Diego Cell ID, organization, space, container ID, and application.

Affected TAS assets on Runtime Issues are clickable and open the asset's detail view in **Assets**.

Diego Cells are also added to the asset inventory as VM instances, enriched with TAS platform metadata such as the TAS deployment name, UUID, and version, Foundation GUID, system domain, and IaaS provider. For information on TAS assets and vulnerability scanning, see [Tanzu TAS assets](https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/asset-managment/asset-classes/compute-assets/tanzu-tas-assets.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/endpoint-security/endpoint-protection/caas-workloads-1.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
