Level 2 · Configuration Management

CM.L2-3.4.3

System Change Management

A change record should establish what changed, who reviewed it, and whether implementation was authorized.

Score: 1 POA&M: Eligible
GAVII Cybersecurity assessment reference

Official reference

The requirement

Track, review, approve or disapprove, and log changes to organizational systems.

DoD CMMC Assessment Guide, Level 2, version 2.13. CM.L2-3.4.3; requirement and objectives, printed page 96 ↗

Assessment objectives

What must be established

Determine if each applicable objective is satisfied. The labels below follow the cited DoD assessment guide.

  1. [a]

    changes to the system are tracked;

  2. [b]

    changes to the system are reviewed;

  3. [c]

    changes to the system are approved or disapproved; and

  4. [d]

    changes to the system are logged.

MET requires evidence that all applicable objectives are satisfied. Final, approved evidence is needed. A NOT APPLICABLE determination needs a scope-based basis and is equivalent to MET for scoring. Enduring exceptions and temporary deficiencies have specific conditions under 32 CFR 170.24; they are not a general permission to defer implementation.

GAVII Cybersecurity assessment approach

Connect the objective to the evidence

Include infrastructure, applications, cloud settings, and security tooling relevant to the scope. Emergency work still needs a defined process and a retained record.

Assessment focus: objectives [a], [b], [c], [d]. Use the methods together; a single example does not establish every objective.

Examine

Examine change requests, approvals or rejections, implementation records, and system change logs.

Interview

How does the process handle an urgent fix, and how is the resulting system state reconciled with the record?

Demonstrate or test

Trace a recent completed change from request through review, decision, implementation, and logging.

Evidence gaps to look for

  • The ticket is closed without evidence of approval.
  • Cloud-console changes occur outside the recorded process.

GAVII Cybersecurity’s examples illustrate ways to examine, interview, and test. They are not a mandatory artifact list or a guarantee of an assessment result. Combine methods and address every applicable objective in the actual scope.

Assessment constraints

Scoring and POA&M eligibility

Score: 1

If this requirement is NOT MET, deduct 1 point from the Level 2 maximum of 110. The deduction applies to the requirement, not separately to each objective.

Scoring rule ↗

POA&M: Eligible

Potentially eligible only if all Conditional Level 2 criteria are satisfied, including a score of at least 88 out of 110 and timely closeout. Eligibility is not a finding that this requirement is MET.

POA&M rule ↗

Conditional Level 2 requires a score of at least 88 out of 110 and satisfaction of every eligibility condition. A 1-point requirement is not automatically eligible. The permitted POA&M must be closed through the appropriate closeout assessment within 180 days of the Conditional CMMC Status Date. An operational remediation plan does not confer Conditional Status.

Assessment planning

Location and observation

Not specifically listed in CAP P.11

This requirement is not specifically listed in CAP P.11. That does not establish that remote assessment is sufficient: the Lead CCA and C3PAO determine an adequate approach for the actual scope and evidence.

CAP §P.11, pages 10–11 ↗

Check the source

References and related requirements

Program timing and contract applicability can change independently of these requirements. Check current DoD program notices and your solicitation or contract before making a compliance decision. Open the official DoD resource hub.

Get your free consultation.