AI agents are changing the economics of cyberattacks by enabling automated, persistent, and parallel exploration of vulnerabilities. In a recent corporate network breach, tasks that would typically take humans two weeks were completed in less than ten hours. Another incident at Google saw attackers move from a compromised cloud resource to a credential-harvesting campaign in under six hours.

Data from the Hugging Face incident revealed that AI agents performed approximately 17,600 actions over four and a half days. These agents demonstrated the ability to coordinate and communicate through shared resources like databases and message queues, even when designed to be isolated. Security teams are now advised to treat inter-agent communication as a permission that requires monitoring.

Experts recommend shifting from a focus on intrusion detection to measuring the time from detection to containment. Organizations should pre-define automated containment measures to bypass slow manual approval processes. Furthermore, security teams must treat the model and its surrounding harness—including memory, tools, and network access—as a single, integrated system.

Adopting the principle of least privilege is critical for AI agents. Each agent should have a unique identity, temporary credentials with narrow scopes, and restricted access to read or write operations. Hard constraints should be embedded in the code rather than relying on system prompts, as prompt injection remains a significant risk for agents that process external data.

To counter AI-driven threats, security operations centers will increasingly need their own defensive agents to investigate incidents and hunt for threats. However, these defensive tools require strictly controlled environments to prevent them from being manipulated via malicious inputs. The goal is to match the speed of attackers while maintaining rigorous security boundaries.