RA-5 Vulnerability Monitoring and Scanning
Monitors vulnerabilities in acquired and third-party components, including dependencies the organization did not choose directly.
3
artefacts
0
held by a system
1
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
none for this control
periodic reviewEvidence produced at each review
- Remediation records including supplier-dependent fixes · Vulnerability scanner / patch tooling
governing documentDocuments that govern the control
- Coverage of acquired and open source components · Policy repository / GRC workspace
- Dependency or bill of materials data driving the monitoring · Policy repository / GRC workspace
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
- scanning covers deployed systems but not embedded dependencies
- fixes blocked on the supplier with no tracking
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 sheet