I was recently digging into some of the newer capabilities being added to Unity Catalog, and it made me realize something interesting.

Most teams still think data governance = managing permissions.

But Databricks seems to be pushing Unity Catalog in a very different direction — it’s slowly becoming a security and governance layer for the entire lakehouse.

And some of the new capabilities make that pretty clear.

Before getting into the features, there’s one shift that’s worth understanding.

The big shift

Just storing data securely is not the same as governing data.

Traditional governance mostly answered one question:

But modern data platforms need to answer much more:

• Is this column sensitive?
• Should this data be masked automatically?
• Can policies apply across hundreds of tables?
• Can we detect sensitive data automatically?

Unity Catalog is starting to handle a lot of this directly inside the platform.

1. When role-based access control stops scaling

Most teams start with something like this:

GRANT SELECT ON TABLE sales TO analyst_role

This works fine… until your platform grows.

Suddenly you have:

• hundreds of tables
• multiple data domains
• different compliance rules
• sensitive columns everywhere

Managing permissions table-by-table becomes painful.

This is where Attribute-Based Access Control (ABAC) comes in.

Instead of writing permissions per table, you define policies based on attributes.

Example ideas:

• mask columns tagged PII
• restrict access if region = EU
• allow finance data only for finance roles

Once the rule exists, it applies automatically across datasets.

Much easier to scale.

2. Finding sensitive data automatically

Another upgrade I found interesting is automatic data classification.

Instead of manually tagging columns, Unity Catalog can scan tables and detect things like:

• email addresses
• phone numbers
• personal identifiers

Once the system identifies them, those columns can be tagged automatically.

And if your governance policies depend on those tags, protection kicks in immediately.

That removes a lot of manual work from governance teams.

3. Data quality signals built into the platform

Another direction Unity Catalog is moving in is data trust.

Datasets can now expose signals like:

• freshness
• completeness
• anomalies

This helps users quickly see if a dataset is healthy or unreliable before they build dashboards or models on top of it.

It’s a small feature, but it’s very useful in large data environments.

4. Making it easier to find and understand data

Unity Catalog is also becoming more of a data discovery layer.

Teams can:

• browse datasets
• see lineage
• check certifications
• request access directly

Instead of data living in random places, it becomes easier to discover and trust.

The bigger picture

As organizations scale their data platforms, things get messy very quickly:

• lots of tables
• lots of teams
• sensitive information everywhere

Manual governance simply doesn’t scale.

The direction Unity Catalog is moving toward is policy-driven governance built directly into the platform.

Which is why I like to think of these new features as data bodyguards.

They sit in front of your data and make sure the right people see the right information — automatically.

Quick Recap :

Unity Catalog is evolving beyond just a metadata catalog.

Some interesting upgrades include:

• Attribute-Based Access Control (ABAC)
• Automatic detection of sensitive data
• Built-in data quality signals
• Better dataset discovery and lineage

Feels like Databricks is slowly turning Unity Catalog into the governance control center of the lakehouse.