Skip to content
nulltapE-reader edition

← All e-reader articles

3 min read

CrowdStrike Adds a Gateway Kill Switch for AI Agents

Falcon Guardian customers can cut off an agent's model access through a gateway. Check which traffic reaches it before relying on the switch.

Read on the standard site

An AI-agent workstation faces a closed gateway shutter on its connection to a cloud model.

An AI agent with access to company files and tools can keep taking actions after a risky instruction. CrowdStrike announced a Falcon Guardian kill switch on November 3 that lets customers cut off an agent’s access to AI models at a centralized gateway. For teams running supported agents, the immediate question is which model calls actually travel through that gateway.

CrowdStrike describes the new intervention as a way to “rapidly cut off AI model access through centralized gateway enforcement.” Turning off a model connection interrupts further model-backed work along that route; an agent’s already-running processes and access to files deserve their own investigation.

Model access meets gateway policy

An agent can read a prompt, call a tool, start a process and touch a resource. Falcon Guardian’s available endpoint sensor records the processes, commands and resources an agent uses, while hooks for Claude Code, OpenAI Codex, GitHub Copilot, OpenCode and Cursor inspect supported agent interactions and can block malicious activity before execution, according to CrowdStrike. Agent Graph links the instruction to the resulting endpoint activity. A gateway operates at a different point: Falcon AI Gateway, which CrowdStrike also marks available now, centrally enforces policy for supported AI traffic, including environments without direct sensor coverage.

That makes the kill switch a control over model access through the gateway. It is useful when an agent is behaving dangerously and its next model call would extend the activity. Inspect the associated endpoint processes and affected resources as well: correlate the blocked model call with processes and resource changes from tools the agent already invoked. If the agent’s model traffic takes another route, route it through an enforced path or restrict that route under your existing egress policy before counting on the gateway action.

Current coverage and announced expansion

CrowdStrike marks the endpoint sensor, the supported agent hooks, Falcon AI Gateway and the kill switch available now. It labels Linux AI-specific discovery and detections for Claude Code and Codex, cloud-workload and Kubernetes agent coverage, the Claude Cowork virtual-machine integration, and macOS endpoint network inspection pre-beta. The announcement also describes forthcoming visibility into Amazon Bedrock AgentCore and pre-beta agent-insider-threat detection in Falcon Next-Gen SIEM. Plan today’s response around the controls deployed in your environment.

These controls act at different points. The agent hooks inspect instructions inside a supported agent; the endpoint sensor shows what ran on the host. A gateway sees supported model traffic and can cut off model access. Join those observations to trace an instruction through a model call and on to a file or process. CrowdStrike’s previously reported attempted agent file share concerns an observed customer action; this announcement concerns a new intervention and where it applies.

Exercise the model cutoff path

For a Falcon Guardian deployment, map each supported agent to its endpoint sensor coverage, hooks and model route. Put the intended model calls behind Falcon AI Gateway policy and identify any separate egress paths. Then use an approved, non-sensitive test agent to trigger the authorized gateway cutoff: inspect the gateway policy state and model-access result, and correlate the agent’s subsequent process and resource activity in endpoint telemetry. The expected result is blocked model access on the tested route; continued tool or file activity calls for separate containment.

Where Linux, Kubernetes, Cowork or managed-platform agents are part of the estate, record the current sensor and route inventory before treating announced pre-beta coverage as deployed.

Primary sources