Topic archive
54 essays tagged Agentsecurity. Practical notes on what happens after the demo: prompts, tools, review packets, evals, rollback, and production ownership.
Claude Code can ship useful patches quickly, but production agents also create authority, evidence, rollback, and audit questions. Teams need the delivery loop and the security loop together.
Before Claude Code becomes a team habit, security should ask about authority, boundaries, evidence, rollback, and ownership. These questions turn agentic coding from a demo into a reviewable operating model.
I published Securing Enterprise AI Agents, a practical book on bounded AI autonomy, AgentSecOps, MCP security, RAG governance, identity, evals, policy, and evidence.
AI agents are not just chatbots with a loop. For production teams, the useful definition is about delegated authority: what the system can see, decide, call, change, and prove afterward.