1 | Purpose, scope and what changed from Rev 3 | 0 |
2.1 | Four risk responses to a software vulnerability | 0 |
2.2 | The software vulnerability management life cycle | 0 |
2.3 | Executing a patch: prepare, deploy, verify and monitor | 0 |
3.0 | Four principles behind the recommendations | 0 |
3.1.1 | Reduce the number of vulnerabilities entering the environment | 0 |
3.1.2 | Deploy applications so that patching is less likely to disrupt operations | 0 |
3.2.1 | Keep software inventories for all computing assets constantly up to date through automation | 0 |
3.2.2 | Use the inventory capabilities built into platforms and assets | 0 |
3.2.3 | Treat patching per asset: record each asset's technical and mission characteristics | 0 |
3.3 | Define the risk response scenarios to be ready for | 0 |
3.4 | Assign every asset to a maintenance group | 0 |
3.5 | Define a maintenance plan for each group and scenario, with a process for choosing between plans | 0 |
3.5.1a | Routine patching: phased deployment with canary assets | 0 |
3.5.1b | Routine patching: flexibility on timing, then forced installation after a grace period | 0 |
3.5.2 | Emergency patching: the routine approach on a highly accelerated schedule | 0 |
3.5.3a | Emergency mitigation: be ready to apply several kinds of mitigation quickly | 0 |
3.5.3b | Emergency mitigation: replace temporary mitigations with permanent fixes on an enforced schedule | 0 |
3.5.4a | Unpatchable assets: approved long-term risk mitigation methods per maintenance group | 0 |
3.5.4b | Unpatchable assets: add vulnerability-specific mitigations where the long-term methods fall short | 0 |
3.5.4c | Unpatchable assets: periodically re-evaluate the alternatives to patching | 0 |
3.5.5 | Track, monitor and regularly review every exception to a maintenance plan | 0 |
3.6a | Build enterprise metrics from the low-level data already collected | 0 |
3.6b | Make enterprise metrics reflect the relative importance of each asset and vulnerability | 0 |
3.6c | Refresh low-level metrics frequently and keep them accurate | 0 |
3.7 | Take software maintenance into account when procuring software | 0 |