> 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.md).

# Working with custom outposts

Custom outposts let you control parts of the outpost infrastructure, such as how the outpost reaches the internet, the network (BYON), or the Azure app registration (BYOA), to meet strict governance r

{% 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 %}

Custom outposts are for organizations whose governance, network, or identity policies require control over parts of the outpost infrastructure that Cortex XDR creates for a standard outpost. With a custom outpost, you choose which parts you own, and Cortex XDR creates the rest. Custom outposts are available for AWS, Azure, and GCP.

This topic explains the benefits and considerations to take into account before choosing to create a custom outpost. While we generally recommend working with standard outposts, custom outposts might be right for you.

## Matrix for deciding between standard and custom outposts

The following table compares standard and custom outposts.

|                              | Standard outpost                                                              | Custom outpost                                                                                        |
| ---------------------------- | ----------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| **Wizard**                   | The outpost creation wizard                                                   | The **Custom Outpost** wizard, with **Global Settings**, **Regional Settings**, and **Summary** pages |
| **Outbound internet access** | Through an egress proxy that Cortex XDR manages                               | **Default**, **Custom**, or **Egress routing off**                                                    |
| **Network**                  | Cortex XDR creates it                                                         | Cortex XDR creates it, or you bring your own                                                          |
| **Azure app registration**   | Cortex XDR creates it, or you bring your own                                  | Cortex XDR creates it, or you bring your own                                                          |
| **Regions**                  | Selected from a list                                                          | Selected from a list, or added one at a time with your network resource IDs                           |
| **Deployment**               | (AWS) CloudFormation, automated or manual. Terraform for AWS, Azure, and GCP. | (AWS) CloudFormation, automated or manual. Terraform for AWS, Azure, and GCP.                         |

## Bring your own network (BYON) and bring your own app registration (BYOA)

A custom outpost offers the following options, which you use in combination with each other. You choose them on the Global Settings page of the wizard.

* **Outpost networking:** Defines how the outpost's scanner VMs reach the internet. Set **Outpost networking** to **Custom** to bring your own network (BYON). You provide the VPC or virtual network, subnets, and, optionally, a proxy. For details, see [Outpost networking options](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-outpost-concepts/outpost-networking-options.md) and [Custom networking (BYON)](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).
* **(Azure) Bring Your Own App Registration:** Use your own pre-created Microsoft Entra ID app registration, and, optionally, your own scanner managed identities, instead of having Cortex XDR create them. This option is also called bring your own app registration (BYOA), and was previously documented as bring your own Azure app. For details, see [Bring your own Azure app registration (BYOA)](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/bring-your-own-azure-app-registration-byoa.md).

You can use each option on its own or combine them.

## When to choose a custom outpost

A standard outpost is fully automated and is the recommended path for most deployments. Choose a custom outpost only if you have a requirement that a standard outpost does not meet, for example:

* Your network team must own the network that the scanner VMs run in, and the subnet-level security controls.
* All outbound traffic must go through an existing corporate forward proxy, TLS-inspecting proxy, or firewall.
* The outpost must not have outbound internet access.
* (Azure) Your organization does not allow a third party to create app registrations or grant admin consent in your tenant.

## Custom outpost workflow

Follow these steps to deploy a custom outpost:

1. Learn the [custom outpost concepts](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-outpost-concepts.md).
2. [Plan your custom outpost](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/plan-your-custom-outpost.md).
3. If you set **Outpost networking** to **Custom**, complete the [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).
4. (Azure) If you bring your own app registration, complete the [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/bring-your-own-azure-app-registration-byoa/prerequisites-for-bringing-your-own-app-registration.md), and [create the Azure app registration](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/bring-your-own-azure-app-registration-byoa/create-the-azure-app-registration.md).
5. [Create a custom outpost](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/create-a-custom-outpost.md).
6. If you set **Outpost networking** to **Custom**, [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).

If you encounter issues, see [Custom outpost troubleshooting](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-outpost-troubleshooting.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.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.
