What evidence do auditors commonly ask for on RA.L2-3.11.1 Risk Assessments?

Risk assessment methodology and defined frequency; Completed risk assessment covering CUI processing, storage and transmission; Evidence results are communicated and used.

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

Assessment covers technology risk only, omitting mission and individual impact

CMMC 2.0 · Risk Assessment

`RA.L2-3.11.1` Risk Assessments

Periodically assess the risk that operating organizational systems, and processing, storing or transmitting CUI, creates for operations, assets and individuals.

Source: CMMC 2.0, RA.L2-3.11.1. 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

hard

to go live

Policy repository / GRC workspace

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

none for this control

periodic reviewEvidence produced at each review

Risk assessment methodology and defined frequency · Policy repository / GRC workspace
Completed risk assessment covering CUI processing, storage and transmission · Policy repository / GRC workspace
Evidence results are communicated and used · Policy repository / GRC workspace

governing documentDocuments that govern the control

none for this control

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Assessment covers technology risk only, omitting mission and individual impact
Performed once with no defined recurrence
Results not linked to remediation decisions

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

PS.L2-3.9.2 Personnel Actions · RA.L2-3.11.2 Vulnerability Scan