Agentic Development Security - Ezra Tanzer, Snyk

AI Engineer27m 33s
0 comments · 0 votesOpen discussionClose discussion
Sign in to join the discussion

    Video summary

    Ezra Tanzer and Dan Arpino describe three areas of agent security: code that agents generate, components they use and actions they take. Ezra Tanzer explains why prompt-based rules alone can be unreliable, then shows deterministic hooks that run scanning tools without placing every result in the agent's context.

    The discussion extends supply-chain review to MCP servers and agent skills. Runtime policies can redact sensitive information or block a command before it executes, rather than depending on an agent to remember a warning. Ezra Tanzer distinguishes these controls from constant human approval, particularly for unattended workflows.

    Dan Arpino demonstrates an experimental local monitoring application that traces agent activity, scans changes and enforces workspace policies. The presenters acknowledge practical limits, including false positives, immature workflows and the need to disable automatic remediation when it would undermine a vulnerability benchmark. The prototype illustrates visibility and bounded enforcement, not a promise of complete protection.

    Original YouTube thumbnailWatch on YouTube

    Share this page

    Ezra Tanzer in blue gestures while Dan Arpino in off-white listens beside the blue and white "AGENT GUARDRAILS" headline. Framed in blue with WWW.ARTIFICIAL-INTELLIGENCE.VIDEO, 20 July 2026 and duration 27m 33s.

    Agent security must cover generated code, connected components and runtime actions, using predictable triggers and policy enforcement while managing false positives and developer friction.