SI-2 Flaw Remediation
Review SI-2
1. Set its parameters
No parameters to set for SI-2.
2. Record its status
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.
Discussion
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 addresses both effectiveness of addressing security issues and for 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). In some situations, organizations may determine that the testing of software or firmware updates is not necessary or practical, such as when implementing simple malicious code signature updates. In testing decisions, organizations consider whether security-relevant software or firmware updates are obtained from authorized sources with appropriate digital signatures. 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.
Enhancements
Review SI-2(2)
1. Set its parameters
No parameters to set for SI-2(2).
2. Record its status
Determine if system components have applicable security-relevant software and firmware updates installed using [Assignment: organization-defined automated mechanisms] [Assignment: organization-defined frequency].
Discussion
Automated mechanisms can track and determine the status of known flaws for system components.
Review SI-2(3)
1. Set its parameters
No parameters to set for SI-2(3).
2. Record its status
(a)Measure the time between flaw identification and flaw remediation; and
(b)Establish the following benchmarks for taking corrective actions: [Assignment: organization-defined benchmarks].
Discussion
Organizations determine the time it takes on average to correct system flaws after such flaws have been identified and subsequently establish organizational benchmarks (i.e., time frames) for taking corrective actions. Benchmarks can be established by the type of flaw or the severity of the potential vulnerability if the flaw can be exploited.
Review SI-2(4)
1. Set its parameters
No parameters to set for SI-2(4).
2. Record its status
Employ automated patch management tools to facilitate flaw remediation to the following system components: [Assignment: organization-defined components].
Discussion
Using automated tools to support patch management helps to ensure the timeliness and completeness of system patching operations.
Review SI-2(5)
1. Set its parameters
No parameters to set for SI-2(5).
2. Record its status
Install [Assignment: organization-defined security-relevant software and firmware updates] automatically to [Assignment: organization-defined system components].
Discussion
Due to system integrity and availability concerns, organizations consider the methodology used to carry out automatic updates. Organizations balance the need to ensure that the updates are installed as soon as possible with the need to maintain configuration management and control with any mission or operational impacts that automatic updates might impose (i.e., implementing a staggered deployment strategy).
Review SI-2(6)
1. Set its parameters
No parameters to set for SI-2(6).
2. Record its status
Remove previous versions of [Assignment: organization-defined software and firmware components] after updated versions have been installed.
Discussion
Previous versions of software or firmware components that are not removed from the system after updates have been installed may be exploited by adversaries. Some products may automatically remove previous versions of software and firmware from the system.
Review SI-2(7)
1. Set its parameters
No parameters to set for SI-2(7).
2. Record its status
a.Conduct root cause analysis to identify 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.
Discussion
Root cause analysis includes a wide range of approaches, tools, and techniques to systematically identify the underlying cause of issues or failures to systems and systems components (hardware, software, and firmware). Organizations consider the severity of the incident to determine what root cause analysis method is used and how quickly implementation of the remediation actions. The root cause analysis includes a timeline, missed warning signs, key decisions, gaps, mitigations, and verification of effectiveness. The actions identified to address the source of the issue are implemented and integrated into applicable organizational policy, procedures, and control implementation.
No Enhancements match this Baseline.
ISO/IEC 27001:2022 Crosswalk
* does not fully satisfy the intent of this control (per NIST's mapping notes).