> 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/data-security-documentation/onboard-and-configure/plan-and-prepare.md).

# Plan and prepare

**Prepare for deployment**

Before you get started with Cortex Data Security, consider the following:

* Determine the amount of log storage you need for your Cortex Data Security deployment. Talk to your partner or sales representative to determine whether you must purchase additional storage within the Cortex Data Security tenant.
* Determine the region in which you want to host Cortex Data Security and any associated services, such as Directory Sync Service. If you plan to stream data from a Strata Logging Service instance, it must be in the same region as Cortex Data Security. For more information, see [Supported regions](/data-security-documentation/onboard-and-configure/deployment-checklist/activation/supported-regions.md).

{% hint style="info" %}
**Note:** Mention the following in this article: If you plan to onboard cloud accounts, decide on a scan mode before you start. Cloud Scan (recommended) runs scanning in the Palo Alto Networks-managed environment with no additional setup or compute cost, while Outpost Scan runs scanning on infrastructure you host for data-residency or compliance requirements and requires additional cloud provider permissions and resources. For a comparison of the two modes and guidance on when to choose Outpost Scan, see [Outpost fundamentals and planning.](/data-security-documentation/onboard-and-configure/csp-onboarding/outpost-onboarding/outpost-fundamentals-and-planning.md)
{% endhint %}

If you plan to onboard cloud accounts, decide on a scan mode before you start. **Cloud Scan** is recommended. It runs scanning in the Palo Alto Networks-managed environment with no additional setup or compute cost. **Outpost Scan** runs scanning on infrastructure you host for data-residency or compliance requirements and requires additional cloud provider permissions and resources. For a comparison of the two modes and guidance on when to choose Outpost Scan, see [Outpost fundamentals and planning](/data-security-documentation/onboard-and-configure/csp-onboarding/outpost-onboarding/outpost-fundamentals-and-planning.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/data-security-documentation/onboard-and-configure/plan-and-prepare.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
