Cyber Essentials is a UK government-backed scheme that focuses on five technical controls. Unlike ISO 27001, it does not ask you to build a large management system. That leads many teams to ask whether they need any documents at all.
In practice, yes. The assessment is built around what you actually do, but you cannot answer it confidently without a defined scope, an inventory, agreed rules and some records. This article sets out what to prepare and why.
Do you need formal documents for Cyber Essentials?#
The scheme is assessed through a self-assessment questionnaire that a certification body reviews. Cyber Essentials Plus adds hands-on technical verification of your environment. Neither route is a document audit in the way an ISO audit is.
Even so, documentation matters for three reasons:
- Accurate answers. Your questionnaire answers must reflect reality across every in-scope device and service. Written standards and inventories stop people guessing.
- Consistency. Without written rules, each administrator configures things differently, which is where gaps appear.
- Repeatability. Certification is renewed. Good records make the next cycle far less painful.
Keep documents short and operational. A two-page standard that people follow is worth more than a long policy nobody reads.
The foundation documents#
Before addressing each control, prepare these core items.
| Document | What it should cover |
|---|---|
| Scope statement | Which locations, networks, users, devices, cloud services and business units are in scope, and what is excluded and why |
| Asset inventory | Laptops, desktops, servers, mobile devices, network equipment, and the operating systems and key software on them |
| Cloud services register | Cloud and SaaS services used, who administers them, and how access is controlled |
| Information security policy (short form) | Management intent, responsibilities and the rules that support the five controls |
| Roles and responsibilities | Who owns firewalls, updates, accounts, endpoint protection and the questionnaire itself |
The scope statement is the most important. A poorly defined scope is a common reason for rework, because it affects every answer that follows.
Documents for each of the five technical controls#
1. Firewalls#
- Firewall and network configuration standard, including default-deny for inbound traffic
- Record of open ports or services, with a business justification and an approver for each
- Procedure for changing firewall rules and reviewing them periodically
- Guidance for protecting devices used outside the office, such as host-based firewalls
2. Secure configuration#
- Baseline build or configuration standard for each device type
- Procedure for removing or disabling unnecessary software, services and default accounts
- Password and authentication standard, including how default credentials are changed
- Rules on auto-run, screen locking and similar device settings
3. User access control#
- Joiner, mover and leaver procedure covering account creation, change and removal
- Administrator account standard, limiting admin rights and separating admin from day-to-day accounts
- Access review record showing accounts are checked and unused ones removed
- Multi-factor authentication standard for cloud services and other relevant access
4. Malware protection#
- Malware protection standard stating which mechanism applies to each device type
- Evidence that protection is enabled, kept up to date and configured to scan or block as intended
- Rules for application allow-listing or approved software sources, where you rely on them
5. Security update management#
- Update and patching procedure with target timeframes, particularly for critical and high-risk fixes
- List of supported software and a plan for anything that is unsupported or approaching end of life
- Update records or reports from your management tools
Records and evidence worth keeping#
Policies describe what you intend to do. Records show what you did. Keep a small evidence folder organised by control so you can answer questions quickly.
- Exports and screenshots of firewall rules, device compliance dashboards and endpoint protection status, with the date captured.
- Access review logs showing who reviewed accounts, when, and what was removed.
- Patch or update reports from your management platform.
- Exception register listing anything that does not meet a control, the reason, the compensating measure and the owner.
- Questionnaire working notes recording how each answer was derived and who confirmed it.
The exception register is often overlooked. It shows you understand your gaps and are managing them, which is far better than discovering them during assessment.
Extra preparation for Cyber Essentials Plus#
Cyber Essentials Plus involves technical testing of a sample of your environment. The documentation is largely the same, but the emphasis shifts to proof that controls work on real systems.
- An up-to-date, accurate device inventory so the sample can be selected and located
- Confirmation that your written standards match actual configurations on those devices
- Evidence that updates and malware protection are applied consistently, not just on a few machines
- A named contact who can provide access and answer technical questions during testing
Do an internal check on a handful of devices before the formal assessment. Differences between policy and practice are easy to find this way.
Keeping the documentation practical#
- Write for administrators. Use plain steps and settings they can follow, not general statements.
- Assign an owner and a review date to each document so it does not drift out of date.
- Reuse what you have. If you already have an IT policy or ISO 27001 documents, map them to the five controls rather than starting again. Our article on what an ISO 27001 toolkit should include explains how structured documentation can be used effectively.
- Test against reality. Before signing off, sample devices and accounts to confirm the document and the environment agree.
Your questionnaire should be approved by a senior person with the authority to confirm that the answers are accurate. Make sure they have seen the scope and the exception register before they sign.
Frequently asked questions#
Is a full set of ISO-style policies required for Cyber Essentials?#
No. The scheme is built around implementing five technical controls, not around a formal management system. However, short written standards, an inventory and records make it much easier to answer accurately and keep the controls consistent.
What is the single most important document to prepare first?#
The scope statement. It defines what the assessment covers, and every other document, inventory and answer depends on it being clear and correct.
Do the documents need to change for Cyber Essentials Plus?#
The core set stays largely the same. The difference is that your environment is technically tested, so inventories, configurations and update evidence must be accurate and consistent across real devices.
If you would rather start from a structured set of policies, procedures, checklists and templates aligned to the five technical controls, the Cyber Essential Toolkit is designed for that purpose, and the team is happy to discuss your situation if you get in touch.
