> For the complete documentation index, see [llms.txt](https://documentation.immuta.com/2024.3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.immuta.com/2024.3/detect-your-activity/getting-started/general-immuta-configuration/native-integration.md).
# Integration Architecture
Immuta is not just a location to define your policy logic; Immuta also enforces that logic in your data platform. How that occurs varies based on each data platform, but the overall architecture remains consistent and follows the [NIST Zero Trust framework](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-207.pdf). The below diagram describes the recommended architecture from NIST:
Immuta lives in the middle control plane. To do this, Immuta knows details about the subjects and enterprise resources, acts as the policy decision point through policies administered by policy administrators, and makes real-time policy decisions using the internal Immuta policy engine.
Lastly, and of importance to how Immuta Secure functions, Immuta also enables the policy enforcement point by administering the policies natively in your data platform in a way that can react to policy changes and live queries.
## Configuring the integration
To use Immuta, you must configure the Immuta integration, which will require some level of privileged access to administer policies in your data platform, depending on your data platform and how the Immuta integration works. If using Databricks, refer to [Databricks roles best practices](/2024.3/detect-your-activity/getting-started/general-immuta-configuration/dbx-roles-best-practices.md) for Databricks before configuring the integration.
* [Snowflake](/2024.3/integrations/snowflake/how-to-guides/enterprise.md)
* [Databricks Unity Catalog](/2024.3/integrations/databricks-unity-catalog/how-to-guides/configure.md)
* [Databricks Spark](/2024.3/integrations/databricks-spark/how-to-guides/configuration/simplified.md)
* [Redshift](/2024.3/integrations/redshift/how-to-guides/redshift.md)
* [Redshift Spectrum](/2024.3/integrations/redshift/how-to-guides/redshift-spectrum.md)
* [Starburst (Trino)](/2024.3/integrations/starburst-trino/how-to-guides/configure.md)
* [Azure Synapse Analytics](/2024.3/integrations/azure-synapse-analytics/configure-azure-synapse-analytics-integration.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://documentation.immuta.com/2024.3/detect-your-activity/getting-started/general-immuta-configuration/native-integration.md?ask=&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.
