For the complete documentation index, see llms.txt. This page is also available as Markdown.
Cortex XDR

Outbound allow-list reference

For custom outposts with custom networking (BYON): look up the outbound destinations, ports, and protocols that the outpost scanner must reach, so you can build your firewall, security group, or proxy

Note: This topic applies only to custom outposts where Outpost networking is set to Custom. If you chose Default or Egress routing off, skip this topic.

The scanner Cortex XDR deploys into your network performs various types of agentless scans, each with its own workflow. For example, some host scans involve taking point-in-time snapshots of workload disks, mounting and reading them for analysis, and deleting them when finished. Other processes, like registry and serverless scanning, pull and read machine and container images. To support these different scan flows in BYON mode, your network must permit the scanner's required outbound traffic. Use this reference to build the network security group, firewall, or proxy allow-list rules the scanner relies on. Re-check the destinations at every outpost upgrade, since new capabilities can add destinations.

At minimum, the scanner needs outbound access (typically TCP 443) to:

  • The cloud's object storage service. For snapshot and image data, and for the outpost's own buckets.

  • The cloud's secret store. AWS SSM Parameter Store, Azure Key Vault, or GCP Secret Manager.

  • The cloud's control plane or resource manager. To enumerate and snapshot workloads.

  • Any data services in scope for DSPM. For example, Azure SQL, Azure Cosmos DB, or AWS DynamoDB.

  • The Cortex XDR tenant control plane and object storage buckets. To report scan results and read/write outpost data, either directly or through your proxy.

The per-cloud tables below enumerate the specific destinations, service tags, and ports. If any destination is blocked by your network security group, firewall, security group, or proxy, snapshot and image scanning fails silently until the block is removed.

AWS

Cortex XDR configures the scanner security group with the egress rules below. The NAT and proxy rows are mutually exclusive: Cortex XDR creates whichever row matches the outbound model you chose in the planning step.

Purpose
Destination
Protocol
Port

Amazon S3 (gateway endpoint)

S3 prefix list

TCP

443

Amazon DynamoDB (gateway endpoint)

DynamoDB prefix list

TCP

443

Cortex XDR interface endpoints

Interface-endpoint security group

TCP

443

Outbound (NAT model)

0.0.0.0/0

TCP

443

Outbound (proxy model)

proxy_host/32

TCP

Proxy port

If you route outbound through a proxy rather than directly, the proxy must reach the destinations Cortex XDR normally reaches through the NAT egress. If your VPC does not have a NAT Gateway and you did not choose the proxy model, the scanner has no path to the internet and scans will fail. You will see these failures as asset errors on the connector until you provision the outbound path.

Azure

In Cortex XDR-managed mode, Cortex XDR attaches a network security group with the outbound rules below from the scanner. In BYON mode, you reproduce equivalent rules in your own network security group or firewall. The source is the scanner subnet or application security group.

Purpose
Destination (Service Tag)
Protocol
Destination port(s)

Azure Storage (bucket communication)

Storage.<region>

Any

443

Azure Key Vault

AzureKeyVault.<region>

Any

443

Azure SQL (DSPM)

Sql.<region>

Any

1433, 11000-11999

Azure Cosmos DB (DSPM)

AzureCosmosDB.<region>

Any

10255

Azure Active Directory

AzureActiveDirectory

Any

443

Azure Front Door

AzureFrontDoor.Frontend

Any

443

Azure Resource Manager

AzureResourceManager

Any

443

Cognitive Services (management)

CognitiveServicesManagement

Any

443

Cognitive Services (frontend)

CognitiveServicesFrontend

Any

443

Azure control plane (DSPM, Registry, Serverless)

AzureCloud

Any

443

Private endpoints (DSPM, Registry)

Scanner's private-endpoint targets

TCP

443, 1433

Snowflake (OCSP) & MongoDB Atlas

See note below.

TCP

80, 27017

The Active Directory, Front Door, Resource Manager, and Cognitive Services rows apply only in Cognitive-Services-enabled regions. If you route outbound through a proxy rather than directly, the proxy must reach these destinations.

Note: For DSPM, when routing through a customer-managed proxy, you must also allow outbound traffic on port 80 (for Snowflake certificate/OCSP checks) and port 27017 (for MongoDB Atlas), in addition to port 443.

GCP

In BYON mode, Cortex XDR keeps the egress rules below on the scanner subnetwork. Your firewall must additionally permit the scanner's outbound traffic to the services it scans, because Cortex XDR creates no default-deny rule and no other egress rules in BYON mode.

Purpose
Destination
Protocol
Port(s)

Private Google Access (private.googleapis.com)

Google PGA ranges

TCP

443

DSPM to Cloud SQL

Private Service Access ranges

TCP

443, 3307

Because Cortex XDR creates no default-deny rule in BYON mode, design your firewall posture explicitly. If you route outbound through a proxy, the proxy must reach these destinations.

Last updated

Was this helpful?