Topic starter
12/06/2026 1:01 am
TL;DR: Identity compromise drives a large share of breaches, with stolen credentials cited in 86% of incidents and compromised identities as the first step in 80%, according to Zluri’s article. That makes identity security a governance problem, not just an authentication problem, because access scope, rotation, and monitoring determine how far an attacker can move.
Editorial analysis by NHI Mgmt Group, based on content published by Zluri: “Identity Security: Why Does It Matter?”.
By the numbers:
- Stolen credentials cause 86% of breaches, according to Zluri.
Key questions
Q: Why does least privilege still fail in real IAM programmes?
A: Least privilege fails when access is granted more broadly than the work requires, then left in place after the need changes.
Q: Why do compromised credentials remain so effective in modern environments?
A: Compromised credentials remain effective because they produce legitimate-looking access.
Q: What breaks when service accounts are not centrally governed?
A: When service accounts are created and maintained outside a central identity process, ownership, purpose, and retirement become unclear.
Practitioner guidance
- Map the full identity estate Inventory human users, third-party accounts, service accounts, and machine identities in one view so entitlement gaps are visible across the whole access surface.
- Tighten role scope before adding more controls Review roles and access packages for over-broad permissions, inherited access, and stale entitlements that exceed current job or workload requirements.
- Bring non-human identities into recertification Include service accounts, automation credentials, and machine identities in access reviews so privileged access does not escape governance simply because it is non-human.
Bottom line: Identity compromise remains a primary breach path because valid credentials can bypass normal controls and expose broader entitlements.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 4 days ago by NHI Mgmt Group
12/06/2026 10:39 am
Least privilege is an entitlement design problem, not a slogan: The article correctly shows that access becomes risky when identities receive more scope than their job actually requires. That is true for employees, vendors, service accounts, and machine identities alike. The practitioner takeaway is that privilege has to be governed as a living entitlement state, not a one-time provisioning decision.
A question worth separating out:
Q: How should security teams prioritise identity work when NHIs outnumber humans at scale?
A: Start with identities that can reach sensitive systems, inherit privilege, or create lateral movement potential. Inventory is only the first step. Prioritisation should focus on blast radius, revocation difficulty, and how much trust a given identity can accumulate across cloud, SaaS, and AI workflows.
👉 Read our full editorial: Identity security gaps expose why least privilege still fails
This post was modified 4 days ago by NHI Mgmt Group