Home › Key concepts › Governance, access and personal data
Key concept · Walk (intermediate) · the same on every platform
Governance, access and personal data
Who owns each dataset, who may see it, and how personal data is protected.
What it is
Governance means every table has an owner, access is granted by role on a need-to-know basis, and personal data (names, phone numbers, IDs) is tagged, masked or removed according to law and policy.
See it happen: Problem Lab: tags, masking by role and an audit trail (simulation), recorded from a real run.
Why it matters
One leaked table can cost more than the whole platform. Good governance also makes data easier to find.
An example
Analysts see customer emails masked as a***@mail.com; only the support role sees them in full.
The common mistake
Giving everyone admin access 'for now'.
Where you meet it on each platform
The idea stays the same; only the product name changes.
| Job | AWS | Azure | Google Cloud | Databricks | Open source |
|---|---|---|---|---|---|
| Catalog and accesswho owns which table, who may read it, where it came from | Glue Data Catalog + Lake Formation | Microsoft Purview | Dataplex | Unity Catalog | OpenMetadata |
| Identity and secretswho is calling, what they may do, where keys live | IAM + Secrets Manager | Entra ID + Key Vault | IAM + Secret Manager | Unity Catalog grants + secrets | Keycloak + sops |
Related ideas
Where it shows up
Part of the Walk level on these paths: Data Engineering (trusting data).