United States

NIST SP 800-40 Rev 4

26 controls. 0 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

26 controls 0 frameworks share controls with it United States verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

No measured overlap with another framework in the corpus.

Every control

CodeControlAlso in
1Purpose, scope and what changed from Rev 30
2.1Four risk responses to a software vulnerability0
2.2The software vulnerability management life cycle0
2.3Executing a patch: prepare, deploy, verify and monitor0
3.0Four principles behind the recommendations0
3.1.1Reduce the number of vulnerabilities entering the environment0
3.1.2Deploy applications so that patching is less likely to disrupt operations0
3.2.1Keep software inventories for all computing assets constantly up to date through automation0
3.2.2Use the inventory capabilities built into platforms and assets0
3.2.3Treat patching per asset: record each asset's technical and mission characteristics0
3.3Define the risk response scenarios to be ready for0
3.4Assign every asset to a maintenance group0
3.5Define a maintenance plan for each group and scenario, with a process for choosing between plans0
3.5.1aRoutine patching: phased deployment with canary assets0
3.5.1bRoutine patching: flexibility on timing, then forced installation after a grace period0
3.5.2Emergency patching: the routine approach on a highly accelerated schedule0
3.5.3aEmergency mitigation: be ready to apply several kinds of mitigation quickly0
3.5.3bEmergency mitigation: replace temporary mitigations with permanent fixes on an enforced schedule0
3.5.4aUnpatchable assets: approved long-term risk mitigation methods per maintenance group0
3.5.4bUnpatchable assets: add vulnerability-specific mitigations where the long-term methods fall short0
3.5.4cUnpatchable assets: periodically re-evaluate the alternatives to patching0
3.5.5Track, monitor and regularly review every exception to a maintenance plan0
3.6aBuild enterprise metrics from the low-level data already collected0
3.6bMake enterprise metrics reflect the relative importance of each asset and vulnerability0
3.6cRefresh low-level metrics frequently and keep them accurate0
3.7Take software maintenance into account when procuring software0

Tell me when NIST SP 800-40 Rev 4 files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for NIST SP 800-40 Rev 4, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition