RA-5 Vulnerability Monitoring and Scanning
Scan for vulnerabilities monthly (FedRAMP); OS/network weekly, web app monthly, database monthly; remediate within FedRAMP timeframes (HIGH critical 15d, high 30d).
6
artefacts
1
held by a system
3
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
system holds itEvidence a system already holds
- Vulnerability scan reports for internal, external, and authenticated scopes · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- Risk acceptance memos signed by accountable executives · Policy repository / GRC workspace
- Risk assessment methodology approved by leadership · Policy repository / GRC workspace
- Penetration test report with retest evidence · Vulnerability scanner / patch tooling
governing documentDocuments that govern the control
- Control implementation statement for RA-5 citing the system mission and inheritance from common controls · Policy repository / GRC workspace
- Risk register with likelihood, impact, and treatment owners · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Vulnerability scanner / patch tooling 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
- Risk register entries lack named owner or due date
- Penetration tests scope narrow and exclude key applications
- Scan coverage gaps for containerised and ephemeral workloads
- Threat intelligence consumed but not operationalised into detections
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(1) Risk Assessment | Supply Chain Risk Assessment. (a) Assess supply chain risks associated with [Assignment: organization-defined systems, system components, and system services]; and (b) Update the supply chain risk assessment [Assignment: organization-defined frequency], when · RA-5(2) Update Vulnerabilities to be Scanned