Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

As organizations deploy increasingly autonomous and interconnected agents, the potential agentic blast radius grows. A single compromised or misaligned agent can trigger a chain of actions spanning credentials, applications, files, and enterprise systems that create consequences extending far beyond its original task. Traditional security approaches weren't designed to understand these behaviors, much less intervene at the speed agents operate. Security teams need more than alerts and investigations.

I am delighted to announce CrowdStrike’s intent to acquire Fiddler at Fal.Con EU 2026. Fiddler, a leader in AI observability, will help ensure enterprise AI agents act as intended with pre-deployment evaluation and continuous behavioral monitoring as part of the CrowdStrike Falcon platform. Every business deploying AI agents asks the same questions: What are our agents doing? Are they staying on task? Are they acting in a way that could put the business at risk?

When Claude Cowork executes code locally, it runs inside an isolated virtual machine on the user's computer. On the host, that VM runs as a single opaque process: The agent's activity inside the VM, including the processes it spawns, the packages it installs, and the network connections it makes, is not visible to the host's endpoint security sensor. Because host folders can be mounted into the VM, sensitive data can sit within the agent's reach.

Every security team is being told to adopt AI. Far fewer have been shown what "good" looks like in practice. Turnkey agents handle common, well-defined security tasks, but no two security teams operate the same way. Each has its own data, playbooks, escalation paths, and risk tolerances; unique context that no vendor can anticipate in a packaged solution.