Patch Management Policy

Patch management asset inventory step

A patch inventory lists each asset, its software down to package level, its owner and its outage limits. NIST SP 800-40 Rev. 4 section 3.2 says updating inventories monthly or quarterly by vulnerability scan “should no longer be used”; it asks for automated, continuous discovery. Read 19 Nov 2026.

Inputs and what the step must produce

Step 1 of the nine-step process feeds every later step: without it, monitoring for releases has nothing to match against. NIST asks for software inventories of “physical and virtual computing assets, including OT, IoT, and container assets,” and accepts that a complete one may be impossible: the realistic goal is “a close-to-comprehensive inventory” kept by automation (NIST SP 800-40 Rev. 4, section 3.2).

Two further sources can fill gaps. Platform interfaces in cloud services can report software continuously, and a vendor's software bill of materials adds package-level detail. CISA describes an SBOM as “a nested inventory, a list of ingredients that make up software components” (CISA, SBOM).

Fields to record per asset

Source: NIST SP 800-40 Rev. 4, section 3.2, read 19 Nov 2026. The lists are examples in the source; an organization chooses its own.
GroupFields NIST lists as examplesUsed later by
TechnicalPlatform type (IT, OT, IoT, mobile, cloud, VM); who administers it; the tool that manages it; network connectivity; controls already in place; primary users and their privilegesDeploy, verify
Mission or businessRole and importance; laws or policies that set how soon a flaw must be fixed; contractual limits on patching; limits on risk responsesAssess and prioritize, approve and schedule

The mission column is where a patch window comes from. NIST's own examples of such a limit are a “highly regulated asset” that can only be patched by its manufacturer after testing and certification, and an asset that “can only be rebooted during a monthly maintenance outage.” Record those as fields, not as notes, so the maintenance group can be built by filter.

A fact that changes the unit of work

NIST's guidance is that patching is approached “from a per-asset perspective,” and decisions should not rest on software and version alone, because each asset's characteristics give context. CISA's BOD 26-04 (issued 10 Jun 2026) repeats the idea: its footnote defines an asset as “the unit of work for patching as defined in NIST SP 800-40 Rev 4” (CISA, BOD 26-04). A policy that counts findings per software package instead of per asset cannot reproduce that timeline logic.

The record to keep

  • The inventory export with a date and the discovery method for each asset (agent, platform interface, network discovery).
  • The date each asset was last seen, so stale entries are visible.
  • The maintenance group assigned to each asset and who approved the assignment.
  • For NIST, the patching history per asset: it “may be particularly helpful to incident responders during an investigation.”

How the inventory requirement is worded in a policy is on asset inventory requirement.

Sources

Last reviewed 19 Nov 2026