What evidence do auditors commonly ask for on RA.L2-3.11.2 Vulnerability Scan?

Scan schedule and scope covering systems and applications; Scan reports across the defined period; Evidence of additional scanning triggered by new vulnerability information.

What is the most common gap auditors find on RA.L2-3.11.2?

Infrastructure scanned while applications are not

CMMC 2.0 · Risk Assessment

`RA.L2-3.11.2` Vulnerability Scan

Scan systems and applications for vulnerabilities periodically and again when new vulnerabilities affecting them are identified.

Source: CMMC 2.0, RA.L2-3.11.2. 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 CMMC 2.0 in the compliance library.

artefacts

held by a system

at each review

easy

to go live

Vulnerability scanner / patch tooling

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

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

Scan reports across the defined period · Vulnerability scanner / patch tooling
Evidence of additional scanning triggered by new vulnerability information · Vulnerability scanner / patch tooling

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

Scan schedule and scope covering systems and applications · Policy repository / GRC workspace

First move

Automate the pull from your Vulnerability scanner / patch tooling. Scan schedule, findings and remediation age straight from the scanner; patch compliance from the patch console.

Common gaps auditors find

Infrastructure scanned while applications are not
Scanning periodic only, with no trigger on new vulnerability disclosure
Authenticated scanning not used so coverage is shallow

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

RA.L2-3.11.1 Risk Assessments · RA.L2-3.11.3 Vulnerability Remediation