Article
LLM Prompt Injection: OWASP Boundary Failures and Controls
Start with a map of prompt-injection failure modes and the boundaries that need controls.
Investigate prompt injection, jailbreaks, trust boundaries, permissions, and data exposure across AI models, agents, and connected tools.
Choose a resource below, or browse all the content in this topic by type.
Article
Start with a map of prompt-injection failure modes and the boundaries that need controls.
Article
Review eight boundaries across an agent system, from incoming data to outgoing actions.
Guide
Apply the security guidance to private messages, connected apps, and agent actions.
Security analysis of connected apps, external tools, and remote MCP servers as capability, scope, approval, disclosure, and side-effect control surfaces.
Two vendor-agnostic control-plane failure patterns—privilege persistence across interaction boundaries and non-enforcing integrity signals—that allow untrusted state to steer tool execution across steps.
How multi-step orchestration (controller) loops change the threat model in tool-using systems, and where to enforce separation, authorization, validation, and budgets to reduce prompt injection, tool misuse, unsafe writes, and unbounded consumption.
How Gmail and WhatsApp content can steer tool-using AI agents, and how least privilege, explicit approval, provenance, memory controls, and audit logs reduce risk.
A forged message can turn a release review into an unauthorized deployment. Follow the handoff between AI agents to see why message verification and action authorization require separate checks.
Why LLM security begins at the integration layer: it turns model inputs and outputs into access to data, system actions, and persistent artifacts before an agent loop exists.
A sink-aware security model for validating, authorizing, encoding, and testing LLM output before it reaches browsers, databases, shells, code runtimes, tools, or privileged workflows.
An engineering guide to preventing authority confusion in prompt assembly by separating authoritative policy from untrusted content with typed provenance.
An architecture-level mapping of prompt-injection-related LLM application failure modes to OWASP LLM Top 10 and NIST AI risk-management categories.
Client-observed security report on text-only confirmations of privileged state or actions where the public article does not include signed backend audit artifacts. Backend state changes are not independently verified in this public report.
A reviewer-oriented threat model for request assembly in AI assistants: what enters context, what gets prioritized or dropped, and where policy, tool, memory, retrieval, and audit checkpoints should be reviewed.
A research-grounded analysis of how role-play may introduce a false safety premise that changes an LLM's interpretation of a restricted request.
Threat model of social engineering against AI decision pipelines; maps prompt injection to enforcement controls outside the model (PDP/PEP, validation, budgets).
A practical audit of eight trust boundaries where untrusted content can influence context assembly, planning, tool routing, write actions, and egress.
A threat model for browsing-enabled and tool-using LLM systems where retrieved web content can steer routing, tool arguments, follow-up calls, or side effects.
Reference diagram showing two common failures: chat-derived context influencing effective privileges, and model output persistence/replay into later context; highlights the server-side AuthZ + authoritative state invariant.
Reference diagram of a provenance boundary failure in prompt assembly, where untrusted input is misclassified as authoritative policy.
Summary schematic of the request-assembly boundary highlighting common failure modes: instruction injection, precedence confusion, truncation, provenance loss, and memory poisoning.
Reference schematic of prompt-injection risk in web tool access: routing manipulation and downstream failure modes (content-based instructions, source poisoning, query leakage, unbounded consumption, improper output handling).