Security
FocusSAST/SCA, dependency and secret-leak vulnerabilities; prompt injection and agent-specific attack surfaces; agent-assisted triage and remediation.
You buildA threat model, SAST / SCA / secret scans in CI, and a prompt-injection test
Core material≈ 3 h 50 min
- 1
- 2Agent-specific framing10 minThe lethal trifecta for AI agentsSimon Willison
And Prompt injection explained (talk with transcript, 15 min).
- 3Real exploit15 minGitHub Copilot: Remote Code Execution via Prompt Injection (CVE-2025-53773)Embrace The Red
A coding-agent attack chain end to end.
- 4Video45 minWhen AI Writes Code: Rethinking App SecurityIsaac Evans of Semgrep
AI-generated vulnerabilities, SAST, security assistants, feedback loops, and risks created by coding agents.
- 5Hands on20 minFinding vulnerabilities in modern web apps using Claude Code and OpenAI CodexSemgrep
Agent-assisted triage in practice.
- 6Coding-agent threat model14 minSafety and Security for Code-Executing AgentsFouad Matin of OpenAI
Remote code execution, prompt injection, exfiltration, containers, network restrictions, approvals, and OS-level sandboxing.
- 7Hands-on labsWeb Security AcademyPortSwigger
Do the Web LLM attacks labs, including indirect prompt injection (≈ 60 min for two labs).
Tools and references
- LinkSemgrepSAST
And CodeQL. Secrets: gitleaks. Dependencies/SCA: OSV-Scanner. Run all three classes in the build.
- LinkMaking Claude Code more secure and autonomous with sandboxingAnthropic
And the claude-code-security-review GitHub Action.
- LinkMCP Tool PoisoningOWASP
And the original Invariant Labs disclosure, MCP Security Notification: Tool Poisoning Attacks.
Additional video track
- Practical sandboxing38 minWhy and How You Need to Sandbox AI-Generated CodeCloudflare's Harshil Agrawal
Capabilities, secrets, networking, cleanup, isolation surfaces, and indirect prompt injection.
Book
- LinkThreat Modeling: Designing for SecurityAdam Shostack
Use the first edition; the second edition, retitled for an AI world, is announced for February 2027.
Build
Threat-model the entire agent workflow: user input, repository content, retrieved web pages, tools, credentials, MCP servers, generated commands, logs, and deployment. Apply least privilege, explicit allowlists, secret isolation, sandboxing, and human approval for irreversible actions.
Run SAST (Semgrep or CodeQL), dependency/SCA (OSV-Scanner), and secret scans (gitleaks) in CI. Plant a harmless indirect-prompt-injection string in an untrusted fixture and verify that the agent treats it as data rather than instructions. Write a short incident playbook for credential exposure, malicious tool output, and runaway cost.