Essential Eight disruption map

Essential Eight disruption map

Which mitigation removes which phase of the chain, and how much of it. Read a row to see where a single control reaches; read a column to see what actually stands in front of one phase.

45%+25-44%under 25%
Essential Eight control01Recon02Res dev03Initial access04Execution05Persistence06Priv esc07Evasion08Cred access09Discovery10Lateral11Collection / C2Reach
Restrict admin privileges---8 ph · 2.40
Application control-----6 ph · 1.60
Patch operating systems------5 ph · 1.30
Multi-factor authentication-------4 ph · 1.20
Patch applications----------1 ph · 0.55
User application hardening--------3 ph · 0.45
Regular backups----------1 ph · 0.10
Restrict Office macros-----------0 ph · 0.00
Controls in play0043333323428 pairs

The number is the share of the phase the control removes when fully effective at ML2. Controls overlap, so the weights in one phase add to more than 100%. Phases 01 and 02 carry no control at all: the actor works on infrastructure you cannot see.

PHASE 04ExecutionApplication control
removes 55% of this phase
When the control holds

A strict allow-list with no path for unsigned or user-writable execution removes the script hosts and proxy binaries the actor leans on. Living-off-the-land still needs an interpreter that your policy permits.

Where it still leaks

Allow-listing signed binaries does not stop signed binaries. PowerShell, WMIC, mshta and ntdsutil are all approved by design, so the actor's execution blends into administrator activity.

T1059.001 PowerShellT1047 Windows Management InstrumentationT1218 System Binary Proxy ExecutionT1059.004 Unix Shell