SI-2 Flaw remediation
Requires system flaws to be identified, reported and corrected, updates related to flaw remediation to be tested for effectiveness and side effects before installation, security relevant software and firmware updates to
5
artefacts
1
held by a system
2
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Change records showing remediation passed through configuration management · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Patch deployment records measured against those timeframes · Vulnerability scanner / patch tooling
- Test evidence for updates before production installation · Document repository
governing documentDocuments that govern the control
- Defined installation timeframes for security relevant updates by severity · Document repository
- Exception register for systems that cannot be patched, with compensating controls · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact 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
- Timeframes defined but routinely missed with no risk acceptance recorded
- Firmware and appliance updates outside the patch process entirely
- Emergency patches installed without testing and without a change record
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 sheetSI-1 Policy and procedures for system and information integrity · SI-3 Malicious code protection