How to Secure Branch Networks Against Machine-Speed, AI-Driven Cyber Threats

Anthropic’s Mythos disclosure in April confirmed what network security teams had been bracing for. A frontier model, without cybersecurity-specific training, autonomously discovered and wrote working exploits for thousands of zero-day vulnerabilities, including 181 against a single browser. Most importantly, AI was now able to assemble existing, individually unremarkable vulnerabilities into a working attack chain.

That changed the meaning of the CVE backlog for network security teams. 

Firewalls, VPN concentrators, badge readers, OT controllers: each class of device has its own vendor, its own update process, and its own maintenance window. Some equipment cannot be patched at all — locked to vendor firmware, or running years beyond end of support. So teams triage by severity, fix what they consider critical, and let the rest pile up in the backlog. 

That way of triaging worked for as long as chaining those CVEs together required a skilled human attacker with plenty of time and patience. Mythos ended that era. The backlog has become the raw material of AI-composed attack chains that can assemble faster than a team can schedule a change window.

The Cloud Security Alliance (CSA) has responded to this AI-based threat with their recommendations for getting "Mythos Ready", highlighting eleven priority actions. Most revolve around building the security program: governance, rebuilt risk models, a permanent VulnOps function. But several are about architecture, and those land squarely on the infrastructure that network security teams run every day: the edge devices, the site-to-site mesh, the branch inspection stack, and the change process. 

When the branch is built like a café, with every site connected to the internet and all connections proxied through the cloud-based Zscaler Zero Trust Exchange,  AI attacks chains suddenly stop cold. There’s no attack surface to explore, and there’s no way  for malware to move laterally.  That model, built on Zero Trust principles, delivers on the architectural actions the CSA calls for. We can condense these into four core tenets:

• Hide,
• Contain,
• Inspect, and
• Respond.

Hide: Remove the Chain’s Starting Point

By nature, legacy networks are inherently exposed to AI-based attack chains. Every branch firewall, VPN concentrator, and SD-WAN appliance with a public IP sits in scanning databases anyone can query, announcing what it is and what version it runs. That identifying detail (vendor, model, and software version) is the device's fingerprint, and it tells an AI attacker exactly which CVEs your team has not fixed yet. The attacker then lines them up one by one, starting with whatever gets it in the door. The next flaw lets it read something it should not, and then a third raises its permissions. Each can be a moderate vulnerability that typically belongs in the backlog, but by exploiting them in sequence, the AI attacker can gain control of the appliance and spread from there.

What Zero Trust Branch changes: branch connectivity is outbound-only to the Zero Trust Exchange. No inbound listener, no DNS record resolving to the site, no port that answers a probe. A scan returns no fingerprint, and without one, the attacker has no starting point to build a chain from. All devices and their CVEs are hidden from public view, preventing an AI attacker from finding a foothold to start the chain from.

This directly aligns with CSA Priority Action #7 (Inventory and Reduce Attack Surface) by eliminating public reachability. Enforcing an outbound-only footprint also supports CSA Priority Action #4 (Prepare for Continuous Patching). When a device can be fingerprinted from the internet, every unpatched CVE on it is a race against an external attacker. When there is no fingerprint, your team patches on its own change window, not the attacker's timeline.

Contain: Collapse the Blast Radius the Chain Depends On

Hiding the branch denies an AI attacker a starting point from the internet, but compromise can arrive other ways: a contractor laptop, a vulnerable badge reader, or a poisoned update to a site controller. Once the attacker is inside, traditional network-centric segmentation works in its favor. With access managed based on network subnets, a site-to-site VPN mesh allows every branch to reach every other branch's address space, making the routing table a map for the AI attacker. One compromised device can open a path to every other site and the data center behind them, putting unpatched devices across the estate within reach. At each site, the attacker bypasses legacy network boundaries to enumerate local devices, including the cameras, badge readers, and OT controllers your team cannot patch, testing each one at machine speed.

What Zero Trust Branch changes: legacy network-centric segmentation is replaced with software-defined, agentless microsegmentation at the branch edge. The Zero Trust Exchange brokers every connection between users and devices to authorized applications. A compromise in one branch cannot spread to another location. Within the branch, agentless microsegmentation isolates every device into a software-defined "network of one" without requiring complex VLAN redesigns or endpoint agent installations. If an exposed IP camera is compromised, microsegmentation instantly collapses the blast radius—preventing lateral movement and leaving the attacker with nowhere to go.

This is the approach CSA Priority Action #8 (Harden Your Environment) calls for, using deep segmentation to limit how far an intrusion spreads once it lands. When each device is isolated, a compromise stays a single-device incident, and the equipment your team cannot patch no longer puts the rest of the estate at risk.

Inspect: See the Chain While It Is Still Being Assembled

Containment limits where an attacker can go, but they still have to communicate to finish the chain. The attacker reaches out to the internet, pulls down tools, and establishes command-and-control channels, producing traffic with each step. At most branches today, this traffic is inspected by the same local hardware appliance that routes it, and performing full SSL/TLS decryption is a heavy computational burden. When traffic spikes during a backup window or a video-heavy afternoon, the appliance runs out of CPU headroom. To keep the site working, sessions get exempted from decryption which quietly narrows inspection coverage, enabling the attacker's traffic to hide inside ordinary encrypted web sessions. This can persist for weeks inside a branch that falsely believes it is inspecting everything.

What Zero Trust Branch changes: inspection moves off the branch appliance and into the cloud-based Zero Trust Exchange. Every flow is inspected, whether it comes from a user or device, and is never scaled back when a site gets busy so attacker traffic cannot hide inside encrypted sessions. Because the Zero Trust Exchange also inspects traffic across thousands of organizations, a threat pattern detected at one branch is immediately shared and blocked across all of them. By forcing every outbound request through this global security fabric, you systematically dismantle the communication channels the attacker needs to complete their chain.

This is the other half of CSA Priority Action #8 (Harden Your Environment): egress filtering, which inspects traffic leaving the site to catch a chaining attack before it completes. When inspection is offloaded to the cloud, threat protection holds no matter how busy a site gets, allowing your team to disrupt the attack chain while it is still assembling.

Respond: Policy That Moves at Machine Speed

As inspection uncovers clear signs of an ongoing intrusion, response must take over immediately to stop the attack where it lies. Unfortunately, legacy response remains bottlenecked by manual, human-speed workflows—generating tickets, waiting for emergency change approvals, and logging into individual appliances. This operational latency is outmatched by autonomous, machine-speed AI threats, making every second of delay an open window for the attacker. That time gap is why an organization can have direct visibility into an attack and still be breached by it.

What Zero Trust Branch changes: an automated incident response loop eliminates human latency from the defensive path. Security teams pre-approve response playbooks in advance. A confirmed threat signal triggers immediate containment through the Ransomware Kill Switch, completely bypassing triage delays, change approval windows, and manual site-by-site logins. Also, microsegmentation automatically isolates the compromised asset from all other local devices and remote sites by default. By instantly collapsing the threat's blast radius to a single device, this surgical response merges detection and containment into a single, unified event and ensures branch operations continue uninterrupted.

This aligns with CSA Priority Action #10 (Build an Automated Response Capability) by enabling systemic, autonomous defense at the edge. When incident response relies on manual tickets and approvals, an AI adversary dictates the pace of the breach. By pre-authorizing automated response playbooks, you shift change control from a frantic, mid-incident scramble to a strategic, pre-built defensive move. Change control still happens, just before an incident rather than in the middle of one.

An AI-composed attack chain needs four things: somewhere to land, somewhere to go, somewhere to take cover, and time to work. Your backlog can't take those away. Your architecture can.

Zero Trust Branch Puts You in Control

Your team's ongoing triage of the backlog was the right move when chaining CVEs took a skilled human attacker acting at human speed. AI has removed that constraint, and patching faster is now a losing race against a machine. An outdated legacy architecture inherently opens you up to attack by providing the network pathways an adversary needs to build an exploit chain.

Zero Trust Branch neutralizes these chains through four tenets that work as a single cohesive set. Hide takes away somewhere to land. Contain takes away somewhere to go. Inspect takes away somewhere to take cover. Respond takes away time required to assemble. An attacker needs all four conditions to finish a chain, and losing even one disrupts their progress. Removing all four ensures that your CVE backlog no longer presents a systemic risk to your enterprise.

Connect with our experts for a tailored architectural walkthrough and see how Zscaler secures your distributed branch locations against autonomous AI threats.