Periodic Table
The software supply chain, laid out so position means something.
Twenty-five domains, 236 controls, laid out in the order the chain runs. Open one to see its controls arranged by the program maturity each demands, how much of the modeled threat it closes, and who actually sells it.
Table
← All 25 domains
20Detection & Response
13 of 17 shown
If a dependency, action or maintainer account we rely on were compromised tonight, how quickly would we know, and have we rehearsed exactly what to do?
Attacks counteredlow to high
- Counters none9
- Counters 1–20
- Counters 3–53
- Counters 6+1
- Table stakes1
Level 2
3 here
Level 3
9 here
- Epa187Engineering Platform Audit Log Monitoring5 attacks countered
- Ede188Extended Detection & Response Correlation3 attacks countered
- Mdr189Managed Detection & Response0 attacks countered
- Rtt190Real-time Threat Detection6 attacks countered
- Riv191Regulatory Incident & Vulnerability Reporting0 attacks countered
- Soa192Security Orchestration & Automated Response0 attacks countered
- Sci193Supply Chain Incident Response4 attacks countered
- Tep194Tabletop Exercise Program0 attacks countered
- Tii195Threat Intelligence Integration0 attacks countered
How this was produced
Every figure above was read from the Gantry knowledge graph, version 7.1.0, and computed when you opened this page — in 303 ms on 2026-10-27. Nothing here is a cached verdict or a dataset assembled for marketing: it is the same model our engagements run on.