What evidence do auditors commonly ask for on CM.L2-3.4.2 Security Configuration Enforcement?

Documented security configuration settings or hardening standards; Evidence of enforcement, for example policy objects or configuration management tooling; Compliance scan results against the defined settings.

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

Standards documented but drift never measured

CMMC 2.0 · Configuration Management

`CM.L2-3.4.2` Security Configuration Enforcement

Define security configuration settings for the IT products used in the system and enforce those settings in operation.

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

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

Evidence of enforcement, for example policy objects or configuration management tooling · Cloud console / configuration management
Compliance scan results against the defined settings · Vulnerability scanner / patch tooling

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

Documented security configuration settings or hardening standards · Policy repository / GRC workspace

First move

Automate the pull from your Cloud console / configuration management. Configuration snapshots and change history from the cloud console or IaC repository, diffed against the baseline.

Common gaps auditors find

Standards documented but drift never measured
Settings applied at build with no ongoing enforcement
Products in use with no defined hardening standard

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.1 System Baselining · CM.L2-3.4.3 System Change Management