EvidenceSheet
NIST SP 800-53 Rev 5 · SI - System and Information Integrity

SI-2 Flaw Remediation

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 organization-defined time period of the release of the updates; and d. Incorporate flaw remediation into the organizational configuration management process.

Source: NIST SP 800-53 Rev 5, SI-2. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open NIST SP 800-53 Rev 5 in the compliance library.

Base controls and their enhancements. Which apply follows the baseline you are assessed against (for example FedRAMP Moderate or High, or the low, moderate and high baselines of SP 800-53B). Text in square brackets is a parameter your organisation sets.

10
artefacts
2
held by a system
2
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

  • Procedures addressing configuration management · Cloud console / configuration management
  • Installation/change control records for security-relevant software and firmware updates · Document repository

periodic reviewEvidence produced at each review

  • Test results from the installation of software and firmware updates to correct system flaws · Source control / CI pipeline
  • Test of Organizational processes for identifying, reporting, and correcting system flaws; organizational process for installing software and firmware updates; mechanisms supporting and/or implementing the reporting and correcting of system flaws; mechanisms supporting and/or implementing testing software an · Document repository

governing documentDocuments that govern the control

  • System and information integrity policy · Policy repository / GRC workspace
  • System and information integrity procedures · Policy repository / GRC workspace
  • Procedures addressing flaw remediation · Policy repository / GRC workspace
  • List of flaws and vulnerabilities potentially affecting the system · Policy repository / GRC workspace
  • List of recent security flaw remediation actions performed on the system (e.g., list of installed patches, service packs, hot fixes, and other software updates to correct system flaws) · Policy repository / GRC workspace
  • System security plan · Policy repository / GRC workspace

First move

Mostly documents and reviews. Pull the 2 system-held artefacts from your Cloud console / configuration management on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

SI-1 Policy and Procedures · SI-2(2) Flaw Remediation | Automated Flaw Remediation Status