<!-- https://cyberessentialssoftware.com/method/ | read 18 Nov 2026 -->

Method

# How the platforms are scored

Weights committed 18 Nov 2026

Ten platforms are ranked for one buyer, a UK supplier of 10 to 250 people that needs Cyber Essentials, often Plus. Seven criteria carry weights of 25, 20, 15, 15, 10, 10 and 5, committed on 18 Nov 2026 at commit 9114c68a before any score existed. Scores were set blind on coded evidence, then reviewed blind. A claim made only by a platform scores at most 7 out of 10.

## What are the seven criteria and their weights?

The weights were committed on 18 Nov 2026 at git commit 9114c68a, before any vendor was scored, and have not changed since. Each criterion is scored from 0 to 10 in steps of 0.5; the total is the weighted mean on the same scale, published to two decimals.

| Criterion | Weight | What it measures |
| --- | --- | --- |
| [Guided route to the certificate](/method/guided/) | 25% | Named experts, a readiness review, and help with the certification body. |
| [Plus readiness](/method/plus/) | 20% | Device, patch, MFA and account evidence for the technical audit, and vulnerability scanning or testing. |
| [Reuse beyond Cyber Essentials](/method/reuse/) | 15% | IASME Cyber Assurance, ISO 27001 and SOC 2 on the same controls. |
| [Continuous monitoring of the five control themes](/method/monitoring/) | 15% | Monitoring of firewalls, secure configuration, user access, malware protection and security update management through integrations. |
| [AI that does the work under control](/method/ai/) | 10% | AI or an agent that drafts answers and policies and does compliance tasks, with review and approval before anything is used. |
| [Pricing transparency](/method/pricing/) | 10% | A published price, published plan contents, and what the certification or assessment itself costs. |
| [Proof](/method/proof/) | 5% | Customers and review counts as published. |

## What rules decide a score?

- A claim published only by the vendor itself (its site, documentation, press releases, customer stories it publishes) scores at most 7 of 10 on a criterion until a second source not controlled by the vendor confirms it. Pricing transparency is the exception: there the vendor's own publication is the thing measured.
- None found scores 0 for that element and is written 'none found on <date>', never 'does not have'.
- Breadth facts (integration counts, framework counts, module counts, headcount, funding) carry at most 10 percent of any ranking.
- Scores are given blind: the scorer sees coded vendors, the rubric and the evidence, and is not told which vendor any code is.
- Each criterion is scored on the evidence for this site's scheme where the anchor names the scheme; general platform evidence counts only where the anchor says so.
- No weight or criterion changes after the first score exists. A score changes only when a sourced fact changes, and the change is logged with the fact.
- Here the integration count is not scored; the five control themes are scored by coverage, not by count.

A vendor is ranked on this site only if its own pages show Cyber Essentials or Cyber Essentials Plus as supported. Every other profiled vendor is listed under the ranking as 'Cyber Essentials not supported on its pages, read 18 Nov 2026' (or 'listed only as partial'), with its score shown for reference and no rank.

## How do the five situations change the weights?

Each situation uses its own weights, written for the buyer in that situation and fixed before scoring. Same criteria, same scores, different weights.

| View | guided | plus | reuse | monitoring | ai | pricing | proof |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Main ranking | 25 | 20 | 15 | 15 | 10 | 10 | 5 |
| [A supplier whose contract, or Defence Cyber Certification, requires Cyber Essentials Plus](/situations/plus-for-a-contract/) | 25 | 35 | 5 | 15 | 5 | 10 | 5 |
| [A firm of 10 to 50 people that needs basic Cyber Essentials for a public-sector bid](/situations/first-certificate-for-a-bid/) | 35 | 5 | 5 | 10 | 10 | 30 | 5 |
| [A supplier that will add ISO 27001 or SOC 2 after Cyber Essentials](/situations/iso-27001-next/) | 20 | 10 | 35 | 15 | 10 | 5 | 5 |
| [A company of 100 to 250 people renewing every year across a growing device estate](/situations/renewals-across-a-growing-estate/) | 15 | 20 | 10 | 35 | 10 | 5 | 5 |
| [A small company with no in-house IT or security person](/situations/no-it-team/) | 40 | 15 | 5 | 10 | 15 | 10 | 5 |

## How is theme coverage read?

The control-theme count beside each platform is not a score. It shows, for each of the five control themes, whether the platform's own records name evidence for it. Direct means a named integration, agent or documented test for that theme; indirect means an adjacent integration or a general statement; none found means nothing on its pages on 18 Nov 2026. The rules are listed on [the controls page](/controls/). The route line is read separately, from the Route Sheet: [how its four stations are filled](/route-sheet/method/).

## How were the facts gathered?

### Who is the buyer?

The question the ranking answers is: which platform gets a UK supplier of 10 to 250 people to Cyber Essentials, and usually Cyber Essentials Plus, and keeps the certificate renewed? The buyer needs the certificate, often Plus, to win or keep a contract, and usually wants ISO 27001 or SOC 2 next. Five situation views re-weight the same scores for narrower cases.

### What are the seven criteria and their weights?

Each criterion is scored from 0 to 10 in steps of 0.5. The total is the weighted mean on the same scale, shown to two decimals. The weights were committed on 18 Nov 2026 at commit 9114c68a, before any score existed, and have not changed.

Guided route to the certificate, 25 per cent: named experts, a readiness review, and help with the Certification Body. Plus readiness, 20 per cent: device, patch, MFA and account evidence for the technical audit, and vulnerability scanning. Reuse beyond Cyber Essentials, 15 per cent: IASME Cyber Assurance, ISO 27001 and SOC 2 on the same controls. Continuous monitoring of the five control themes, 15 per cent: firewalls, secure configuration, user access, malware protection and security update management. AI that does the work under control, 10 per cent: agents and drafting, with review before use. Pricing transparency, 10 per cent: a published price, plan contents and what the certification itself costs. Proof, 5 per cent: named customers and review counts as published.

### Which platforms are ranked?

A platform is ranked only if its own pages show Cyber Essentials or Cyber Essentials Plus as supported. On 18 Nov 2026, ten of fourteen profiled platforms qualify. The other four are listed under the ranking as not supported on their pages, or listed only as partial, with their score shown for reference and no rank. Their profiles say so in the first sentence.

### What is the cap on vendor-only claims?

A claim that only the platform publishes scores at most 7 out of 10 on a criterion until a source the platform does not control confirms it. Pricing transparency is exempt. A missing element scores 0 and is written none found on the date. Breadth facts carry at most 10 per cent of any ranking. The five control themes are scored by coverage, not by integration count.

### What does blind scoring mean here?

Scorers received coded evidence packs, the rubric and the cap rule, and were not told which platform any code stood for. They scored each criterion element by element. A second reviewer, again blind, checked each score against its evidence and the cap, and checked the same evidence earned the same points for every code. The review made 3 score corrections, all upward (Delve monitoring 2 to 4, Secureframe guided route 1 to 3, Thoropass guided route 5 to 7), corrected 1 scheme status and fixed 16 evidence labels. A later blind consistency check of the pricing criterion lowered one more score: DataGuard's pricing transparency, from 8 to 4, because its only price figures are for a separate consulting service.

Final scores are published as they came out. No score was lifted or lowered to change a position.

### How are ties and situation views handled?

Ties print as joint, for example joint 3rd, and the next rank skips accordingly. The five situation views use their own weights, committed on the same day, for a supplier whose contract requires Plus, a firm of 10 to 50 people bidding for a public-sector contract, a supplier adding ISO 27001 or SOC 2, a company of 100 to 250 people renewing across a growing estate, and a small company with no IT person. A platform's rank can differ between views, and each view shows its weights.

### Changelog

18 Nov 2026: first edition. Weights and criteria committed at commit 9114c68a. Blind scores and blind review completed and published. Read date for all facts: 18 Nov 2026.

18 Nov 2026: pricing consistency check, DataGuard 8 to 4. Elements (a) and (b) count only a price for the platform or a scheme package being ranked, because the only figures found were for a separate consulting service.

## What has changed since the scores were published?

Nothing has changed in the weights, criteria or anchors since they were committed (the pricing reading for a price that belongs to a different product was clarified on 18 Nov 2026 and is printed on the pricing criterion page). Scores were given blind on coded packs, then checked by a second blind review before publication; a score changes only when a sourced fact changes, and that change is logged here with the fact.

- 18 Nov 2026: first publication. All 14 platforms scored on seven criteria and five situations.

## Sources

- [NCSC: Cyber Essentials overview](https://www.ncsc.gov.uk/cyberessentials/overview) ncsc.gov.uk/cyberessentials/overview, read 18 Nov 2026
- [IASME: Cyber Essentials](https://iasme.co.uk/cyber-essentials/) iasme.co.uk/cyber-essentials/, read 18 Nov 2026

Last reviewed 18 Nov 2026.

## Keep reading

- [Guided route to the certificate: all scores and reasons](/method/guided/)
- [Plus readiness: all scores and reasons](/method/plus/)
- [Reuse beyond Cyber Essentials: all scores and reasons](/method/reuse/)
- [Platform profiles](/platforms/)
- [The five situations](/situations/)
- [Route Sheet field definitions](/route-sheet/method/)
- [How the Danzell Change Log is built](/danzell-change-log/method/)
