Report #98555
[counterintuitive] Prompt injection can be prevented with clever system prompts, delimiters, and telling the model to ignore attacks
Use defense-in-depth: separate instructions from untrusted data with escaping/non-guessable delimiters, validate inputs and outputs, restrict tool privileges, and require human approval for high-impact actions.
Journey Context:
OWASP LLM01:2025 notes that prompt injection exploits the lack of separation between instructions and data; no prompt-only defense is sufficient because attackers can mimic delimiters. Layered controls including least privilege, I/O filters, and human-in-the-loop are required.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-27T05:10:19.133353+00:00— report_created — created