RA-5 Vulnerability Monitoring and Scanning
a. Monitor and scan for vulnerabilities in the system and hosted applications organization-defined frequency and/or randomly in accordance with organization-defined process and when new vulnerabilities potentially affecting the system are identified and reported; b. Employ vulnerability monitoring tools and techniques that facilitate interoperability among tools and automate parts of the vulnerability management process by using standards for: 1. Enumerating platforms, software flaws, and improper configurations; 2. Formatting checklists and test procedures; and 3. Measuring vulnerability impact; c. Analyze vulnerability scan reports and results from vulnerability monitoring; d. Remediate legitimate vulnerabilities organization-defined response times in accordance with an organizational assessment of risk; e. Share information obtained from the vulnerability monitoring process and control assessments with organization-defined personnel or roles to help eliminate similar vulnerabilities in other systems; and f. Employ vulnerability monitoring tools that include the capability to readily update the vulnerabilities to be scanned.
Source: NIST SP 800-53 Rev 5, RA-5. 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.
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
- Vulnerability scanning results · Vulnerability scanner / patch tooling
- Patch and vulnerability management records · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- Risk assessment · Policy repository / GRC workspace
- Assessment report · Policy repository / GRC workspace
- Test of Organizational processes for vulnerability scanning, analysis, remediation, and information sharing; mechanisms supporting and/or implementing vulnerability scanning, analysis, remediation, and information sharing · Vulnerability scanner / patch tooling
governing documentDocuments that govern the control
- Risk assessment policy · Policy repository / GRC workspace
- Procedures addressing vulnerability scanning · Policy repository / GRC workspace
- Vulnerability scanning tools and associated configuration documentation · Policy repository / GRC workspace
- System security plan · Policy repository / GRC workspace
First move
Common gaps auditors find
- Vulnerability scans are not run at the defined frequency or when new vulnerabilities affecting the system are reported
- Legitimate vulnerabilities from scan reports remain unremediated beyond the organization-defined response times
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 sheetRA-3(4) Risk Assessment | Predictive Cyber Analytics · RA-5(2) Vulnerability Monitoring and Scanning | Update Vulnerabilities to Be Scanned