United Statesstandard

CMMC Level 2

Without CMMC Level 2 certification, your organisation cannot bid on or retain US Department of Defense contracts involving Controlled Unclassified Information.

Mapped to Microsoft controls
Effective DateDecember 2024 (final rule)
Enforcement BodyUS Department of Defense (DoD) via C3PAOs
Penalty FrameworkNon-compliance results in inability to bid on DoD contracts containing the CMMC clause (DFARS 252.204-7021). Existing contracts may not be renewed. False claims of compliance are subject to the False Claims Act, which carries treble damages and per-claim penalties of $11,000-$23,000. The DoD is also implementing a phased enforcement approach where contractors self-assess initially but must achieve third-party certification by the time it appears in their contract requirements.

The Cybersecurity Maturity Model Certification (CMMC) 2.0 is the US Department of Defense's framework for protecting Controlled Unclassified Information (CUI) across the defence industrial base. Level 2 aligns directly with the 110 security requirements of NIST SP 800-171 Revision 2.

For UK-based suppliers to the US DoD, CMMC compliance is increasingly a contractual prerequisite. The challenge is significant: the 110 requirements span access control, audit and accountability, configuration management, identification and authentication, incident response, and more.

StremarControl engineers and operates the Microsoft-native controls required for CMMC mandates, translating NIST 800-171 requirements into Microsoft 365 GCC configurations—implementing controls that satisfy each requirement, producing structured evidence, and maintaining compliance through continuous monitoring to enable UK defence suppliers to compete for US DoD contracts.

Why This Matters Now

If your organisation handles Controlled Unclassified Information (CUI) as part of the US defence supply chain - whether as a prime contractor or a Tier 2/3 supplier - CMMC Level 2 certification will be a contractual requirement embedded in DoD solicitations. Without it, you cannot bid on or renew contracts involving CUI. For UK-based defence suppliers, this creates a dual compliance burden: UK Cyber Essentials Plus for MOD contracts and CMMC Level 2 for US DoD work. The appropriate Microsoft cloud depends on the data type, contractual requirements, and export-control scope. GCC High commonly supports CMMC Level 2/3 and ITAR-sensitive scenarios when configured appropriately.

Scope & Applicability

CMMC Level 2 applies to any organisation in the Defence Industrial Base (DIB) that processes, stores, or transmits Controlled Unclassified Information (CUI) as defined by NIST SP 800-171. This includes prime contractors, subcontractors at all tiers, and suppliers who handle CUI even incidentally. The scope encompasses all information systems, network segments, and endpoints that process CUI. For M365 environments, the CUI enclave must be architecturally isolated - typically via M365 GCC or GCC High with dedicated Conditional Access policies, sensitivity labels, and DLP rules scoped to CUI data types.

Core Obligations

01
AC.L2-3.1.1 to 3.1.22

Access Control

Limit system access to authorised users, processes, and devices. Control CUI flow, employ least privilege, and enforce separation of duties.

02
AU.L2-3.3.1 to 3.3.9

Audit and Accountability

Create, protect, and retain system audit records. Ensure actions can be uniquely traced to individual users.

03
IA.L2-3.5.1 to 3.5.11

Identification and Authentication

Identify and authenticate users, devices, and processes. Use multi-factor authentication for network and privileged access.

04
MP.L2-3.8.1 to 3.8.9

Media Protection

Protect, control, sanitise, and account for media containing CUI. Encrypt CUI on digital media during transport.

05
SC.L2-3.13.1 to 3.13.16

System and Communications Protection

Monitor, control, and protect communications at system boundaries. Employ FIPS-validated cryptography.

Microsoft 365 Control Mapping

How each obligation maps to enforceable Microsoft 365 controls and the evidence they produce.

Obligation

AC.L2-3.1.1 - Authorised Access

M365 Control

Conditional Access requiring compliant device + MFA. Hardware security keys (YubiKey 5 FIPS) for all CUI-accessing users. Session controls limiting token lifetime.

Evidence

CA policy exports, hardware key registration report, session control configuration.

Obligation

AU.L2-3.3.1 - Audit Logging

M365 Control

Unified Audit Log configured for extended retention (where applicable licenses and policies are deployed). Sentinel log aggregation with immutable storage. All admin actions logged with user identity, timestamp, and affected resource.

Evidence

Audit log retention policy, Sentinel data connector status, sample audit query results.

Obligation

MP.L2-3.8.1 - Media Protection

M365 Control

BitLocker with FIPS 140-2 compliant encryption. 30-day automated key rotation. Endpoint DLP blocking transfer of labelled CUI to removable media.

Evidence

BitLocker compliance report, key rotation logs, DLP policy match report for removable media.

Obligation

SC.L2-3.13.1 - Boundary Protection

M365 Control

Defender for Endpoint network protection. Conditional Access blocking access from non-compliant networks. Information barriers preventing CUI cross-contamination between clearance levels.

Evidence

Network protection event logs, CA policy evaluation logs, information barrier status report.

Implementation Timeline

November 2021
CMMC 2.0 announced, reducing from 5 levels to 3
December 2023
CMMC proposed rule published in Federal Register
October 2024
CMMC final rule effective - phased implementation begins
2025-2026
CMMC requirements begin appearing in new DoD solicitations
2028
Full CMMC implementation across all applicable DoD contracts

Related Frameworks

Ready to get CMMC-ready?

Start with a fixed-scope sprint. We assess your Microsoft 365 controls against CMMC requirements, close gaps, and produce audit-ready evidence.