Building Secure Backend Services with AI Agents
summary
An engineer demonstrates that prompts alone fail and recommends containing agents in a docker sandbox with a restricted filesystem and command whitelist after an agent nearly rewrites the global Maven config, shows a staged workflow—brainstorm → plan → execute → council review—that spawns subagents for tasks, uses an LLM council (PCI expert, mean code reviewer, arbiter) for consensus, enforces a credential secret manager, and records session logs and chains of thought so audits can trace exactly why an agent tried to escape.
AI-written summary · about
chapters (10)
- 0:00Secure Services with AI Agents: Why Security Teams Are Excited (and Terrified)
- 0:44The “Helpful” Agent That Almost Rewrote My Machine
- 1:58Myth #1: You Can Prompt an Agent Into Being Safe
- 3:05Contain the Body: Build a Locked-Down Agent Playground
- 4:28Myth #2: AI Will Replace Security Review (Meet the LLM Council)
- 6:04End-to-End Feature Workflow: Brainstorm → Plan → Execute → Council Review
- 7:33Assume Failure: Audit Trails, Session Logs, and Debugging Agent Behavior
- 8:20Myth #3: This Is Too Hard—Start Small and Scale Up Safely
- 9:30Practical Checklist & Final Takeaways (No Secrets, Human-in-the-Loop, Cross-Validate)
- 11:07Closing: Don’t Fear the Great Escape + Thanks & Contact
related talks
22mBuilding Secure Services with AI Agents: Patterns From Real-World Engineering
40mHow To Tame Your Agents?
01h 03mBuilding Secure Infrastructure for Productive AI Agents
19mBuilding Secure Services with AI Agents: Practical Patterns
45mYour AI Agent Has Production Access: Now What? (Jack)
39mBuilding Safe AI Agents
24mAI Governance for developers: A practical framework for deploying autonomous coding agents safely…
20mBuilding intelligent, secure, and scalable autonomous systems