Databricks access governance: are your controls keeping up?

TL;DR: Databricks access governance breaks when identity provider controls stop at the edge and miss Unity Catalog grants, workspace roles, and tokens that keep pipelines running, according to Oleria Security. The practical gap is that long-lived access often survives outside SSO, review, and revocation workflows, leaving standing privilege across analytics and AI environments.

Editorial analysis by NHI Mgmt Group, based on content published by Oleria Security: “Identity security & governance for Databricks”.

By the numbers:

• 30.9% of organisations store long-term credentials directly in code, according to the Ultimate Guide to NHIs.
• 71% of NHIs are not rotated within recommended time frames, increasing the risk of compromise over time, according to the Ultimate Guide to NHIs.

Key questions

Q: What breaks when Databricks governance stops at the identity provider?

A: Effective access breaks down because the identity provider cannot fully describe permissions that are created inside workspaces and Unity Catalog.

Q: Why do Databricks personal access tokens create governance risk?

A: Personal access tokens create risk because they can keep authenticating workloads outside normal SSO and MFA enforcement.

Q: How should security teams govern Databricks service principals and tokens?

A: Treat them as governed non-human identities with named ownership, expiry, rotation, and offboarding requirements.

Practitioner guidance

• Map effective Databricks access across all planes Trace permissions from the identity provider into workspace roles, nested groups, Unity Catalog grants and compute usage so reviews reflect actual reach.
• Inventory and age all Databricks tokens Track personal access tokens, OAuth secrets and secret scopes with creation date, expiration date and owner so stale credentials stand out.
• Review service principal permissions against real usage Compare service principal entitlements with audit logs for jobs, pipelines and notebooks, then remove catalog or workspace rights that are never exercised.

Bottom line: Databricks governance fails when teams trust directory views that do not reflect workspace, catalog and compute access.

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →