---
id: CP-246
slug: patch-management-deployment-delay
lang: en
title: Patch management and deployment delay
description: Why the gap between a patch's release and its installation helps attackers, and what each employee does about it.
canonical_url: https://startbrain.io/cyberpedia/en/articles/patch-management-deployment-delay/
markdown_url: https://startbrain.io/cyberpedia/en/articles/patch-management-deployment-delay.md
publisher: Brain (https://startbrain.io)
license: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/)
cite_as: Brain, "Patch management and deployment delay", Cyberpedia, 2026. https://startbrain.io/cyberpedia/en/articles/patch-management-deployment-delay/ (CC BY 4.0)
wing: 3
theme: report_incidents
reflex: cr-031
schema: G4
updated: "2026-11-10"
translations:
  en: https://startbrain.io/cyberpedia/en/articles/patch-management-deployment-delay/
  fr: https://startbrain.io/cyberpedia/fr/articles/gestion-correctifs-delai-deploiement/
  de: https://startbrain.io/cyberpedia/de/articles/korrekturverwaltung-bereitstellungsdauer/
  es: https://startbrain.io/cyberpedia/es/articles/gestion-parches-plazo-despliegue/
  it: https://startbrain.io/cyberpedia/it/articles/gestione-patch-tempo-distribuzione/
  nl: https://startbrain.io/cyberpedia/nl/articles/patchbeheer-uitroltermijn/
  pl: https://startbrain.io/cyberpedia/pl/articles/zarzadzanie-poprawkami-czas-wdrozenia/
  pt: https://startbrain.io/cyberpedia/pt/articles/gestao-correcoes-prazo-implementacao/
  ja: https://startbrain.io/cyberpedia/ja/articles/patch-kanri-haifu-chien/
sources:
  - "n": 1
    title: Keeping devices and software up to date
    publisher: NCSC (UK)
    url: https://www.ncsc.gov.uk/collection/device-security-guidance/managing-deployed-devices/keeping-devices-and-software-up-to-date
    published: "2021-06-29"
    accessed: "2026-11-10"
  - "n": 2
    title: 2021 Top Routinely Exploited Vulnerabilities
    publisher: CISA
    url: https://www.cisa.gov/news-events/cybersecurity-advisories/aa22-117a
    published: "2022-04-27"
    accessed: "2026-11-10"
  - "n": 3
    title: "BOD 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities (Revoked)"
    publisher: CISA
    url: https://www.cisa.gov/news-events/directives/bod-22-01-reducing-significant-risk-known-exploited-vulnerabilities-revoked
    published: "2021-11-03"
    accessed: "2026-11-10"
  - "n": 4
    title: 2022 Top Routinely Exploited Vulnerabilities
    publisher: CISA
    url: https://www.cisa.gov/news-events/cybersecurity-advisories/aa23-215a
    published: "2023-08-03"
    accessed: "2026-11-10"
  - "n": 5
    title: Pourquoi et comment bien gérer ses mises à jour ?
    publisher: Cybermalveillance.gouv.fr
    url: https://www.cybermalveillance.gouv.fr/tous-nos-contenus/bonnes-pratiques/mises-a-jour
    published: "2019-11-26"
    accessed: "2026-11-10"
  - "n": 6
    title: "Guide to Enterprise Patch Management Planning: Preventive Maintenance for Technology"
    publisher: NIST
    url: https://csrc.nist.gov/pubs/sp/800/40/r4/final
    published: "2022-04-06"
    accessed: "2026-11-10"
  - "n": 7
    title: Vulnerability management guidance
    publisher: NCSC (UK)
    url: https://www.ncsc.gov.uk/collection/vulnerability-management/guidance
    accessed: "2026-11-10"
  - "n": 8
    title: Exploit Public-Facing Application, Technique T1190 - Enterprise | MITRE ATT&CK®
    publisher: MITRE ATT&CK
    url: https://attack.mitre.org/techniques/T1190/
    accessed: "2026-11-10"
---

# Patch management and deployment delay

A patch is a vendor's answer to a known flaw. Until it is installed, the flaw stays open on the device, even though it is now documented. The UK's NCSC puts it this way: once updates are available, attackers can work out which flaws they fix and start attacking devices that have not installed them [1].

This article describes the gap between the release of a patch and its installation. It explains what the employee does on their side and what the company organizes to shorten it.

## In 30 seconds

- Where it happens: on all software, from the operating system to the browser and office applications [1]. Attackers also target systems reachable from the Internet, such as mail servers and VPNs [2].
- What the attacker wants: to exploit the flaw while the patch is not installed [1].
- The reflex: install updates as soon as they are offered, ideally within a few days, and restart when the device asks [1].
- If you have put it off: install the pending update and restart when the device asks [1].

## Straight answers

### Why is the gap between release and installation dangerous?

Because the patch reveals what was wrong. For flaws that attackers actually exploit, the delay is short. Among vulnerabilities known to have been exploited (fewer than 4% of all known vulnerabilities), 42% were used on the day of disclosure, 50% within 2 days and 75% within 28 days, according to CISA [3].

Proof-of-concept code often circulates very quickly. For most of the top flaws exploited in 2021, researchers or other actors published such code within two weeks of disclosure [2].

### Does an old flaw still matter?

Yes. In 2022, malicious actors exploited older flaws more often than recently disclosed ones, and they targeted unpatched systems exposed to the Internet [4]. The agencies that wrote this advisory note that attackers do best in the first two years after public disclosure, and that a flaw's value then declines as software gets patched [4].

### What happens if I put off the restart?

Some updates require a manual restart. If the device has not restarted in a long time, the update may not be installed [1]. Cybermalveillance.gouv.fr observes that update messages are often ignored because they interrupt a task, and advises using idle periods (lunch, a meeting, overnight) [5].

### Is my antivirus enough?

No, the two do not play the same role. Patches repair known flaws that attackers can use to compromise a device, whereas antivirus updates bring signatures that detect recently spotted malware [1]. The antivirus is itself software that must be kept up to date [1]. The joint advisory on the flaws exploited in 2022 recommends applying patches in a timely manner and, in addition, using security tools such as endpoint detection and response (EDR) [4].

### What about a personal device or one outside the company's fleet?

It is a weak point. It takes only one device that is not up to date and is exposed to a flaw to open a breach in the digital environment, and the list includes computers, phones and connected objects [5]. If the company allows personal devices, it may not have the right to force updates, or the device may no longer be supported; the NCSC then suggests restricting access to company resources from devices that are not up to date [1].

## How it works

Enterprise patch management, according to NIST, is the process of identifying, prioritizing, acquiring, installing and verifying the installation of patches, updates and upgrades across the organization [6]. NIST presents it as preventive maintenance, a cost of doing business and not an option [6].

The first task is the inventory. The NCSC asks organizations to know which systems and software exist, who is responsible for them and which vulnerabilities they contain [7]. Cybermalveillance.gouv.fr also advises identifying all the devices and software in use so that they can be updated [5]. CISA's advisories recommend a centralized patch management system that sets the order of priority [4].

The second task is prioritization. A vulnerability's severity score (CVSS) does not say whether it is actually used in attacks, and CISA finds that widespread attacks have combined vulnerabilities rated "high", "medium" or even "low" [3]. It recommends handling first the vulnerabilities known to be exploited, which appear in its catalog, then critical and high vulnerabilities on Internet-facing equipment [3][4]. To be listed, a vulnerability must have a CVE identifier, a clear remediation action and reliable evidence of real-world exploitation [3].

Target deadlines come from there. A US directive, which applied only to federal agencies, set two weeks to fix the flaws in the catalog (six months for those whose CVE identifier predated 2021) [3]. That directive is revoked and replaced by BOD 26-04, devoted to prioritizing updates according to risk [3].

The NCSC sets as a principle to put in place a default update policy: apply updates as soon as possible, and ideally automatically [7]. Not updating is a risk decision taken at management level [7]. For devices that cannot be patched, Cybermalveillance.gouv.fr cites disconnecting from the Internet, separating them from the rest of the network and disabling vulnerable services [5]. CISA's measures add replacing end-of-life software and applying vendor-approved workarounds when a patch cannot be installed quickly [4].

On the attack side, MITRE's technique T1190 describes exploiting a weakness in an Internet-facing system to gain initial access to the network [8]. Network edge devices are targets, notably those that do not support strong on-device defenses [8].

## What you do

- Turn on automatic updates when possible, in particular for the system, the browser, office applications and the antivirus [1].
- Install updates as soon as you are notified, ideally within a few days [1].
- Follow the device's instructions: some updates require Wi-Fi, mains power, available space or a restart [1].
- Restart when asked. If the timing is bad, schedule it for an idle period rather than ignoring it [5].
- Check from time to time that the device is updating properly, because automatic updates can stop, for example when storage is full [1].
- Make a backup before updating, so that you can roll back [5].
- Install updates only from official sites or channels [5].
- In a company that has an IT department, it is generally the one in charge of updates [5]. Report to it a computer or device that is not up to date, or an update that fails.

## Pitfalls

- Putting off the restart. Users can often defer or refuse updates, which is why the company seeks to check that computers comply [1].
- Relying on automatic mode without checking it. Automatic updates may happen only under conditions (Wi-Fi, mains power, a specific time, enough storage) and the user may have turned them off [1].
- Forgetting devices outside the fleet, including connected objects [5].
- Believing that the antivirus takes the place of a patch [1].
- Clicking on a fake update. Malicious ads or windows imitate update alerts to get a virus installed [5].
- Keeping a device or software that is no longer supported. Devices and software are supported for a limited time, then they no longer receive updates [1].

## Real cases

### Log4Shell, December 2021

The vulnerability CVE-2021-44228, known as Log4Shell, affects Apache's Log4j logging library, built into thousands of products worldwide [2]. It was disclosed in December 2021 [2]. CISA's advisory sees in it proof that malicious actors can quickly turn a known flaw into an attack and target organizations before they have applied the patch [2]. A specially crafted request allows complete control of a vulnerable system [2].

### Atlassian Confluence, September 2021

The vulnerability CVE-2021-26084 affects Confluence Server and Data Center. Proof-of-concept code was published within a week of its disclosure, and mass exploitation attempts were observed in September 2021 [4]. It thus became one of the most exploited vulnerabilities [4].

### Fortinet FortiOS, from 2020 to 2022

The vulnerability CVE-2018-13379, which affects Fortinet's SSL VPNs, was exploited repeatedly in 2020, 2021 and 2022 [4]. For CISA, this continued exploitation indicates that many organizations have not applied patches in a timely manner and remain vulnerable [4].

## Sources

1. NCSC (UK), "Keeping devices and software up to date", 29 June 2021. https://www.ncsc.gov.uk/collection/device-security-guidance/managing-deployed-devices/keeping-devices-and-software-up-to-date (accessed 10 November 2026)
2. CISA, "2021 Top Routinely Exploited Vulnerabilities", 27 April 2022. https://www.cisa.gov/news-events/cybersecurity-advisories/aa22-117a (accessed 10 November 2026)
3. CISA, "BOD 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities (Revoked)", 3 November 2021. https://www.cisa.gov/news-events/directives/bod-22-01-reducing-significant-risk-known-exploited-vulnerabilities-revoked (accessed 10 November 2026)
4. CISA, "2022 Top Routinely Exploited Vulnerabilities", 3 August 2023. https://www.cisa.gov/news-events/cybersecurity-advisories/aa23-215a (accessed 10 November 2026)
5. Cybermalveillance.gouv.fr, "Pourquoi et comment bien gérer ses mises à jour ?", 26 November 2019. https://www.cybermalveillance.gouv.fr/tous-nos-contenus/bonnes-pratiques/mises-a-jour (accessed 10 November 2026)
6. NIST, "Guide to Enterprise Patch Management Planning: Preventive Maintenance for Technology", 6 April 2022. https://csrc.nist.gov/pubs/sp/800/40/r4/final (accessed 10 November 2026)
7. NCSC (UK), "Vulnerability management guidance". https://www.ncsc.gov.uk/collection/vulnerability-management/guidance (accessed 10 November 2026)
8. MITRE ATT&CK, "Exploit Public-Facing Application, Technique T1190 - Enterprise | MITRE ATT&CK®". https://attack.mitre.org/techniques/T1190/ (accessed 10 November 2026)

---

Original source: Cyberpedia, the public cybersecurity and AI encyclopedia published by Brain. Canonical version: https://startbrain.io/cyberpedia/en/articles/patch-management-deployment-delay/
You may reuse this text freely under the CC BY 4.0 license (https://creativecommons.org/licenses/by/4.0/), provided you credit "Brain, Cyberpedia" with a link to the canonical URL above.
