owasp/secure-agent-playbook

prompt-injection-test

Test LLM-integrated applications against known prompt injection techniques, evasion methods, and attack intents using the Arcanum PI Taxonomy.

Ver código fuente
Documento original del Skill

Contenido del repositorio de origen con títulos, ejemplos, código, tablas, enlaces e imágenes preservados.

Prompt Injection Testing

Systematically test an LLM application's prompt injection defenses by following the full procedure in plays/prompt-injection-testing.md.

Based on the Arcanum PI Taxonomy by Jason Haddix (Arcanum Information Security). CC BY 4.0.

Steps

  1. Scope and Input Surface Mapping — Identify all paths where attacker-controlled content reaches the LLM: direct (chat, API params) and indirect (file uploads, web fetches, RAG docs, tool outputs, MCP resources).
  1. Test by Attack Intent (13 intents) — For each authorized intent, attempt to achieve the attacker's goal:
  • INT-01 System Prompt Leak, INT-02 Jailbreak, INT-03 Tool Enumeration
  • INT-04 API Enumeration, INT-05 Get Prompt Secret, INT-06 Attack Users
  • INT-07 Data Poisoning, INT-08 Denial of Service, INT-09 Discuss Harm
  • INT-10 Multi-Chain Attacks, INT-11 Generate Image, INT-12 Test Bias
  • INT-13 Business Integrity
  1. Test by Attack Technique (18 techniques) — Apply known payload construction methods:
  • Framing, Narrative Smuggling, Cognitive Overload, Meta-Prompting
  • Russian Doll, Memory Exploitation, Act as Interpreter, Contradiction
  • End Sequences, Inversion, Rule Addition, Variable Expansion
  • Link Injection, Puzzling, Anti-Harm Coercion, ASCII/Spatial
  • Binary Streams, Spatial Byte Arrays
  1. Apply Evasion Layers (20 evasions) — When techniques are blocked, retry with obfuscation:
  • Encoding: base64, hex, morse, cipher, reverse
  • Language: alt language, fictional language, phonetic substitution, emoji
  • Structural: JSON/XML wrapping, markdown, metacharacter confusion, whitespace, splats
  • Advanced: steganography, link smuggling, graph nodes, waveforms, case changing
  1. Execute Test Matrix — Combine intents x techniques x evasions. Prioritize: high-impact intents first, indirect surfaces second, evasion sweeps against defenses that blocked direct attempts.
  1. Assess Results — For each successful injection, document: severity, attack path (intent + technique + evasion + surface), exact payload, detection gap, and remediation.
  1. Defense Validation — Check the 5-layer defense checklist: ecosystem hardening, model guardrails, prompt-layer defenses, data-layer controls, application-layer validation.

Output

Test results summary table (intent / technique / evasion / surface / result / severity), detailed findings using templates/finding.md, defense coverage checklist with gaps highlighted, and prioritized recommendations.

OWASP References

  • LLM01: Prompt Injection
  • LLM05: Improper Output Handling
  • LLM06: Excessive Agency
  • LLM07: System Prompt Leakage
del mismo repositorio

Más Skills

Todos los Skills
owasp
Comunidad

code-review-security

Security-focused code review mapped to OWASP Top 10 and ASVS. Use when reviewing pull requests, auditing files or modules for vulnerabilities, or performing pre-merge security gate checks. Covers injection, auth, authorization, cryptography, data exposure, misconfiguration, and deserialization.

instalaciones
1
GitHub Stars
184
Actualizado
25 sept
owasp
Comunidad

llm-risk-assess

Comprehensive LLM security assessment against OWASP Top 10 for LLM Applications 2025. Use when reviewing LLM-integrated applications, RAG pipelines, chatbots, AI agents, or GenAI features. Covers prompt injection, data poisoning, supply chain, excessive agency, and more with real-world attack scenarios and testing methodologies.

instalaciones
1
GitHub Stars
184
Actualizado
25 sept
owasp
Comunidad

prd-securability-enhancement

Enhance PRDs, feature specs, user stories, or product briefs with explicit OWASP ASVS coverage and FIASSE v1.0.4 SSEM implementation guidance — before code is written. Trigger on "harden the PRD/spec", "choose ASVS level", "map features to ASVS", "find missing security requirements", "add NFRs for security", "make these requirements securable", "security-review my product brief". For code review use securability-engineering-review; for code generation use securability-engineering.

instalaciones
1
GitHub Stars
184
Actualizado
25 sept
owasp
Comunidad

security-guidance

Security-first development guidance based on OWASP ASVS (Application Security Verification Standard). Use this skill automatically when planning or implementing any code that touches user input, authentication, data persistence, network communication, file I/O, cryptography, or access control. This skill ensures all generated code adheres to industry-standard security practices with explicit references to applied guidance.

instalaciones
2
GitHub Stars
184
Actualizado
25 sept