Topic starter
06/11/2026 6:37 pm
TL;DR: Nexis’s analysis says Gartner’s Hype Cycle for Digital Identity 2025 names Identity Visibility and Intelligence Platforms, or IVIP, as a category for rapid integration and visibility across IAM data, events, relationships, posture and analytics. NHI Mgmt Group’s view is that the real issue is not a new label but the need to govern fragmented identity stacks as one control surface.
Editorial analysis by NHI Mgmt Group, based on content published by Nexis: “Governing the Identity Patchwork: What IVIP Has to Deliver”.
By the numbers:
- A large enterprise CISO operates roughly 83 separate cybersecurity tools, according to Nexis.
Key questions
Q: How do teams find hidden access conflicts across IAM systems?
A: Teams find hidden access conflicts by reconciling identity records from HR, directories, SaaS, cloud and PAM into a single entitlement view, then comparing roles, groups, approvals and effective access for each person.
Q: Why does access review fail when identity data is dispersed across systems?
A: Access review fails because reviewers cannot reliably tell which record is current when ownership, entitlement, and activity data are split across multiple platforms.
Q: How should organisations govern service accounts alongside workforce access?
A: Organisations should govern service accounts with the same identity governance model used for workforce access, but with tighter ownership, purpose and secret controls.
Practitioner guidance
- Build a cross-system identity inventory Unify roles, entitlements, privileged accounts and service accounts into one view so conflicting access can be compared across platforms rather than inside each tool.
- Rework recertification around joined-up evidence Base access reviews on correlated entitlement, usage and approval data, not on isolated exports from separate governance and PAM systems.
- Surface segregation-of-duties conflicts across domains Check for combinations that look safe in one system but create incompatible authority when human and non-human identities are assessed together.
Bottom line: Fragmented IAM stacks can preserve hidden access conflicts even when each individual system appears to be operating correctly.
What's in the full article
Nexis's full blog post covers the operational detail this analysis intentionally leaves for the source:
- How the IVIP capability set maps across IGA, PAM and non-human identity workflows
- The operational differences between simple visibility, posture management and remediation
- The governance implications of integrating service accounts into entitlement reviews
- The rationale behind the category's placement in Gartner's identity landscape
👉 Read Nexis's analysis of IVIP and fragmented identity governance →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/11/2026 6:42 pm
IVIP is best understood as a governance layer over fragmentation, not as a substitute for fixing the estate. The value is in making disparate identity data usable across IGA, PAM and non-human identity systems. That matters because governance decisions depend on the ability to see conflicts, not just store records. Practitioners should treat the category as an operational bridge, not an architecture endpoint.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: What is the difference between visibility and protection in identity governance?
A: Visibility tells you which identities exist, what they can access, and where risk is concentrated. Protection goes further by using that visibility to enforce policy, restrict access, and create auditable control actions. In practice, visibility is the prerequisite for response, while protection is the operational outcome that reduces exposure across the enterprise.
👉 Read our full editorial: IVIP exposes identity risk hidden across fragmented IAM stacks