Notifications
Clear all
Topic starter
06/06/2026 1:59 am
TL;DR: Databricks environments rely on personal access tokens, service principals, secrets, and consumer installations, which creates exposed control points when ownership, rotation, and visibility are weak, according to Oasis Security. The governance problem is not Databricks-specific; it is the familiar NHI failure pattern where long-lived credentials outlast accountability and expand blast radius.
NHIMG editorial — what this means for NHI practitioners
By the numbers:
- 85% of organisations lack full visibility into third-party vendors connected via OAuth apps , 38% have no or low visibility, and a further 47% have only partial visibility.
Questions worth separating out
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.
Q: Why do Databricks integrations create NHI governance risk?
A: Because integrations often receive access once and then persist long after the original approval has faded from memory.
Q: What breaks when secret rotation is not tied to ownership review?
A: Rotation alone can refresh a credential while leaving the wrong owner, the wrong permissions, or the wrong business purpose in place.
Practitioner guidance
- Separate Databricks identity classes in inventory Track personal access tokens, service principals, secrets, and consumer installations as distinct NHI classes with their own owners, expiry rules, and review cadence.
- Require explicit ownership for every non-human identity Make human ownership attestation part of the Databricks approval flow so each token or service principal has a named accountable owner.
- Bind rotation to deactivation and revalidation Rotate secrets on a schedule, then verify that the credential is still needed and still mapped to the right workload.
What's in the full announcement
Oasis Security's full blog covers the operational detail this post intentionally leaves for the source:
- A real-time Databricks identity inventory model that maps consumers, resources, permissions, human owners, and secrets.
- Specific examples of Databricks actions and authentication methods that the integration can surface for review.
- Automation details for secret rotation, owner attestation, and inactive identity cleanup in Databricks workflows.
- Cross-platform expansion notes for Databricks deployments across AWS and GCP.
👉 Read Oasis Security's analysis of Databricks NHI security and lifecycle controls →
Databricks NHI security: what IAM teams need to fix first?
Explore further
06/06/2026 3:23 am
Databricks security is really NHI lifecycle governance in disguise. The article shows that the platform’s operational model depends on identities that are not human but still carry human-grade business authority. PATs, service principals, secrets, and consumer installations all need issuance, ownership, rotation, and offboarding discipline. When those controls are fragmented, Databricks becomes a governance problem, not just a platform problem. Practitioners should treat Databricks as a lifecycle-managed identity surface, not a storage or analytics exception.
A few things that frame the scale:
- 85% of organisations lack full visibility into third-party vendors connected via OAuth apps, according to The State of Non-Human Identity Security.
- Only 1.5 out of 10 organisations are highly confident in their ability to secure NHIs, compared to nearly 1 in 4 for securing human identities, according to The State of Non-Human Identity Security.
A question worth separating out:
Q: How do organisations know if Databricks NHI controls are actually working?
A: Look for fewer orphaned identities, clear ownership on every token and service principal, and a visible decline in unused or over-permissioned integrations. If the environment still contains credentials with no business owner, controls are not working. The strongest signal is that lifecycle actions happen before access becomes stale, not after.
👉 Read our full editorial: Databricks NHI governance depends on visibility, rotation, and ownership
