Patch Management Policy

CIS Control 7 patch management

CIS Controls v8, Control 7 (Continuous Vulnerability Management), sets cadences rather than deadlines: monthly or more frequent for operating system and application patching and for remediation, quarterly for internal scans. It has no severity tiers. Safeguards 7.1 to 7.7 were quoted from the August 2023 guide on 19 Nov 2026.

Build a policy with CIS Controls v8

4.3 Patch windows

CIS Controls v8

SeverityWindow3143090180 daysClock startsSet by
CriticalMonthly, or more frequentNot stated (a cadence)CIS Controls v8, 7.3 and 7.4
HighMonthly, or more frequentNot stated (a cadence)CIS Controls v8, 7.3 and 7.4
MediumMonthly, or more frequentNot stated (a cadence)CIS Controls v8, 7.3 and 7.4
LowMonthly, or more frequentNot stated (a cadence)CIS Controls v8, 7.3 and 7.4

Framework clauses, read 19 Nov 2026:

  • CIS Controls v8: 7.3: monthly, or more frequent; 7.4: monthly, or more frequent; 7.7: monthly, or more frequent

7.37.4to policy 4.3

Cadence, not a clock

Control 7 is the only framework in the Patch Window Table that expresses patch timing as a recurring cadence with no severity input. Safeguards 7.3 and 7.4 tell an enterprise to perform operating system and application updates "through automated patch management on a monthly, or more frequent, basis." Nothing in the text says how long after a vendor release an update may wait, or that critical items run on a faster track.

The control's stated aim is to "remediate, and minimize, the window of opportunity for attackers" and to "monitor public and private industry sources for new threat and vulnerability information."

7.37.47.7to policy 4.3

Safeguards 7.1 to 7.7 as published

CIS Controls v8, Control 07 safeguards, from the August 2023 guide PDF. Implementation groups as marked in the safeguard index. The v8.1 wording was not read on 19 Nov 2026.
SafeguardText (verbatim)CadenceImplementation groups
7.1 Establish and Maintain a Vulnerability Management Process"Establish and maintain a documented vulnerability management process for enterprise assets."Documentation reviewed annually or on significant changeIG1, IG2, IG3
7.2 Establish and Maintain a Remediation Process"Establish and maintain a risk-based remediation strategy documented in a remediation process, with monthly, or more frequent, reviews."Monthly or more frequent review of the strategyIG1, IG2, IG3
7.3 Perform Automated Operating System Patch Management"Perform operating system updates on enterprise assets through automated patch management on a monthly, or more frequent, basis."Monthly or more frequentIG1, IG2, IG3
7.4 Perform Automated Application Patch Management"Perform application updates on enterprise assets through automated patch management on a monthly, or more frequent, basis."Monthly or more frequentIG1, IG2, IG3
7.5 Perform Automated Vulnerability Scans of Internal Enterprise Assets"Perform automated vulnerability scans of internal enterprise assets on a quarterly, or more frequent, basis."Quarterly or more frequent (scans)IG2, IG3
7.6 Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets"Perform scans on a monthly, or more frequent, basis."Monthly or more frequent (scans)IG2, IG3
7.7 Remediate Detected Vulnerabilities"Remediate detected vulnerabilities in software through processes and tooling on a monthly, or more frequent, basis, based on the remediation process."Monthly or more frequentIG2, IG3

Two details change how a policy should read the table. Safeguard 7.2's monthly cadence is for reviewing the remediation strategy, not for installing patches. And 7.5 and 7.6 are scanning cadences, so they belong in a vulnerability-scanning clause, not in the patch window.

7.37.47.7to policy 4.3

What is missing from the page

The CIS Controls v8.1 safeguard text could not be read on 19 Nov 2026: the v8.1 download sits behind a form and the control 7 page on cisecurity.org shows only the overview. Every figure here is therefore v8 as published in August 2023. A policy that cites v8.1 should check the 7.3, 7.4 and 7.7 wording before copying it.

7.37.47.7to policy 4.3

What a policy must write to meet it

  • A documented vulnerability management process, reviewed at least yearly and after significant change (7.1).
  • A written remediation strategy that is risk-based and reviewed monthly or more often (7.2).
  • A monthly or faster automated cycle for operating system updates and for application updates, stated separately (7.3, 7.4).
  • For IG2 and IG3 enterprises, a monthly or faster remediation cadence tied to the remediation process (7.7) and scan cadences of quarterly internal and monthly external (7.5, 7.6).

Because Control 7 has no severity tiers, a policy that adopts it still needs a separate rule for urgent items. The policy section on severity and patch windows shows how a severity table sits above a baseline cadence, and NIST SP 800-40 is the planning guide for the faster tracks.

Evidence the text implies

The safeguards ask for documents and records, not named artifacts: the vulnerability management process with its review date, the remediation process with monthly review dates, and automated patch management output showing the cycle ran. The guide names no assessor, so what a given assessor accepts is outside this page.

Sources

Last reviewed 19 Nov 2026