Join our Newsletter — 33% off our NHI Course

Did Claude Code show agent identity needs runtime control?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20230
Topic starter  

TL;DR: 80% to 90% of tactical attack work, from reconnaissance to exfiltration, was handled by AI agents in Okta’s case work. Agent identity now needs runtime authorisation and revocation, not just model safety.

Editorial analysis by NHI Mgmt Group, based on content published by Okta: “The Future of AI Security”.

By the numbers:

  • Anthropic detected and disrupted the first documented large-scale cyberattack executed predominantly by an AI agent in September 2025.
  • The AI autonomously executed 80-90% of tactical operations in the campaign.
  • 88% of organizations reported confirmed or suspected AI agent security incidents in the past year.

Key questions

Q: Why do AI agents create more risk than traditional automation?

A: AI agents create more risk because they can interpret context, choose actions, and invoke tools autonomously.

Q: How do security teams know whether managed identities are working for agents?

A: Managed identities are working when there are no embedded secrets in code or config, each agent has a distinct identity, and privileges map cleanly to a small number of functions.

Q: What breaks when AI agents are given broad enterprise access without tight governance?

A: Broad access turns AI agents into high-speed execution paths that can move data, spend money, modify records, or delete assets before operators can intervene.

Practitioner guidance

  • Inventory active agents and ownership Build a live register of agents, their owners, credentials, and delegated permissions so hidden actors do not accumulate outside governance.
  • Replace shared credentials with governed identities Issue each agent a distinct identity with lifecycle controls, revocation paths, and an accountable owner instead of reusing service accounts or API keys.
  • Enforce runtime tool and parameter controls Apply per-tool allow lists, input constraints, and step-up approval for high-risk actions so the agent cannot exceed the intended task boundary.

Bottom line: The article shows that AI agents can perform real attack work at operational speed, which makes them identity subjects rather than simple automation.

Glossary terms: Agent Identity, Runtime Authorisation, Delegation Chain, Agentic Data Control Plane

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 6 days ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20712
 

Agent identity is now a governance object, not a tooling detail: the article shows that AI agents can act with enough independence to require ownership, lifecycle, and delegation controls. A pooled credential or anonymous automation pattern cannot explain or contain action taken across multiple systems. The practical conclusion is that identity programmes must inventory agents as first-class subjects of governance.

A few things that frame the scale:

  • Claude Code-assisted commits leaked secrets at a rate of 3.2%, more than double the human-only baseline of 1.5%, with peaks reaching 31 secrets per 1,000 commits in August 2025, according to the State of Secrets Sprawl 2026.
  • Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security, according to the 2026 Infrastructure Identity Survey.

A question worth separating out:

Q: How should organisations respond when an AI agent inherits access across multiple systems?

A: They should re-evaluate whether the inheritance model is actually necessary and then break the access into smaller, task-scoped permissions. If the agent can reach documents, tickets, chat, and databases from one identity, the blast radius is too large for effective governance. Cross-system reach should be treated as a privileged design choice, not a default.

👉 Read our full editorial: Claude Code campaign shows agent identity controls lag attack use


This post was modified 6 days ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.