Guide Vulnerability Management Cybersecurity

Vulnerability remediation: patch deadlines, exceptions and what the frameworks require

Knowing what to fix first is half the job. The other half is committing to deadlines, handling the systems you cannot patch, showing auditors that the process works and telling the board whether you are keeping up.

17 November 2026
8 min read
Key takeaways
  • Set remediation targets by tier and count from the date the fix was released, not the date your scanner found the issue.
  • Give firewalls, VPNs and other edge devices their own process: check vendor advisories weekly, keep management interfaces off the internet and look for signs of compromise after patching.
  • Not applying an update is a senior management risk decision. Record each exception with an owner, compensating controls and an expiry date.
  • Cyber Essentials requires critical and high-risk updates within 14 days of release. ISO 27001 control 8.8 sets no deadline, but auditors expect defined targets and evidence that you meet them.
  • Report to the board the share of known exploited vulnerabilities fixed within target, confirmed by a rescan, alongside scan coverage and open exceptions.

This guide covers remediation targets, edge devices, exceptions, framework requirements and board metrics. For the vulnerability management lifecycle and how to prioritise beyond CVSS, see our vulnerability and patch management guide.

Setting remediation targets

Remediation targets turn priorities into deadlines that people can be held to. The table below is a starting point we use with clients. Adjust it to your risk appetite and regulatory obligations, but keep the Cyber Essentials 14-day rule as a floor if you hold or plan to hold the certification.

Tier What qualifies Suggested target
Emergency On the CISA KEV catalogue or known to be actively exploited, on an internet-facing or business-critical system Mitigate within 48 hours (sooner for exposed systems under active attack), fully fixed within 7 days
Critical / High Vendor rates the issue critical or high, the CVSS v3 base score is 7 or above, or the vendor gives no severity 14 days from release (the Cyber Essentials requirement)
Medium CVSS v3.x base score 4.0 to 6.9, with no known exploitation 30 days
Low CVSS v3.x base score below 4.0, or findings that need significant access to exploit 90 days, or the next scheduled cycle

Apart from the Cyber Essentials 14-day rule, the tiers and targets above are an example of a locally defined policy, not a standard. The score thresholds use CVSS v3.x, where 7.0 to 10.0 is high or critical severity, which is also what Cyber Essentials references. CVSS v4.0 uses different metrics and its scores are not directly comparable with v3.x; if your scanners or vendors already report v4.0 scores, review the thresholds and record in your policy which version you use.

For Cyber Essentials, the 14-day clock starts when the vendor releases the update. For your own targets, measure from the date the fix or the vulnerability became public, not from the date your scanner found it. That stops slow scanning from hiding slow patching. Where no fix exists yet, use the exception process below until one does. Turn on automatic updates wherever the platform supports it. Cyber Essentials requires it where possible, and it removes most routine patching from the queue.

Edge devices and remote access

Firewalls, VPN concentrators, remote access gateways and other network appliances are the systems attackers most want to compromise and the ones organisations most often forget to update. They sit on the internet, they often run firmware that needs a manual update, and they rarely support endpoint security agents.

Give them their own process. Subscribe to the vendor’s security advisories and check them weekly. Make sure management interfaces are not reachable from the internet. Replace appliances that have reached end of support, because vendors stop releasing fixes for them. When a critical vulnerability is announced, patch first, then check for signs that the device was compromised before the patch. Attackers who exploited the flaw early may already have installed persistence that survives the update. Hardening guides such as the CIS Benchmarks help reduce the exposed surface in the first place.

When you cannot patch

Sometimes there is no fix yet, the fix breaks a critical application, or the system belongs to a supplier who controls the update. The NCSC guidance is direct: the decision not to apply an update is a senior-level risk decision, not one for an individual administrator to make alone.

Handle it as a formal exception. Apply compensating controls: isolate the system on its own network segment, restrict who and what can connect to it, disable the vulnerable feature, or add monitoring for exploitation attempts. Record the exception in your risk register with a named owner, the reason, the controls in place and an expiry date. Decide in advance who can approve an exception and when it must go to a senior risk owner. Test that the compensating controls work, and reassess the exception when the threat, the exposure or the available fixes change. Isolation reduces exposure, yet removable media, supplier access and local users can still reach an isolated system. Review it before it expires. An exception without an end date becomes a permanent gap that nobody remembers approving.

Unsupported software needs a plan of its own. Cyber Essentials requires all in-scope software to be licensed and supported, and unsupported software must be removed or moved into a separate sub-set with no internet access. Our article on Windows 10 end of life covers one of the most common current examples. Supplier-managed systems belong in your contracts too; our supply chain security guide covers how to set patching expectations for suppliers.

What the frameworks require

Most security frameworks that UK organisations work to include vulnerability management, with different levels of detail.

Cyber Essentials

Security Update Management is one of the five technical controls in the Cyber Essentials requirements (v3.3). It covers servers, desktops, laptops, tablets, mobile phones, firewalls, routers and cloud services. All in-scope software must be licensed and supported, automatic updates must be enabled where possible, and updates must be applied within 14 days of release where the vendor rates the issue critical or high, the CVSS v3 score is 7 or above, or the vendor publishes no severity details. The NCSC recommends applying all updates within 14 days, though only the critical and high-risk ones are mandatory.

The Danzell question set, used for assessment accounts created from 27 April 2026, made the 14-day questions for operating systems, firmware and applications automatic fail points. Before that, a missed deadline could be marked as a non-compliance without failing the assessment outright. See our comparison of Cyber Essentials and ISO 27001 for how the two schemes fit together.

ISO/IEC 27001:2022

Annex A control 8.8, Management of technical vulnerabilities, requires you to obtain information about technical vulnerabilities, evaluate your exposure and take appropriate measures. The control does not set a fixed timetable. To show it works, you will typically need a defined process, remediation timescales, evidence that you meet them, and a record of risk-accepted exceptions. Control 5.9 (inventory of information and other associated assets) supports it. Our ISO 27001 guide for SMEs covers the wider certification process.

UK NIS Regulations and the Cyber Security and Resilience Bill

Operators of essential services and relevant digital service providers are assessed against the NCSC Cyber Assessment Framework, where outcome B4.d covers vulnerability management. The Cyber Security and Resilience Bill, now in the House of Lords, would bring managed service providers and data centres into scope, so more suppliers will need to show a working vulnerability management process.

If you operate in the EU: NIS2 and the Cyber Resilience Act

NIS2 Article 21(2)(e) requires essential and important entities to cover security in the acquisition, development and maintenance of systems, including vulnerability handling and disclosure. If you make products with digital elements sold in the EU, the Cyber Resilience Act has required manufacturers to report actively exploited vulnerabilities since 11 September 2026, with the main security obligations following on 11 December 2027.

Metrics to report to the board

Boards do not need scan counts. They need to know whether the organisation is fixing the right things fast enough. Six measures cover most of it.

Known exploited vulnerabilities within target. The percentage of KEV-listed or actively exploited vulnerabilities fixed within your emergency deadline. This is the single most useful number. Show how long overdue KEV items have been open, and count an item as fixed only when a rescan confirms it: a successful patch deployment does not close the vulnerability.

Median time to remediate by tier. How long fixes actually take, compared with the targets in your policy.

Remediation within target. The percentage of findings fixed within the deadline for their tier, with overdue items broken down by owner and asset class. A healthy median can hide a long tail of old, severe findings.

Scan coverage. The percentage of assets in your inventory that were scanned in the last 30 days. Low coverage makes every other metric look better than it is.

Open exceptions. The number of risk-accepted vulnerabilities, how old they are, and how many have passed their expiry date.

Unsupported assets. The number of systems running software that no longer receives security updates, with a plan and a date for each.

Ryland Deakin
About the author
Lead Consultant, Cyvra · CISM · CompTIA Security+ · MCP

Ryland has delivered cybersecurity, compliance, and IT management programmes for regulated organisations across the UK and the Netherlands for over 20 years. View full profile

Common questions

How quickly does Cyber Essentials require us to patch?

Within 14 days of the update being released, where the vendor describes it as fixing a critical or high-risk vulnerability, the CVSS v3 base score is 7 or above, or the vendor provides no severity details. This applies to operating systems, firmware and applications on all in-scope devices and cloud services. Under the Danzell question set used from 27 April 2026, missing the 14-day deadline is an automatic fail. The NCSC recommends applying all other updates within 14 days as well, but that part is advisory.

What should we do with systems we cannot patch?

Treat them as formal exceptions approved at senior level. Reduce the risk with compensating controls such as network segmentation, restricted access, disabling the vulnerable feature and extra monitoring. Record each exception in the risk register with an owner, the reason, the controls and an expiry date, and review it before it expires. For unsupported software, plan its replacement. Cyber Essentials requires unsupported software to be removed or isolated in a separate sub-set with no internet access.

Which vulnerability metrics should we report to the board?

Six cover almost everything: the percentage of known exploited vulnerabilities fixed within your emergency target, median time to remediate by tier, the share of findings fixed within target, scan coverage of your asset inventory, open exceptions and how many are past their expiry date, and the number of unsupported assets. Count something as fixed only when a rescan confirms it.

Cybersecurity Assessment

Find out which vulnerabilities matter before an attacker does

Our assessment reviews your asset visibility, patching performance and exposure alongside four other security domains. You leave with a prioritised roadmap.

Disclaimer: This article is for general informational purposes only and does not constitute legal, regulatory, or professional advice. Cyvra makes no warranty as to the accuracy or completeness of this content, which may not reflect the most current regulatory developments. Readers should seek independent legal and regulatory advice appropriate to their specific circumstances. Cyvra accepts no liability for any loss arising from reliance on this content.