Topic starter
24/06/2026 8:45 pm
TL;DR: PlainID's analysis of secure-by-design agent workflows finds agentic AI makes access control a runtime governance problem because agents can retrieve data, call APIs, and take actions autonomously. IAM teams need privilege, logging, and verification to follow each agent action across prompts, tools, APIs, and outputs, not a single account.
Editorial analysis by NHI Mgmt Group, based on content published by PlainID: “Secured by Design: Building Trustworthy Agentic AI from the Ground Up”.
By the numbers:
- More than 50% of successful cyberattacks against AI agents through 2029 will exploit access control weaknesses, according to Gartner research cited by PlainID.
- The average cost of a UK data breach reached £4.53 million, according to Gartner research cited by PlainID.
- 28% of breaches were linked to human error, according to Gartner research cited by PlainID.
Key questions
Q: Why do AI agents increase access risk compared with fixed workloads?
A: Because an agent can assemble its access path at runtime, the true blast radius is not always known at provisioning time.
Q: What breaks when access control is bolted onto AI applications only at the code level?
A: Brittle, scattered enforcement creates inconsistent policy decisions and makes it easy for gaps to appear between ingestion, retrieval, and execution.
Q: When should organisations use runtime authorization for AI agents?
A: Use runtime authorization when agent behavior can change based on context, tools, or delegated workflows.
Practitioner guidance
- Embed authorization into agent workflows Make runtime authorization part of the agent’s execution path so each data retrieval, tool call, and API action is checked before it can proceed.
- Scope privileges across the full agent surface Define what the agent may access, do, retrieve, and expose across prompts, tools, APIs, data sources, and responses, not just at account creation.
- Instrument autonomous actions for auditability Log each autonomous decision and execution step with enough context to reconstruct why the agent acted and whether the action stayed within policy.
Bottom line: Agentic AI turns authorization into a runtime governance problem because agents can make independent access decisions during execution, not just at login or provisioning time.
Glossary terms: Agentic Identity, Runtime Authorisation, Secure-by-Design, Identity Traceability
What's in the full article
PlainID's full article covers the operational detail this post intentionally leaves for the source:
- How the platform frames identity-aware authorization across prompts, MCP tools, APIs, and response handling
- The vendor's implementation-oriented explanation of security by design for agentic AI workflows
- The stated runtime authorization and traceability model for enterprises managing human and AI identities at scale
- The article's discussion of 35M+ managed identities and 99.99% uptime as part of its platform context
👉 Read PlainID's analysis of agentic identity security by design and access control →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 7 days ago by NHI Mgmt Group
25/06/2026 5:32 am
Security by design becomes the governing model once agents can act independently. Traditional IAM assumes an access request can be reviewed before a human or workload proceeds. Agentic systems collapse that assumption because decision and execution can happen inside the same runtime loop, so governance has to move from periodic review to enforced authorization at action time.
A few things that frame the scale:
- The agentic AI market is already worth $5 billion and is projected to reach $50 billion by 2030.
A question worth separating out:
Q: What is the difference between least privilege for humans and least privilege for AI agents?
A: Human least privilege usually maps to a job role, while AI-agent least privilege must map to a task, a time window, and a specific allowed action. Agents often combine planning and execution in one workflow, so broad roles are too loose. The practical standard is short-lived, operation-specific access with a clear stop condition.
👉 Read our full editorial: Agentic identity security by design is becoming the access control test