Periodic Table
The software supply chain, laid out so position means something.
Twenty-five domains, 348 products, 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
16Runtime & Kubernetes Protection
24 shown
Can only verified, policy-compliant workloads run in our clusters, and would we detect a container behaving like an attacker within minutes?
Who maintains it
- Foundation7
- Community0
- Company17
Open Source
14 here
- Cil241Cilium2 capabilities
- Fal242Falco2 capabilities
- Ist243Istio3 capabilities
- Kc244Kata Containers2 capabilities
- Kub245KubeArmor3 capabilities
- Kube246Kubescape5 capabilities
- Kub2247Kubewarden2 capabilities
- Kyv248Kyverno4 capabilities
- Lin249Linkerd1 capabilities
- Og250OPA Gatekeeper2 capabilities
- Oc251OWASP Coraza2 capabilities
- Tet252Tetragon3 capabilities
- Gvi253gVisor1 capabilities
- Kb254kube-bench1 capabilities
Commercial
8 here
- Aw231AWS WAF3 capabilities
- Ap232Aqua Platform6 capabilities
- Cp233Contrast Protect2 capabilities
- Daa234Datadog App and API Protection3 capabilities
- Fng235Fastly Next-Gen WAF3 capabilities
- Rha236Red Hat Advanced Cluster Security for Kubernetes5 capabilities
- Ssec237Sysdig Secure7 capabilities
- Upw238Upwind4 capabilities
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 388 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.