CMMC Level 1 control library
Every control CMDash tracks for CMMC Level 1, in the order the standard itself uses. Each one is a row in the product with an owner, a status, evidence and its own history — this page is the public index of what those rows are.
17 controls6 families17 mapped to other frameworksNo published text extract yet
Families
Access Control · 4
| AC.L1-3.1.1 | Limit system access to authorized users Maps to CMMC Level 2 |
| AC.L1-3.1.2 | Limit access to authorized transactions and functions Maps to CMMC Level 2 |
| AC.L1-3.1.20 | Control connections to external systems Maps to CMMC Level 2 |
| AC.L1-3.1.22 | Control information posted to publicly accessible systems Maps to CMMC Level 2 |
Identification & Authentication · 2
| IA.L1-3.5.1 | Identify users, processes, and devices on the system Maps to CMMC Level 2 |
| IA.L1-3.5.2 | Authenticate identities before granting access Maps to CMMC Level 2 |
Media Protection · 1
| MP.L1-3.8.3 | Sanitize or destroy media before disposal or reuse Maps to CMMC Level 2 |
Physical Protection · 4
| PE.L1-3.10.1 | Limit physical access to organizational systems and facilities Maps to CMMC Level 2 |
| PE.L1-3.10.3 | Escort visitors and monitor visitor activity Maps to CMMC Level 2 |
| PE.L1-3.10.4 | Maintain audit logs of physical access Maps to CMMC Level 2 |
| PE.L1-3.10.5 | Control and manage physical access devices Maps to CMMC Level 2 |
System & Communications Protection · 2
| SC.L1-3.13.1 | Monitor and control communications at system boundaries Maps to CMMC Level 2 |
| SC.L1-3.13.5 | Separate publicly accessible components from the internal network Maps to CMMC Level 2 |
System & Information Integrity · 4
| SI.L1-3.14.1 | Identify, report, and correct system flaws in a timely manner Maps to CMMC Level 2 |
| SI.L1-3.14.2 | Provide protection from malicious code Maps to CMMC Level 2 |
| SI.L1-3.14.4 | Keep malicious code protection mechanisms current Maps to CMMC Level 2 |
| SI.L1-3.14.5 | Perform periodic and real-time scans for malicious code Maps to CMMC Level 2 |
Where this comes from
Control identifiers, families and titles are the rows CMDash’s own seed data writes for CMMC Level 1 2.0, published from a build-time export rather than read from any customer’s workspace. Cross-framework mappings are CMDash’s own, and each one is shown on both frameworks it connects.
Track these controls in CMDash
Every control on this page becomes a row with an owner, a status, evidence and an audit trail — with the crosswalks already wired, so evidence mapped once counts in more than one framework.