Skip to content

AI Security

Attacking AI systems, and defending them.

AI security covers the ways AI systems get attacked — prompt injection, data poisoning, jailbreaks, model extraction — and the defenses against them, from guardrails and red teaming to keeping autonomous agents inside safe bounds.

An agent's input can come from someone other than its user. Greshake and colleagues studied indirect prompt injection, where attackers place instructions in material an LLM application retrieves, and demonstrated attacks on integrated applications (Greshake et al., Not what you've signed up for). For a builder, an external document or tool result deserves a different trust boundary from an authorized instruction. Test what happens when retrieved material asks the agent to disclose data or take an unrelated action.

Charles Guillemet in episode 65 argues for hardware-enforced controls when agents can move money. Dan Lorenc in episode 68 discusses the pressure AI-assisted attacks put on patching. Can you secure an AI agent with software? develops the first conversation, while AI agent identity and permissions covers access boundaries. The prompt injection definition is a useful starting point for the input attack itself.

Start here

  1. Time to Exploit is Negative: AI Broke the Patch Cycle | Dan Lorenc, Chainguard 3:42 in transcript

    Hear how cheap models turn known vulnerabilities into exploits in minutes, shrinking the window for patches.

  2. You Can't Secure an AI Agent with Software | Charles Guillemet, Ledger 9:24 in transcript

    Examine hardware-enforced signatures for an agent policy engine.

Go deeper

6 episodes

Explainers on this topic

Terms on this topic

Guests on this topic

DJ SampathDan LorencCharles GuillemetKris LovejoyJeetu PatelMalte Ubl