03.14.01 Flaw Remediation
Identify, report, and correct system flaws; test software and firmware updates for effectiveness and side effects before installation; install security-relevant updates within defined time periods.
Source: NIST SP 800-171 Rev 3, 03.14.01. 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-171 Rev 3 in the compliance library.
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
- Patch reports · Vulnerability scanner / patch tooling
- Patch testing evidence · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Patch management policy · Policy repository / GRC workspace
- SLA tracking · Policy repository / GRC workspace
First move
Common gaps auditors find
- critical patches past SLA
- no test cycle
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 sheet03.13.15 Session Authenticity · 03.14.02 Malicious Code Protection