Native 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. The below diagram describes the recommended architecture from NIST:
![](https://documentation.immuta.com/~gitbook/image?url=https%3A%2F%2F1751699907-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FlWBda5Pt4s8apEhzXGl7%252Fuploads%252FKNlA8zh65Uq7VwTjVmgF%252Fzero-trust.png%3Falt%3Dmedia%26token%3D53a37db1-c7e4-4552-9d3f-1e48088aae99&width=768&dpr=4&quality=100&sign=2e935681&sv=1)
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 native integration
To use Immuta, you must configure the Immuta native 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. Refer to Snowflake roles best practices for Snowflake before configuring the native integration.
Last updated