Next upHack for Humanity: San Francisco (powered by Google Gemini)
Tech Talks · 1:05:16

Securing Code You Didn't Write: The AI Era's New Threat Model

Coding agents expand the software supply chain to include repositories, configuration, comments, connectors, and tool output. Rome Thorstenson examines reported attacks and outlines practical controls for permissions, secrets, prompt injection, and defense in depth.

Rome Thorstenson
Rome Thorstenson
Sep 17, 2026
Summary

The security boundary changes when a coding agent can read untrusted material and act with developer privileges. Rome Thorstenson maps that path across repositories, configuration files, comments, connectors, plugins, and MCP tools, using reported incidents to show how instructions can cross into execution. His practical guidance centers on reducing what an agent can read and do, keeping credentials out of chat and behind purpose-built tools, and applying defense in depth. Security feedback should also move into design, implementation, and QA rather than waiting for a final review or dependency audit.