Topic starter
24/06/2026 7:30 pm
TL;DR: Access bottlenecks are slowing analytics and AI initiatives because traditional IAM tools were built for application access, not granular data governance, according to Collibra. The real issue is that manual, ticket-based controls cannot keep pace with governed self-service access for humans and AI agents.
Editorial analysis by NHI Mgmt Group, based on content published by Collibra: “Introducing Collibra Data Access: Connect the right users to the right data faster”.
By the numbers:
- 92% of data consumers at banks said the data they need is often unavailable or takes too long to be made available, according to a Deloitte survey cited by Collibra.
Key questions
Q: What breaks when access governance is still built around tickets and long-lived credentials?
A: Ticket-based and credential-heavy models break when work moves faster than human approval cycles.
Q: Why does governance that stays at the documentation layer create risk for AI and analytics programs?
A: Documentation alone leaves a gap between policy intent and actual data use.
Q: How do security teams know whether data masking is actually working?
A: Data masking is working when users can complete their task without seeing sensitive values they are not authorised to view.
Practitioner guidance
- Define the data access last mile Map where approval ends and data exposure begins across your main warehouses, schemas and sensitive tables.
- Replace ticket-based access with governed self-service Measure how much access friction still depends on spreadsheets, manual approvals and repeated coordination across platforms.
- Standardise masking policies across data platforms Use one policy model for sensitive fields so users see only what their role permits, even when the data is replicated across Snowflake, Databricks or BigQuery.
Bottom line: Traditional IAM alone does not solve the problem of governed access to sensitive data across modern analytics and AI environments.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
25/06/2026 4:49 am
Data access governance is becoming a data-plane problem, not just an identity problem. When the business value sits in the dataset itself, coarse application access is too blunt to express who should see which fields, rows or masked values. That shifts the governance burden from login-time authorisation to ongoing data entitlement enforcement. Practitioners should treat the data layer as part of the identity control surface.
A question worth separating out:
Q: Which teams are accountable for governed self-service data access?
A: Accountability usually spans data governance, IAM, platform engineering and the business data owner. The key is that access decisions must be governed centrally while being enforced where the data lives. If ownership is split but policy is not, the result is slower approvals, weaker audit trails and inconsistent access decisions across platforms.
👉 Read our full editorial: Data access governance for AI agents needs data-level controls