Start hereVerify contract and boundary
~63 days leftOpen step
Guide library
Certification Europe

Cyber Essentials

UK Cyber Essentials and Cyber Essentials Plus

Demonstrate five baseline technical controls and decide whether independent testing is needed.

Who it applies to

Organizations seeking a UK government-backed baseline, including suppliers whose contract specifies Cyber Essentials.

What you’ll produce

Cyber Essentials certificate or Cyber Essentials Plus certificate for the assessed scope.

Plus adds technical verification. Use the version of the requirements and questionnaire applicable to the assessment date.

Check the published assessment fees
TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

Which certificate and scope will the customer accept?
Get the contract wording and determine whether Cyber Essentials or Cyber Essentials Plus is expected. Check if the customer permits any scoped subset and arrange the required assessment route.
What can we replace or remove before assessment?
Have IT identify unsupported devices, operating systems or applications. Budget for upgrades, access changes, endpoint management and Plus testing if needed.
Who owns changes after certification?
Name a person to approve scope and responses, one who operates IT controls, and a backup to track renewal and changes.

How to spend the first week

  1. Bring the contract and inventory of internet-connected devices, servers, user access and SaaS. Include remote staff and relevant personally owned devices.
  2. Compare the inventory with the current requirements and questionnaire for your assessment date. Record unsupported software, gaps in MFA and exceptions needing clarification.
  3. Book the applicable assessment and give each fix an owner, due date and test. Put renewal on the operating calendar.

What to review each week

Track unsupported in-scope software, users or services with missing required MFA, outstanding assessment issues and the renewal date.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

Cyber Essentials kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Verify contract and boundary · IT lead + procurement [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Bring the contract and inventory of internet-connected devices, servers, user access and SaaS. Include remote staff and relevant personally owned devices.
2. Compare the inventory with the current requirements and questionnaire for your assessment date. Record unsupported software, gaps in MFA and exceptions needing clarification.
3. Book the applicable assessment and give each fix an owner, due date and test. Put renewal on the operating calendar.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
The whole journeyabout 63 days across 4 steps
  1. 01Verify contract and boundaryIT lead + procurement · ~7 days
  2. 02Implement the five baseline controlsIT operations · ~21 days
  3. 03Submit assessment and arrange Plus if neededSenior signatory + assessor · ~21 days
  4. 04Renew and keep controls operatingIT lead · ~14 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 10 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Verify contract and boundaryIT lead + procurementBefore purchaseSet a start dateContract requirement; Device and service inventoryOpen
Implement the five baseline controlsIT operationsBefore submissionSet a start dateBaseline configurations; Access review; Update evidenceOpen
Submit assessment and arrange Plus if neededSenior signatory + assessorOn the scheme’s current scheduleSet a start dateSigned questionnaire; Testing evidence; CertificateOpen
Renew and keep controls operatingIT leadEvery 12 monthsSet a start dateRenewal calendar; Change inventoryOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Verify contract and boundary

    Who IT lead + procurement When Before purchase

    Confirm the required certificate level and identify devices, cloud services, internet gateways and exclusions.

    How to do this step

    Before you start

    Customer requirement, company scope, IT asset inventory, cloud service list and current scheme materials.

    1. List devices, cloud services and networks used to perform the covered work. Include unmanaged or remote endpoints where relevant.
    2. Document each proposed exclusion and how it is made technically distinct. Ask the assessor about ambiguous cases before answering the questionnaire.
    3. Check that the proposed scope and certificate level satisfy the contract, then confirm the current requirements version.

    What a reviewer should see

    The approved scope identifies company devices, permitted remote access and included cloud services. Each exclusion has a named reason and supporting evidence.

    When to escalate

    Raise a customer requirement for full-company coverage if the proposed application leaves out a business unit or service.

    What to produce

    Contract requirementMemo

    Gather first

    • Current agreement and service description
    • Applicable flow-down terms or engagement requirements
    • Contract owner and legal review

    How to prepare it

    1. Make a clause-by-clause worksheet. Quote only what you need to identify the current clause, and record each required subject and unresolved question.
    2. Mark where scope, instructions, evidence, security, subprocessors, incident notice, audit rights or termination affect the work. Route proposed wording to authorized reviewers.
    3. Record the signed or agreed version, responsible parties and the dates you need to revisit it. Save the source agreement in its restricted store.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Party and service
    Northstar hosting provider, production backup
    Clause or requirement
    Incident notification and contacts
    Current position
    General notice terms. No operational escalation contacts listed.
    Change to review
    Add named response channel and request confirmation of the timing.
    Owner, status and record
    Vendor lead, legal review pending, contract register V-018

    Check before handing it over

    The executed version covers the agreed roles and evidence paths. Review any jurisdiction-specific clauses with counsel.

    Give named obligations to operations and procurement. Use this worksheet to track review and keep the executed agreement as the authority.

    Device and service inventorySpreadsheet

    Gather first

    • Asset exports or system discovery
    • Service owner interviews
    • Approved scope and architecture

    How to prepare it

    1. Export a dated baseline from the source system. Give each asset, service or record class a stable ID and remove duplicates without losing links to the source.
    2. Add ownership, purpose, sensitivity and any vendor or system it depends on. Mark unknowns explicitly and assign them to someone to resolve.
    3. Reconcile the register against an independent source such as cloud billing or the production deployment list. Set a refresh cadence and an owner.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    ID
    SYS-014
    Item
    Production billing database
    Owner
    Platform operations
    Location and purpose
    Production EU region, stores invoice and account data
    Impact and dependencies
    High. Identity provider and managed backups.
    Verified on
    2026-11-10, cloud inventory export

    Check before handing it over

    Each item has one accountable owner. The source and as-of date let a reviewer trace it back.

    Share the reviewed inventory with the people building the control, privacy or testing scope.

  2. 02

    Implement the five baseline controls

    Who IT operations When Before submission

    Check firewalls, secure configuration, user access, malware protection and security update management within scope.

    How to do this step

    Before you start

    Approved scope, export access to administration tools and the current technical requirements.

    1. Check firewall and device configuration against actual settings. Remove unused services, default credentials and unauthorized admin access.
    2. Export software support status, updates and effective MFA settings. Compare the systems and accounts in the exports with the scope inventory.
    3. Test malware protection and user access with an ordinary user and an administrator. Track settings that can be bypassed and verify remediation.

    What a reviewer should see

    The IT lead can show a scoped account inventory, actual MFA enforcement and update status for the same devices listed in the questionnaire.

    When to escalate

    Raise unsupported in-scope software, unverified devices or unsafe exceptions before submission.

    What to produce

    Baseline configurationsSpreadsheet

    Gather first

    • Applicable criteria, requirements or risk decisions
    • Current procedures and configurations
    • Names of people operating or reviewing each control

    How to prepare it

    1. Give each requirement and implemented control an ID. Write a short control statement naming who does what, when and in which system.
    2. Record the evidence the control produces and how it could be tested. For a shared or inherited control, state who owns each part.
    3. Walk through one control with its operator. Check a real recent run, record gaps and obtain approval for exclusions or alternate controls.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement
    Production access is reviewed periodically.
    Control ID
    AC-04
    Control activity
    IAM team exports administrator roles every quarter. System owners approve or revoke each assignment.
    Owner and frequency
    IAM lead, quarterly
    Evidence
    Export with filters, annotated review and removal tickets
    Test and status
    Reconcile export to current roles. Inspect approvals. Operating.

    Check before handing it over

    A different person can operate the control or test it using the matrix and its evidence links.

    Give the baseline to control owners and the assessor before walkthroughs or sampling.

    Access reviewSpreadsheet

    Gather first

    • Authoritative list of users and privileges
    • Employment or contractor status
    • Approval and role criteria

    How to prepare it

    1. Export accounts and entitlements as of the review date. Separate privileged, shared and service accounts and attach the export to the review record.
    2. Ask each system owner to approve or remove every assignment. Record the business reason, named reviewer, date and any exception expiry.
    3. Open removal tickets, verify the actual permission was removed and reconcile completed tickets against the review decisions.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    System and account
    Production, operator-17
    Entitlement
    Billing administrator
    Decision and reason
    Remove. Operator moved to customer support.
    Reviewer and date
    System owner, 2026-10-03
    Removal evidence
    IAM-114, role absent from follow-up export

    Check before handing it over

    Every row has a dated decision. Removals are supported by observed state or a verified ticket.

    File the review and removal evidence together so assurance can test both approval and follow-through.

    Update evidenceSpreadsheet

    Gather first

    • Control descriptions and test request
    • Source system records
    • Defined period and evidence access rules

    How to prepare it

    1. Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
    2. Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
    3. Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Evidence ID
    EV-021
    Control or request
    AC-04, October administrator review
    Period and scope
    1 to 31 Oct 2026 UTC, production tenant
    Source and capture
    IAM export filtered to active elevated roles
    Link or record ID
    Restricted workpaper EV-021 plus ticket IAM-114
    Reviewer and status
    Security assurance, verified

    Check before handing it over

    A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.

    Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.

  3. 03

    Submit assessment and arrange Plus if needed

    Who Senior signatory + assessor When On the scheme’s current schedule

    Have the signatory approve the self-assessment. For Plus, agree sample coverage and coordinate independent testing and remediation.

    How to do this step

    Before you start

    Current questionnaire, assessment scope, configuration evidence and external assessor dates.

    1. Write answers against the real configuration and have a second person check each response against source records.
    2. For Plus, provide the test scope, representative equipment and secure arrangements for the assessor’s technical checks.
    3. Track assessor questions, remediation and accepted responses, then verify the certificate wording and scope.

    What a reviewer should see

    The file shows who approved the answers, evidence for them and the issued certificate with expiry and scope.

    When to escalate

    Escalate when a discrepancy in testing or certificate scope would invalidate a customer commitment.

    What to produce

    Signed questionnaireOfficial form

    Gather first

    • Current issuer form and eligibility rules
    • Agreed environment and assessor route
    • Evidence for every applicable response

    How to prepare it

    1. Confirm which current version, form and signing route apply. Download it from the authority or obtain the approved version from your assessor.
    2. Cross-reference each applicable question to evidence. Document the basis for excluded or inapplicable items. Reconcile scope and dates across companion documents.
    3. Have the authorized signatory and assessor review where required. Submit the original completed form using the approved channel and record acceptance.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Form and version
    Current official form for the confirmed validation route
    Question or section
    Identify the item or form section without copying form text.
    Evidence reference
    EV-021, annotated review and scope evidence
    Reviewer and outcome
    Authorized signer and assessor where required
    Submission record
    Keep date, recipient and reference after acceptance.

    Check before handing it over

    The original form version, scope and signers match the validation route and each response has supporting evidence.

    Use the issuer’s official form for validation. The download is a preparation worksheet.

    Testing evidenceSpreadsheet

    Gather first

    • Control descriptions and test request
    • Source system records
    • Defined period and evidence access rules

    How to prepare it

    1. Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
    2. Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
    3. Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Evidence ID
    EV-021
    Control or request
    AC-04, October administrator review
    Period and scope
    1 to 31 Oct 2026 UTC, production tenant
    Source and capture
    IAM export filtered to active elevated roles
    Link or record ID
    Restricted workpaper EV-021 plus ticket IAM-114
    Reviewer and status
    Security assurance, verified

    Check before handing it over

    A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.

    Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.

    CertificateIssuer document

    Gather first

    • Correct portal or issuer contact
    • Approved scope and submission record
    • File access and sharing requirements

    How to prepare it

    1. Confirm which issuer or portal supplies this record and who can retrieve it. Gather the submission reference, holder name, scope and expected date.
    2. When the document arrives, verify recipient, scope, dates, version, conditions and any required verification link. Escalate discrepancies to the issuer.
    3. Save the original in the approved location. Record renewal or response actions and limit distribution to authorized recipients.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Document expected
    Issuer’s final decision or confirmation
    Reference
    Official portal or case ID
    Received and verified by
    Compliance coordinator, 2026-11-10
    Scope and conditions
    Matches the agreed service boundary and version. Follow-up recorded separately.
    Location and access
    Restricted evidence folder, named reviewers only

    Check before handing it over

    The original can be traced to the issuer and its scope and date match the engagement or application.

    Send the verified record or approved summary to decision makers. The download is a tracking sheet for the original document.

  4. 04

    Renew and keep controls operating

    Who IT lead When Every 12 months

    Maintain scope and current configurations, monitor update deadlines and book reassessment ahead of expiry.

    How to do this step

    Before you start

    Certificate, the assessed scope, upgrade calendar and schedule of planned changes.

    1. Set reminders for software end of support, patch evidence, service changes and renewal. Give a named owner time to act on each.
    2. Check whether new devices, cloud services or acquired teams change scope or risk before going live.
    3. Use the current questionnaire and requirements at renewal. Repeat configuration checks and preserve the evidence.

    What a reviewer should see

    A new SaaS service has an approved scope decision, tested MFA and enrollment in the renewal evidence collection.

    When to escalate

    Raise changes that weaken an assessed control or threaten renewal before customer commitments lapse.

    What to produce

    Renewal calendarSpreadsheet

    Gather first

    • Current obligations, expiry dates or audit window
    • Delivery dependencies and owner availability
    • Official rules or engagement confirmation

    How to prepare it

    1. Separate official due dates, trigger-based clocks and team target dates. Write down the event or rule that starts each clock.
    2. Work backward from each milestone. Include lead time for review and submission, and name the owner and backup.
    3. Cross-check the dates with the source or reviewer and make reminders actionable. Record the next verification point for changing rules.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Milestone
    Quarterly access review approved
    Date and kind
    2026-12-18, internal target
    Trigger or source
    Internal access control schedule v3
    Prerequisite
    Access export by 2026-12-09
    Owner and reminder
    IAM lead, remind one week before
    Status
    Scheduled

    Check before handing it over

    Every external deadline links to a real source. Planning targets are visibly marked.

    Add approved dates to the team calendar and share them with the people scheduled to deliver or review.

    Change inventorySpreadsheet

    Gather first

    • Case, change or communication records
    • Required fields and timing
    • Named case owner and authorized recipients

    How to prepare it

    1. Give each event a record ID. Record the action or request, receipt or send time, owner and the deadline or next date.
    2. Write the decision and link the response or supporting record. Track delivery, escalation or verification separately so a sent message is distinguishable from an accepted one.
    3. Review open rows on a regular cadence. Restrict personal details to the case system and keep the register to IDs and necessary dates.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Record ID
    REQ-022
    Event and date
    Verified access request received 2026-11-07 UTC
    Owner and target
    Privacy operations, internal review by 2026-11-23
    Decision and status
    Approved response, sent securely
    Completion evidence
    Case delivery record, 2026-11-24
    Follow-up
    None, approved by the reviewer

    Check before handing it over

    Every open item has a next action and closed items have a verifiable record of closure or delivery.

    Use the log at case reviews and provide a restricted copy only where the engagement requires it.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes