Notifications
Clear all
Topic starter
23/06/2026 7:01 pm
TL;DR: Semantic layers map business meaning to physical data assets so analytics and AI systems can use consistent definitions, reducing metric drift and ambiguous outputs, according to Collibra. The governance lesson is that shared meaning is now infrastructure, not documentation, when AI is asked to answer business questions.
NHIMG editorial — based on content published by Collibra: What is a semantic layer? How shared business meaning powers better AI and analytics
Questions worth separating out
Q: How should teams govern identity data when AI systems consume it directly?
A: Teams should govern identity data the same way they govern business-critical metrics: define authoritative terms, map them to live sources, and ensure every consuming system uses the same meaning.
Q: Why do inconsistent definitions create risk in IAM programmes?
A: Inconsistent definitions cause access decisions, reviews, and reporting to diverge across systems.
Q: What breaks when identity terminology is not standardised?
A: What breaks is not just reporting.
Practitioner guidance
- Standardise identity terminology across systems Define one authoritative meaning for account types, entitlement classes, lifecycle states, and policy labels, then map every consuming system back to that source of truth.
- Bind policy decisions to governed metadata Ensure access reviews, entitlement approvals, and AI-assisted decisions consume the same business context that your catalog or glossary records, rather than local field names.
- Test for semantic drift before automating decisions Compare how the same identity concept is represented in IAM, PAM, SIEM, data catalog, and AI workflows, then fix mismatches before enabling automated action.
What's in the full article
Collibra's full blog post covers the operational detail this post intentionally leaves in the source:
- How the semantic layer maps glossary terms to physical assets across catalog and lineage views
- Examples of how business definitions are carried into AI and analytics consumption paths
- The distinction between BI semantic layers and governance semantic layers in enterprise architecture
- Practical examples of how data products retain meaning when shared across teams
👉 Read Collibra's full blog post on semantic layers and shared business meaning →
Semantic layers and AI accuracy: what practitioners need now?
Explore further
25/06/2026 2:48 am
Shared meaning is now a control plane requirement, not a documentation problem. The article correctly frames semantic consistency as infrastructure because AI and analytics fail when the enterprise cannot agree on what a business term means. That same failure pattern applies in identity governance, where role names, entitlement labels, and lifecycle states often diverge by system. The practitioner conclusion is simple: if meaning is not governed centrally, every downstream decision inherits ambiguity.
A few things that frame the scale:
- The average estimated time to remediate a leaked secret is 27 days, despite 75% of organisations expressing strong confidence in their secrets management capabilities, according to The State of Secrets in AppSec.
- Organisations maintain an average of 6 distinct secrets manager instances, creating fragmentation that undermines centralised control, according to The State of Secrets in AppSec.
A question worth separating out:
Q: How can security teams tell whether their governance model is semantically sound?
A: A semantically sound model produces the same answer regardless of which system queries it. If the same identity concept yields different values, different owners, or different lifecycle states across tools, the governance model is fragmented. Teams should test for consistency across catalog, IAM, PAM, and AI workflows before trusting automated decisions.
👉 Read our full editorial: Semantic layers create shared meaning for AI and analytics
