Notifications
Clear all
Topic starter
28/08/2026 12:04 pm
TL;DR: Enterprise identity is failing because fragmented IAM stacks cannot govern humans, machines, and AI agents at the speed modern environments demand, according to Newcore. Its central claim is that runtime, continuous authorization becomes mandatory when AI and NHI activity compresses exposure windows to seconds, not hours.
NHIMG editorial — based on content published by Newcore: Enterprise Identity is breaking
By the numbers:
- A typical enterprise identity stack uses 11 tools for workforce identity security, increasing operational complexity and policy drift.
Questions worth separating out
Q: What breaks when identity signals are analysed in separate consoles?
A: What breaks is causal reconstruction.
Q: Why do AI agents and NHIs require runtime authorization?
A: Because their work can happen faster than batch governance cycles.
Q: What do IAM teams get wrong about unified identity platforms?
A: They often assume aggregation alone solves governance.
Practitioner guidance
- Map duplicated identity decisions across tools Identify where the same role change, privilege grant, or revocation is handled in IdP, PAM, and IGA separately.
- Shorten the authorization review window Find identities that can complete sensitive actions before governance state refreshes, especially service accounts and AI agents.
- Unify identity telemetry before expanding AI access Require shared event visibility across authentication, authorization, and governance before granting broader access to agents or workloads.
What's in the full article
Newcore's full analysis covers the operational detail this post intentionally leaves for the source:
- The step-by-step identity stack breakdown across IdP, PAM, IGA, NHI, and authorization engines.
- The runtime authorization comparison between static session checks and continuous decisioning.
- The practical examples of how policy drift appears across Okta, SailPoint, and CyberArk workflows.
- The real-world enterprise bandwidth problem created by managing multiple disconnected identity consoles.
👉 Read Newcore's analysis of fragmented identity stacks and runtime authorization →
Identity silos and runtime authorization: are your controls keeping up?
Explore further
View Full Forum → | NHI Foundation Course → | Our Services →
28/08/2026 12:04 pm
Identity silos are now a structural access-control problem, not an IT admin inconvenience. When authentication, governance, and privileged access sit in separate consoles, the enterprise cannot prove that one current decision applies everywhere. The result is policy drift by design, because each tool evaluates a different slice of the identity state. Practitioners should treat this as a control architecture issue, not a dashboard problem.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to Ultimate Guide to NHIs.
- A separate finding shows that 97% of NHIs carry excessive privileges, which means visibility gaps quickly become privilege governance gaps.
A question worth separating out:
Q: Why do service accounts and AI agents need different controls from human users?
A: Service accounts and AI agents authenticate and act without the predictable patterns that human identity systems expect. They can operate across runtimes, scale quickly, and carry permissions into automated workflows. That means access decisions should consider workload context, runtime behaviour, and time-bound authority rather than relying only on user-centric IAM patterns.
👉 Read our full editorial: Unified identity control planes are now a governance requirement
