Skip to content
All CMMC practices
CMMC · Rev 2.13L2CM · Configuration Management

CM.L2-3.4.2

Security Configuration Enforcement

Requirement

Establish and enforce security configuration settings for information technology products employed in organizational systems.

Assessment objectives

An assessor checks each lettered objective separately. The letters in brackets elsewhere on this page, such as [a] or [b,c], refer to these.

Determine if:

  1. asecurity configuration settings for information technology products employed in the system are established and included in the baseline configuration; and
  2. bsecurity configuration settings for information technology products employed in the system are enforced.

From the CMMC Level 2 Assessment Guide v2.13 · publisher approved 2026-10-31.

How to implement

Pick a recognized hardening standard for each product you use (CIS Benchmarks, DISA STIGs or Microsoft security baselines), apply the most restrictive settings your business can live with, write down and approve any deviations, and then enforce the settings centrally so they cannot drift. Check regularly, with a compliance scan or by comparing sample systems with the baseline, that the settings are actually in place.

The minimum for a small organization · Expert CMMC's reading, not official text

Choose the most restrictive security settings each product you use can run with, usually from a published benchmark, and make them part of the baseline [a]; then make sure systems actually run with those settings [b]. Record any setting you cannot apply, with the reason and who approved it. Pushing settings from a central tool and checking for drift is the common way to keep them in force.

Required outcome: what the requirement or its objectives call for. Recommended way: one common way to get there. Going further: worth doing, more than this practice asks.

  1. 1
    Required outcomePolicyEstablish the most restrictive security configuration settings appropriate for each IT product in the system and include them in the baseline configuration.[a]
  2. 2
    Required outcomeTechnicalApply the settings to every system they cover and keep them in force, recording each approved deviation.[b]

    You can tell it worked when sample systems, checked with a compliance scan or by comparing their settings with the baseline, match it apart from recorded deviations.

  3. 3
    Recommended wayPolicyFor each product in the inventory (Windows, macOS, servers, firewall, switches, Microsoft 365 or Google Workspace tenant, browsers, Office), name the hardening source and level you follow, for example CIS Level 1, the Microsoft security baseline or the DISA STIG, and include those settings in the baseline configuration (CM.L2-3.4.1).[a]
  4. 4
    Recommended wayProcessTailor and test: apply the settings to a pilot group, record any setting you cannot apply with the business reason, the risk, any compensating measure and the approver, and keep this deviation log with the baseline.[a]
  5. 5
    Recommended wayTechnicalEnforce centrally: Intune security baselines and settings catalog profiles or Group Policy for Windows; MDM profiles for macOS and mobile; configuration templates and backups for network devices; tenant security settings for Microsoft 365 or Google Workspace. Remove local admin rights so users cannot change the settings.[b]
  6. 6
    Recommended wayTechnicalVerify and correct drift: run a compliance scan (CIS-CAT, SCAP Compliance Checker, Wazuh SCA, Defender Vulnerability Management or Nessus compliance audits; CISA ScubaGear for Microsoft 365) at least quarterly and after major changes, fix failures or add them to the deviation log, and keep the reports.[b]

Evidence to collect

Artifacts that show the practice is implemented and operating. Tags show which assessment objectives each one supports.

A process you started recently is shown honestly by its dated procedure, the first record it produced and the date it began. No evidence row needs more history than the process has existed, and the review periods shown are suggestions unless a guide page or regulation is named beside them.

Security configuration standard with deviation log[a]

Also supports 1 other practice: keep it once

Configuration compliance scan reports[b]

The detail for 3 evidence items: how to produce each, how fresh it must be, what it must include and what it does not show.

Free with an account. Create a free account or sign in.

How assessors check

What an assessor examines, asks and tests: 3 notes.

Free with an account. Create a free account or sign in.

Tools and products

Named options a contractor can adopt, with an honest cost tier. The industry standard is listed even when it is expensive, alongside what is free and acceptable for a very small shop.

CIS Benchmarks and CIS-CAT LiteHardening standard and scannerFree
DISA STIGs and SCAP Compliance CheckerDoD hardening standard and scannerFree
Microsoft Intune security baselinesEnforcementPaid
CISA ScubaGearMicrosoft 365 configuration assessmentFree
Wazuh security configuration assessmentOpen-source compliance scanningFree
Tenable Nessus ProfessionalVulnerability and compliance scanningPaid

10 dated vendor facts and notes on 6 products for this practice: what each assumes, what it does not cover and what stays yours.

Free with an account. Create a free account or sign in.

Editorial mentions, not endorsements. Pricing and tiers change; confirm with the vendor and check FedRAMP or GCC High availability where CUI is involved.

Common pitfalls

  • Saying 'we follow CIS' with no record of which benchmark, which level and which settings were excepted.
  • Settings applied once by hand and never enforced, so they drift as devices are rebuilt or updated.
  • Hardening workstations but leaving firewalls, switches, printers and the cloud tenant on defaults.
  • No scan evidence, so there is no proof the settings are actually in place.

Platform notes

  • Microsoft 365 (GCC / GCC High)
  • Google Workspace
  • On-premises or MSP-managed

Notes for 3 platforms.

Free with an account. Create a free account or sign in.

Related practices: CM.L2-3.4.1, CM.L2-3.4.6, CM.L2-3.4.7, RA.L2-3.11.2, CM.L3-3.4.2e

Editorial implementation guidance published November 14, 2026. It is not part of the official requirement and does not replace the assessment guide.

The NIST requirements this practice is built on, what NIST made of each in the newer edition, and the SP 800-53 controls behind them, each from an official NIST or DoD table. Open any one to read it and see every CMMC practice it supports.

NIST SP 800-171 Rev 2

3.4.2

SP 800-171 Rev 3

03.04.02

SP 800-53 Rev 4

CM-2CM-6CM-8CM-8 (1)

SP 800-53 Rev 5

CM-2DCM-6DSCM-8DCM-8(1)D
How these were reached
  • CM-2 · Baseline Configuration
    • D SP 800-171 Rev 2 Appendix D → SP 800-53 Rev 4 control → NIST's Rev 4 → Rev 5 comparison · via 800-53 Rev 4 CM-2 → 800-53 Rev 5 CM-2
  • CM-6 · Configuration Settings
    • D SP 800-171 Rev 2 Appendix D → SP 800-53 Rev 4 control → NIST's Rev 4 → Rev 5 comparison · via 800-53 Rev 4 CM-6 → 800-53 Rev 5 CM-6
    • S source control of the SP 800-171 Rev 3 or SP 800-172 Rev 3 requirement (NIST OSCAL) · via 800-171 Rev 3 03.04.02 → 800-53 Rev 5 CM-6NIST: 03.04.02 also: 3.13.7 addressed by
  • CM-8 · System Component Inventory
    • D SP 800-171 Rev 2 Appendix D → SP 800-53 Rev 4 control → NIST's Rev 4 → Rev 5 comparison · via 800-53 Rev 4 CM-8 → 800-53 Rev 5 CM-8
  • CM-8(1) · System Component Inventory | Updates During Installation and Removal
    • D SP 800-171 Rev 2 Appendix D → SP 800-53 Rev 4 control → NIST's Rev 4 → Rev 5 comparison · via 800-53 Rev 4 CM-8 (1) → 800-53 Rev 5 CM-8(1)

Rev 5 paths: D SP 800-171 Rev 2 Appendix D → SP 800-53 Rev 4 control → NIST's Rev 4 → Rev 5 comparison; S source control of the SP 800-171 Rev 3 or SP 800-172 Rev 3 requirement (NIST OSCAL); C SP 800-172 (Feb 2021) Appendix C. NIST also names this Rev 3 requirement as the successor of other withdrawn requirements: open “How these were reached” under the Rev 5 controls for which, in NIST's words.

Where each link comes from (11 links from 5 official documents)

32 CFR Part 170 Office of the Federal Register / GPO

  • CM.L2-3.4.2 → 3.4.2“Level 2 security requirement”32 CFR 170.14(c)(1) numbering (REQ is the NIST SP 800-171 R2 requirement number) and 170.14(c)(3)

NIST SP 800-171 Rev 2 → Rev 3 change analysis NIST

  • 3.4.2 → 03.04.02“Significant Change”sheet "Change Analysis 800-171 R2-R3" row 37

NIST SP 800-171 Rev 2 NIST

  • 3.4.2 → CM-2“Appendix D mapping”p.81 Table D-4
  • 3.4.2 → CM-6“Appendix D mapping”p.81 Table D-4
  • 3.4.2 → CM-8“Appendix D mapping”p.81 Table D-4
  • 3.4.2 → CM-8 (1)“Appendix D mapping”p.81 Table D-4

NIST SP 800-53 Rev 4 → Rev 5 comparison NIST

  • CM-2 → CM-2“Changes control text Adds parameter”sheet "Rev4 Rev5 Compared" row 269
  • CM-6 → CM-6“Changes control text Changes parameter Changes discussion”sheet "Rev4 Rev5 Compared" row 297
  • CM-8 → CM-8“Adds control text Changes discussion”sheet "Rev4 Rev5 Compared" row 312
  • CM-8 (1) → CM-8(1)“Adds discussion”sheet "Rev4 Rev5 Compared" row 313

NIST SP 800-171 Rev 3 (OSCAL) NIST

  • 03.04.02 → CM-6“Source control”control 03.04.02 link rel=reference (CM-06)

Trace notes

Notes marked NIST state what the owners' own files say. Notes marked Expert CMMC note are our reading of the links, not official guidance. Neither is a crosswalk link.

About this practice

  • Expert CMMC note

    Appendix D maps CM-2, CM-6, CM-8 and CM-8(1) jointly to 3.4.1-3.4.2. For 3.4.2 the direct source is CM-6 (configuration settings); CM-2 and CM-8 serve 3.4.1.

    Relies on: NIST SP 800-171 Rev 2

About SP 800-171 Rev 2 3.4.2

  • Expert CMMC note3.4.2 ↔ CM-2 (SP 800-53 Rev 4)

    NIST SP 800-171 Rev 2 Appendix D maps basic requirements 3.4.1 and 3.4.2 jointly to CM-2, CM-6, CM-8, CM-8(1). CM-2 mainly supports 3.4.1, not 3.4.2 specifically.

    Relies on: NIST SP 800-171 Rev 2, p.81, Appendix D, Table D-4

  • Expert CMMC note3.4.2 ↔ CM-8 (SP 800-53 Rev 4)

    NIST SP 800-171 Rev 2 Appendix D maps basic requirements 3.4.1 and 3.4.2 jointly to CM-2, CM-6, CM-8, CM-8(1). CM-8 mainly supports 3.4.1, not 3.4.2 specifically.

    Relies on: NIST SP 800-171 Rev 2, p.81, Appendix D, Table D-4

  • Expert CMMC note3.4.2 ↔ CM-8 (1) (SP 800-53 Rev 4)

    NIST SP 800-171 Rev 2 Appendix D maps basic requirements 3.4.1 and 3.4.2 jointly to CM-2, CM-6, CM-8, CM-8(1). CM-8(1) mainly supports 3.4.1, not 3.4.2 specifically.

    Relies on: NIST SP 800-171 Rev 2, p.81, Appendix D, Table D-4

Further discussion

Information security is an integral part of a company’s configuration management process. Security-related configuration settings are customized to satisfy the company’s security requirements and are applied them to all systems once tested and approved. The configuration settings must reflect the most restrictive settings that are appropriate for the system. Any required deviations from the baseline are reviewed, documented, and approved. Example You manage baseline configurations for your company’s systems, including those that process, store, and transmit CUI. As part of this, you download a secure configuration guide for each of your asset types (servers, workstations, network components, operating systems, middleware, and applications) from a well-known and trusted IT security organization. You then apply all of the settings that you can while still ensuring the assets can perform the role for which they are needed. Once you have the configuration settings identified and tested, you document them to ensure all applicable machines can be configured the same way [a,b]. Potential Assessment Considerations • Do security settings reflect the most restrictive settings appropriate [a]? • Are changes or deviations to security settings documented [b]?

Practice guide notes

Implementation guidance

Editorial examples to help you plan. Adapt them to your environment; the official requirement and objectives remain authoritative.

In plain language

Define and enforce secure configuration settings for the technology you use.

Implementation example

Example from the source assessment guide (not a mandatory implementation): You manage baseline configurations for your company’s systems, including those that process, store, and transmit CUI. As part of this, you download a secure configuration guide for each of your asset types (servers, workstations, network components, operating systems, middleware, and applications) from a well-known and trusted IT security organization. You then apply all of the settings that you can while still ensuring the assets can perform the role for which they are needed. Once you have the configuration settings identified and tested, you document them to ensure all applicable machines can be configured the same way [a,b].

Evidence examples

Examples suggested by the source guide (not an exhaustive or mandatory checklist): Configuration management policy; baseline configuration; procedures addressing configuration settings for the system; configuration management plan; system security plan; system design documentation; system configuration settings and associated documentation; security configuration checklists; evidence supporting approved deviations from established configuration settings; change control records; system audit logs and records; other relevant documents or records

Common mistakes

Documenting a baseline without applying it or checking for drift.

Track this in a workspace

The compliance workspace tracks each objective, its evidence and the tasks to close gaps. It is open to invited contractors while in pilot: request access below.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Source: DoD CIO · https://dodcio.defense.gov/CMMC/