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

# Custom outpost concepts

Learn the concepts behind custom outposts: the Outpost networking options and the resources that Cortex XDR creates for you in a custom outpost.

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

A custom outpost lets you choose which parts of the outpost infrastructure you own. Cortex XDR creates and manages everything that you do not supply yourself. Before you plan a custom outpost, understand the choices that the Create Outpost wizard offers and what each choice means for your environment.

## How the outpost reaches the internet

Every custom outpost has an **Outpost networking** setting that defines how the outpost's scanner VMs reach the internet. You choose **Default**, **Custom**, or **Egress routing off** on the Global Settings page of the wizard. Your choice also defines how you select regions on the Regional Settings page.

For details about each option, 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).

## What Cortex XDR creates for you

Cortex XDR creates the resources that the outpost needs, such as identities, roles, storage, queues, and security groups, with secure defaults. If you set **Outpost networking** to **Custom**, you supply the network, and Cortex XDR creates everything else. Some resources are global to the outpost, and some are created in each region.

For the full lists for each CSP, see [What Cortex creates in 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/custom-outpost-concepts/what-cortex-creates-in-a-custom-outpost.md).

## What's next?

When you understand the concepts, [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).


---

# 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-outpost-concepts.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.
