RA-5(3) Vulnerability Monitoring and Scanning | Breadth and Depth of Coverage (RA-5(3))
Vulnerability Monitoring and Scanning | Breadth and Depth of Coverage. Define the breadth and depth of vulnerability scanning coverage
Source: FedRAMP High (NIST SP 800-53 Rev 5 baseline), RA-5(3). 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 FedRAMP High (NIST SP 800-53 Rev 5 baseline) in the compliance library.
A FedRAMP baseline is a subset of NIST SP 800-53 Rev 5, enhancements included.
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
- Scanner configuration showing the target scope and the checks enabled, matched against that definition · Cloud console / configuration management
- Scan results demonstrating the defined breadth was actually reached, with an accounted list of assets not scanned · Vulnerability scanner / patch tooling
- Evidence of authenticated scanning where depth requires it, and the credentials scope used · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- Reconciliation of scan targets against the system component inventory · Vulnerability scanner / patch tooling
governing documentDocuments that govern the control
- The documented definition of breadth and depth of vulnerability scanning coverage, stating which components and which vulnerability classes are in scope · Policy repository / GRC workspace
First move
Common gaps auditors find
- Breadth and depth asserted from the tool default rather than defined by the organisation, which is exactly what this enhancement requires
- Scan coverage never reconciled against the asset inventory, so unscanned hosts are invisible
- Unauthenticated scanning presented as satisfying depth, missing configuration and patch level findings
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-5(2) Update Vulnerabilities to be Scanned · RA-5(4) Discoverable Information