> 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-xdr/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/custom-networking-byon.md).

# Custom networking (BYON)

For custom outposts with custom networking (BYON): deploy the outpost into a VPC or virtual network that you own, learn what you take on, and review what is not supported.

{% hint style="info" %}
**License type:** This feature is included with a Cortex XDR license that has the Cloud Posture Security or Cloud Runtime Security add-on.
{% endhint %}

In a custom outpost, set **Outpost networking** to **Custom** to bring your own network (BYON). You provide the VPC or virtual network, subnets, and, optionally, a proxy. Cortex XDR deploys the outpost's resources into your network, and creates everything else. Custom networking is available for AWS, Azure, and GCP.

{% hint style="info" %}
**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.
{% endhint %}

## When to use custom networking

Custom networking is not the default path. **Default** networking is fully automated and is the recommended path for most deployments. Consider custom networking only when one of the following is a requirement that your organization cannot waive:

* **Network ownership:** A security or governance policy forbids workloads in a network that a cloud vendor creates or controls. The scanner VMs must run in a network that your organization owns.
* **Existing egress path:** All outbound traffic must go through an existing corporate egress path, such as a forward proxy, a TLS-inspecting proxy, or a central firewall that you already operate.
* **Subnet-level security ownership:** Your network team must own and audit subnet-level security controls, such as network security groups, firewall rules, and security groups.

## What you take on with custom networking

With custom networking, you provide the network layer, and Cortex XDR provides everything that runs inside it. You accept the following responsibilities for the life of the outpost:

* **Network resources:** You create and own the VPC or virtual network, subnets, route tables, NAT gateways, firewall rules, network security groups, security groups, and any outbound proxy. Cortex XDR does not create, manage, monitor, or repair them.
* **Outbound connectivity:** Cortex XDR does not deploy its managed egress proxy. The scanner VMs reach only the destinations that your network allows. If the required outbound access is missing or changes, scans fail until you fix the network.
* **Subnet-level security:** Allowing the scanner's required traffic, and denying everything else according to your policy, is your responsibility.
* **Diagnosis of misconfigurations:** Most failures with custom networking are network misconfigurations, such as missing outbound access, missing service endpoints, a subnet that is too small, or a proxy that does not work. Your network team must fix them.

## Key Terraform blocks and settings

If you deploy with Terraform, the bundle that the wizard generates contains a Terraform module and a pre-filled `template_params.tfvars` file. You do not edit `template_params.tfvars`, but you review it to confirm that it matches your network.

<details>

<summary>Key Terraform blocks and settings for custom networking</summary>

| Terraform block or setting                     | Description                                                                                                                                                                                                                                                  |
| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `byon_config` block                            | The network for the outpost. It contains the VPC or virtual network and the subnets, by region. The shape of the block differs for each CSP. The regions in this block are the only regions that the outpost enables.                                        |
| `proxy_config` block                           | The outbound proxy configuration for the scanner VMs. It groups the proxy host, port, and the `enabled`, `auth_enabled`, and `tls_enabled` settings. It is filled in only if you turn on **Outbound proxy**.                                                 |
| `proxy_config.enabled` setting                 | Turns the outbound proxy on or off. It is valid only with custom networking.                                                                                                                                                                                 |
| `auth_enabled` setting                         | Tells the scanner VMs that your proxy requires a username and password. When it is `true`, you must supply both `proxy_username` and `proxy_password`.                                                                                                       |
| `tls_enabled` setting                          | Tells the scanner VMs that your proxy performs TLS inspection. When it is `true`, you must supply the CA certificate in `ca_cert_content`.                                                                                                                   |
| `proxy_username` and `proxy_password` settings | The credentials for a proxy that requires authentication. You pass them on the `terraform apply` command line, not in `template_params.tfvars`, so they stay out of source control. Cortex XDR moves them into your CSP's secret store on the first `apply`. |
| `ca_cert_content` setting                      | The CA certificate that the scanner VMs trust when your proxy performs TLS inspection. You enter the certificate in the wizard in PEM format, and the bundle stores it as base64-encoded PEM.                                                                |

</details>

## What is not supported

The following items are not supported with custom networking. Terraform enforces most of them at plan time, and the deployment fails with a validation error before any resource is created. Some items require a change to your network, not to your Terraform inputs, so review them before you begin.

The following restrictions apply to every CSP:

* **Mixing regions:** You cannot have some regions use your network and other regions use a network that Cortex XDR creates in the same outpost. Only the regions that you add are enabled.
* **Changing the Outpost networking option after deployment:** To change it, destroy the outpost and deploy it again.
* **An outbound proxy without custom networking:** The outbound proxy, proxy authentication, and TLS inspection are available only when **Outpost networking** is set to **Custom**.
* **Proxy authentication without both credentials:** When proxy authentication is on, both the proxy username and the proxy password are required.
* **TLS inspection without a CA certificate:** When TLS inspection is on, the CA certificate is required.
* **IPv6:** Custom networking supports IPv4 only. IPv6 address space, IPv6-only subnets, and dual-stack connectivity are not supported.
* **Shared or host-project networks:** The network must be a standalone VPC or virtual network that the outpost identity can use directly.

The following restrictions apply to specific CSPs:

* (AWS) **A Cortex XDR egress proxy:** There is no managed egress proxy. You must provide outbound access through a NAT gateway or your own proxy.
* (AWS) **A region with no subnets:** Each region must have at least one Availability Zone subnet.
* (AWS) **A subnet outside the VPC:** Each subnet must belong to the VPC that you enter for the same region.
* (Azure) **A subnet outside the virtual network:** The subnet must belong to the virtual network in the same region.
* (Azure) **A subnet without the required service endpoints:** The subnet must have both the `Microsoft.Storage` and `Microsoft.KeyVault` service endpoints.
* (Azure) **Subnet security managed by Cortex XDR:** Cortex XDR does not attach or manage a network security group on your subnet.
* (GCP) **A default-deny posture managed by Cortex XDR:** Cortex XDR keeps only the egress firewall rules that it needs, and does not create a default-deny rule. You own your firewall posture.
* (GCP) **Shared VPC:** Host and service-project networks are not supported.

## What's next?

Continue with the following topics:

* [Custom networking prerequisites](https://cortex-docs.paloaltonetworks.com/cortex-xdr/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/custom-networking-byon/custom-networking-prerequisites.md)
* [(Optional) Validate your network and proxy values](https://cortex-docs.paloaltonetworks.com/cortex-xdr/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/custom-networking-byon/validate-your-network-and-proxy-values.md)
* [Outbound allow-list reference](https://cortex-docs.paloaltonetworks.com/cortex-xdr/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/custom-networking-byon/outbound-allow-list-reference.md)
* [Terraform validation reference](https://cortex-docs.paloaltonetworks.com/cortex-xdr/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/custom-networking-byon/terraform-validation-reference.md)
* [Maintain your network after deployment](https://cortex-docs.paloaltonetworks.com/cortex-xdr/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/custom-networking-byon/maintain-your-network-after-deployment.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-xdr/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-custom-outposts/custom-networking-byon.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.
