Topic starter
20/08/2026 5:49 pm
TL;DR: AI workloads can still hold excessive access even when CIEM looks clean, ARMO reports, because declared-versus-used checks do not separate justified actions from inherited or unjustified scope. Identity governance has to track effective scope and behavior together or it will keep reading exercised access as safe access.
Editorial analysis by NHI Mgmt Group, based on content published by ARMO: “How to Identify and Reduce Excessive Permissions in AI Workloads”.
Key questions
Q: Why do AI workloads create risk when they inherit broad cloud permissions?
A: They create risk because AI systems can execute many actions at machine speed, so inherited privileges become operational reach rather than passive access.
Q: What do security teams get wrong about AI agent permissions?
A: Teams often assume that permissions are safe if the agent was approved at deployment.
A: The failure mode is that CIEM is measuring exercised access, not justified access.
Practitioner guidance
- Classify AI permission excess by failure mode Separate unused excess, unjustified use, and inherited overreach before you change policy.
- Trace effective scope through the full identity chain Inspect service accounts, cluster roles, workload identity bindings, and any transitive role assumptions that contribute to the agent's real access.
- Correlate prompts, tool calls, and API events Use runtime telemetry that links prompt context to tool selection and downstream API activity.
Bottom line: AI workload excess is not a single problem, because unused grants, unjustified actions, and inherited scope failures need different controls.
Glossary terms: Unjustified use, Inherited overreach, Declared-Versus-Used Diagnostic, Prompt-To-Tool Correlation
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 2 days ago by NHI Mgmt Group
20/08/2026 6:29 pm
Declared-versus-used analysis is the wrong primary diagnostic for AI workloads. That assumption was designed for deterministic systems whose legitimate actions are bounded by code and stable over time. It fails when an agent's action set shifts with prompts, retrieval context, and tool availability, because observed use no longer proves appropriate use. The implication is that permission governance for agents has to classify context, not just count calls.
A few things that frame the scale:
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job, according to the 2026 Infrastructure Identity Survey.
- 19% of organisations give AI systems dramatically more access than human employees, nearly one in five granting unrestricted privilege, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: How should organisations investigate inherited overreach in AI workloads?
A: Start with the agent's visible service account, then trace every binding and assumption that contributes to effective scope across the platform. If the excess sits above the workload boundary, a local policy edit will not remove it, so the investigation has to follow the identity chain end to end.
👉 Read our full editorial: AI workload permissions: why CIEM misses agent-specific excess