CaaS Workloads ↗
Deploy the Cortex XDR container-embedded agent on Container as a Service (CaaS) environments to extend runtime security and vulnerability scanning to containerized workloads. The container-embedded Cortex XDR agent provides malware prevention, exploit protection, vulnerability assessment, and altered binary execution restriction for containers running on managed container services.
The Cortex XDR container-embedded agent is a purpose-built agent designed for containerized environments. The agent embeds directly into your existing workflows.
The container-embedded agent is embedded directly into your container image during the Docker build process. The agent runs as an entry point within your application container, providing runtime security and vulnerability scanning without requiring a separate container.
This topic explains the process of how to embed the Cortex XDR agent in your dockerfile.
Notice
This feature requires a Cloud Runtime Security or Cortex XSIAM Premium license. Every 10 container-embedded agents will consume a single Cortex Runtime Security license.
CaaS container-embedded agent installer
The following managed container services are supported. See the prerequisites tables below for the requirements for each container service.
- AWS ECS Fargate; containers using x86_64 and AArch64 architecture
- Azure Container Instances (ACI); containers using x86_64 architecture
- Google Cloud Run (GCR); containers using x86_64 architecture
Prerequisites
Before you deploy the container-embedded agent, verify the following:
| Prerequisite | Details |
|---|---|
| Supported Environment | AWS ECS Fargate; containers using x86_64 and aarch64 architecture |
| Requirements | Cortex XDR agent version 9.2.0 or later Required resources per container:
Dockerfile requirements:
Assets discovery: Onboard the relevant AWS environments Drift detection: Container registry image scanning |
| Limitations |
|
| Prerequisite | Details |
|---|---|
| Supported Environment | Azure Container Instances (ACI) containers using x86_64 architecture |
| Requirements | Cortex XDR agent version 9.3.0 or later In your YAML deployment file, define the following: a) Required resources per container:
b) Azure container registry credentials imageRegistryCredentials: Server: Full ACR Username: Access Key Admin Username Password: Access Key Admin User Password c) There are two valid identity options, one of these identities must be defined:
d) The relevant identity must have Reader and AcrPull permissions
f) For the User Identity option, assign the following Environment Variables:
|
| Supported deployments |
|
| Prerequisite | Details |
|---|---|
| Supported Environment | Google Cloud Run (GCR) containers using x86_64 architecture |
| Requirements | Cortex XDR agent version 9.3.0 or later a) Required resources per container:
b) Dockerfile requirement: For log retention, set the environment variable path: XDR_LOG_DIR = </opt/traps/log> Note: Do not use /var/log or any subdirectories from it. |
| Supported deployments |
|
| Limitations |
|
To create the Cortex XDR container-embedded agent Dockerfile via API.
See the API reference guide: Create distributions
To create the Cortex XDR container-embedded agent Dockerfile via user interface:
- In your Cortex management console, navigate to Inventory → Endpoints → Installations, click Create.
- Select CaaS as the Package Type and in Metadata, select Container Embedded as the Deployment Type.
- Define the configuration settings for version and proxy (optional).
- Upload your Dockerfile. Cortex XSIAM validates your Dockerfile against the prerequisites.
- A new Agent Installation instance will be created- right-click it and download the newly generated Dockerfile.
Embed the Cortex XDR container-embedded agent Dockerfile into your container image:
- Select the newly generated Dockerfile.
- Re-build your container image using the newly generated Dockerfile.
- During the build process, the agent binary will be fetched from the Cortex repository and baked into the image.
- Once the build process is successfully finished, you are ready to use the new container image in your CaaS environments, based on the prerequisites above.