SI.L2-3.14.1 Flaw Remediation
Identify system flaws, report them, and correct them within a timely period.
3
artefacts
0
held by a system
1
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
none for this control
periodic reviewEvidence produced at each review
- Patch and remediation records with dates showing timeliness · Vulnerability scanner / patch tooling
governing documentDocuments that govern the control
- Flaw identification sources and process · Document repository
- Defined timeframes for correction by severity · Document repository
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Flaws identified but remediation timeframes undefined
- Patching covers operating systems only, omitting applications and firmware
- Reporting step absent so flaws are not tracked
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 sheetSC.L2-3.13.16 Data at Rest · SI.L2-3.14.2 Malicious Code Protection