Patch Management Policy

Patch management terms

32 patch management terms, from Binding operational directive to Unpatchable asset, each with a plain definition and a sourced example drawn from NIST SP 800-40 Rev. 4, CISA BOD 26-04, FedRAMP, PCI SSC FAQ 1597, Cyber Essentials v3.3 and Microsoft, read on 19 Nov 2026.

Binding operational directive (BOD)

A directive CISA issues to federal agencies that sets required actions, deadlines for them and actions CISA itself will take.

Example: BOD 26-04, dated 10 Jun 2026, "supersedes and hereby revokes" BOD 19-02 and BOD 22-01 and sets Phase I, II and III actions (CISA). See CISA BOD 26-04.

Calendar days

Days counted on the calendar, weekends and holidays included, as opposed to business days.

Example: BOD 26-04 states "Days are calendar days" (CISA); the HIPAA proposal writes "15 calendar days" (90 FR 898).

Canary assets

A small subset of the assets to be patched that receives a patch first, so that problems show up before the rollout expands.

Example: NIST SP 800-40 Rev. 4 says these assets "act as canaries" and that, in an emergency, the canary period "could last a few minutes to a few hours" (NIST).

Clock start

The event from which a patch deadline is counted. Frameworks differ, so the same number of days can mean different calendar dates.

Example: Cyber Essentials counts "within 14 days of release"; the HIPAA proposal counts from "identifying the need to patch"; BOD 26-04 counts from KEV listing or agency identification, "whichever event occurs first" (NCSC, CISA).

Critical or high-risk update (Cyber Essentials)

In the scheme, an update that fixes vulnerabilities the vendor calls critical or high risk, or that have a "CVSS v3 base score of 7 or above"; it must be installed within 14 days of release.

Example: The scheme adds that a single vendor update covering several issues "must be installed within 14 days" if it covers any critical or high-risk issue (NCSC v3.3). See Cyber Essentials.

Derogation

A permitted departure from a rule, here the choice not to apply a security patch, which must be documented.

Example: NIS2 point 6.6.2 lets entities "choose not to apply security patches when the disadvantages of applying the security patches outweigh the cybersecurity benefits" and requires them to "duly document and substantiate" the reasons (EUR-Lex). See NIS2.

Exception (to a maintenance plan)

A case where an asset does not follow its group's patch plan. A policy's exceptions clause records who may grant one, for how long and with what safeguards.

Example: NIST asks that all exceptions "be reviewed regularly to determine if the maintenance plan can be implemented now" (NIST); the HIPAA proposal allows two documented exceptions (90 FR 898). See the exceptions clause.

Fix on system upgrade

A BOD 26-04 timeline value meaning the vulnerability is remediated at the next scheduled major upgrade or rebuild of the asset.

Example: Rows 15 and 16 of Table 1 (not publicly exposed, not in the KEV, not automatable) carry this value (CISA).

Forensic triage

A check, required alongside the 3-day deadline in three rows of BOD 26-04 Table 1, of whether the asset is already compromised.

Example: BOD 26-04 requires the agency to complete remediation or mitigation within three days "and carry out a forensic triage of the asset" (CISA).

Grace period

A set time during which a rule applies but enforcement or consequences are deferred, or the time a patch policy allows before installation is forced.

Example: FedRAMP's grace period for its vulnerability rules ends 7 Mar 2027 (NTC-0014); NIST advises "forcing installation after a grace period has ended" for routine patches (NIST).

In the KEV

A BOD 26-04 decision point that is Yes when the CVE ID has an entry in CISA's Known Exploited Vulnerabilities Catalog.

Example: On 19 Nov 2026 the catalog's JSON feed reported 1,786 entries, catalog version 2026.11.18 (CISA feed). NIST notes that other organizations "may voluntarily choose to use the catalog to help prioritize their patching efforts" (NIST).

Licensed and supported software

In Cyber Essentials, software the organization has a legal right to use and that a vendor has committed to support with regular vulnerability fixes, with a published date when that stops.

Example: Software that becomes unsupported must be removed from devices or kept out of scope behind a defined subset that blocks traffic to and from the internet (NCSC v3.3).

Live patching

Applying a security fix to running code, usually the Linux kernel, without a reboot.

Example: Canonical Livepatch patches "critical and high severity Linux kernel vulnerabilities" while the system runs (Ubuntu); Red Hat's live kernel patches are for selected Important and Critical CVEs and are supported at no extra cost for 6 months after the errata date (Red Hat); the kernel documentation notes "Only functions that can be traced could be patched" (kernel.org). See systems that cannot be rebooted.

Maintenance group

A set of assets with similar characteristics that generally have the same software maintenance needs for each risk response scenario.

Example: NIST's examples include mobile workforce laptops (tolerant to downtime), an on-premises datacenter (scheduled outage windows) and legacy OT assets whose software cannot be patched (NIST).

Maintenance plan

The actions to take when a scenario occurs for a maintenance group, "including the timeframes for beginning and ending each action."

Example: NIST asks for one plan per group per scenario, so four scenarios and three groups mean up to twelve plans (NIST). See NIST SP 800-40.

Maintenance window

A scheduled period in which a system may be taken out of service for work such as patching. NIST calls the periods scheduled outage windows.

Example: In NIST's example the on-premises datacenter "must adhere to scheduled outage windows for all non-emergency situations" (NIST). See maintenance windows in a policy.

Optional non-security preview update

A Microsoft cumulative update released in the fourth week of the month, typically used for early validation of the monthly security update.

Example: Microsoft lists it beside the monthly security update on the second Tuesday and the as-needed out-of-band update (Microsoft Learn).

Patch compliance rate

The share of in-scope assets or vulnerabilities patched by their deadline. NIST warns that a single organization-wide percentage is not actionable.

Example: NIST's notional matrix shows 95.2 % patched by deadline for critical vulnerabilities on high-importance assets against 81.4 % on low-importance assets; the figures are illustrative (NIST).

Patch SLA

The written time commitment in a patch policy: how long after release or identification a patch must be installed, by severity or asset class.

Example: FedRAMP Class D allows 12 hours at its tightest cell and 192 days at its loosest; Cyber Essentials allows 14 days (FedRAMP, NCSC). See the Patch Window Table.

Patch Tuesday

Microsoft's name for its monthly security update release, on the second Tuesday of each month.

Example: Microsoft publishes it "typically at 10:00 AM Pacific Time"; the next two dates computed from the rule are 8 Dec 2026 and 12 Jan 2027 (Microsoft Learn).

Potential Agency Impact (PAIN)

FedRAMP's measure of how much a vulnerability could affect agencies, written as an "N-rating" from PAIN-5 (shortest timeframes in the tables) to PAIN-2, which sets the timeframe together with internet reachability and likely exploitability.

Example: In Class A and B, PAIN-5 gives 4 days and PAIN-2 gives up to 192 days depending on column (FedRAMP). See FedRAMP.

Publicly exposed

In BOD 26-04, an asset accessible to unauthenticated or untrusted entities via public networks, regardless of its physical or logical location.

Example: If one method finds a system publicly exposed, the value is set to Yes, and removing it from the internet moves the timeline back (CISA).

Remediate (BOD 26-04 sense)

To eliminate the vulnerability "through patching, decommissioning the system, or another action."

Example: CISA says its use is intentionally consistent with DoD Instruction 8531.01, NIST SP 800-53 Rev. 5 and NIST SP 800-216 (CISA).

Resolved and addressed (PCI SSC)

The Council's two verbs for vulnerabilities: resolved means the entity solves or fixes it; addressed means the entity decides whether to resolve it or reduce the risk another way.

Example: FAQ 1597 applies resolved to critical and high-risk vulnerabilities and addressed to lower-risk ones, per the entity's targeted risk analysis (PCI SSC). See PCI DSS.

Risk response

NIST's four choices for a vulnerable asset: accept, mitigate, transfer or avoid. Patching sits under mitigate.

Example: NIST describes mitigate as "Reduce the risk by eliminating the vulnerabilities" and avoid as "Ensure that the risk does not occur by eliminating the attack surface" (NIST).

Security update

Microsoft's term for "a widely released fix for a product-specific, security-related vulnerability."

Example: Microsoft separates it from an update, which "addresses a noncritical, non-security-related bug" (Microsoft Learn).

Service pack and update rollup

Microsoft's terms for tested, cumulative sets of fixes packaged together; an update rollup is "a tested, cumulative set of hotfixes, security updates, critical updates, and updates."

Example: A service pack is "a tested, cumulative set of all hotfixes, security updates, critical updates, and updates" (Microsoft Learn).

Software bill of materials (SBOM)

"A nested inventory, a list of ingredients that make up software components," in CISA's words.

Example: NIST notes some vendors provide machine-consumable data on software composition, such as an SBOM, to help keep inventories current (CISA, NIST).

Targeted risk analysis (TRA)

In PCI DSS, the documented analysis that supports a time frame the entity sets for a requirement.

Example: FAQ 1597 says lower-risk vulnerabilities are addressed "in accordance with the entity's risk as defined and documented in a targeted risk analysis" (PCI SSC).

Technical impact

In BOD 26-04, how much control an exploit gives an adversary: total control or partial control.

Example: Total control includes the case where the exploit "reliably reveals log-in credentials"; a denial-of-service attack is limited control (CISA).

Third-party component

Commercial, open-source or other software the organization acquires and builds into or runs beside its own, which a policy must keep patched.

Example: NIST SSDF task PW.4.4 asks organizations to verify that such components comply with the organization's requirements "throughout their life cycles" (NIST SP 800-218). See third-party patching.

Unpatchable asset

An asset that cannot be easily patched because the vendor provides no patch (end of life) or because it must run uninterrupted.

Example: NIST's scenario 4 uses "isolation or other methods to mitigate the risk" and plans to reevaluate the alternatives periodically (NIST).

Sources

Last reviewed 19 Nov 2026