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

About the site

# Editorial policy

Read 18 Nov 2026

Every fact on this site has a source URL and a read date, and the read date for this edition is 18 Nov 2026. Scores were set blind on coded evidence, by criteria and weights fixed before any score existed. A claim made only by the platform itself scores at most 7 out of 10 until a second source confirms it. Where nothing was found, the site says none found on the date. Errors are corrected in the open.

## How are facts gathered and dated?

Each fact is read from a page and stored with the page address and the date read. For this edition that date is 18 Nov 2026. Scheme facts come first from NCSC, IASME, GOV.UK and the Ministry of Defence. Platform facts come from each platform's own pages, its documentation and its dated releases. Where an issuer's page and a platform's page disagree, the issuer's page wins and the platform's claim is labelled as its own.

Where two issuer sources differ, both are stated. The start date of Danzell is an example: IASME's download page says purchases from 27 April 2026, and an IASME article says accounts created after 26 April 2026. The site uses 27 April and notes the difference.

## How are absences written?

The site writes none found on 18 Nov 2026 where a page was read and held nothing on a point. It never writes that a platform does not have something, because a page we did not read may say otherwise. Review sites such as G2, Capterra and TrustRadius returned HTTP 403 on 18 Nov 2026, so review counts shown are the platforms' own quotes and score under the cap below.

## What is the vendor-only cap?

A claim published only by the platform itself, on its site, documentation, press releases or customer stories, scores at most 7 out of 10 on a criterion. The cap lifts only when a source the platform does not control confirms the claim and names the platform. A third-party page that does not name the platform confirms nothing. Pricing transparency is exempt, because there the platform's own publication is the thing measured. Breadth facts, such as integration counts, carry at most 10 per cent of any ranking.

## How are scores set and checked?

The criteria, weights and anchors were committed on 18 Nov 2026, before any score. Scorers saw coded evidence packs and were not told which platform any code was. A second round of blind review checked every score against its evidence and the cap. That review raised 3 scores (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. The [method](/method/) lists the sequence. Scores are published as they came out, whatever any platform's position.

## How are news items chosen?

News items come from primary sources: NCSC, IASME, GOV.UK and the Ministry of Defence, plus platforms' own dated releases that concern Cyber Essentials or UK buyers. Each item shows its source and whether it is a platform's own page. An item appears when it changes what a UK supplier should do, not because it is recent.

## How are corrections handled?

A score changes only when a sourced fact changes, and the change is logged with the fact. A factual error is fixed on the page, and the fix is recorded in the [corrections log](/corrections/) with its date. To report an error, write to editor@cyberessentialssoftware.com.

## Sources

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

Last reviewed 18 Nov 2026.

## Keep reading

- [Method](/method/)
- [Editorial policy](/editorial-policy/)
- [Corrections](/corrections/)
- [Platforms](/platforms/)
