SI-2: Flaw Remediation
PF v1.0 References:
- NIST Special Publication 800-53 Revision 5:
- SI-2: Flaw Remediation
- Identifies, reports, and corrects information system flaws;
- Tests software and firmware updates related to flaw remediation for effectiveness and potential side effects before installation;
- Installs security-relevant software and firmware updates within [Assignment: organization-defined time period] of the release of the updates; and
- Incorporates flaw remediation into the organizational configuration management process.
Organizations identify information systems affected by announced software flaws including potential vulnerabilities resulting from those flaws, and report this information to designated organizational personnel with information security responsibilities. Security-relevant software updates include, for example, patches, service packs, hot fixes, and anti-virus signatures. Organizations also address flaws discovered during security assessments, continuous monitoring, incident response activities, and system error handling. Organizations take advantage of available resources such as the Common Weakness Enumeration (CWE) or Common Vulnerabilities and Exposures (CVE) databases in remediating flaws discovered in organizational information systems. By incorporating flaw remediation into ongoing configuration management processes, required/anticipated remediation actions can be tracked and verified. Flaw remediation actions that can be tracked and verified include, for example, determining whether organizations follow US-CERT guidance and Information Assurance Vulnerability Alerts. Organization-defined time periods for updating security-relevant software and firmware may vary based on a variety of factors including, for example, the security category of the information system or the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw). Some types of flaw remediation may require more testing than other types. Organizations determine the degree and type of testing needed for the specific type of flaw remediation activity under consideration and also the types of changes that are to be configuration-managed. In some situations, organizations may determine that the testing of software and/or firmware updates is not necessary or practical, for example, when implementing simple anti-virus signature updates. Organizations may also consider in testing decisions, whether security-relevant software or firmware updates are obtained from authorized sources with appropriate digital signatures.
SI-2(1): Central Management
The organization centrally manages the flaw remediation process.
SI-2(2): Automated Flaw Remediation Status
The organization employs automated mechanisms [Assignment: organization-defined frequency] to determine the state of information system components with regard to flaw remediation.
SI-2(3): Time To Remediate Flaws / Benchmarks For Corrective Actions
The organization: Measures the time between flaw identification and flaw remediation; and Establishes [Assignment: organization-defined benchmarks] for taking corrective actions.
SI-2(5): Automatic Software / Firmware Updates
The organization installs [Assignment: organization-defined security-relevant software and firmware updates] automatically to [Assignment: organization-defined information system components].
SI-2(6): Removal Of Previous Versions Of Software / Firmware
The organization removes [Assignment: organization-defined software and firmware components] after updated versions have been installed.