- CMMC adds verified cybersecurity to DFARS 252.204-7012 to protect controlled unclassified information and federal contract information.
- Three cumulative levels: Foundational Level 1, Advanced Level 2, Expert Level 3, aligning controls to contractor risk and data sensitivity.
- Most contractors handling CUI must achieve Level 2, which requires a third-party audit every three years and annual executive affirmation.
- DoD contracts will require CMMC compliance prior to award, with exceptions for COTS products and purchases below the $10,000 micro-purchase threshold.
Last Updated on November 16, 2026
The Cybersecurity Maturity Model Certification (CMMC) program is a US Department of War (DoW) initiative created to safeguard controlled unclassified information (CUI) and federal contract information (FCI) shared through non-government systems across the defense industrial base (DIB). CMMC builds on longstanding trust-based cybersecurity requirements specified in the Defense Federal Acquisition Regulation Supplement 252.204-7012 clause (DFARS 7012) by adding a verification component.
While the current self-attestation regime based on the NIST SP 800-171 Rev. 2 standard is “one size fits all,” CMMC defines three levels of compliance and certification requirements to “right-size” cybersecurity with a contractor’s actual risk profile based on the data they need to protect.
This article gives business stakeholders a concise overview of the three CMMC levels to help you understand your compliance requirements and the effort involved.
Key takeaways
- The CMMC maturity model offers three certification levels: Foundational (Level 1), Advanced (Level 2), and Expert (Level 3). Most DIB orgs that handle CUI are required to meet Level 2 requirements.
- Each of the three CMMC levels has an associated set of practices (called controls in NIST 800-171) organized around domains (called control families in NIST 800-171). There are 15 practices at Level 1, 110 at Level 2, and 134 at Level 3.
- Except for COTS products and procurements below the micro-purchase threshold, all DoW contracts will eventually require CMMC compliance.
What are the 3 CMMC Levels?
CMMC requires DIB orgs that handle sensitive unclassified defense information to implement progressively more advanced cybersecurity controls depending on the risk associated with their data. CMMC compliance requirements “flow down” the supply chain along with the sensitive data they are meant to protect.
DoW contracts and RFPs will specify the CMMC level(s) required for prime contractors and their subcontractors. Compliance with a specific CMMC level will be a precondition of contract award.
The CMMC levels are “cumulative.” To achieve certification at a given level, a business must demonstrate that it complies with the requirements of the lower levels.
The 3 CMMC levels are:
- Level 1: Foundational. This level requires basic cybersecurity measures to protect FCI only. Annual certification self-assessments are also required, along with an attestation by a senior company representative.
- Level 2: Advanced. This level applies to DIB contractors that handle CUI as well as FCI. Depending on the contract, it requires either a self-assessment or an audit by a Certified Third-Party Assessment Organization (C3PAO). Reassessments are every third year with annual executive affirmation of ongoing compliance.
- Level 3: Expert. This highest CMMC maturity level is reserved for contractors working with highly sensitive CUI on the most critical DoW programs, which are likely to be targets of advanced persistent threats (APTs) and nation state actors. Besides passing a CMMC Level 2 audit, organizations subject to CMMC Level 3 will need to fulfill 24 additional requirements per NIST 800-172 and undergo a second assessment by the DoW’s Defense Industrial Base Cybersecurity Assessment Center (DIBCAC). A government-led reassessment is required every third year along with annual executive affirmation of ongoing compliance.
Table 1 summarizes the critical features and differences among the three CMMC levels.
| CMMC Level | Purpose | Requirements | Assessment | POA&Ms OK? |
|---|---|---|---|---|
| 1 | Foundational: Ensure protection of FCI | 15 controls per FAR clause 52.204-21 | Annual self-assessment + annual affirmation | Not permitted |
| 2 (C3PAO) | Advanced: Ensure protection of CUI | 110 controls per NIST 800-171 Rev. 2 | Third-party assessment every 3 years + annual affirmation | Permitted; must be closed out within 180 days |
| 2 (Self) | Advanced: Ensure protection of less sensitive CUI on select programs | 110 controls per NIST 800-171 Rev. 2 | Self-assessment every 3 years + annual affirmation | Permitted; must be closed out within 180 days |
| 3 | Expert: Ensure protection of highly sensitive CUI on critical DoW programs | 134 controls per NIST 800-171 Rev. 2 and NIST 800-172 | Government-led assessment every 3 years + annual affirmation | Permitted; must be closed out within 180 days |
Table 1: CMMC levels
What are CMMC practices?
Each of the three CMMC levels defines an associated set of practices, aka controls. To achieve certification at a specific level, an organization must demonstrate that it has both implemented and operationalized the associated practices for that level and the preceding levels.
Like ISO 27001 and other trusted frameworks, CMMC strongly emphasizes continuous improvement and governance to effectively manage the required practices over time, versus just standing them up and documenting them for a certification audit. Beyond just meeting a requirement “on paper,” DIB orgs seeking CMMC certification will need to prove to auditors and other stakeholders that they have operationalized the requirements within day-to-day business activities.
These are the practices/controls associated with each CMMC level:
- CMMC Level 1 focuses on protecting FCI but not CUI. It specifies 15 practices that correspond to the requirements defined in 48 CFR 52.204-21, “Basic Safeguarding of Covered Contractor Information Systems.”
- CMMC Level 2 focuses on protecting CUI. It includes all 110 practices from NIST 800-171, “Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations.”
- CMMC Level 3 focuses on protecting highly sensitive CUI from sophisticated threats. It includes the 110 practices from NIST 800-171 plus 24 additional practices from NIST 800-172, “Enhanced Security Requirements for Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations.”
What are CMMC domains?
Similar to the NIST 800-171 control families, CMMC organizes its practices into 14 interdependent domains. Table 2 lists the 14 CMMC domains and 110 associated practices at CMMC Level 2.
| Domain | Summary | Number of Practices |
|---|---|---|
| Access Control (AC) | Monitor all access events in your CMMC environment and limit access to data and systems. | 22 |
| Audit & Accountability (AU) | Retain audit records to hold users accountable and support cyber incident forensics. | 9 |
| Awareness & Training (AT) | Make sure that users know the cybersecurity risks associated with their role and activities, understand cybersecurity policies, and can recognize and help block threats (e.g., phishing attacks). | 3 |
| Configuration Management (CM) | Establish and maintain baseline software configurations. | 9 |
| Identification & Authentication (IA) | Allow only authenticated users to access company networks, systems, or data. | 11 |
| Incident Response (IR) | Develop a strategy and plan that drives efficient and effective responses to cyber incidents. | 3 |
| Maintenance (MA) | Perform system maintenance in accordance with best practices to protect the confidentiality of sensitive data. | 6 |
| Media Protection (MP) | Make certain that both paper and digital media containing CUI are secure. | 9 |
| Personnel Security (PS) | Track and manage user activities in relation to CUI, e.g., employees leaving the organization. | 2 |
| Physical Protection (PE) | Protect assets from loss, theft, and/or damage from physical occurrences. | 6 |
| Risk Assessment (RA) | Perform regular risk assessments and vulnerability scans. | 3 |
| Security Assessment (CA) | Assess and validate that cybersecurity controls are effective and safeguard data in accordance with acceptable risks. | 4 |
| Systems & Communications Protection (SC) | Track and protect data as it is received or transmitted by IT systems. | 16 |
| System & Information Integrity (SI) | Efficiently monitor, flag, and mitigate vulnerabilities to protect sensitive data from malicious code. | 7 |
Table 2: CMMC domains
How is CMMC 2.0 Level 2 different from NIST 800-171?
From the standpoint of controls, CMMC Level 2 is built on NIST 800-171 Rev. 2. NIST 800-171 has specified the cybersecurity requirements for DoW contractors handling CUI since December 31, 2017.
However, CMMC adds a third-party certification process based on three compliance tiers.
Contracts requiring CMMC Level 2 will also include the DFARS 7019 clause, which requires contractors to upload a NIST 800-171 compliance score into the DoW’s Supplier Performance Risk System (SPRS) database. This ensures that all contract participants have documented an assessment of their cybersecurity practices and explicitly provided the DoW with that data.
Does my business need to comply with CMMC now?
All prime contractors, subcontractors, and suppliers that want to bid on or participate in future DoW contracts that contain the CMMC DFARS clause (DFARS 7021) will need to attain CMMC certification at the specified level prior to contract award. Contractors must maintain their CMMC compliance status throughout the contract’s duration.
During the suspension, the specified level can only be Level 1 (Self) or Level 2 (Self).
Exceptions may include:
- Contracts for commercial off the shelf (COTS) products only.
- Contracts below the micro-purchase threshold of $15,000.
Cloud service providers (CSPs), Managed Service Providers (MSPs), Managed Security Service Providers (MSSPs), SaaS providers, IT consultants, and other External Service Providers (ESPs) that deliver a service relating to accessing, managing, and/or protecting CUI for a DoW contract may be subject to CMMC compliance. DIB orgs can optionally include an ESP in its system security plan, to be assessed for CMMC compliance alongside them versus requiring the ESP to have its own CMMC certification.
Which CMMC level should we pursue?
The first step towards CMMC for any defense supplier is to identify their CMMC level. There are several key inputs to this decision:
- If your current contract specifies NIST 800-171 compliance, then, at least in the eyes of the US government, you handle controlled unclassified information (CUI). NIST 800-171 compliance is equivalent to CMMC Level 2.
- If your current contract has a DFARS 7012 clause, then you are likewise deemed to handle CUI and most likely need a CMMC Level 2 compliance.
- Are you looking to pursue future business on projects that require receiving CUI from the DoW? Achieving CMMC Level 2 certification now would be a significant advantage.
- If you participate in a “highest priority” DoW program (e.g., missile guidance) and need to protect CUI from advanced persistent threats (APTs), then you need to comply with CMMC Level 3.
- If you know you only handle Federal Contract Information (FCI) to fulfill your DoW contracts, then you may only need to comply with CMMC Level 1 (Foundational), which requires just 15 controls.
What is our CMMC scope?
Along with identifying your CMMC level, you need to define the scope of your CMMC environment as a preliminary step toward gap assessment. Scoping determines the subset of your overall IT infrastructure that will be subject to assessment for CMMC compliance. CMMC’s purpose is to protect CUI. Therefore, CMMC scoping is all about knowing what CUI you handle, where it resides, and what assets (systems, processes, people, including third-party assets) store, transmit, process, or create CUI. Questions to ask include:
- Where does CUI enter our environment?
- Where is it stored?
- How is it processed?
- Do we create any CUI?
- How does it exit our systems and where does it go?
- How is it archived or destroyed?
Using this information, you can diagram your CUI data flows and identify the assets associated with those flows. This activity illuminates the boundaries of your CMMC compliance environment, often called a CMMC enclave.
Why can’t we start with a gap assessment?
A gap assessment identifies the gaps between your current cybersecurity posture and a set of requirements, such as CMMC Level 1, 2, or 3. So why not pick a CMMC level and perform a gap assessment based on the corresponding controls?
You want to conduct your scoping exercise before your gap assessment because how you implement CMMC, or any other comprehensive cybersecurity framework, is strongly impacted by your scope and the identified risks you face. Therefore, by definition, you cannot accurately assess gaps until you define the scope.
Nor can you fully assess gaps until you assess risks. Until you know the risk level you must mitigate, you won’t know how robust an associated control needs to be.
For example, you know you handle CUI, so you start your CMMC certification journey with a gap assessment against CMMC Level 2. Based on those results, you undertake a $50,000/multi-month migration to the Microsoft 365 GCC “government cloud” to meet CMMC Level 2 requirements. But because you didn’t initially scope your CUI environment, you recognize too late that some of your CUI is subject to International Traffic in Arms Regulations (ITAR). Because of the extra security that ITAR requires, you actually needed to implement Microsoft 365 GCC High to achieve CMMC Level 2 certification. The cost and effort for your original migration have thus been wasted, and you need to migrate yet again.
Should we do our CMMC gap assessment in-house?
Can you get the accurate and comprehensive assessment results you need with internal resources, or should you consider hiring a third-party expert?
If you have strong in-house cybersecurity expertise, you can save money by conducting a DIY CMMC gap assessment. Here are some factors to consider:
- If your business is already NIST 800-171 compliant and has posted a valid score to that effect in the DoW’s Supplier Performance Risk System (SPRS), you probably have the people, processes, and systems in place to confirm CMMC compliance internally. You’re also much more likely to have compliance reporting in place to support your gap assessment than if your cybersecurity was less mature.
- If you think you’re “close” to NIST 800-171 compliance (approximately 80% of controls), an in-house gap assessment can work, provided you have an accurate system security plan (SSP) and a formal risk assessment program in place as starting points. These are critical governance elements that help ensure you understand your true cybersecurity posture.
- If you’re “far” from NIST 800-171 compliance, you may not be ready for a gap assessment. Every CMMC certification project must follow a logical, structured approach to ensure the results meet business goals. To provide context for a gap assessment, you first need to define your CUI scope, determine whether it can be reduced, and then conduct a risk assessment. Many SMBs lack scoping and risk assessment experience and would benefit from third-party guidance to set them up for success.
What are the advantages of leveraging a third party for CMMC gap assessment?
Some of the benefits to engaging an external resource for your CMMC gap assessment effort include:
- You get an independent, objective evaluation of how well your cybersecurity controls are performing, based on an unbiased approach. If your in-house team implemented a control incorrectly or incompletely, will they have the expertise to identify that in your gap assessment?
- As a stepping stone to CMMC certification, a third-party gap assessor can provide an attestation of your security posture that you can use to demonstrate NIST 800-171 or CMMC alignment or conformance to a prime contractor or government agency.
- With a third-party gap assessment, the vendor can provide specialized expertise to evaluate operational technology (OT), Internet of Things (IoT) assets, cloud-based services, and other systems that may be in scope for your CMMC certification but are unfamiliar to your internal team.
- A third-party gap assessment demonstrates to stakeholders that your organization is serious about improving its cybersecurity posture and protecting CUI. This helps build trust and credibility because the results are supported by an impartial assessment.
What’s next?
CBIZ Pivot Point Security offers a full complement of CMMC advisory and consulting services. We tailor our consulting services to your unique situation, working with you to determine what it will take for your organization to achieve and maintain compliance at your designated CMMC level. Contact us today to connect with a CMMC expert about your company’s unique compliance scenario.

