Firewalling the AI Era: Why the Network Still Decides

AI is not just changing what runs on enterprise networks. It is changing who—or what—acts on them. Software is becoming autonomous. Agents authenticate, select models, discover tools, invoke APIs, retrieve data, modify systems and delegate work—often without a human approving each step, and increasingly without a human approving any of them. Consider a simple request: Fix the failing build. An AI coding agent might access a repository, consult a model, discover an MCP server, download dependencies, modify code and launch tests. One human instruction can become hundreds of machine-initiated interactions. To the network, these are separate connections. To the user, they are one task. To security, they are a chain of actions taken under delegated authority. The unit of risk is expanding from the session to the task. Identity is necessary. Authority is not enough. For decades, firewalls have asked: Who is communicating, with which application, to what destination, and should we allow the connection? Those questions remain essential. But they…