What evidence do auditors commonly ask for on CM.L2-3.4.3 System Change Management?

Change records showing request, review, decision and implementation; Change approval authority definition; Evidence unapproved changes are detected.

What is the most common gap auditors find on CM.L2-3.4.3?

Emergency changes bypass the process with no retrospective record

CMMC 2.0 · Configuration Management

`CM.L2-3.4.3` System Change Management

Track changes to systems, review them, approve or reject them, and log the decision together with the change.

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

artefacts

held by a system

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

Change records showing request, review, decision and implementation · Cloud console / configuration management

periodic reviewEvidence produced at each review

Evidence unapproved changes are detected · Cloud console / configuration management

governing documentDocuments that govern the control

Change approval authority definition · 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

Emergency changes bypass the process with no retrospective record
Approvals recorded without evidence of review
Infrastructure changes tracked but application changes not

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.2 Security Configuration Enforcement · CM.L2-3.4.4 Security Impact Analysis