Skip to content

METHOD, read 13 Nov 2026

Weights fixed first, evidence second, scores last, each step dated

Download the weights (JSON)See the full index

The index answers one question: which tool shows a security team the AI agents on its machines and stops the ones that go wrong. The seven criteria below are what a buyer asking that question weighs, written down before any evidence was gathered, so a reader can agree or disagree with the weights before seeing a score.

Each tool is scored 0 to 10 on each criterion from its evidence file, a list of facts with a quote, a source URL and the date it was read. The weighted sum of the scores, divided by 10, is the total on a 0 to 100 scale. Ties break on the higher score on the heaviest criterion, then by name.

The criteria and their weights

CriterionWhat is scored, with evidenceWeight
Sees agentic activity on the endpointAn inventory of AI agents, skills, plugins, MCP servers and extensions across desktop apps, IDEs, command-line agents and browsers, as documented25
Stops the actionBlocking a harmful agent action before it completes, with the action types named, against detection or alerting after the fact25
Deployment frictionAgentless or light deployment, operating systems covered, time to deploy as published15
Beyond the endpointCoverage of browsers, cloud workspaces and SaaS-hosted agents in the same policy10
Policy and governanceThe policy model, the audit trail, and integrations with EDR, SIEM and the identity provider10
TransparencyPublic documentation, a published price, published research10
ProofNamed customers, funding, independent analyst coverage5

Weights fixed 12 Nov 2026 and committed before the first score. The committed file is published as weights.json.

What each score means

Score 0
none found on the read date
Score 1-3
mentioned, partial, or limited to one surface or one action type
Score 4-6
documented and working, with gaps the documentation shows
Score 7
the most a vendor claim or vendor documentation alone can earn: detailed, specific, covering the whole criterion
Score 8-10
detailed and confirmed by a second source (third-party write-up, or observed directly in public documentation, code or a release record)

The rules every score follows

  • Every vendor is scored 0 to 10 on every criterion, whole numbers, from the evidence file only, by a scorer given no brief about any vendor.
  • A vendor claim scores at most 7 until a second source confirms it (kind third-party or observed).
  • None found scores 0 and is written "none found on the read date", and is never written as a missing feature.
  • Breadth facts (module counts, integration counts, headcount, funding) carry at most 10 percent of any ranking; they inform Proof only, which weighs 5.
  • The total is the weighted sum of the scores divided by 10 (0 to 100 scale, published to one decimal).
  • Ties break on the higher score on the heaviest criterion, then by name.
  • Once the first score exists, no weight and no criterion changes. A score changes only when a sourced fact changes, logged with the fact.

How the tie-break reads the heaviest criterion: where two criteria share the top weight, as Sees and Stops do on the site weights at 25 each, the first listed (Sees) counts as the heaviest: ties on the site weights break on Sees, then by name, which is how the published ranking script applied it, so stating it changes no order. Each situation has a single heaviest criterion.

The five situations and their own weights

Each situation page ranks the same scores under weights a buyer in that situation would use. They were committed together with the site weights, before any vendor was scored.

SituationSeesStopsDeploymentBeyondPolicyTransparencyProof
Coding agents25351551055
Regulated data30155152555
Lean team with EDR30202551055
Staff rollout202015251055
Board in 30 days4053010555

Situation weights, each set summing to 100.

  • Coding agents: A coding agent with a shell can delete, exfiltrate or install in seconds, so stopping the action before it completes matters most, followed by seeing which agents, MCP servers and extensions each developer runs.
  • Regulated data: An auditor asks for the inventory and the evidence trail, so seeing every AI tool and keeping a policy record with an audit log outweigh how fast the tool installs.
  • Lean team with EDR: A small team needs the missing view quickly without another heavy agent to run, so visibility and low deployment friction carry the most weight.
  • Staff rollout: Staff-wide assistants and browser agents live in the browser and in SaaS as much as on the laptop, so coverage beyond the endpoint under one policy weighs most.
  • Board in 30 days: A 30-day inventory deadline rewards the widest view of agents on the most machines, deployed fastest; blocking can follow later.

Evidence pass of 12 Nov 2026 and the blind re-score

On 12 Nov 2026 a second evidence pass added facts for every vendor, and all 112 cells (16 tools, 7 criteria) were then re-scored blind from the updated evidence files under the same weights. 70 scores changed; each change is listed with the facts it now cites in the score change log (JSON: score-changes.json).

Re-scope of Palo Alto Networks, 12 Nov 2026: 13 facts about Cortex Agentic Endpoint Security, which is the Koi product, were moved to the Koi profile because Koi has its own profile. Palo Alto Networks was then re-scored blind against the other 15 vendors' reviewed scores, and its total moved from 58.0 to 44.0. The three rows for that re-scope are at the end of the score change log.

Evidence pass of 13 Nov 2026

On 13 Nov 2026 a further evidence pass ran one search plan for all 16 tools alike: the same news and analyst queries, the same source types and the same budget of 45 fetches per tool, aimed at second sources for scores at the 7-of-10 cap and for lower scores resting on vendor claims alone, anything published since the first read, and evidence against each current score. It added 134 facts from 78 new source pages, plus 35 records of a second source looked for and none found. The 87 cells those facts touched were re-scored blind and checked by a second blind reviewer under the same rubric and weights; 20 scores moved, 15 up and 5 down, and every other cell kept its score.

ToolCriterionBeforeAfterMoved by
Aim SecurityDeployment friction45aim-security-69
Aim SecurityPolicy and governance56aim-security-71
Aim SecuritySees agentic activity on the endpoint78aim-security-67; aim-security-66
Aim SecurityStops the action57aim-security-64; aim-security-65
BayProof98bay-57; bay-56
CrowdStrikeBeyond the endpoint76crowdstrike-52
Harmonic SecurityBeyond the endpoint87harmonic-security-53
IslandBeyond the endpoint78island-51
Koi (Cortex Agentic Endpoint Security)Deployment friction26koi-48; koi-49; koi-55
Koi (Cortex Agentic Endpoint Security)Policy and governance24koi-51; koi-56
Koi (Cortex Agentic Endpoint Security)Stops the action35koi-50; koi-54
LayerX (now Akamai Workforce Protector)Sees agentic activity on the endpoint45layerx-57
Noma SecurityBeyond the endpoint65noma-security-55
Noma SecurityDeployment friction76noma-security-52; noma-security-56
Palo Alto NetworksPolicy and governance45palo-alto-networks-57
Pillar SecurityPolicy and governance45pillar-security-47
SentinelOneBeyond the endpoint67sentinelone-57
SentinelOneDeployment friction45sentinelone-56
SentinelOneProof45sentinelone-59; sentinelone-60
WitnessAIDeployment friction45witnessai-58

Every score the 13 Nov 2026 pass moved. Fact ids are in the evidence dataset.

The Stops score and the Action Control Matrix measure different things: the matrix counts which of six action types a vendor documents, while the Stops score rates how specific and confirmed the blocking evidence is (action types named, blocking before completion, a second source), so a tool can document fewer action types and still score higher on Stops.

How the scoring was kept blind

Scoring was done from the evidence files by a scorer given the rubric and the files, with no brief about any vendor. The evidence for every vendor was gathered to the same template: the same six surfaces, the same six actions, the same questions on price, deployment and documentation.

The weights file was committed before the first score file existed and has not changed since. The build checks this from the git history, checks that every ranked view and head-to-head on the site matches the scores file, and fails if any of them differ.

The weights file carries the fixed date 12 Nov 2026. Scores are dated 13 Nov 2026. Download the weights file, the same file the build reads.

What the scores leave out

The index reads public sources: vendor documentation, release notes, press and analyst coverage, and public code. It does not test products in a lab, so a documented capability is a statement about what the vendor publishes and a missing one is a statement about what could be found.

Breadth facts such as headcount, funding and the number of integrations inform the Proof criterion only, which carries 5 of 100, and never more than 10 percent of any ranking.

Short answers to 30 common questions are on the FAQ page.

Changelog

  • 12 Nov 2026: the seven criteria, their weights and the five situation weightings fixed and committed before any evidence was gathered or any vendor scored.
  • 12 Nov 2026: blind scores for 16 tools, then an evidence pass and a blind re-score of every cell (70 scores changed, each in the score change log).
  • 12 Nov 2026: Palo Alto Networks re-scoped, with the Cortex Agentic Endpoint Security facts moved to the Koi profile, and re-scored blind.
  • 13 Nov 2026: a further evidence pass on one plan for all 16 tools; 20 scores moved.
  • 16 Nov 2026: a new design and the answer layer (question headings, who should pick what, what would change this ranking, the release log and the action finder). No weight, score, ranking, vendor or page address changed.

Sources

  1. Committed weights file, fixed 12 Nov 2026 (JSON), read 13 Nov 2026
  2. Evidence dataset, CSV, read 13 Nov 2026

Last reviewed 13 Nov 2026.