Different levels of abstraction
A kill chain can describe doctrine, a concrete technical mission thread, or an analytical sequence used to locate delays and failure points. A kill web describes the wider architecture from which multiple such threads can be formed.
Neither term automatically determines how centralized the organization is. A self-contained platform can execute a chain with delegated authority; a nominally distributed web can still bottleneck at one cloud, gateway, identity service, or approval node.
Structural comparison
| Dimension | Kill chain | Kill web |
|---|---|---|
| Primary question | Can the planned sequence complete? | Which permissible combination now offers the best mission outcome? |
| Topology | Predominantly ordered and bounded | Branching graph of alternatives and substitutions |
| Pairing | Often planned in advance | Selected or changed as state and constraints change |
| Failure response | Repair, use a rehearsed alternate, or abort | Reroute, substitute, redistribute, or degrade gracefully |
| Data model | Point-to-point may be sufficient | Shared semantics, provenance, interfaces, and mediation are foundational |
| Authority | Usually clear within one defined thread | Must remain explicit across organizations and alternatives |
| Testing | Finite known configurations | Large and partly emergent combination space |
| Principal risk | Critical-link failure and serial delay | Common-mode failure, bad-data propagation, orchestration error, and complexity |
| Measure of merit | Performance of the assigned path | Mission continuity across disruption and recomposition |
When a simple chain is better
Not every mission benefits from dynamic composition. A mature, rehearsed, self-contained chain can be faster, easier to certify, easier to secure, and easier to audit than a broad web. The correct design goal is not maximum connectivity; it is enough independent, trusted, governable pathways to survive the expected disruption.
KillWebs.com therefore treats the chain as an essential execution and accountability unit rather than an obsolete artifact.
How the two sites fit together
KillChains.com
Explains selected sequences, their stages, evidence, interruption points, automation, and control.
KillWebs.com
Explains how multiple sequences can be composed, compared, degraded, and recomposed without confusing reachability with authority.
Research basis: KW-RPT-002, KW-RPT-013, and KW-RPT-014.