Every vendor gets a 0 to 5 score on seven criteria, each with a one-line reason. Totals are weighted averages computed from published weights, ties are shown as ties, and each head-to-head draws one tug-of-war bar per criterion. The scores are an editorial assessment of public vendor material, not the result of hands-on testing.
What does a tug-of-war bar show
Figure 1. Upwind is stronger on runtime by 0.9, so the marker sits well toward Upwind.
The left vendor is the first name in the page title. The marker starts at the center and moves toward the stronger vendor. A gap of 1.5 points or more pins it to the end. The label above the marker names the stronger vendor and the size of the gap. Under every bar are the two reasons behind the two scores, so you can disagree with a specific judgement rather than with a total.
Which seven criteria do we score
The seven criteria, their weights and what we look for.
Criterion
Weight
What we look for
Agentless coverage and time to value
18%
How much of the estate (VMs, containers, serverless, PaaS, AI services) is visible without installing anything, across how many clouds, and how fast.
How findings are correlated into exploitable paths and ranked, so teams fix the few things that matter.
Code-to-cloud and AppSec
14%
SCA, SAST, IaC, secrets and image scanning, and tracing a cloud risk back to the code and owner that caused it.
AI workload security
12%
Inventory and posture for models, AI services, pipelines, agents and MCP servers, plus runtime detection for AI-specific threats.
Ecosystem and integrations
12%
Integrations, partner and marketplace reach, platform breadth around the CNAPP, and market footprint.
Pricing transparency
10%
Whether a buyer can model cost from public material before talking to sales.
What do the numbers mean
What each score band means in this rubric.
Score
Meaning
4.5 to 5.0
Leading. A buyer comparing on this criterion would shortlist it.
4.0 to 4.4
Strong. Covers the criterion well with a named gap.
3.5 to 3.9
Adequate. Present, but narrower or tied to an add-on or another product.
2.0 to 3.4
Partial. Exists in limited form or only as a published unit without prices.
0 to 1.9
Minimal. For pricing, 1.5 means quote only.
How are totals and ties handled
Total = sum of (score x weight) / 100, computed in code from the data on the matrix page, never typed by hand. We sort by the exact value and show one decimal. When two displayed totals are equal we show a tie (for example, 3=). On a head-to-head, a criterion where both vendors have the same score is counted as tied and the marker sits at the center.
Where does the evidence come from
Vendor product pages, documentation, pricing pages and press releases, fetched and reviewed on 4 November 2026 for all nine vendors. Each comparison lists dated citations under the fact table; an older cloud-coverage statement retains its original source date. Vendor claims such as detection times, noise reduction percentages or customer counts are attributed to the vendor and are not our measurements. Where a vendor does not publish a detail, we write "Not established in this review" and score conservatively. A failed or missing page is not evidence that a feature does not exist.
November evidence review
All 63 criterion scores were reconsidered on 4 November 2026 using the same bands and the existing 18, 16, 18, 14, 12, 12 and 10 percent weights. These weights were not changed after reviewing the vendors. The bands guide editorial judgement; the rubric does not provide a measured capability-to-decimal formula, so a small score gap is not a measured performance difference.
Runtime reviews now consider documented sensor prevention and response rather than how recently a sensor was introduced. Code reviews distinguish native scanning from imported findings. AI posture is separate from prompt-layer runtime protection. Ecosystem scores consider documented connectors and technical workflows, not corporate relationships.
The buyer-situation picks apply fixed, separately published weight sets to the same scores and preserve ties. Compliance, small-team efficiency and rollout speed are not separately tested criteria: these picks are shortlists based on stated proxies, not certification or deployment guarantees.
What are the limitations
Limitations
Public sources only. We did not run the products, attend demos or interview vendors.
Marketing pages describe capabilities, not how well they work in a specific environment. Use these comparisons to decide what to test in a proof of concept, not as the result of one.
Scores are a snapshot. Vendors ship quickly; we re-review every vendor at least once a quarter and date every page.
Weights reflect a general multicloud buyer. A Kubernetes-heavy team would weight runtime higher; an Azure-only team would weight pricing and ecosystem differently.
How do I report an error
Contact us with the page, the claim and a public source. We check corrections within five business days and note material changes on the page.
Frequently asked questions
Are these scores based on testing?
No. They are an editorial assessment of public vendor material, reviewed in November 2026. We did not run the products.
Why are the weights not equal?
Buyers weigh coverage and prioritization more heavily than pricing when choosing a CNAPP, so those criteria carry 18% each and pricing transparency 10%. The weights are published so you can apply your own.
Why is the left vendor on the left?
It is the first vendor named in the page title. The order says nothing about which vendor is stronger.