Databricks Spark Query Audit Logs
In addition to the executed Spark plan, the tables, and the tables' underlying paths for every audited Spark job, Immuta captures the code or query that triggers the Spark plan. Immuta audits the activity of Immuta users on Immuta data sources.
Requirements
Databricks users registered as Immuta users: Note that the users' Databricks usernames must be mapped to Immuta. Without this, Immuta will not know the users are Immuta users and will not collect audit events for their data access activity.
Store audit logs
By default Databricks audit logs expire after 90 days. Export the universal audit model (UAM) logs to S3 or ADLS Gen2, and store audit logs outside of Immuta in order to retain the audit logs long-term.
Audit schema
Each audit message from the Immuta platform will be a one-line JSON object containing the properties listed below.
Property | Description | Example |
---|---|---|
action | The action associated with the audit log. |
|
actor.type | The Immuta user type of the actor who made the query. |
|
actor.id | The Immuta user ID of the actor who made the query. |
|
actor.name | The Immuta name of the user who made the query. |
|
actor.identityProvider | The IAM the user is registered in. |
|
sessionId | The session ID of the user who performed the action. |
|
actionStatus | Indicates whether or not the user was granted access to the data. Possible values are |
|
actionStatusReason | When a user's query is denied, this property explains why. When a query is successful, this value is | |
eventTimestamp | The time the query occurred. |
|
id | The unique ID of the audit record. |
|
customerId | The unique Databricks customer ID. |
|
targetType | The type of targets affected by the query; this value will always be |
|
targets | A list of the targets affected by the query. | See the example below |
auditPayload.type | The type of audit record; this value will always be: |
|
auditPayload.queryId | The unique ID of the query. If the query joins multiple tables, each table will appear as a separate log, but all will have the same query ID. |
|
auditPayload.query | The query that was run in the integration. Immuta truncates the query text to the first 2048 characters. | See the example below |
auditPayload.startTime | The date and time the query started in UTC. |
|
auditPayload.duration | Not available for Databricks Spark audit events. |
|
auditPayload.accessControls | Includes the user's groups, attributes, and current project at the time of the query. | |
auditPayload.policySet | Provides policy details. | |
auditPayload.technologyContext.type | The technology the query was made in. |
|
auditPayload.technologyContext.clusterId | The Databricks cluster ID. |
|
auditPayload.technologyContext.clusterName | The Databricks cluster name. |
|
auditPayload.technologyContext.workspaceId | The Databricks workspace ID. |
|
auditPayload.technologyContext.pathUris | The Databricks URI scheme for the storage type. |
|
auditPayload.technologyContext.metastoreTables | The Databricks metastore tables. |
|
auditPayload.technologyContext.queryLanguage | The |
|
auditPayload.technologyContext.queryText | The | See the example below |
auditPayload.technologyContext.immutaPluginVersion | The Immuta plugin version for the Databricks Spark integration. |
|
receivedTimestamp | The timestamp of when the audit event was received and stored by Immuta. |
|
Example queryText
Below is an example of the queryText
, which contains the full notebook cell (since the query was the result of a notebook). If the query had been from a JDBC connection, the queryText
would contain the full SQL query.
This notebook cell had multiple audit records associated with it.
Example audit record
Enriched Databricks audit logs
Beyond raw audit events (such as “John Doe queried Table X in Databricks"), the Databricks audit records include the policy information enforced during the query execution, even if a query was denied.
Queries will be denied if at least one of the conditions below is true:
User does not meet policy conditions.
User is not subscribed to the data source.
Data source is not in the user's current project.
Data source is in the user's current project, but the user is not subscribed to the data source.
Data source is not registered in Immuta.
User entitlements
The user's entitlements
represent the state at the time of the query. This includes the following fields:
Property | Description |
---|---|
project | The user's current project. |
attributes | The user's attributes. |
groups | The user's groups. |
impersonatedUsers | The user that the current user is impersonating. |
Policy information
The policySet
includes the following fields:
Property | Description | Possible values |
---|---|---|
subscriptionPolicyType | The type of subscription policy. |
|
type | Indicates whether the policy is a subscription or data policy. Query denied records will always be a subscription policy |
|
ruleAppliedForUser | True if the policy was applied for the user. If |
|
rationale | The policy rationale written by the policy creator. | - |
global | True if the policy was a global policy. If |
|
mergedPolicies | Shows the policy information for each of the merged global subscription policies, if available. | - |
Last updated