Join our Newsletter — 33% off our NHI Course

Why do indirect prompt injections steer Agentic AI workflows?

 

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

TL;DR: Agentic AI widens the attack surface across tools, credentials, configuration, and memory, because autonomous workflows can be redirected by indirect prompt injection, credential theft, supply-chain tampering, and excessive permissions, says CyberArk. Autonomy now spans the full execution path, so permissions and output checks need to match the agent’s actual reach.

Editorial analysis by NHI Mgmt Group, based on content published by CyberArk: “Agents Under Attack: Threat Modeling Agentic AI”.

Key questions

Q: Why does indirect prompt injection create more risk than a malformed request in AI applications?

A: Indirect prompt injection is risky because the payload arrives as ordinary content, such as a support ticket, document, or code comment.

Q: How should security teams reduce the impact of credential theft in AI-assisted attacks?

A: Security teams should assume harvested credentials will be used quickly and at scale, then design for containment rather than recovery.

Q: What breaks when AI agents are given broad standing access?

A: Broad standing access breaks governance because the agent can move from one task to another without a fresh authorization check.

Practitioner guidance

  • Define separate control points for LLM, tools, config, and memory Inventory which layer can change decisions, which layer can execute actions, and which layer can persist context across runs.
  • Constrain agent permissions to the smallest workable scope Use tightly bounded credentials and repository rights so a compromised workflow cannot pivot into unrelated systems or higher-value codebases.
  • Validate model outputs before any side effect Do not allow raw model output to drive commits, API calls, branch creation, or escalation paths without deterministic checks.

Bottom line: Agentic AI expands the control problem from model behaviour to the full execution path, including tools, credentials, configuration, and memory.

Glossary terms: Agentic AI, Indirect Prompt Injection, Tool Access Scope, Persistent Memory

Explore further

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


This topic was modified 1 week ago by NHI Mgmt Group

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

Agentic AI changes the identity problem from access to action. The security boundary is no longer just who can authenticate, but what the system can decide to do after authentication. Once an LLM can trigger tools, the control plane must govern execution rights, not only login rights. The practitioner conclusion is that agentic systems need identity and workload governance together, not as separate programmes.

A few things that frame the scale:

A question worth separating out:

Q: What signals show that an agentic workflow is being manipulated?

A: Look for repeated review loops, unexpected tool calls, changes in repository selection, and output that contradicts the stated policy or task. Those are signs that context has overridden intended control flow and the agent is no longer behaving as designed.

👉 Read our full editorial: Agentic AI threat modeling exposes the real attack surface



   
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.