> For the complete documentation index, see [llms.txt](https://documentation.immuta.com/saas/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/saas/configuration/integrations/databricks/databricks-unity-catalog/reference-guides/databricks-unity-catalog-integration-reference-guide/security-and-compliance.md). # Security and Compliance ## Authentication methods ### Registering the connection The Databricks Unity Catalog integration supports the following authentication methods to register a connection. The credentials provided must be for an account with the permissions listed in the [Register a Databricks Unity Catalog connection guide](/saas/configuration/integrations/databricks/databricks-unity-catalog/how-to-guides/connect-unity-catalog.md#requirements). * **Personal access token (PAT)** * **OAuth machine-to-machine (M2M)** ### Identity providers for user authentication The built-in Immuta IAM can be used as a complete solution for authentication and user entitlement. However, you can connect your existing identity management provider to Immuta to use that system for authentication and user entitlement instead. Each of the supported identity providers includes a specific set of configuration options that enable Immuta to communicate with the IAM system and map the users, permissions, groups, and attributes into Immuta. See the [Identity managers guide](/saas/configuration/people/section-contents/reference-guides/index.md) for a list of supported providers and details. See the [Databricks Unity Catalog integration reference guide](/saas/configuration/integrations/databricks/databricks-unity-catalog/reference-guides/databricks-unity-catalog-integration-reference-guide.md#user-registration-and-id-mapping) for details about user provisioning and mapping user accounts to Immuta. ## Auditing and compliance Immuta provides auditing features and governance reports so that data owners and governors can monitor users' access to data and detect anomalies in behavior. You can view the information in these audit logs on [dashboards](/saas/govern/detect-your-data/detection.md) or export the full audit logs to S3 and ADLS for long-term backup and processing with log data processors and tools. This capability fosters convenient integrations with log monitoring services and data pipelines. See the [Audit documentation](/saas/govern/detect-your-data/audit/reference-guides/index.md) for details about these capabilities and how they work with the Databricks Unity Catalog integration. ### Databricks Unity Catalog query audit Immuta uses Databricks tables from the `system` catalog to understand the queries users make and present them in the query audit logs. The audit ingest is set when [registering the connection](/saas/configuration/integrations/databricks/databricks-unity-catalog/how-to-guides/connect-unity-catalog.md) and can be scoped to only ingest specific workspaces if needed. The default ingest frequency is every 24 hours, but this can be configured to a different frequency on the [Immuta app settings page](/saas/configuration/application-configuration/how-to-guides/config-builder-guide.md#integration-settings). Additionally, audit ingestion can be manually requested at any time from the Immuta audit page. When manually requested, it will only search for new queries that were created since the last query that had been audited. The job is run in the background, so the new queries will not be immediately available. See the [Databricks Unity Catalog audit page](/saas/govern/detect-your-data/audit/reference-guides/query-audit-logs/databricks-uc.md) for details about the contents of the logs and an example of the resulting audit record. #### Governance reports Immuta governance reports allow users with the `GOVERNANCE` Immuta permission to use a natural language builder to instantly create reports that delineate user activity across Immuta. These reports can be based on various entity types, including users, groups, projects, data sources, purposes, policy types, or connection types. See the [Governance report types](/saas/govern/detect-your-data/audit/reference-guides/reports.md) page for a list of report types and guidance. --- # 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://documentation.immuta.com/saas/configuration/integrations/databricks/databricks-unity-catalog/reference-guides/databricks-unity-catalog-integration-reference-guide/security-and-compliance.md?ask=&goal= ``` `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.