How can organisations reduce risk from AI-assisted attacks on identities?

Why This Matters for Security Teams

AI-assisted attacks compress the time between discovery, abuse, and exfiltration, which means identity controls must absorb faster attacker iteration than many current programmes are built for. The practical risk is not just credential theft, but rapid chaining across accounts, tools, and privileges once a secret is exposed. In the NHI context, that makes short-lived access, narrow scope, and fast revocation more important than perimeter assumptions. NHIMG research on The 52 NHI breaches Report shows how often identity failures become breach multipliers, while Top 10 NHI Issues highlights the operational gaps that let secrets linger and privileges widen.

Current guidance suggests treating every exposed identity as a short-lived blast-radius problem, not a one-time authentication event. That aligns with broader direction in NIST Cybersecurity Framework 2.0 and with threat reporting such as Anthropic — first AI-orchestrated cyber espionage campaign report, which illustrates how AI can accelerate reconnaissance and task execution. In practice, many security teams encounter identity abuse only after an attacker has already used one secret to unlock several systems, rather than through intentional detection.

How It Works in Practice

Reducing risk starts with assuming the attacker will move quickly once any NHI or human credential is exposed. That means replacing long-lived secrets with JIT credentials, shrinking token TTLs, and enforcing least privilege at the workload level. For AI agents and automation, the better model is workload identity plus runtime policy evaluation: the system proves what the agent is, then decides what it may do based on the current task, context, and risk. This is more resilient than static RBAC alone, because autonomous behaviour is not reliably predictable in advance.

Operationally, teams should combine secret hygiene with identity containment:

• Issue ephemeral credentials per task and revoke them automatically on completion.
• Use PAM for high-risk actions, especially where agent tool access can change system state.
• Apply zero standing privilege so identities do not retain idle access between jobs.
• Evaluate requests at runtime with policy-as-code instead of relying only on pre-set roles.
• Monitor for rapid multi-stage behaviour such as enumeration, privilege escalation, and data movement.

For AI-specific threat context, MITRE ATLAS adversarial AI threat matrix helps teams reason about agent abuse patterns, while DeepSeek breach is a reminder that exposed secrets and exposed data often travel together. Where identity controls are weak, attackers can often reach usable access in minutes rather than hours, which is why speed of revocation matters as much as strength of authentication. These controls tend to break down in environments with shared service accounts, hard-coded secrets in pipelines, and sprawling tool integrations because the identity boundary is already blurred.

Common Variations and Edge Cases

Tighter identity control often increases operational overhead, requiring organisations to balance faster containment against workflow friction. That tradeoff is most visible in multi-agent systems, CI/CD automation, and vendor-integrated workloads, where overly strict controls can interrupt legitimate execution if the policy model is too coarse.

Best practice is evolving for autonomous systems, but the direction is clear: static IAM is usually too blunt when agents can adapt, chain tools, and retry actions at machine speed. In these cases, intent-based authorisation is more useful than role-only access because the decision can reflect the task being attempted, the data involved, and the trust level of the calling workload. The OWASP NHI Top 10 is a useful reference for agentic risks, and JetBrains GitHub plugin token exposure shows how quickly a single leaked token can become a wider identity incident. In practice, the hardest cases are long-running agents with broad toolchains, because their access needs change mid-task and static roles either overgrant or fail unexpectedly.

Where there is no universal standard yet, organisations should document the policy decision path: what the agent may request, which context is mandatory, how TTL is enforced, and what triggers immediate revocation. That approach fits the direction of CISA cyber threat advisories and keeps AI-assisted attacks from turning one compromised identity into a broad operational failure.

Related resources from NHI Mgmt Group

• How should teams reduce the risk of exposed AI credentials being abused?
• When do non-human identities pose the greatest risk to organizations?
• Why do non-human identities create more risk than many human accounts?
• Why do non-human identities create more remediation risk than many human accounts?