> 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-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/view-and-manage-outposts.md).

# View and manage outposts

Learn how to view outposts, check their status and version, and manage them from the All Outposts page.

{% hint style="info" %}
**License type**: This feature is included with a Cortex XSIAM Premium license. It is also included with any other Cortex XSIAM product that has the Cloud Runtime Security add-on.
{% endhint %}

After you create and deploy an outpost, you monitor and manage it from the **All Outposts** page. This page lists every outpost in your Cortex XSIAM tenant, across all cloud service providers (CSPs), and shows the status and version of each outpost.

To open the page, navigate to **Settings → Data Sources & Integrations → Outposts**.

## Outpost status

The **Status** column shows the overall health of each outpost. An icon next to the status helps you identify outposts that need attention.

| Status    | Icon             | Description                                      |
| --------- | ---------------- | ------------------------------------------------ |
| Connected | Green check mark | The outpost is connected to Cortex XSIAM.        |
| Warning   | Yellow alert     | The outpost has issues that you should review.   |
| Error     | Red X            | The outpost has errors that you need to resolve. |
| Disabled  | Gray minus sign  | The outpost is disabled.                         |

A newly deployed outpost appears in **Connected** status after the outpost template deployment completes. For details, see [Outpost creation workflow](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/outpost-creation-workflow.md).

To investigate an outpost that is not connected, right-click the outpost and select **View Outpost errors**.

## Outpost updates

An **Update available** indicator appears next to the outpost status, for any status value, when an outpost needs to be updated. The updated template is older than the current template.

Hover over the **Update available** indicator to see the version details.

The indicator does not appear when the outpost template is current, or before the outpost reports its version to Cortex XSIAM.

To update the outpost, right-click the outpost and select **Edit** to download the updated template, and then run the template again in your CSP account. For AWS outposts that you deployed with CloudFormation, create a new stack with the updated template rather than updating the existing stack.

## Outpost management

Right-click an outpost in the table to manage it. The available actions depend on the outpost type, its status, and your user role.

* **Edit:** Change the outpost configuration. Not available for Cortex-managed outposts. The account identifier (the AWS **Account ID**, the GCP **Project ID**, or the Azure **Tenant ID**) is shown but cannot be changed.
  * If you change only the instance name, Cortex XSIAM applies the change immediately without generating a new template, and shows **Your changes have been applied successfully.**
  * If you change other settings, such as the regions in **Modify Scope by Regions** or the cloud tags, download the updated template and deploy it again in your CSP account.
  * For AWS outposts, you can only download a template for the same IaC tool that you chose when you created the outpost. For an outpost created with CloudFormation, either with **Execute in AWS** or **Download CloudFormation**, click **Download CloudFormation**, and deploy the updated template as a new stack rather than updating the existing stack. For an outpost created with Terraform, click **Download Terraform**.
  * For custom outposts, you can edit all the settings in the **Custom Outpost** wizard. The same rules apply for the instance name and for deploying the updated template.
* **Delete:** Delete the outpost. For details, see [Delete an outpost](#delete-an-outpost).
* **View Outpost Instances:** View the cloud instances that use the outpost. Available only when at least one cloud instance uses the outpost.
* **View Outpost errors:** View the open errors and issues for the outpost. Not available when the outpost status is `Connected`.

{% hint style="info" %}
Users with a view-only role can view outposts but cannot edit or delete them.
{% endhint %}

{% hint style="info" %}
If you edit an outpost whose previous changes are still pending, because the template from the earlier edit has not yet been deployed in your CSP, Cortex XSIAM first shows **Previous edits pending your action in the CSP**. Click **Show how to apply these changes** to see the deployment options for the pending template. Under **Manage unsaved changes**, select one of the following options:

* **Revoke pending changes:** Discard the pending changes, and then click **Revoke**.
* **Edit pending state:** Continue editing on top of the pending changes, and then click **Edit**.

If you already deployed a template from the previous edit in your CSP, those changes are applied.
{% endhint %}

To create a new outpost, click **New Outpost** and select the CSP. For details, see [Outpost creation workflow](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/outpost-creation-workflow.md).

### Delete an outpost

Before you delete an outpost, move all cloud instances that use it to a different outpost. If any cloud instances still use the outpost, Cortex XSIAM lists them and asks you to confirm before you continue.

After Cortex XSIAM deletes the outpost, clean up the outpost permissions and resources in your CSP account.


---

# 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-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/cloud-service-provider-csp-onboarding/outpost-onboarding/view-and-manage-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.
