> 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/cortex-data-security-data-sources-and-connectors/cloud-service-provider-csp-onboarding.md).

# Cloud service provider (CSP) onboarding

Learn about onboarding your cloud service provider to Cortex Data Security.

Connect your cloud service provider (CSP) from the **Data Sources & Integrations** page. Onboarding creates a unified, normalized inventory of your cloud assets. This inventory gives you visibility and context for incident investigations.

Cortex Data Security supports onboarding these cloud service providers:

* Amazon Web Services (AWS)
* Microsoft Azure
* Google Cloud Platform (GCP)
* Oracle Cloud Infrastructure (OCI)

Onboarding has two phases:

1. Configure the authentication template in Cortex Data Security.
2. Deploy the template in your CSP environment.

Review your provider's prerequisites before starting. Then complete the provider-specific onboarding workflow. For end-to-end cloud service provider permission onboarding, see [Cloud service provider (CSP) onboarding](/data-security-documentation/onboard-and-configure/csp-onboarding.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/data-security-documentation/cortex-data-security-data-sources-and-connectors/cloud-service-provider-csp-onboarding.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.