In Part 1, we explored why traditional security models struggle with autonomous agents. As developers begin delegating more work to AI systems, a growing amount of activity happens outside familiar checkpoints such as repositories, CI/CD pipelines, and deployment environments. That naturally raises a new question: If governance needs to exist where agents actually execute work, what does that look like in practice?
Most organizations already have policies.
The challenge isn’t writing these rules. The challenge is enforcing them when software systems can increasingly take actions on their own. This is where a useful distinction emerges:
A prompt can influence behavior.
A runtime can restrict behavior.
