TL;DR: Modern identity risk now sits in the gaps between cloud, SaaS, communication, and AI tools, where shadow admins, standing privilege, partial offboarding, and identity drift become invisible in isolation, according to Unosecur. The practical issue is not tool count but correlation: fragmented identity data prevents teams from answering who has access to what, and whether that access still belongs there.
NHIMG editorial — based on content published by Unosecur: Your identity stack lives in 100+ tools. Your security sees them as one
By the numbers:
- 96% of organisations store secrets outside of secrets managers in vulnerable locations including code, config files, and CI/CD tools.
- Only 5.7% of organisations have full visibility into their service accounts.
Questions worth separating out
Q: What breaks when identity tools cannot see each other's access data?
A: Access reviews, privilege cleanup, and offboarding all become incomplete because each tool only sees local entitlements.
Q: Why do disconnected identity systems increase breach risk?
A: Disconnected systems hide overprivileged accounts, orphaned identities, disabled authentication controls, and exposed credentials.
Q: How should security teams build a complete identity inventory?
A: Start by reconciling HR, directory, cloud, application, and privileged-access sources into one operating view.
Practitioner guidance
- Build a cross-system identity inventory Combine directory, cloud, SaaS, ticketing, and collaboration data into one entitlement view so privilege paths can be traced end to end.
- Map standing privilege to expiry and ownership Assign each privileged grant an owner, a purpose, and a revocation trigger across every connected system.
- Reconcile partial offboarding across peripheral tools Check whether departed users, contractors, and project staff still retain access in SaaS, collaboration, and code repositories after their main account is disabled.
What's in the full article
Unosecur's full blog covers the operational detail this post intentionally leaves for the source:
- A connector-by-connector view of how the 100+ integrations span cloud, SaaS, ticketing, and AI-related systems.
- Examples of the specific identity exposures surfaced by correlation across tools, including shadow admins and toxic privilege combinations.
- The practical rationale for the minute-scale integration approach and what that changes for onboarding identity sources.
- The article's own walkthrough of how visibility becomes intelligence and then action across a fragmented stack.
👉 Read Unosecur's analysis of identity fragmentation across 100+ tools →
Identity fragmentation across cloud, SaaS, and AI tools: what teams miss?
Explore further
View Full Forum → | NHI Foundation Course → | Our Services →
Identity fragmentation is now an entitlement graph problem, not a tooling problem. The core security failure is the absence of a correlated view across cloud, SaaS, collaboration, and AI-linked systems. When access decisions are distributed across tools, teams lose the ability to see privilege paths, toxic combinations, and ownership drift as a single identity event. Practitioners should treat cross-platform correlation as the governance layer, not the reporting layer.
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.
- 79% of organisations have experienced secrets leaks, with 77% of these incidents resulting in tangible damage.
A question worth separating out:
Q: Who is accountable when a partially offboarded account is still active?
A: Accountability should sit with the system owner who can prove revocation, not with the team that first created the access. When offboarding crosses multiple tools, each owner must validate that their part of the access path is removed. If no one can prove closure, the account should be treated as still live and therefore still risky.
👉 Read our full editorial: Identity fragmentation across 100+ tools is the real security gap