Cyber SecurityReviewed 28 October 2026

How Do We Prepare for a Cyber Essentials Assessment?

Prepare for Cyber Essentials with a practical plan for scope, devices, cloud services, accounts, remediation, evidence and management sign-off.

Caleb AdohGrowth Marketing Manager, NetMonkeys

What is the quick answer?

Start with the current official question set and requirements. Agree your scope, inventory devices and cloud services, allocate owners, check the five control areas and fix gaps before submitting answers. Keep evidence of what was checked and arrange senior sign-off. If you also need Plus, plan technical testing with your Certification Body rather than treating the questionnaire as the entire project.

What should we do before buying an assessment?

Begin by downloading the current official question set and reading it alongside the requirements. IASME identifies Danzell for purchases from 27 April 2026. An old spreadsheet saved from a previous project may no longer be the right starting point.

Give the project a sponsor and an internal coordinator. The sponsor approves priorities and resolves business decisions. The coordinator gathers information, tracks tasks and keeps suppliers aligned. In a small business one person may perform both roles, but the responsibilities still need to be clear.

Cyber Essentials preparation support can help you establish a workable preparation plan. Agree what the engagement will produce before committing to a deadline. Useful outputs include a confirmed scope, a reliable inventory, a gap register and evidence supporting the eventual answers. Buying assessment access is a process step; it is not proof that the organisation is ready to submit.

↑ Back to contents

How do we define the assessment scope correctly?

The official requirements for IT infrastructure v3.3 explain scope. Agree boundaries with the Certification Body. Relevant cloud services cannot simply be excluded, and a scope omitting end-user devices is not acceptable. Use the document to resolve details rather than inventing exceptions.

Prepare a plain description of the business entity and activities. Explain locations, remote working, shared infrastructure and any separate business units. If the organisation belongs to a group, ask who operates common services and which entities use them. A diagram can help a discussion, but it should be supported by an understandable written explanation.

Test the proposed description with operations and finance as well as IT. They may know about systems or locations missing from the initial picture. Resolve discrepancies before assessment begins. A scope that everyone interprets differently will make later answers unreliable and can leave the commercial team uncertain about what certification would demonstrate to customers.

↑ Back to contents

What should our device and software inventory contain?

Create a working inventory containing device type, owner, user, operating system, location and management arrangement. Record enough information to distinguish similar systems. Include the person who can answer questions about each group of assets. If a device is no longer in use, confirm its status rather than leaving it indefinitely in an ambiguous list.

For software, identify important applications and who manages their lifecycle. A finance tool, browser extension or specialist operational application may have a different support arrangement from the main operating system. Ask departments to review the list so that the project does not rely solely on centrally purchased tools.

IT infrastructure management can help develop a dependable inventory. Treat it as a source for decisions, not a spreadsheet created only to satisfy the project. Note when information was checked and how changes will be recorded. A list that cannot be maintained soon becomes a historical document rather than useful evidence about the current environment.

↑ Back to contents

How should we organise firewall preparation?

Ask the responsible administrator to explain the firewall arrangement for each working scenario. Office networks, remote devices and hosted systems may have different owners. Your preparation task is to establish who can check the relevant configuration, approve changes and provide an intelligible account of the result.

Keep a record of business reasons for unusual connectivity. When someone says an old exception must remain, identify the application owner and ask them to confirm the need. This turns a vague technical discussion into a business decision. Avoid removing access without understanding which process relies on it and how any change will be tested.

The project coordinator should record findings, owners and completion evidence. Where another provider manages the boundary, agree how it will respond to questions. Do not assume that the presence of a box labelled firewall proves the configuration is suitable. Preparation is about knowing how the environment is managed and checking it against the current requirements.

↑ Back to contents

How should we review secure configuration?

Start by asking how a new device is prepared for use and how that standard is maintained. Compare the intended build with devices already issued to employees. The practical question is whether the organisation has a repeatable method or relies on each engineer and user making their own choices.

Review variations deliberately. A specialist application may need a different setup from the office standard, but someone should know why and manage the difference. Record the business owner and approved approach. Unexplained exceptions are difficult to assess and can persist long after the original reason has disappeared.

modern workplace security can help organise consistent workplace and device practices. For the preparation project, request a clear account of the checks performed and changes made. Avoid relying on a policy document alone. A policy can describe the intended position while the actual device estate has drifted through years of replacement, temporary workarounds and informal requests.

↑ Back to contents

How do we check security updates without guessing?

Understand which team monitors updates, how deployment is performed and how failed installations are followed up. A system configured to request updates is not the same as evidence that relevant updates were installed. Ask for the records and reporting your organisation uses to know the difference.

The requirements set a 14-day deadline for specified vulnerability fixes, including high or critical vulnerabilities, CVSS v3 scores of at least 7, and fixes where severity information is absent. Check the detailed criteria in the official document. Do not reduce the rule to a claim that every possible update has an identical mandatory deadline.

managed IT support can support a managed approach to routine updating. Prepare a plan for systems that cannot be changed through the normal process. Include the application owner, testing needs and decision date. A permanent exception based on an undocumented concern is harder to manage than an agreed action with accountable people and a clear resolution path.

↑ Back to contents

How should we review accounts and administrator access?

Build a list of the systems through which people access business information. Identify who approves accounts, who creates them and how departures or role changes reach the administrators. Compare those arrangements with actual records. A process that exists only in an induction document may not cover contractors, temporary workers or old subscriptions.

The current requirements state that cloud-service authentication must use multi-factor authentication. Check each relevant service rather than assuming that one protected Microsoft login means every separate application is covered. Ask the responsible administrator to explain the method and any unresolved issue.

Microsoft 365 support can support account and configuration work in a Microsoft environment. Coordinate with HR and managers so that technical changes match real responsibilities. Review administrative access with particular care and retain the business reason for it. The project should leave the organisation knowing who has access and who can authorise future changes.

↑ Back to contents

What should we check about malware protection?

Ask which protection approach applies to each relevant device group and who manages it. Then establish how the business knows the chosen arrangement is active and functioning. A software invoice or licence count is not a complete operating record. Someone needs to review status, handle problems and ensure new devices enter the normal management process.

Arrange the review with the technical owner and use the current scheme requirements for the formal criteria. Keep findings tied to particular assets or groups so that remediation can be tracked. If an unfamiliar device type needs a different approach, ask the Certification Body to clarify rather than guessing from a standard laptop checklist.

managed endpoint detection and response can form part of wider endpoint security where it fits your needs. Distinguish that broader service from the particular certification requirement being addressed. Avoid purchasing products solely because their names sound reassuring. Ask how the proposed approach will be implemented, monitored and supported after the preparation project has ended.

↑ Back to contents

How do we collect reliable information about cloud services?

Use purchasing records, staff interviews and administrator knowledge to build the service list. Departmental tools can be missed if the project looks only at the main IT invoice. Marketing platforms, file-sharing services and operational subscriptions should each have an identified business owner who can explain why they are used.

For each service, record the administrative contact, relevant account arrangements and where supporting information can be obtained. Ask who performs each operational task. A provider may operate the underlying platform while your organisation still controls important settings and user decisions. The preparation team needs to understand those boundaries.

managed cloud services can help coordinate responsibilities across hosted systems. Keep evidence in a controlled location and avoid placing passwords or sensitive access details in the assessment working document. The objective is to demonstrate understanding and management, not to create an unnecessary collection of secrets that introduces a separate security problem.

↑ Back to contents

How should we handle remote workers and personal devices?

Ask employees how they access business services in practice. A formal policy can differ from everyday behaviour, especially where the organisation has grown quickly or allowed temporary arrangements. Explain that the purpose is accurate preparation so people feel able to disclose the actual working pattern.

Record device ownership, use and management, then apply the official scope guidance with the Certification Body. Do not make a broad assumption that every personal device is excluded or that every device in a home must be included. Details matter, and unusual scenarios should be clarified before the final answers are written.

Coordinate changes with employees and managers. If the business decides to replace an unmanaged working arrangement, provide a practical alternative and explain the transition. Simply banning a method without giving staff a workable route can drive the activity out of view. Preparation should improve visibility and responsibility while keeping essential work organised.

↑ Back to contents

What information do we need from external IT suppliers?

Give each supplier a specific request containing the systems it manages, the relevant question and the evidence needed. Avoid asking whether everything is compliant. That phrase can produce a reassuring answer without revealing what was checked, which systems were included or who will resolve gaps.

Create a responsibility record across suppliers. One may handle devices, another a hosted application and a third network connectivity. Identify dependencies so a task does not sit between contracts with no owner. Where suppliers disagree, bring the issue back to the internal coordinator and responsible business owner.

small business IT support can help a business without its own IT team coordinate practical work. Your organisation still needs an internal person who understands decisions, approves changes and retains the outputs. Keep inventories, configuration explanations and project records accessible to the business so that future renewal does not depend entirely on one individual at a supplier.

↑ Back to contents

How do we turn gaps into an achievable remediation plan?

For each gap, record the affected assets, the required outcome, proposed action, owner and target date. Add dependencies and the evidence that will show completion. This is more useful than a list of technical observations because management can see what must happen and who can move it forward.

Distinguish a confirmed gap from missing information. If nobody knows a setting, first assign a check. If the setting is known to be wrong, assign a change. Mixing uncertainty and confirmed failures can lead to unnecessary work or an optimistic plan that assumes unanswered questions will resolve themselves.

cyber security audit services can help establish the starting position and check that remediation addresses findings. Keep optional broader improvements visible but separate from the immediate project. Management should be able to approve necessary work without losing sight of other risks or treating every proposed security enhancement as a compulsory requirement of certification.

↑ Back to contents

What evidence should we retain during preparation?

Keep an evidence index rather than an unstructured dump of screenshots. For each important answer, identify the responsible person, date checked and supporting record. The evidence should help someone understand why the answer is accurate. It need not reproduce sensitive details that are irrelevant to that explanation.

Use a controlled working location and clear naming. Remove outdated versions from the active set or mark them so they cannot be mistaken for current evidence. If a supplier sends information through email, retain the useful record in the project location instead of leaving critical evidence in one employee’s inbox.

Record changes made during preparation and the checks confirming them. That creates a practical handover for the people maintaining the environment afterwards. It also helps if a project contact leaves. The aim is continuity of understanding, so the business can explain its position without relying on a single person remembering how each answer was established.

↑ Back to contents

How should management review and sign off the submission?

Arrange a review before the final submission rather than asking a director for an urgent signature at the end of the day. Provide the scope, a plain explanation of the checks and a list of any outstanding questions. Management should know who prepared the information and how exceptions were handled.

Invite challenge. Ask whether new staff, subscriptions, acquisitions or operational changes could make an answer incomplete. A final review is an opportunity to correct the position before making the declaration. Do not treat it as a ceremonial approval after technical staff have already decided everything.

When questions remain, resolve them with the responsible people or Certification Body. Do not fill uncertainty with a generic answer copied from a sample. Keep the submitted version and supporting project record. That gives your organisation a stable reference for future assurance work and helps maintain consistency between technical evidence, management declarations and customer communications.

↑ Back to contents

How do we prepare if Cyber Essentials Plus is also required?

Discuss the technical assessment early with the Certification Body. Explain the environment, relevant locations and available contacts. Agree how access, scheduling and communication will be handled. The technical work should be planned alongside business activity rather than arriving as a surprise after the questionnaire stage.

Do a practical coordination check. Can the relevant people make devices available? Does another supplier need to approve or facilitate access? Who receives findings and authorises changes? These questions help prevent avoidable delays even when the technical environment is in a good position.

Ask for the applicable follow-up and retest terms in writing. Do not assume that a readiness review guarantees the assessment result. Independent testing may identify something requiring attention. A sensible plan includes a way to record findings, allocate action and communicate progress without inventing certainty about a pass or promising a customer an outcome before it has been achieved.

↑ Back to contents

How do we maintain readiness after the assessment?

Embed the important tasks into normal operations. Device purchasing, account changes and new subscriptions should update the same records used during preparation. Give the inventory and evidence owners a route to hear about change. Otherwise the carefully assembled project picture will become inaccurate as the business continues to grow.

Review progress through manageable routines. Focus on exceptions, unresolved actions and changes in responsibility rather than asking managers to reread the entire assessment every month. Keep a clear renewal owner and allow time to check the current requirements before the next application.

managed cyber security services can support continuing security management where appropriate. Ask for outputs that your organisation can understand and retain. The long-term benefit of preparation is a business that knows its environment and can maintain its controls. The certificate is a useful result, while that everyday understanding makes future assessments and customer assurance conversations more straightforward.

↑ Back to contents

What else do businesses ask?

Which Cyber Essentials question set should we use?

Use the version applicable to your purchase date. IASME identifies Danzell for purchases from 27 April 2026. Check its current official download page before starting.

Do we need to fix gaps before submitting?

Your answers should accurately describe controls that meet the applicable requirements. Identify and resolve gaps, then confirm the resulting position rather than describing intended future work as already completed.

Can our IT provider prepare the answers for us?

A provider can assist with technical information and remediation, but the organisation needs an accountable internal owner and appropriate senior sign-off. Understand and retain the basis of the submitted answers.

Who wrote this guide, and how was it checked?

Written by Caleb Adoh, Growth Marketing Manager at NetMonkeys. Preparation was checked against the linked IASME question-set page and official Requirements for IT Infrastructure v3.3 on 28 October 2026. The project workflow is editorial guidance, not a substitute for the complete requirements or the assessor’s scope decisions.

How can NetMonkeys help your business?

Talk to our team about your priorities and agree a practical next step.

Speak to NetMonkeys