Topic starter
06/11/2026 6:56 pm
TL;DR: Data hygiene is what determines whether automation produces reliable access decisions or just faster mistakes, according to READI's analysis of IAM practice. Practitioners need consistent identity data before identity-first security or zero trust can operate safely.
Editorial analysis by NHI Mgmt Group, based on content published by READI: “Reflections on the Gartner Identity and Access Management Summit 2024”.
Key questions
Q: Why do disconnected apps create so much IAM risk?
A: Disconnected apps create risk because identity changes no longer propagate automatically, so access can outlive the business event that should have removed it.
Q: How does identity automation affect access reviews?
A: Identity automation makes access reviews more current by continuously synchronising entitlements, account status, and role assignments from authoritative systems into the review set.
Q: How should teams improve identity data quality before automation?
A: Teams improve identity data quality before automation by first fixing the source record, standardising required attributes, and reconciling duplicates, stale accounts, and mismatched identifiers.
Practitioner guidance
- Establish a canonical identity record Define one governed identity source that reconciles person, account and entitlement attributes before automation consumes them.
- Normalise disconnected application data Inventory legacy and disconnected systems, then map their identity attributes into a standard model that workflow tools can trust.
- Separate routine tasks from high-risk decisions Automate repeatable identity operations, but keep privileged changes and exceptions behind explicit approval or review.
Bottom line: Identity automation depends on clean source data, not just better workflow design.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/11/2026 6:56 pm
Identity automation is only as good as the data model underneath it. If the same identity attributes are duplicated, stale or inconsistent across source systems, automation will scale error faster than it scales control. That is why data hygiene is not a support function for IAM, but the condition that makes identity governance reliable.
A few things that frame the scale:
- 69% of security leaders agree identity management must fundamentally shift to address agentic AI systems, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What is the best way to govern human approvals in IAM workflows?
A: The best way to govern human approvals in IAM workflows is to use defined approval gates with named approvers, role-based routing, segregation of duties checks, and time-bound decision records. Approvals should be tied to the specific entitlement, requester, and business justification, with escalation for missing responses and audit logs for every decision.
👉 Read our full editorial: Data hygiene now governs identity automation at scale