About This Architecture

Prompt injection attack flow demonstrates how malicious user input can override system instructions in a single LLM context window without trust separation. The attack exploits the lack of boundary enforcement between system rules and user prompts, allowing attacker text to manipulate model behavior and leak confidential information. This architecture pattern highlights a critical vulnerability in naive LLM endpoint implementations that treat all input equally. Security teams can fork and customize this diagram to document threat models, design input validation strategies, and implement prompt isolation techniques. Defending against prompt injection requires explicit trust boundaries, input sanitization, and context window segmentation.

People also ask

How do prompt injection attacks work against LLM endpoints and what causes them to succeed?

Prompt injection attacks succeed when user input and system instructions share a single, unseparated context window. Without explicit trust boundaries, attacker text can override confidential system rules, causing the model to follow malicious instructions instead of original safeguards, resulting in leaked or manipulated replies.

Prompt Injection Attack Flow

Autointermediateprompt injectionLLM securityAI threat modelingsecurity architectureattack flowtrust boundaries
Domain: SecurityAudience: Security architects and AI/ML engineers designing LLM applications
5 views0 favoritesPublic

Created by

July 14, 2026

Updated

August 12, 2026 at 8:35 AM

Type

flowchart

Need a custom architecture diagram?

Describe your architecture in plain English and get a production-ready Draw.io diagram in seconds. Works for AWS, Azure, GCP, Kubernetes, and more.

Generate with AI

AI-generated. Verify before production use. Learn more

Report this diagram