EvidenceSheet
CMMC 2.0 · Configuration Management

CM.L2-3.4.4 Security Impact Analysis

Analyze the security impact of a proposed change before it is implemented.

Source: CMMC 2.0, CM.L2-3.4.4. 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.

3
artefacts
1
held by a system
1
at each review
moderate
to go live
Cloud console / configuration management
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

  • Security impact analysis recorded within change records · Cloud console / configuration management

periodic reviewEvidence produced at each review

  • Evidence analysis occurs prior to implementation · Cloud console / configuration management

governing documentDocuments that govern the control

  • Criteria defining when deeper analysis is required · Policy repository / GRC workspace

First move

Start with the 1 of 3 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

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

CM.L2-3.4.3 System Change Management · CM.L2-3.4.5 Access Restrictions for Change