Topic starter
06/11/2026 6:39 pm
TL;DR: Connecting applications to a governance platform only moves identity data, and inconsistent accounts, stale attributes and unmapped entitlements can drive automated access decisions at scale, according to READI. NHI Mgmt Group sees identity data normalization and correlation as the real control boundary, because governance built on bad inputs becomes fast, confident and wrong.
Editorial analysis by NHI Mgmt Group, based on content published by READI: “Identity data quality: the problem nobody wants to own.”.
Key questions
Q: Why does identity data quality matter so much in IAM programmes?
A: Because every provisioning, certification, and role-mapping decision depends on accurate identity data.
Q: Why do identity certifications fail when account data is inconsistent?
A: Identity certifications fail when account records do not reliably resolve to one person, so reviewers cannot tell which access is truly owned by the same identity.
Q: How should teams govern disconnected applications that do not expose APIs?
A: Treat them as governed exceptions with a defined workflow, not as informal manual tasks.
Practitioner guidance
- Normalize identity attributes before automating decisions Define authoritative attribute sources, standard value sets and transformation rules for the fields that drive provisioning, recertification and deprovisioning.
- Implement deterministic identity correlation Require repeatable matching rules for duplicate accounts, contractor records and system-specific identifiers so one person or workload resolves to one governed identity.
- Standardise entitlement semantics across applications Create a shared mapping for roles and entitlements so reviewers can interpret access labels consistently across connected systems.
Bottom line: Identity governance breaks down when account and entitlement data cannot be normalized into a consistent model.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/11/2026 6:41 pm
Identity data quality is the hidden control plane of governance. Governance tooling does not create trust in access data, it consumes whatever the connected systems provide. If the source model is inconsistent, the downstream review, provisioning and certification logic inherits that inconsistency as policy output. Practitioners should treat identity data quality as an operating control, not a data-cleanup exercise.
A question worth separating out:
Q: What is the difference between identity transport and identity transformation?
A: Identity transport moves identity data from one system to another, usually in the source format and structure. Identity transformation changes that data during ingestion or synchronisation by normalizing, correlating and mapping attributes, identifiers and relationships so different systems can interpret them consistently. Transport is about movement. Transformation is about meaning and interoperability.
👉 Read our full editorial: Identity data quality is the missing control in governance automation