> 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-cloud-posture-management/onboard-and-configure/deployment-steps-and-checklist/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-standard-outposts.md).

# Working with standard outposts

Standard outposts are the recommended way to create dedicated set of infrastructure resources that extends the reach of Cortex Cloud into your environment.

Standard outposts are the recommended deployment path for most organizations. Cortex Cloud generates a Terraform template tailored to the values you enter in the outpost creation wizard, and you run that template in your CSP account to provision every resource the outpost needs, such as VPC or VNet, subnets, storage, secret vault, IAM roles or service accounts, scanner managed identities, and the trust relationship back to Cortex Cloud.

This approach gives you the fastest, most consistent path to coverage while keeping the number of manual steps low. Cortex owns the resource definitions, naming conventions, and network topology, while you own the CSP account they run in.

### What standard outposts include

A standard outpost deployment covers the full outpost lifecycle end to end:

* **Provisioning.** Cortex-generated Terraform creates all outpost infrastructure in your CSP account, including networking, storage, secret vault, IAM roles, scanner managed identities, and (for Azure) the Entra ID app registration and its federated identity credentials.
* **Trust establishment.** The template configures the trust relationship between your CSP account and Cortex Cloud automatically, using federated identity credentials rather than long-lived secrets.
* **Registration.** Once the Terraform apply completes for both the outpost and then the CSP onboarding, your cloud environment sends a registration callback to Cortex Cloud, and the outpost transitions from **Pending** to **Connected**.
* **Ongoing scanning.** After the outpost reaches **Connected**, Cortex schedules scans against the resources you onboard.

### Outpost deployment criteria

A standard outpost is suitable for your organization if the following conditions apply to your environment:

* Your organization is comfortable running Cortex-generated Terraform in your CSP account.
* Default naming conventions, network topology, and resource configurations meet your governance requirements.
* You do not need to use your own VPC or VNet, or route egress through your own proxy.

{% hint style="info" %}
**Notes**:

* Azure Entra ID app registration is supported with standard outposts.
* For alternative, custom outpost deployment options, contact your Palo Alto Networks representative.
  {% endhint %}

### What's next?

* [Create a standard outpost](/cortex-cloud-posture-management/onboard-and-configure/deployment-steps-and-checklist/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-standard-outposts/create-a-standard-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-cloud-posture-management/onboard-and-configure/deployment-steps-and-checklist/cloud-service-provider-csp-onboarding/outpost-onboarding/working-with-standard-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.