Skip to main content

Appendix A: Compliance Controls

CMMC Level 2 Controls

This matrix maps technical implementation to Microsoft 365 capabilities. Administrative controls (Policy, HR, Physical Security) are noted where specific Microsoft technologies support them.
Author's Note on NIST Versions

You may notice that NIST has labeled SP 800-171 Rev 2 as "Withdrawn" in favor of Rev 3. For CMMC Level 2 compliance, Revision 2 remains the mandatory standard. The DoD's CMMC Final Rule (32 CFR Part 170) specifically mandates Rev 2. All technical configurations in this book — including Entra ID Conditional Access and Intune Device Compliance — are designed to meet the Rev 2 assessment objectives.

CMMC PracticeMicrosoft TechnologyBook Reference
ACCESS CONTROL (AC)
AC.L2-3.1.1 (Authorized Access)Entra ID (Conditional Access)Conditional Access Policies
AC.L2-3.1.2 (Access Enforcement)Entra ID Conditional Access enforcing approved access authorizationsConditional Access Policies
AC.L2-3.1.3 (CUI Flow Control)Teams (Private Channels), ExchangeSecure Collaboration
AC.L2-3.1.5 (Least Privilege)Entra ID PIM (Just-in-Time Access)Access Governance
AC.L2-3.1.14 (Remote Access)Azure Virtual Desktop (AVD Gateway as the single managed remote access point — no direct RDP, no VPN required for CUI access)Scenario: Azure Virtual Desktop
AC.L2-3.1.15 (Privileged Remote Access)Azure Virtual Desktop (Virtual Machine Administrator Login role — restricts privileged console access to named admin accounts, logged in Entra sign-in logs)Scenario: Azure Virtual Desktop
AC.L2-3.1.16 (Wireless Access)Intune (Wi-Fi Config Profiles)OIB Deployment — Wi-Fi Configuration
AC.L2-3.1.18 (Mobile Devices)Intune (MAM/MDM)Mobile Device Management & App Protection
AWARENESS & TRAINING (AT)
AT.L2-3.2.1 (Security Awareness Training)Defender for Office 365 (Attack Simulation Training)Threat Defense
AUDIT & ACCOUNTABILITY (AU)
AU.L2-3.3.1 (System Auditing)Microsoft Sentinel, Purview AuditSIEM Strategy
AU.L2-3.3.2 (User Accountability)Entra ID (Sign-in Logs)Identity Foundation
AU.L2-3.3.5 (Audit Analysis)Microsoft Sentinel (Analytics Rules)SIEM Strategy
AU.L2-3.3.7 (Audit Retention)Azure Storage (Diagnostic Settings)Audit Readiness
CONFIGURATION MANAGEMENT (CM)
CM.L2-3.4.1 (Baseline Config)Intune (Device Compliance Policies); Entra ID device object hygiene (accurate inventory of managed endpoints)OIB Deployment, Entra Device Hygiene
CM.L2-3.4.6 (Least Functionality)MDE Attack Surface Reduction (ASR) Rules — blocks execution of unnecessary system features and living-off-the-land binariesDefender for Endpoint
CM.L2-3.4.7 (Unauthorized Software)Defender for Endpoint (Software Inventory)Threat Defense
CM.L2-3.4.9 (User-Installed Software)Intune (Endpoint Privilege Management)OIB Deployment
IDENTIFICATION & AUTHENTICATION (IA)
IA.L2-3.5.1 (Identification)Entra ID (User Accounts)Identity Foundation
IA.L2-3.5.3 (MFA)Entra ID (Conditional Access)Conditional Access Policies
IA.L2-3.5.7 (Password Complexity)Entra ID (Password Protection)Identity Foundation
INCIDENT RESPONSE (IR)
IR.L2-3.6.1 (Incident Handling)Microsoft Sentinel (Incident Management); MDE Incidents and automated investigation provide the response workflowSIEM Strategy, Defender for Endpoint
IR.L2-3.6.2 (Incident Reporting)Defender XDR (Alerts); MDE incident timeline and audit log satisfy documentation requirementsThreat Defense, Defender for Endpoint
MAINTENANCE (MA)
MA.L2-3.7.5 (Remote Maintenance)Azure Virtual Desktop (Secure Admin Workstations — Virtual Machine Administrator Login gated by phishing-resistant CA)Virtual Desktop Strategy, Scenario: Azure Virtual Desktop
MEDIA PROTECTION (MP)
MP.L2-3.8.1 (Media Protection)BitLocker (Intune Policy)OIB Deployment
MP.L2-3.8.7 (Portable Storage)Defender for Endpoint (Device Control)Threat Defense
PERSONNEL SECURITY (PS)
PS.L2-3.9.2 (Personnel Termination)Entra ID (Account Disable/Revocation)Identity Foundation
PHYSICAL PROTECTION (PE)
PE.L2-3.10.1 (Physical Access)Azure Virtual Desktop (CUI never touches end-user hardware — users see only a rendered screen; data remains in Azure Government FedRAMP High datacenters)Virtual Desktop Strategy, Scenario: Azure Virtual Desktop
RISK ASSESSMENT (RA)
RA.L2-3.11.2 (Vulnerability Scan)Defender Vulnerability ManagementThreat Defense
SECURITY ASSESSMENT (CA)
CA.L2-3.12.1 (Security Controls)Compliance Manager / Secure ScoreAudit Readiness
CA.L2-3.12.3 (Continuous Monitoring)Microsoft Sentinel; MDE Secure Score, device health reports, and alert pipeline provide continuous monitoring evidenceSIEM Strategy, Defender for Endpoint
SYSTEM & COMMUNICATIONS (SC)
SC.L2-3.13.1 (Network Boundary Monitoring)Azure Firewall (deny-all with explicit allow rules, FQDN-based egress control for AVD session hosts)AVD Firewall Reference, Scenario: Azure Virtual Desktop
SC.L2-3.13.5 (Subnetworks / No Public Exposure)Azure Virtual Desktop (session hosts have no public IPs; inbound via AVD Gateway service tag only; outbound via Azure Firewall UDR)Scenario: Azure Virtual Desktop
SC.L2-3.13.8 (Data in Transit)TLS 1.2+ (Office 365 Defaults); AVD Gateway enforces TLS on all RDP sessionsSecure Collaboration, Scenario: Azure Virtual Desktop
SC.L2-3.13.11 (FIPS Encryption)Intune (BitLocker FIPS Policy)OIB Deployment
SC.L2-3.13.16 (Data at Rest)Purview Information Protection (Encryption)Sensitivity Labels
SYSTEM & INFORMATION INTEGRITY (SI)
SI.L2-3.14.1 (Flaw Remediation)Intune (Windows Autopatch/Updates)OIB Deployment
SI.L2-3.14.2 (Malicious Code)Defender AntivirusThreat Defense
SI.L2-3.14.4 (Malicious Code Protection Updates)MDE platform and signature updates managed by Microsoft — no separate update infrastructure requiredDefender for Endpoint
SI.L2-3.14.7 (Identify Unauthorized Use)MDE behavioral analytics and anomaly detection — surfaces unexpected process execution, lateral movement, and data exfiltration patternsDefender for Endpoint

📩 Don't Miss the Next Solution

Join the list to see the real-time solutions I'm delivering to my GCC High clients.