Software Securityhome
Fix a findingSearch
Tag

Prompt injection

7 guides tagged Prompt injection, grouped by topic, with the SDLC phase and role each is written for.

SDLC phases
Roles

Application security

1 guide

AI security

6 guides
Guide · AI security

Contain prompt injection at the application boundary

Assume retrieved content can influence model output; enforce data access and consequential actions in components the model cannot authorize for itself.

Design, Development · Developers, AppSec engineers, Platform engineers and SREs

Guide · AI security

Red-team LLM applications and agents by their effects

A red-teaming method for LLM features and agents: scope the whole system, map attacks to OWASP and MITRE ATLAS identifiers, score trials from observed effects, report rates with confidence intervals and retest on every model or provider change.

Design, Testing, Security program · Developers, AppSec engineers, Platform engineers and SREs

Guide · AI security

Constrain MCP and multi-agent trust boundaries

Validate each connection and delegated action without treating a token for another service, a tool description, another agent or a state handle as authority.

Design, Development · Developers

Guide · AI security

Secure AI-assisted development with coding assistants and agents

Treat generated code, suggested packages, repository text and MCP servers as untrusted inputs, and confine coding agents with OS-level isolation and short-lived, narrowly scoped credentials.

Design, Development · Developers, AppSec engineers

Guide · AI security

Keep secrets and controls out of hidden context (OWASP LLM08:2026)

OWASP LLM08:2026 Hidden Context Exposure, which replaced System Prompt Leakage: why system prompts, tool schemas and retrieved policy text get extracted, what must never be in them, and how to enforce rules where a leak changes nothing.

Design, Development · Developers, AppSec engineers

Guide · AI security

Defend agent memory and context against poisoning (OWASP ASI06)

OWASP ASI06 Memory & Context Poisoning: how an instruction or false fact saved once in agent memory, conversation summaries or a retrieval store steers later sessions, users and agents, and the write, scope, provenance, expiry and recovery controls that contain it.

Design, Development · Developers, AppSec engineers

All tags, lifecycle stages and roles

Find your next answer

Type to search. Search runs in your browser.

Searches run in your browser, but the host can infer them from the index files they load. The address shows your search so you can bookmark or share it.