From Kill Chain to Kill Web: What the New Era of Air and Missile Defense Really Demands

Retired U.S. Air Force Brigadier General Matthew Isler has written a serious and well-grounded assessment of where integrated air and missile defense stands today and where it must go. Published in War on the Rocks on May 14, 2026, his piece, “The New Era of Air and Missile Defense”, deserves close reading by anyone thinking through the future of distributed, networked warfare.

More than that, it deserves to be placed in a broader analytical context, because what Isler describes as a structural failure of current defensive architecture is precisely what the kill web concept anticipated, and what recent combat, above all, Operation Epic Fury and the subsequent regional defense against Iranian retaliation, has now validated at operational scale.

Isler’s core argument is that modern air and missile defense has reached a structural limit. The model that worked over the past two decades remains effective within its original design envelope, but the threat has moved faster than the architecture. Ballistic missiles, cruise missiles, one-way attack drones, and loitering munitions are no longer niche tools. They are now routine instruments of coercion, employed in combinations designed to overwhelm decision-making, exhaust interceptor magazines, exploit the seam between sensors and shooters, and impose cost exchanges that favor the attacker over time. Coalition defenses in recent operations performed well tactically, Isler notes, while still revealing what he calls “strategic fragility.”

That framing is precise and analytically honest. But I would go further: what Isler identifies as implementation gaps are not merely technical shortfalls waiting to be corrected by better systems or more interoperable software. They reflect a deeper conceptual mismatch, the persistent reliance on a kill chain model in an environment that now demands a kill web.

The Kill Chain’s Structural Failure

The kill chain, as a conceptual model, treats targeting as a sequential process: detect, decide, act. Its logic is linear, and its effectiveness depends on that linear sequence remaining intact. When sensors feed shooters through a cleared, protected, predictable pathway, the model delivers results. But the moment adversaries begin designing attacks to disrupt that pathway. through saturation, deception, jamming, physical destruction of fixed nodes, or sheer mass. the kill chain’s linearity becomes its fatal weakness.

Isler describes exactly this dynamic, even if he does not use the kill chain framing explicitly. His four failure modes. magazine exhaustion, limited but consequential penetrations, insufficient integration for mass attacks, and cost asymmetry, are all downstream consequences of an architecture that still fights largely as a collection of individual systems linked by shared situational awareness rather than fire-control-level integration. Each interceptor, as he puts it, “depends on its own sensor and must establish its own track before it can engage.” The integration exists “at the display level rather than at the level required to execute an engagement.”

This is the kill chain problem in precise form. Systems share a picture. They do not share a targeting solution. And when the attack volume exceeds the capacity of individual systems operating in their own engagement envelopes, the picture is not enough.

The kill web concept, which Ed Timperlake and I developed over a decade of work with allied practitioners, addresses this directly. The kill web is not an architecture so much as a design principle: any sensor can cue any shooter, engagement authority can be distributed across the network, and the network itself, not any individual platform or node, is the fire-control system. Degrade one node, and the network reroutes. Exhaust one magazine, and the web shifts the engagement to an available shooter with a different interceptor or a different engagement layer entirely.

What Epic Fury Confirmed

Isler draws heavily on Operation Epic Fury and the subsequent defense against Iranian retaliation, and rightly so. These were not episodic raids. They were full-scale, sustained, multi-domain air and missile defense battles that exposed the current model’s limits at operational scale. Coalition defenses intercepted large volumes of threats and preserved critical infrastructure, a genuine tactical success. But the strategic picture was more complicated.

High-end interceptors were consumed at rates unsustainable in a prolonged campaign. Some attacks penetrated defenses and struck critical assets, including, according to published satellite imagery analysis, equipment at fifteen U.S. military sites across the region. And critically, the cost exchange initially favored Iran. It was only when U.S. and Israeli offensive operations degraded Iranian air defenses and reduced Iranian launch capacity that the defensive burden began to ease.

That sequence is analytically decisive. It confirms what the kill web framework has always insisted: purely defensive postures fail against adversaries who can scale attack volume at low cost. Defense becomes sustainable only when it is paired with offensive operations that reduce the salvo at its source. The same sensor network that supports defensive engagements must be able to cue time-sensitive targeting of mobile launchers, maintain custody through their relocation cycle, and pass targeting data fast enough for a strike before they can reposition. Defense and offense are not separate missions sharing a common picture. They are integrated functions of a single network fighting simultaneously across the defensive and offensive dimensions.

Isler frames this as the “strategic shift” in his argument, and it is the right framing. But the implication runs deeper than he states. It means that the command-and-control architecture for air and missile defense can no longer be designed around defensive intercept as the primary function with offensive action as an adjunct. The offensive-defensive integration must be designed in from the outset, with pre-delegated authorities, common data environments, and coalition interoperability built into the architecture before the first shot is fired.

The Hardest Problem Is Not Institutional: It Is Cultural

Isler acknowledges that the strongest counterargument to his vision is institutional and political rather than technical. Sovereign reluctance to share data, classification barriers, mismatched software baselines, and unclear command relationships have historically limited real integration even when partners share a common operational picture. He argues, persuasively, that phased federation is the practical path forward: start with warning and track sharing, build command relationships and delegated authorities through exercises, then expand toward battle-management and fire-control integration as policy permits.

This is correct as far as it goes. But my experience working with allied practitioners in the Pacific, in Europe, and in the Middle East over four decades suggests the deeper problem is cultural rather than institutional. Institutions can be reformed. Authorities can be pre-delegated. Software baselines can be aligned. What is harder to change is the mental model that commanders and procurement officials bring to the problem.

The kill chain model is not just an architecture. It is a cognitive habit. It inclines planners toward evaluating systems as standalone performers, toward organizing command relationships around individual service domains, and toward treating integration as a desirable add-on rather than the foundational design requirement. As long as that mental model persists, the best-designed kill web architecture will be implemented as a more sophisticated collection of individual systems connected by a better common operating picture which is to say, as an improved kill chain rather than a genuine kill web.

Isler’s formulation of the acquisition test is exactly right: “The central acquisition test is no longer whether a platform performs well on its own, but whether it integrates with and strengthens the resilience and depth of the larger defensive system fighting as a whole.” That test has to be applied not just to hardware procurement but to command arrangements, to exercise design, to training pipelines, and to the conceptual frameworks that general officers bring to planning. The cultural shift has to accompany the architectural one.

IBCS and the Coalition Integration Challenge

Isler discloses his commercial interest clearly: Northrop Grumman is the prime contractor for the Integrated Battle Command System, the U.S. Army program most closely aligned with the fire-control-level integration concepts he describes. That transparency is appropriate, and his argument is careful to be about the architectural requirement rather than any specific solution.

IBCS is important in this context for reasons that extend well beyond the U.S. Army. As a fire-control-level integration system that allows any sensor to cue any shooter across a network, it operationalizes key elements of what Isler calls Integrated Air Missile Defense 3.0 and what I would frame as kill web architecture applied to the ground-based air defense problem. The question of whether and how IBCS can be extended into coalition settings, what data it can share, at what classification levels, with which partners, under what pre-delegated engagement authorities, is not a technical footnote. It is the central operational question for allied integrated air and missile defense in the Pacific, in Europe, and in the Middle East.

The architecture has to be designed with coalition integration as a first-order requirement, not a follow-on activity. That means building releasability into the data model from the start, designing for user-defined access controls that can accommodate different national caveats, and exercising the command relationships and delegated authorities in peacetime so that transitions from defense to offense can happen at network speed when the campaign demands it.

The Larger Lesson

What Isler’s article ultimately describes, framed in the terms that our analytical work has used for years, is the transition from the kill chain to the kill web as an operational reality rather than a conceptual aspiration. Recent combat has validated the requirement. It has also shown the cost of moving too slowly.

The militaries that adapt first and design coalition integration into the architecture from the outset rather than as an afterthought will be the ones that can absorb and counter mass attacks without exhausting themselves in the process. The ones that do not adapt will find that even impressive tactical performance conceals a deepening strategic fragility.

That is not a prediction. It is an observation already confirmed in the operational record. The question now is how quickly the lessons translate into architecture, into acquisition, and into the cultural shift in military thinking that makes both sustainable.