Describe and verify
You describe what is in place; a certification body verifies the description against the scope you declared. A point in time is enough for most of it.
Journey B · For a mature SME that already holds Essentials
This page is for the organisation that holds Cyber Essentials, has a customer or a tender demanding Cyber Trust, and suspects that the gap is not knowledge but evidence: operating records, logs over a quarter, supplier artefacts, and scope decisions nobody has written down.
Cyber Essentials is largely a self-assessment plus independent desktop verification. Cyber Trust is a two-stage audit where the second stage looks at evidence of implementation and of effectiveness over a period. That single change removes the shortcut you are used to.
You describe what is in place; a certification body verifies the description against the scope you declared. A point in time is enough for most of it.
Stage 2 asks whether the controls actually work, using implementation data and logs — roughly three months of them — rather than a policy that says they should.
A Trust mark runs for three years with annual surveillance. Evidence that is collected once and never refreshed is evidence that will age out of the audit.
Cyber Trust has five tiers. The numbers below are the cumulative count of assessable statements in the current questionnaire, including the Cyber Essentials cross-references that carry over. They describe the workload — they are not a readiness score, and they are not a prediction of what you will achieve.
Cumulative through the selected tier, from the current Cyber Trust questionnaire. A separate logging check applies at Promoter but is not part of the assessable Promoter denominator, so it is tracked on its own rather than counted as a statement.
Not the theory — the artefacts you will suddenly be asked for.
The biggest change from Essentials
A policy saying backups run weekly stops being evidence. What satisfies the reviewer is a dated record showing they ran, plus a restore test showing they can be restored from.
You will need: three months of run records and at least one successful restore test.
Hardware and software logging enabled
At Promoter a separate logging requirement applies: logging must be enabled on the hardware and software in scope. It is not one of the assessable Promoter domains, so it does not change the denominator — but it has to be on, and it has to be demonstrable.
You will need: a configuration record per in-scope device or service, dated.
Risk assessment, treatment and declaration
Trust uses the official workbook for inherent risk, preparedness, residual risk, risk treatment and declaration. The catalogue of official risk scenarios runs to 54 entries; the scenario applies to you is yours to argue, with reasons recorded.
You will need: a risk register with owners, treatments and review dates.
Microsoft 365, AWS, and everything else hosted
A cloud service in your estate is in scope by default as a shared-responsibility arrangement. The optional cloud pillar is added by an explicit, documented decision — never by accident, and never in a way that erases your baseline obligations.
You will need: a tenant inventory with owner, edition, licence count and admin count.
MSP, cloud provider, software vendor
You can use a supplier’s own assurance report for the scope, period and assumptions it covers — and only for those. Your MSP’s SOC 2 report does not certify your use of the service.
You will need: the report, its scope and its period, with the assumptions read.
Ownership, joiners, movers, leavers
Trust expects roles to have owners and to be reviewed. For most mature SMEs the work here is not technical: it is naming the accountable role for each area and dating the last review.
You will need: a dated accountability list and one joiner-mover-leaver record.
The single most common reason a Trust application stalls is that the evidence window was not planned before anyone needed it. Three months of logs cannot be manufactured on the day the assessor asks. Here is the shape of the window.
| Window | What to gather | Who provides it | What it unlocks |
|---|---|---|---|
| Days 1–14 Scope |
Scope decision per system and site; confirmed obligations; an owner and a date per gap | Sponsor with the IT lead | A declared scope that does not change mid-audit |
| Days 1–21 Baselines |
Device inventory, tenant and licence counts, admin roster, MFA policy and registration, backup configuration | Your MSP or internal IT | The population every later measurement is divided by |
| Days 1–90 The window itself |
Backup run records, patch and protection status, logging configuration, access reviews, restore test | MSP and platform owners, continuously | Operating evidence with a date range — the part Stage 2 asks for |
| Days 30–60 Risk |
Inherent risk assessment, treatments, residual risk, exceptions with scope and expiry | Sponsor with the assessor liaison | A risk narrative that matches the evidence |
| Days 45–75 Suppliers |
MSP and supplier assurance reports, with scope, period and assumptions | Procurement and the suppliers themselves | Reusable third-party assurance, honestly scoped |
| Days 60–90 Rehearse |
Self-assessment against the official workbook, gaps closed, evidence pack assembled | Everyone, once | A calm Stage 1 submission instead of a scramble |
Composite example · not a real customer
74 staff, two sites, marine supplies, an in-house IT team of two, Cyber Essentials held since 2024 — and a new customer contract that names Cyber Trust Promoter.
“The Essentials certificate told us we had controls. The Trust window told us which controls were actually running, which was the question our new customer was really asking.”
— composite customer voice, written for this example
Most of what you gathered for Essentials is still useful. The trap is assuming equivalence — and the honest answer differs row by row.
| Essentials artefact | In Trust | What to do |
|---|---|---|
| Device inventory and endpoint protection records | Reusable with review | Confirm the population still matches, then bring it forward. Fresh records beat old ones. |
| MFA policy pages | Not sufficient alone | Policy shows what should happen. You also need registration and observed enforcement, separately. |
| Self-assessment responses | Reusable as a starting point | Re-read against the Trust workbook. The two schemes share some wording and not all of the meaning. |
| Backup configuration screenshot | Not sufficient alone | Configuration is not a run record, and a run record is not a restore test. |
| Policies and procedures | Reusable as design evidence | Policy, implementation and operating evidence are recorded as separate things. |
| Supplier questionnaires completed last year | Reusable with review | Check the date, the scope and whether anything material has changed since. |
These are the certification body’s rules, quoted from the scheme and its workbook. We prepare the evidence and the scope. We do not set the thresholds and we do not make the decision.
No. The scheme does not make Essentials a product-enforced prerequisite for Trust. In practice the material overlaps, and if you already hold Essentials much of that evidence is reusable — which is exactly why this page exists.
The evidence window is about three months, and it cannot be compressed because it is made of things that have to happen over time. Preparation around it — scope, inventory, risk register, supplier reports — runs in parallel and takes considerably less.
No. A hand-off to an MSP is a first-class route in this product. What matters is that the request is specific, the answer is dated and attributed, and the scope of the answer is recorded so that a supplier statement is never read as your own evidence.
No, and we will not pretend to. We can tell you honestly what is covered, what is missing, what is stale and what is unknown — and who owns each one. Whether you pass is the certification body’s decision, made against the scheme’s own workbook.
We will quote a fixed price for the engagement after the first conversation, once we know your size, your tenant count and how much of the evidence already exists. There is no subscription required to keep your own records and re-assess selected checks.
A scoping session that identifies the three artefacts most likely to stall your application — and who has to produce them.