Patch Management Policy

Patch management asset inventory

NIST SP 800-40 Rev. 4 says inventories updated monthly or quarterly by a vulnerability scan should no longer be the model, and asks for constant updates by automation. The inventory clause names the fields recorded for every asset, how often discovery runs, and who owns an asset found without one.

What the section must say

  • The fields recorded for each asset.
  • How the inventory is kept current (automatic discovery, platform APIs, agent reporting), and how often.
  • Who owns an asset found without an owner, and by when.
  • That patching decisions use the per-asset record, not only the software version.

NIST SP 800-40 Rev. 4 section 3.2 says organizations should establish and constantly maintain up-to-date software inventories for physical and virtual assets, including OT, IoT and container assets, in one inventory or several. A realistic goal is a close-to-comprehensive inventory built on automation. If scans supply software inventory, they need sufficient access, which means authenticated scanning, to detect changes.

Fields NIST lists

Characteristics listed in NIST SP 800-40 Rev. 4 section 3.2, read 19 Nov 2026.
GroupField to recordWhy it matters to a patch decision
TechnicalPlatform type (IT, OT, IoT, mobile, cloud, VM)Selects the maintenance plan
TechnicalWho administers it (IT, third party, end user, vendor, shared responsibility)Decides who can act
TechnicalHow it is managed (endpoint tool, VM manager, container manager)Decides how the patch is delivered
TechnicalNetwork connectivity and existing security controlsSets exposure and available mitigations
TechnicalPrimary users or interconnected services and their privilegesSets blast radius
MissionRole and importance to the organizationSets the window tier
MissionLaws, regulations or policies on how soon a vulnerability must be addressedSets the strictest window
MissionContractual restrictions on patchingSets who may patch
MissionRestrictions on risk responses, for example reboot only in a monthly maintenance outageSets the schedule

Sample wording

3.1 [Company name] keeps an inventory of every asset in scope. For each asset it records: owner; platform type; administering party; management tool; internet exposure; maintenance group; legal, contractual or outage limits on patching; installed software and versions; date of last patch.

3.2 The inventory is updated by automated discovery at least [weekly] and by platform or agent reporting [daily] where available. A scan that cannot log in to the asset does not count as a software inventory.

3.3 An asset with no owner is assigned one within [5] working days or isolated from the network.

3.4 Software bills of materials supplied by vendors are attached to the asset record where they exist.

Common mistakes

  • Quarterly refresh. NIST says monthly or quarterly updating by scan was acceptable when assets were static and inside a fixed perimeter, and that this model should no longer be used.
  • Version-only records. NIST says risk response and prioritization should not be based solely on which software and versions are in use, because each asset has its own technical and mission context.
  • No patch history. NIST adds that a per-asset patching history may help incident responders in an investigation.
  • SBOMs treated as the inventory. CISA describes an SBOM as a nested inventory of software components, a list of ingredients; it describes software, not the assets that run it, and CISA lists 2026 updates to the SBOM minimum elements on its SBOM page (headline read, guidance not opened).

Next: severity and patch windows. The first step of the monthly cycle uses this inventory: process step 1. The fuller variant for estates with several inventory systems is the enterprise template.

Sources

Last reviewed 19 Nov 2026