Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.
Cortex XSIAM

Custom networking prerequisites

For custom outposts with custom networking (BYON): confirm that your network and outbound path meet the prerequisites before you create the outpost.

Before you create a custom outpost with custom networking, confirm that your network meets the prerequisites in this topic. Terraform validates most of these prerequisites at plan time and fails with a clear error. Some configurations, such as private endpoints on the subnet, are not validated, to avoid requiring excessive permissions. Confirming them now prevents failures when you deploy.

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.

For the full set of validation rules, see the Terraform validation reference.

Outbound path

The scanner VMs must be able to reach the internet and the required cloud service endpoints. Confirm that the outbound path that you chose when you planned your custom outpost exists and works:

  • Direct outbound: Your NAT gateway or firewall allows outbound HTTPS (port 443) to the destinations in the Outbound allow-list reference.

  • Outbound proxy: Your proxy is reachable from the subnets, and it can reach the destinations in the allow-list on behalf of the scanner VMs. If the proxy performs TLS inspection, have its CA certificate ready in PEM format.

The outbound path affects the rules that Cortex XSIAM creates and the rules that you own, according to your CSP:

  • (AWS) If you use direct outbound, Cortex XSIAM allows the scanner direct egress to 0.0.0.0/0 on port 443, and your VPC must have a NAT gateway or an equivalent route to the internet. If you use an outbound proxy, Cortex XSIAM allows the scanner egress only to the proxy on the proxy port.

  • (Azure) Cortex XSIAM does not attach a network security group to your subnet. You own the network security group or firewall rules that carry the scanner's traffic to the allow-list destinations or to your proxy.

  • (GCP) Cortex XSIAM keeps only the egress firewall rules that the scanner needs, for Private Google Access and for DSPM to Cloud SQL, and does not create a default-deny rule. You own every other firewall rule for the subnetwork.

Network prerequisites for each CSP

Confirm the following prerequisites for your CSP.

AWS
  • A supported region: Each region that you add must be a supported AWS region that is available and enabled in your account.

  • At least one subnet for each region: Each region must have at least one Availability Zone with a subnet ID.

  • Route tables with no existing S3 or DynamoDB gateway endpoint route: Cortex XSIAM creates its own S3 and DynamoDB gateway VPC endpoints, each with an endpoint policy, and associates them with the route table of each subnet that you enter. If a subnet has no explicit route table association, it uses the VPC main route table, so Cortex XSIAM associates the endpoints with the main route table. A route table can't have more than one endpoint route to the same service, so these route tables must not already have a gateway endpoint route to S3 or DynamoDB.

  • Other subnets that share the route table: Any other subnet that uses one of these route tables also sends its S3 and DynamoDB traffic through the Cortex XSIAM gateway endpoints, and the endpoint policies apply to it. The S3 endpoint policy allows only the Cortex XSIAM outpost IAM roles to access the outpost buckets in your account, and allows read-only access to buckets in other accounts. The DynamoDB endpoint policy allows only read-only actions. As a result, S3 requests from those subnets to other buckets in your account, and DynamoDB write requests, are denied.

  • No private hosted zone for the interface endpoint services: Cortex XSIAM creates interface VPC endpoints in your VPC for Amazon ECR (API and Docker), AWS STS, AWS Systems Manager (SSM), AWS Lambda, and Amazon CloudWatch monitoring. AWS turns on private DNS for these endpoints by default, and doesn't allow an interface endpoint with private DNS when a private hosted zone in the VPC (including one shared from another account) already covers the same service name. Make sure that no such private hosted zone exists.

Azure
  • Service endpoints on the subnet: The subnet must have both the Microsoft.Storage and Microsoft.KeyVault service endpoints. Without them, Azure rejects the creation of storage and Key Vault resources with a NetworkAclsValidationFailure error. To add them, run the following command:

  • The subnet is in the virtual network: The subnet that you enter must be in the virtual network that you enter for the same region.

  • A supported location: Each region that you add must be a supported Azure location.

  • Private endpoint network policies disabled on the subnet: Private endpoint network policies must be disabled on the subnet, so that Cortex XSIAM's private endpoints can attach. To set this when you create the subnet, add --disable-private-endpoint-network-policies true to the az network vnet subnet create command.

  • Enough IPv4 address space: The subnet must have enough IPv4 address space for scanner VMs, proxies, and private endpoint network interfaces. The minimum is a /27. A /24 is a safe starting point as workloads scale.

GCP

GCP VPCs are global, so you provide one VPC and one subnetwork for each region.

  • A VPC: You enter the VPC in the Compute VPC ID field on the Global Settings page.

  • At least one regional subnetwork: You enter a Compute Subnetwork URI for each region that you add.

  • A supported region: Each region that you add must be a supported GCP region.

  • A standalone VPC: The VPC must be a standalone VPC that the outpost identity can use directly.

  • Private Google Access enabled: Private Google Access must be enabled (privateIpGoogleAccess = true) on each subnetwork, so that the scanner VMs can reach Google APIs through the Private Google Access routes that Cortex XSIAM creates.

What's next?

When your network meets the prerequisites, create a custom outpost.

Last updated

Was this helpful?