TL;DR: Most identity programs fail before recertification because they only cover a fraction of enterprise systems, leaving legacy platforms, custom apps, and databases outside governance, according to Hydden. The real constraint is not review cadence but coverage that can be established quickly and kept trustworthy as source systems change.
NHIMG editorial — what this means for NHI practitioners
Questions worth separating out
Q: How should IAM teams handle systems that are outside their identity governance tools?
A: Treat them as governance gaps, not exceptions.
Q: Why do identity programs lose coverage after onboarding a source system?
A: Because source systems change while connectors often assume stability.
Q: What do security teams get wrong about connector catalogues?
A: They treat catalogue support as the end of the governance problem.
Practitioner guidance
- Inventory the unmanaged long tail List every application, database, directory, file feed, and niche SaaS instance that holds identities or entitlements, then mark which ones are outside your current governance boundary.
- Validate source trust after onboarding Do not treat initial connector setup as proof of ongoing coverage.
- Require explainable field mapping Document how source fields map into the normalised identity model, including any assistant-proposed transformations.
What's in the full announcement
Hydden's full article covers the operational detail this post intentionally leaves for the source:
- How the Universal Collector is configured for cloud, SaaS, directory, database, file feed, and CLI sources.
- How the built-in assistant maps source fields into a standard identity model and how those mappings are reviewed.
- How protected validation mode works before production collection is committed.
- How the platform handles on-premises and restricted-network deployments.
👉 Read Hydden's analysis of identity coverage and the Universal Collector →
Identity coverage gaps: what IAM teams are missing?
Explore further