Journey B · For a mature SME that already holds Essentials

You already passed the self-assessment. Now you need evidence over time.

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.

  • Plan horizon: about 90 days before Stage 2
  • Essentials is not an enforced prerequisite — but reuse is real
  • Three years validity, with annual surveillance

Why Trust is a different job

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.

Essentials

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.

Trust

Operate and demonstrate

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.

Trust, continued

Keep it alive

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.

And the scope grows. The traditional baseline does not disappear. A cloud service such as Microsoft 365 or AWS in your estate brings shared-responsibility questions with it, and optional technology pillars — cloud, operational technology, artificial intelligence — are added by explicit decision, with a reason and an owner recorded.

The tier ladder, honestly sized

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.

Supporter 13 statements
Practitioner 38 statements
Promoter 75 statements
Performer 131 statements
Advocate 189 statements

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.

What changes at Promoter, in practice

Not the theory — the artefacts you will suddenly be asked for.

Operating evidence, not policy

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.

Logging you can show

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, treated — not just known

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.

Cloud, decided explicitly

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.

Suppliers who can prove something

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.

People who can be named

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 90-day evidence plan

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.

Indicative 90-day evidence window · dates are relative to the start 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
Start the window before you start the paperwork. If your Stage 2 assessment is in April, the logging, backup and protection records that matter need to be running from January. Retrofitting evidence is the single most expensive mistake in this journey.

A worked example: Trisail Marine Supplies

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.

Colleagues reviewing a security plan together in an office
Trisail’s IT lead of two and an external assessor liaison ran the window together, fortnight by fortnight.

What nearly stalled it

  • MFA registration was being read as enforcement. 96% of accounts had a second factor registered, but no one could show what happened when a sign-in failed the check. Registration, policy and enforcement are three different facts.
  • The cloud decision had never been written down. Their Microsoft 365 tenant was in scope as a shared-responsibility service, and nobody could say who owned the tenant.
  • The evidence window had not started. They applied four months before the assessor needed three months of logs. The application date moved. That was the expensive one.

What the window produced

  • Three months of dated backup run records, and two successful restore tests.
  • A logging configuration record for every in-scope device and service.
  • A tenant inventory with owner, edition, licence count and admin count.
  • Their MSP’s assurance report, read for scope and period, with the assumptions written down.
  • A risk register where each treatment named an owner and a review date.
  • Two things still unknown, each with an owner and a request date — carried into Stage 1 openly.
“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

Reusing your Essentials evidence, honestly

Most of what you gathered for Essentials is still useful. The trap is assuming equivalence — and the honest answer differs row by row.

How Essentials artefacts carry across · reuse is a reviewed decision, never automatic
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.
Never let a shared artefact close two objectives automatically. Evidence can support more than one framework clause. The conclusion is always reviewed separately for each one, and unreviewed mappings earn no credit.

The scheme’s own rules, and where we stop

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.

The scheme’s thresholds

  • Supporter requires 100% Yes responses across the assessable statements.
  • Through the selected tier the workbook requires zero No responses, fewer than 20% N/A, and at least 80% Yes.
  • N/A needs a justification and validation by the certification body. A local note is not an official N/A.
  • One response per statement for the organisation, across the scoped technology pillars.

Where Security Passport stops

  • Our dashboard shows evidence coverage — never a certification probability.
  • We never count missing, stale or denied access as a pass, and we suppress a rate when the denominator is unknown.
  • We never write an official Yes, No or N/A into the scheme’s workbook.
  • We never display an issuer, scope, date or validity period we have not been given.
One more thing to be clear about. The tier your organisation ultimately reaches is determined by the certification body against the official risk assessment — not by a product recommendation and not by anything on our dashboard. A risk-informed suggestion we give you is advice about where to look, never a prediction of your outcome.

Questions a Trust applicant asks us

Do we have to hold Essentials first?

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.

How long does this actually take?

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.

Our evidence sits with our MSP. Does that disqualify us?

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.

Can you tell us we will pass?

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.

What does this cost?

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.

Start the window today, not at the deadline.

A scoping session that identifies the three artefacts most likely to stall your application — and who has to produce them.