Cyber SecurityReviewed 28 October 2026

What Happens If We Fail Cyber Essentials Plus?

Understand Cyber Essentials Plus findings, remediation, retesting and the 2026 update rules, then build a practical recovery plan.

Caleb AdohGrowth Marketing Manager, NetMonkeys

What is the quick answer?

If Cyber Essentials Plus testing identifies a failure, ask the assessor to confirm the finding, applicable remediation process and deadline in writing. Fix the underlying issue throughout the relevant scope, preserve evidence and arrange the required retest. Under the 2026 update-management process, a repeat finding in the second device sample can also lead to revocation of the basic Cyber Essentials certificate. Do not assume a failed test is simply an extra fee and another attempt.

Does one failed technical test stop us receiving the certificate?

Cyber Essentials Plus includes independent technical testing. A business cannot treat an unresolved failed test as a minor administrative exception and assume certification will follow. IASME’s current certification guidance states that the required elements must be passed. Ask your assessor to explain the finding and the next decision point for your specific assessment.

Distinguish an initial finding that can enter the relevant remediation process from an assessment that has already reached a final unsuccessful outcome. These are different situations with different actions. The assessor’s written communication should tell you which applies, what remains open and what evidence or testing is required next.

Our Cyber Essentials preparation support can help businesses organise the technical response. The first step is to understand the actual result. Avoid commitments to a customer or director based on an informal summary such as nearly passed. Use the assessor’s terminology and keep the assessment record intact. Make sure everyone involved knows who can authorise further work and communicate an accurate status.

↑ Back to contents

What changed in the 2026 update-management retest process?

IASME’s April 2026 scheme update explains why selective patching is insufficient. Where the initial device sample fails update-management testing, the retest checks the original sample and a new random sample. Remediation needs to cover the wider assessment scope rather than only the devices already examined. A second failure under this process can revoke the verified self-assessment certificate.

The practical lesson is to investigate distribution and control, not merely the machine that produced the finding. Ask whether devices were missing from management, update deployment failed, an application was excluded or staff postponed required restarts. The same symptom can have several causes, and different causes require different fixes.

Have the assessor confirm the specific procedure applying to your case, including the remediation window and consequences. Do not borrow a deadline from an old self-assessment email. The currently published internal-vulnerability remediation process describes a 30-day window for its initial sample. Your plan must match the assessor’s written instructions and distinguish technical completion from the later availability of the systems for retesting.

↑ Back to contents

What should we ask the assessor immediately?

Request the exact finding, affected test and evidence needed for closure. Clarify which devices, accounts, services or network boundaries the finding concerns. Ask which part of the current specification is being applied and whether additional sampling or validation will be required. This prevents an engineer fixing a symptom while missing the assessment requirement.

Confirm dates explicitly, including when the remediation period starts and when access must be available for retesting. Ask how delayed access or a disputed finding is handled under the applicable process. Record the answer in the project notes and give everyone working on remediation the same version.

Also clarify commercial arrangements. Additional engineering, retesting, travel or a fresh application may have separate costs, depending on the agreement and outcome. Ask what is included before approving more work. A technical finding should be resolved through evidence, while cost and scheduling questions should be handled openly. Keep a separate decision log so a conversation about fees cannot be mistaken for an extension to an assessment deadline.

↑ Back to contents

Should we treat an assessment failure as a cyber incident?

An assessment failure and a confirmed compromise are different. A missing update or configuration problem identifies an issue that needs attention; it does not by itself establish that somebody has exploited it. Equally, preparation should not suppress signs of suspicious activity because the team is focused on obtaining a certificate.

Ask the technical lead whether the finding includes indicators requiring incident investigation. If it does, use the organisation’s incident response route and preserve relevant information. Do not erase logs or rebuild affected systems solely to make a test look clean before the situation has been understood. Record why urgent containment or preservation decisions were taken.

Our managed security services can form part of a discussion about ongoing operations and escalation. Keep responsibilities clear: the assessor determines assessment results, engineers perform authorised remediation and the business manages operational consequences. If there is an incident, customer communications and reporting decisions need their own appropriately qualified review. The assessment timetable should not become a substitute for investigating what happened or protecting affected people.

↑ Back to contents

How do we establish the full extent of the problem?

Start with the relevant population, not the individual asset in the report. Compare the assessment scope, device inventory and management reports. Identify equipment that was offline, recently added or administered differently. Include variations across locations and teams so a familiar office setup does not become the assumed model for everything.

For an application issue, establish where the application is installed and how its components are updated. For an identity issue, identify affected account types and services. For a network issue, inspect equivalent configurations rather than assuming one office is unique. The purpose is to find related exposure before the retest reveals it.

A focused review through cyber security audit services can help when the original records are incomplete. Define the review question precisely, such as whether all relevant devices receive a particular update. Ask for a documented population and exceptions so the conclusion can be checked. Record unknown systems as actions requiring investigation, rather than excluding them silently from an apparently reassuring report.

↑ Back to contents

How should we prioritise changes without breaking operations?

Create a short action record for each finding. Include the owner, affected population, proposed change, test method, dependencies and deadline. Identify actions needing business approval, such as replacing equipment or changing access. Separate independent tasks from work that depends on a supplier, application test or maintenance window.

Assess operational impact before deploying broadly. A business-critical application may need a representative test and a rollback plan. That is a reason to organise controlled change quickly, not a reason to ignore the finding. Explain the risk and timing to the process owner so the business can make an informed decision.

Our infrastructure management services are relevant when remediation spans devices, network equipment and server dependencies. Ask for records showing what changed and what was tested. Avoid a rushed collection of undocumented fixes that solves today’s sample but leaves nobody able to maintain the corrected state. Agree the point at which a delayed dependency must be escalated, so the team has time to consider alternatives.

↑ Back to contents

Why is patching only the sampled devices a poor response?

It addresses the visible assessment result while leaving the deployment process unexplained. If ten similar devices receive updates through the same mechanism and one is missing an important fix, the business needs to know whether that mechanism works reliably. Repairing the single device cannot answer the wider question.

Look for recurring operational causes. A device might not check in, a software package might be missing from deployment or a configuration might allow indefinite postponement. A good response identifies the cause, corrects the relevant population and verifies that the normal process can keep it corrected. Check that reporting distinguishes pending deployment from confirmed installation.

A dependable managed IT support arrangement should make ownership of these tasks clear. Ask what happens when an update fails, who reviews unmanaged assets and who contacts users whose equipment remains unavailable. The aim is reliable operating practice rather than an annual scramble. Give exceptions an owner and a due date, and make sure someone has authority to act when a user or supplier cannot meet the plan.

↑ Back to contents

What evidence should we preserve before the retest?

Keep the original finding, change approvals, deployment records and validation results together. Identify which systems were included and when checks were made. If a device was replaced, record the relationship between the retired asset and its replacement. If a configuration changed, preserve enough detail to understand the final state without exposing secrets.

Do not rely solely on a screenshot of a green dashboard. Explain the report’s coverage, excluded population and meaning of its status. A report generated before a device restarted or a configuration applied may not prove the intended outcome. Ask the engineer to distinguish deployment from confirmed completion.

Store evidence in a controlled location and provide it through the assessor’s agreed method. Avoid scattering administrative records across personal inboxes. The business owner should have an index showing each finding, responsible person, evidence and retest status. This makes questions easier to answer without improvising explanations. Keep an unchanged copy of the original report so the response can be traced to the issue that was actually identified.

↑ Back to contents

How do we handle cloud or Microsoft 365 findings?

Identify the service and administrative boundary involved. An apparent sign-in issue might depend on a tenant setting, an account type, an application connection or a separate supplier. Establish who can change the relevant configuration and who can approve its effect on users. Do not assume that every cloud change belongs to the same provider.

Test the intended user journey after the change. A successful administrator sign-in does not establish that ordinary employees and service workflows behave as expected. Record the accounts and scenarios tested without passwords or unnecessary personal data. Ask the assessor which evidence or access they need for the relevant requirement.

Our Microsoft 365 support services can help businesses review dependencies. Provide staff with clear instructions and a support route before a broad change. If users cannot work, they may create unmanaged alternatives. The plan therefore needs practical adoption as well as configuration. Verify the less visible connections used for payroll, finance and other scheduled tasks instead of testing only the most familiar employee account.

↑ Back to contents

What if an external supplier cannot fix the issue in time?

Escalate early and document the dependency. Ask the supplier for a named technical contact, realistic delivery date and evidence they can provide. Explain the assessment deadline and business impact, but do not assume the assessor can accept an unresolved issue because it sits outside your direct administration.

Investigate alternatives with the appropriate people. Options might involve replacing a component, changing how a service is used or redesigning an integration. Any proposed scope change needs proper review and assessor clarification. Removing a supplier from the paperwork while the underlying connection remains is not a sound solution.

A review of managed cloud services can be helpful when ownership is fragmented across hosting, application and support suppliers. If the deadline cannot be met, tell decision-makers promptly and plan for the actual outcome. Keeping a sales promise alive through optimistic updates creates a second problem. Ask the supplier to identify the earliest dependable milestone and any business decision that would allow the work to progress.

↑ Back to contents

What should we tell customers or procurement teams?

Use accurate status language and avoid implying certification before it is awarded. Explain whether assessment work is ongoing, remediation is in progress or the assessment has concluded unsuccessfully. Share information appropriate to the relationship and contract, with legal or procurement input where needed.

Ask the customer which requirement and deadline matter. A tender may specify a certificate, scope or evidence route. Your account manager should not promise that a remediation plan will be accepted as a substitute. Obtain written clarification rather than treating a friendly conversation as a contractual change. Preserve the exact wording of the requirement alongside the response.

Prepare a concise update containing the issue owner, next milestone, dependencies and uncertainty. Avoid circulating detailed vulnerability information more widely than necessary. A controlled explanation is more useful than silence or exaggerated assurance. Keep wording consistent across sales, management and supplier questionnaires. If a customer requests technical detail, decide who can receive it and use an appropriate sharing method rather than forwarding the entire assessment folder.

↑ Back to contents

What if our basic Cyber Essentials certificate is revoked?

Ask the certification body to confirm the recorded status, reason, effective date and route forward. Review where the certificate has been supplied, referenced or displayed. The business needs to know which customers, contracts and internal records depend on that status before deciding what communication is required.

Do not assume every agreement has the same notification obligation. Have the relevant contract owner check the wording and obtain appropriate advice where necessary. Update statements that would otherwise be misleading and record the decisions. A technical recovery plan and a commercial communication plan should share facts while serving different purposes.

If supplier responsibilities are unclear, review the outsourced IT support agreement alongside the records. Establish what was promised, what evidence existed and which operating process failed. The immediate priority remains remediation and accurate status, while discussions about responsibility or fees should use records rather than assumptions. Confirm who owns a fresh application if one is needed, including authorisation, evidence preparation, budget and communication with the certification body.

↑ Back to contents

How do we prevent the same failure at renewal?

Perform a root-cause review after the urgent work is complete. Ask why the issue escaped normal operations and which signal would have revealed it earlier. Separate individual mistakes from process weaknesses. A reminder to be more careful rarely fixes missing asset coverage or unclear ownership.

Assign a lasting control owner and a review method. Device health exceptions need somebody who can investigate missing equipment and obtain action from staff. A recurring report without an owner simply stores the problem. Set a review rhythm matching the rate of change and the importance of the systems.

Our managed endpoint detection and response services may be relevant to the wider operating model, but another tool should not be treated as automatic closure of an update or configuration issue. Define the problem first, then choose a control and evidence method that address it. Revisit the finding after normal business changes, such as a new office or application, to confirm the corrected process still reaches the whole intended population.

↑ Back to contents

What should our recovery plan look like this week?

Bring the assessor’s findings, current scope, inventory and supplier contacts into one review. Confirm the applicable process and dates. Allocate each technical action, business decision and evidence task to a named person. Make blocked dependencies visible immediately rather than waiting for the next scheduled meeting.

Agree what counts as complete before arranging the retest. Check the affected population, confirm any required broader remediation and make the necessary systems available. Keep customers and directors informed through accurate milestones. If success is uncertain, say so early enough for them to make realistic decisions. Give the coordinator a clear escalation route for missing access or unavailable equipment.

To discuss technical remediation and preparation, contact NetMonkeys. A useful conversation starts with the actual finding and the assessor’s instructions, not a request to guarantee a pass. The aim is a controlled response that resolves the weakness, supports the assessment and leaves a more dependable way of operating. Preserve the lessons and assign ongoing ownership before closing the project, rather than treating the certificate as the final operational task.

↑ Back to contents

What else do businesses ask?

Do we always have 30 days to fix every issue?

Do not assume a universal window. The current internal-vulnerability process describes a 30-day initial remediation period, but confirm the procedure, start date and deadline for your finding with the assessor.

Can failure affect our basic Cyber Essentials certificate?

Yes. Under the 2026 update-management sampling process, specified repeat failures can lead to revocation of the verified self-assessment certificate. Ask the certification body to confirm the status and consequences in your case.

Does failure prove we suffered an attack?

No. A control failure and a confirmed compromise are different. Investigate suspicious activity through the incident response route while managing the finding through the required assessment process.

Who wrote this guide, and how was it checked?

Written by Caleb Adoh, Growth Marketing Manager at NetMonkeys. Reviewed 28 October 2026 against IASME current certification guidance and April 2026 changes. Recovery methods are editorial recommendations. The assessor must confirm the applicable remediation, retest and certification status for your assessment.

How can NetMonkeys help your business?

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

Speak to NetMonkeys