> 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/vendor-specific-data-sources/snowflake/how-to-onboard-snowflake.md).

# How to onboard Snowflake

Integrate Cortex Data Security with your Snowflake account to gain comprehensive visibility into any data and posture risk existing in your Snowflake environment. This integration enables automated scanning of all assets in Snowflake, including data classification and risk assessment.

You can add Snowflake as a third-party data source in Cortex Data Security .

* In order to use Snowflake, you must be registered with one of these cloud providers: Amazon AWS, Microsoft Azure, or Google Cloud Platform (GCP).
* Ensure you have the necessary account permissions to onboard. It is recommended to use `Account Admin` as the role for the onboarding.

**Configuration Step**

1. Navigate to **Settings** → **Data Sources & Integrations**.
2. On the **Data Sources & Integrations** page, click **+ Add New**.
3. On the **Add Data Sources or Integrations** page, search for **Snowflake**, then hover over it and click **Add**.
4. On the **New Data Source Snowflake** **integration instance settings** page, do the following:
   1. Enter a display name for your Snowflake integration instance.
   2. Enter a **Data Sharing Account Identifier**.

      The account identifier can be found using the user information at the bottom left. Hover over the account you wish to onboard and select the copy option at the top right. The account identifier is usually of the format:

      `(organization).[account]`
   3. (Optional) If you have a Snowflake account that is protected by a network policy, turn on the My Snowflake account is protected by network policies toggle button. The network policies are related to the IP allow list.
   4. Select a cloud platform and choose a region.
   5. (Optional) If you want to use an existing user:
      1. Click Show advance settings and then turn on the Use an existing user toggle button.
      2. Enter the user name and the login name.
5. Click Next.

**Establish Connection Step**

1. Open your Snowflake console in a new tab.
2. Using the copy or download icons, copy or download the script in the Generated script text box and paste it into a new worksheet in Snowflake.
3. Select the entire script and select Run all.
4. Once the script runs without errors, come back to the Snowflake screen and click Verify Connection to check if the instance is detected.

**Verify Connection Step**

1. A success or failure message appears on the screen.
2. If a success message appears, you can do the following:
   * View the instance's information in the Snowflake Posture instances.
   * View the assets in Asset Inventory, once the first scan is complete.

**Delete a Snowflake instance**

1. Navigate to **Settings** → **Data Sources & Integrations**.
2. On the **Data Sources & Integrations** page, select the **Snowflake** integration or filter to search for it and then select it.
3. On the **Snowflake** page, right click the row of the integration instance you want to delete.
4. From the drop down menu, select **Settings** and from the integration instance settings page select the **Delete** checkbox and then click **Delete**.

   The **Snowflake** instance is now removed, including all previous scans.


---

# 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/cortex-data-security-data-sources-and-connectors/vendor-specific-data-sources/snowflake/how-to-onboard-snowflake.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.