Notifications
Clear all
Topic starter
26/08/2026 11:50 am
TL;DR: Cybersecurity detections are now 82% malware-free, according to SailPoint, which means valid credentials and immature identity governance are driving more risk than perimeter tools can absorb. The harder lesson is that 63% of organisations remain in early identity maturity stages, so checklist deployments often create long-term security debt rather than durable control.
NHIMG editorial — based on content published by SailPoint: Beyond the checklist: unmasking the hidden costs of immature identity
By the numbers:
- 82% of cybersecurity detections are now malware-free, meaning attackers increasingly bypass perimeter controls by using valid credentials.
- 63% of organisations remain stuck in the early stages of their identity journeys.
- Advanced identity maturity drives a 70% risk reduction in security incidents.
Questions worth separating out
Q: How should security teams evaluate whether their identity program is actually mature?
A: Focus on operating resilience, not deployment status.
Q: Why do brittle integrations weaken identity governance?
A: Brittle integrations weaken governance because the control depends on data that no longer arrives reliably.
Q: What do organisations get wrong about identity checklists?
A: They confuse feature coverage with control quality.
Practitioner guidance
- Audit identity programme debt across lifecycle controls Measure how much manual work still exists in provisioning, recertification, deprovisioning, and access exceptions.
- Test connector resilience under real application change Review which connectors are vendor-maintained, which are custom-built, and which fail when target systems update.
- Replace snapshot reviews with continuous identity signals Use always-on monitoring for entitlement outliers, privilege changes, and access anomalies so teams can act between scheduled recertifications.
What's in the full article
SailPoint's full blog covers the operational detail this post intentionally leaves for the source:
- Versionless architecture and continuous update handling for identity platforms
- Why connector maintenance model and integration depth affect long-term control quality
- How embedded AI changes entitlement review, outlier detection, and access recommendations
- The broader platform and ecosystem argument behind the total cost of ownership discussion
👉 Read SailPoint's analysis of hidden identity program costs and maturity gaps →
Identity program maturity: where the hidden operational costs land?
Explore further
26/08/2026 11:51 am
Checklist identity is a maturity illusion, not a governance strategy. A platform can satisfy procurement criteria and still fail to control real-world access risk if lifecycle, visibility, and review processes remain immature. The article is right to separate deployment from maturity, because the difference shows up in operational drag, not just security posture. Practitioners should treat maturity as the control state that matters, not the launch milestone.
A few things that frame the scale:
- 91.6% of secrets remain valid five days after the targeted organisation is notified, showing a critical gap in remediation procedures, according to Ultimate Guide to NHIs.
- Only 5.7% of organisations have full visibility into their service accounts, which explains why identity maturity claims often outrun operational reality.
A question worth separating out:
Q: How do identity teams reduce hidden cost without weakening security?
A: By using lifecycle discipline to remove rework, not by accepting lighter controls. Prioritise stable integrations, continuous review signals, and clean offboarding so the team spends less time repairing the platform and more time reducing access risk.
👉 Read our full editorial: Identity program maturity is the real cost centre in cybersecurity
