Skip to main content
XenonStack

Elixirdata

XenonStack Blog SAP Databricks Governance and Security: Enterprise Guide

and | Published | Updated

SAP Databricks Governance and Security: Enterprise Guide
15:52

Key takeaway

  • Govern and secure SAP Databricks: Unity Catalog controls, ABAC tags, audit logs, GDPR and HIPAA evidence, and AI agent oversight, in an adoption sequence.

SAP Databricks is the managed Databricks service included in SAP Business Data Cloud, and governance and security for it mostly sit in one place: Unity Catalog. According to the Databricks launch post, SAP Databricks became generally available on 30 April 2025. For a CISO or CDO the practical question is which controls apply to SAP data once it is shared into that environment, and who owns each one.

This guide answers that question in order: where the control points are, what the SAP Databricks governance documentation says Unity Catalog manages, how to map risks to controls, how AI agents change the picture, and what to adopt first. It builds on our guides to SAP Business Data Cloud with Databricks and data governance for business-ready data, and the Databricks service page.

Where do governance and security sit in SAP Databricks?

The Databricks launch post describes SAP Databricks as "a fully managed version of Databricks included natively as a service in SAP Business Data Cloud". It says data products in SAP Business Data Cloud reach SAP Databricks through Delta Sharing, with "secure, bidirectional data access without physically copying data between systems". The SAP Databricks documentation describes receiving shares over an open sharing protocol it calls OpenSharing. The SAP Business Data Cloud page says SAP Business Data Cloud "unifies and governs all SAP data" and keeps its original business context and semantics.

In practice this gives three control points, each with a different owner.

Control pointWhat it governsTypical ownerSource
SAP Business Data Cloud data products and sharesWhich SAP data is published and shared into SAP DatabricksSAP data and platform teamSAP and Databricks pages above
Unity Catalog in SAP DatabricksAccess to catalogs, schemas, tables, volumes and models; lineage; audit; profilingData platform and governance teamSAP Databricks governance documentation
Identity, agents and applications on topWho or what calls the data, and what it may do with the answerSecurity, risk and AI platform teamNIST SP 800-207, OWASP LLM Top 10

A gap at any of the three undermines the others. For example, fine-grained policy in Unity Catalog does not decide what an AI agent does with a result. That is why the rest of this guide treats data policy and agent policy as separate layers. Our guide to an open and unified metadata platform covers the metadata side in more depth.

What does Unity Catalog manage in SAP Databricks?

The SAP Databricks governance documentation lists the following. Where the page gives no detail we say so rather than fill the gap.

Two-column diagram mapping four risks (over-broad access, clear sensitive columns, data leaving via storage, unknown access history) to Unity Catalog controls
CapabilityWhat the documentation saysWhat it means for you
Centralised access controlAdministrators manage permissions for teams and individuals across workspaces; privileges are managed with access control lists through UIs or SQLOne place to grant and review access, instead of per-workspace rules
Securable objectsSchemas, tables, volumes (non-tabular data), registered ML models, external locations and credentialsFiles and models need the same review as tables
LineageCaptured at runtime down to column level, including notebooks, jobs and dashboardsImpact analysis before a change; evidence for reviewers
AuditingThe page names auditing; the audit log system table (system.access.audit) records user identity, service, action, request parameters and responseFeeds investigation and access reviews; retention is not stated on the page
Data profilingMonitors statistical properties and quality of tablesEarly warning on quality drift in governed tables
External locationsAdministrators can make external locations read-only to prevent data exfiltrationA simple guardrail for data leaving through storage

Sources: SAP Databricks governance documentation and audit log system table documentation, read 12 November 2026. Details of each privilege are on separate pages that we did not read, so confirm them against your own metastore before you design roles.

Which newer controls matter for SAP data?

Two changes in the April 2026 release notes matter most. On 2 April 2026 governed tags became generally available, letting administrators define a controlled set of tags for access control, data classification and cost tracking. On 6 April 2026, when you mount an SAP Business Data Cloud share to a catalog, SAP semantic metadata (table and column comments, keys and governance tags) syncs into Unity Catalog, and the SAP governance tags can be used in ABAC policies.

According to the Unity Catalog ABAC documentation, attribute-based access control evaluates attributes on securable objects. Policies attach at catalog, schema or table level and take effect automatically on anything carrying the targeted governed tags. It supports row filter policies, column mask policies, and GRANT and DENY policies. At the time we read it, metastore-level policies, policies on views and DENY policies were marked Beta, so check status before relying on them for regulated data.

How do you map risks to controls?

Start from the risk, not the feature. The mapping below is a design aid. The control column names Unity Catalog features from the documentation above; the risk column is editorial.

RiskControl to applyWhere it lives
Over-broad access to sensitive SAP dataLeast-privilege grants; ABAC with governed tags and SAP governance tags; row filters and column masksUnity Catalog
Sensitive columns reaching analysts or models in clearColumn mask policies on tagged columnsUnity Catalog (ABAC)
Data leaving through storageRead-only external locationsUnity Catalog
Not knowing who touched whatAudit log system table and column-level lineageUnity Catalog and system tables
Implicit trust in a user, device or agentAuthenticate and authorise before each session; no trust from network locationIdentity layer; see NIST SP 800-207
An agent doing more than intendedScoped agent identity, approvals and decision traces outside the data platformAgent governance layer

The zero trust row follows NIST SP 800-207, which says zero trust "assumes there is no implicit trust granted to assets or user accounts" and that authentication and authorisation happen before a session with a resource begins. Our guides to zero trust security architecture and SOC systems cover how this connects to monitoring and response.

Which regulations apply, and what does the platform do about them?

No platform makes an organisation compliant on its own. The platform supplies controls; your policies, evidence and processes decide compliance. Two regimes come up most often with SAP data.

RegimeWhat the official source saysWhat to evidence
GDPRSee the GDPR text on EUR-Lex; we cite it as a link only and have not summarised articles hereAccess limits, lineage and audit records for personal data
HIPAAThe HHS HIPAA Security Rule page says the Security Rule sets standards for electronic protected health information and requires fitting administrative, physical and technical protectionsWho can reach ePHI, and a record of access

Neither source names SAP Databricks, so confirm scope with your counsel and your SAP and Databricks contracts.

What changes when AI agents query governed SAP data?

Agents add a decision layer above the data platform. The OWASP Top 10 for LLM Applications (2025) lists risks that apply here, including Sensitive Information Disclosure (LLM02) and Excessive Agency (LLM06). Unity Catalog can limit what an identity reads, but it does not record why an agent acted or whether a person approved it.

Teams therefore add a separate layer. ElixirData Context OS keeps governed context, versioned policy and decision traces in one decision layer above AI agents, and AgentGRC keeps autonomous agent actions inside policy, with the audit trail risk teams need. ElixirClaw is an agentic OS platform to build, orchestrate and govern AI agents and automation workflows while keeping humans in control. For the security side see cybersecurity challenges in agentic AI, GUI agents and securing AI models with Microsoft Security.

What is a sensible adoption sequence?

StepActionDone when
1Inventory which SAP data products are shared into SAP Databricks and who owns eachEvery shared product has a named owner
2Classify sensitive data with governed tags, using SAP governance tags where they syncSensitive columns carry tags
3Replace ad hoc grants with group-based least-privilege grantsNo direct user grants on sensitive tables
4Add column mask and row filter policies on tagged dataPolicy tests pass for each role
5Route audit logs and lineage into a regular access reviewA review has run at least once
6Put agents behind scoped identities, approvals and decision tracesEach agent action can be traced to a policy

Our guide to Data DevOps covers how to test and deploy such policy changes safely.

Video: data governance in the enterprise

XenonStack video: data governance and enterprise information management.

What are the trade-offs, and when should you hold back?

  • Beta features. Metastore-level ABAC, ABAC on views and DENY policies were marked Beta when read. Use them in non-regulated scopes first.

  • Two catalogs of truth. SAP-side authorisations and Unity Catalog grants are separate mechanisms. Decide which is authoritative for each dataset. We have not verified how SAP-side authorisations map to Unity Catalog, so treat that as an open design question.

  • Tag discipline. ABAC is only as good as the tags. Untagged data is unprotected by tag-based policy.

  • Do not start with agents. If access, lineage and audit are not in place, adding agents multiplies the exposure.

Context Workshop. To map one decision your agents should make on SAP and Databricks data, and the context and policy it depends on, book a Context Workshop. See what happens in the workshop.

Frequently asked questions

Where is governance enforced in SAP Databricks?

Mainly in Unity Catalog, which the SAP Databricks documentation describes as providing centralised access control, lineage and auditing across workspaces. SAP Business Data Cloud governs which SAP data products are shared in.

Can SAP governance tags be used in access policies?

Yes. The April 2026 release notes say that when an SAP Business Data Cloud share is mounted to a catalog, SAP semantic metadata including governance tags syncs into Unity Catalog and the tags can be used in ABAC policies.

Is ABAC generally available in Unity Catalog?

Governed tags became generally available on 2 April 2026. The ABAC documentation marks metastore-level policies, policies on views and DENY policies as Beta, so check the current status before relying on them.

Does SAP Databricks make us GDPR or HIPAA compliant?

No platform does that alone. It supplies controls such as access limits, lineage and audit logs. Compliance depends on your policies and evidence, and on the official texts for each regime.

How should we govern AI agents that use this data?

Treat agent policy as its own layer. Give each agent a scoped identity, require approvals for risky actions and keep decision traces. OWASP lists Excessive Agency among the top risks for LLM applications.

Related reading

Continue with data governance for business-ready data and the open and unified metadata platform.

Next Steps towards Governance and Security

Talk to our experts about the next steps in Governance and Security. Discover how industries and departments implement robust security frameworks, compliance strategies, and risk management to protect data and ensure regulatory adherence. Leverage AI-driven governance to automate security operations, enhance data integrity, and optimize enterprise security.

Follow XenonStack on LinkedIn: XenonStack on LinkedIn for new guides on agentic AI, data and platform engineering.

Table of Contents

navdeep-singh-gill

Navdeep Singh Gill

Global CEO and Founder of XenonStack

LinkedIn profile

Navdeep Singh Gill is serving as Chief Executive Officer and Product Architect at XenonStack. He holds expertise in building SaaS Platform for Decentralised Big Data management and Governance, AI Marketplace for Operationalising and Scaling. His incredible experience in AI Technologies and Big Data Engineering thrills him to write about different use cases and its approach to solutions.

Get the latest articles in your inbox

Subscribe Now

Interested in solving your challenges with the XenonStack team?
Get Started

Tell us about you and your priorities so we can prepare the right conversation. It takes about 2 minutes.

Please Select your Industry
Banking
Fintech
Payment Providers
Wealth Management
Discrete Manufacturing
Semiconductor
Machinery Manufacturing / Automation
Appliances / Electrical / Electronics
Elevator Manufacturing
Defense & Space Manufacturing
Computers & Electronics / Industrial Machinery
Motor Vehicle Manufacturing
Food and Beverages
Distillery & Wines
Beverages
Shipping
Logistics
Mobility (EV / Public Transport)
Energy & Utilities
Hospitality
Digital Gaming Platforms
SportsTech with AI
Public Safety - Explosives
Public Safety - Firefighting
Public Safety - Surveillance
Public Safety - Others
Media Platforms
City Operations
Airlines & Aviation
Defense Warfare & Drones
Robotics Engineering
Drones Manufacturing
AI Labs for Colleges
AI MSP / Quantum / AGI Institutes
Retail Apparel and Fashion

Continue