SI-02 Flaw Remediation
System and Information Integrity
Description
a. Identify, report, and correct system flaws; b. Test software and firmware updates related to flaw remediation for effectiveness and potential side effects before installation; c. Install security-relevant software and firmware updates within [Assignment: organization-defined time period] of the release of the updates; and d. Incorporate flaw remediation into the organizational configuration management process.
Supplemental Guidance
The need to remediate system flaws applies to all types of software and firmware. Organizations identify systems affected by software flaws, including potential vulnerabilities resulting from those flaws, and report this information to designated organizational personnel with information security and privacy responsibilities. Organizations consider establishing a controlled patching environment for mission-critical systems. Security-relevant updates include patches, service packs, and malicious code signatures. Organizations also address flaws discovered during assessments, continuous monitoring, incident response activities, and system error handling. By incorporating flaw remediation into configuration management processes, required remediation actions can be tracked and verified. Organization-defined time periods for updating security-relevant software and firmware may vary based on a variety of risk factors, including the security category of the system, the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw), the organizational risk tolerance, the mission supported by the system, or the threat environment. Some types of flaw remediation may require more testing than other types. Organizations determine the type of testing needed for the specific type of flaw remediation activity under consideration and the types of changes that are to be configuration-managed. Flaw remediation testing analyzes both the effectiveness of addressing security issues and any potential side-effects on functionality, system and system component performance, and operations. When implementing remediation activities, organizations consider the order and timing of updates to validate correct execution within the system environment and to support system and component availability needs (i.e., implementing a staggered deployment strategy). Organizations verify that software and firmware updates come from authorized sources prior to downloading.In testing decisions, organizations consider whether security-relevant software or firmware updates are obtained from authorized sources with appropriate digital signatures.
Enhancements (6)
What NIST adds to this control. Select one to read its statement.
SI-02(02) Automated Flaw Remediation Status ModerateHigh
Determine if system components have applicable security-relevant software and firmware updates installed using [Assignment: organization-defined automated mechanisms] [Assignment: organization-defined frequency].
SI-02(03) Time to Remediate Flaws and Benchmarks for Corrective Actions
a. Measure the time between flaw identification and flaw remediation; and b. Establish the following benchmarks for taking corrective actions: [Assignment: organization-defined benchmarks].
SI-02(04) Automated Patch Management Tools
Employ automated patch management tools to facilitate flaw remediation to the following system components: [Assignment: organization-defined system components].
SI-02(05) Automatic Software and Firmware Updates
Install [Assignment: organization-defined security-relevant software and firmware updates] automatically to [Assignment: organization-defined system components].
SI-02(06) Removal of Previous Versions of Software and Firmware
Remove previous versions of [Assignment: organization-defined software and firmware components] after updated versions have been installed.
SI-02(07) Root Cause Analysis
a. Conduct root cause analysis to identify the underlying causes of issues or failures; b. Develop actions to address the root cause of the issue or failure; c. Implement the actions and monitor the implementation for effectiveness.
Withdrawn by NIST:
- SI-02(01) Central Management, now in PL-09
Patterns that use this control (12)
Grouped by the emphasis each pattern gives it.
Critical (2)
Important (9)
- SP-001 Client Module
- SP-002 Server Module
- SP-011 Cloud Computing Pattern
- SP-023 Industrial Control Systems
- SP-026 PCI Full Environment
- SP-028 Secure DevOps Pipeline Pattern
- SP-043 Security Metrics and Measurement
- SP-046 External Attack Surface Management
- SP-054 CBDC and Digital Currency Infrastructure (draft)
Standard (1)
MITRE ATT&CK Techniques (84)
ATT&CK v16.1Techniques mitigated by this control, mapped via CTID.