Executive findings
From the 21 November 2026 landscape. Click a category card below to list its offers.
How to read the D3 views
Ports of the named Observable notebooks, bound to this report.
Capability bubbles — D3 pack (@d3/bubble-chart/2). Nested circles are categories; leaf area is the balanced score.
Edge bundling — radial cluster + curveBundle (@d3/hierarchical-edge-bundling/2). Hover: orange = outgoing depends-on; cyan = incoming dependents.
Timeline — (@tezzutezzu/world-history-timeline). Public first-release years; every bar ends at this snapshot.
Nested treemap — (@d3/nested-treemap). Click a leaf.
Sequences sunburst — (@kerryrodden/sequences-sunburst). Buying paths from the selection guidance, not live usage share.
Pie / chord / Sankey / force tree — Observable pie, chord, Sankey and force-directed tree. Chord is category-to-category import counts.
World Voronoi — (@d3/world-airports-voronoi) applied to public cloud-region cities that CNAPP/VM cloud modules assess.
Nested treemap — offer catalogue
D3 treemap. Click a leaf for the detail pane. Area follows the balanced score, not revenue share.
Sequences sunburst — buying paths
Kerry Rodden sequences sunburst. Percentages are share of mapped selection paths, not production traffic.
Pie — listed offers by category
Observable @d3/pie-chart/2. Counts of named offers in this snapshot, not revenue.
If the core is… you still import
Bill-of-materials check from the dependency chapter. A healthy architecture has one detection layer, optional aggregator, and a validation slice.
Compare listed cores
Side-by-side from the selection guidance. Click a row. This is a fit comparison, not a procurement ranking.
Categories in this report
Six scored archetypes (A–F) plus adjacent intel, ITSM, cloud APIs and BAS. Click a card.
Capability bubble chart
D3 pack layout (Observable @d3/bubble-chart/2). Outer circles are categories. Click a bubble to lock the detail pane. Area is the balanced 0–100 score, not market share.
Hierarchical edge bundling — dependency mapping
D3 cluster + curveBundle.beta(0.85) (Observable @d3/hierarchical-edge-bundling/2). Hover a leaf: orange = outgoing depends-on; cyan = incoming dependents.
Stack timeline
World-history timeline layout (Observable @tezzutezzu/world-history-timeline). Start years are public first-release or founding years used only for this view. Every bar ends at the 21 November 2026 snapshot.
Benchmark graphs
Index of native criterion sums (leader = 100), change vs leader, stacked mix, and a pie of balanced weighted scores for the top cluster. The analysis did not publish SKU revenue, so the pie is score mass, not dollars.
Index chart (leader = 100)
Native profile sums for the twenty scored offers, ordered by balanced rank.
Change versus leader (%)
Same profile sums as percent below Tenable.
Stacked mix — native capability contribution
Each bar is the 12-criterion 0–5 profile. Color is the criterion, not a quality rank.
Balanced score mass — top cluster
Weighted totals out of 100 for the eight highest balanced scores. Not revenue.
Compare and correlate — heatmaps
Top: twelve benchmark criteria 0–5. Middle: qualitative CTEM-layer coupling 1–5 (not Pearson). Bottom: detection coverage Full=5, Part=2, not offered=0 from the feature tables.
Benchmark capability heatmap
Section 6.2 balanced scores. Darker cyan is stronger. Aggregators score near 1 on scan breadth by design.
CTEM layer coupling heatmap
How stages tend to move together in real programmes. Diagonal is 5. Discovery couples tightly to prioritisation; validation is still weakly wired into VM platforms.
Detection coverage heatmap
Section 5.1: network, agent, agentless, containers, DAST, SCA, IaC, OT/IoT, EASM, CIS. Full=5, Part=2, dash=0.
Gap analysis
Holes against the CTEM reference model and cross-industry unmet needs. Bar length is decision impact (5 = structural). A gap is a design problem, not a claim that a product is unusable.
| Gap | Impact | Pattern | Business impact | Gate |
|---|
Dependency mapping
Canonical CTEM toolchain, force-directed tree (Observable @d3/force-directed-tree), chord (Observable @d3/chord-diagram) and Sankey (Observable @d3/sankey/2). Drag nodes in the tree.
Canonical CTEM toolchain
Public intel → collect → CMDB context → prioritise → ticket/patch → validate → SLA. Each layer is only as good as the layer beneath it.
Force-directed tree
Chord — category imports
How many named depends-on edges run from one category into another.
Sankey — CTEM delivery system
Layered flow. Link width is illustrative path weight from the landscape, not ticket volume.
| Edge | Needs | Failure | Proof | Related |
|---|
Distribution of cloud data centers by vendor
Equal-earth projection + Delaunay Voronoi in the spirit of Observable @d3/world-airports-voronoi. Points are public commercial-region city centroids for AWS, Azure, Google Cloud, Oracle and IBM — the hyperscalers that CNAPP and cloud VM modules actually assess. Cells show nearest listed region, not exclusive coverage, building counts, or power. Land silhouette is a coarse outline for orientation only.
Catalogue
Scored VM offers plus adjacent intel, ITSM, BAS and cloud-API nodes. Search across name, ticker and description.
| Short | Name | Category | Kind | Ticker | Era | Description |
|---|