CMMC Level 2: Requirements, assessment and what to do first
Protect CUI, comply and plan with clarity CMMC Level 2 requires organizations in defense supply chains to implement 110 NIST SP 800-171 security requirements that protect Controlled Unclassified Information (CUI). Learn what the requirements mean, how assessments work, and how to identify the gaps to address first.
Talk to a CMMC Advisor
Submit your details below to schedule your confidential 30-minute scoping review:
What is CMMC Level 2?
The Cybersecurity Maturity Model Certification (CMMC) Level 2 framework helps the Department of War (DoW) verify that contractors have implemented the cybersecurity safeguards required to protect CUI. It builds existing federal requirements rather than creating an entirely new set of security controls.
For contractors handling CUI, CMMC Level 2 compliance involves more than installing security software.
Key requirements for CMMC Level 2 compliance:
- Defined Assessment Scope: Identify the systems, assets, and services that handle CUI.
- Implemented Security Controls: Apply to the 110 applicable NIST SP 800-171 security requirements.
- Documented Policies: Establish clear security policies and procedures.
- System Security Plan (SSP): Document your system boundaries and how security requirements are implemented.
- Verifiable Evidence: Maintain evidence demonstrating that security controls are implemented and operating effectively.
Program status: On July 13, 2026, the Department of War announced the suspension of CMMC Phase II requirements, which had been scheduled to begin on November 10, 2026. Phase I self-assessment requirements remain in place, and existing contractual cybersecurity obligations continue. Check out the latest official guidance and your specific contract before deciding which assessment applies.
What CMMC Level 2 Requires
CMMC Level 2 compliance centers on five essential areas:
110 security requirements
Implement the requirements in NIST SP 800-171 Revision 2 across 14 control families.
CUI protection
Identify and safeguard the systems that process, store, or transmit Controlled Unclassified Information.
Documented security practices
Maintain an accurate SSP, applicable policies, procedures, and supporting evidence.
Assessment and scoring
Complete the applicable self-assessment or certification assessment, following the requirements specified for your contract.
Ongoing accountability
Submit required results and affirmations, maintain your security posture, and address outstanding findings within permitted timeframes.
Our Results
CMMC compliance numbers grounded in Department of War regulatory criteria.
The 110 Requirements: 14 Control Families
The NIST SP 800-171 CMMC Level 2 compliance standards cover 110 security requirements organized into 14 families. Each family addresses a different part of protecting CUI, from controlling access to detecting incidents and maintaining system integrity.
| Control family | What it covers |
|---|---|
| Access Control (AC) | Restricting access to authorized users, devices, and permitted activities. |
| Awareness and Training (AT) | Educating personnel about security responsibilities and cybersecurity risks. |
| Audit and Accountability (AU) | Recording, reviewing, and retaining relevant system activity. |
| Configuration Management (CM) | Establishing secure configurations and controlling system changes. |
| Identification and Authentication (IA) | Verifying user and device identities before granting access. |
| Incident Response (IR) | Detecting, reporting, analyzing, and responding to security incidents. |
| Maintenance (MA) | Controlling and monitoring system maintenance activities. |
| Media Protection (MP) | Protecting, handling, sanitizing, and disposing of information-bearing media. |
| Personnel Security (PS) | Managing personnel-related security risks, including termination and transfer procedures. |
| Physical Protection (PE) | Restricting physical access to facilities, equipment, and systems. |
| Risk Assessment (RA) | Identifying vulnerabilities, assessing risk, and managing security weaknesses. |
| Security Assessment (CA) | Evaluating security controls and monitoring their effectiveness. |
| System and Communications Protection (SC) | Protecting communications, system boundaries, and information flows. |
| System and Information Integrity (SI) | Identifying flaws, monitoring threats, and maintaining system integrity. |
A successful CMMC Level 2 assessment requires evidence that the applicable requirements are implemented within the defined assessment scope.
The goal is to document the proof.
Who needs CMMC level 2?
CMMC Level 2 is relevant to defense contractors and subcontractors whose DoW work involves Controlled Unclassified Information and whose contracts require the corresponding CMMC status.
CUI is unclassified information that requires safeguarding or dissemination controls under applicable laws, regulations, or government-wide policies. Depending on the contract and information involved, it may include technical drawings, engineering specifications, manufacturing information, program documentation, or other sensitive government-related data.
Your company does not need to be a large defense manufacturer to fall within scope. Small businesses, specialist suppliers, engineering firms, IT providers, and subcontractors may all have obligations depending on the work they perform and the information they handle.
The first step is to review your contracts, statements of work, CUI markings, and information handling instructions. Establish what information your organization receives or generates, where it is stored, how it moves between people and systems, and which external service providers support those activities.
Do not assume that every document received from a defense customer is automatically CUI. Classification and handling must be based on applicable requirements and authoritative designation. Equally, do not assume that a small volume of CUI eliminates the need to comply with.
Your required CMMC status depends on the applicable contract and assessment requirements, not simply your company’s size, revenue, or preferred cybersecurity maturity.
CMMC Level 2 Compliance Requirements
Determine the right compliance path for your organization based on your contract requirements and the latest official guidance.
1. Define your assessment scope
Identify the people, facilities, devices, applications, networks, and external services that process, store, or transmit CUI, along with relevant security protection assets. Correct scoping prevents gaps in coverage and helps avoid bringing unnecessary systems into the assessment boundary.
2. Implement the 110 requirements
Review each requirement against your existing environment. Determine what is implemented, partially implemented, or missing, and identify the evidence required to demonstrate compliance. Technical safeguards, administrative processes, and physical security measures may all be necessary.
3. Develop and maintain your SSP
The System Security Plan describes the system boundary, operating environment, relevant connections, and how applicable security requirements are implemented. It should reflect the actual environment, not an idealized future state.
4. Maintain policies and supporting evidence
Depending on the requirement, evidence may include access to reviews, configuration records, training records, incident response procedures, audit logs, vulnerability management records, and documented approvals. Assessors evaluate whether the evidence supports the claimed implementation.
5. Address cloud and external service providers
If a cloud service provider processes, stores, or transmits CUI, the applicable CMMC rules require the service offering to be FedRAMP Authorized at the Moderate baseline or higher, or to meet the applicable FedRAMP Moderate-equivalent requirements under DoW policy. The contractor must also document responsibilities and relevant infrastructure in the SSP and assessment scope.
6. Complete the applicable assessment
Depending on the contract and current program requirements, this may involve a Level 2 self-assessment or a third party certification assessment conducted by an authorized CMMC Third Party Assessment Organization (C3PAO).
Get the CMMC level 2 110-control checklist
- Use the 110-Control Checklist to organize the NIST SP 800-171 requirements
- Review implementation status across all 14 families
- Identify missing evidence before assessors arrive
- Prioritize the remediation work ahead
CMMC Level 2 scoring and POA&M rules
CMMC Level 2 assessments use the prescribed scoring methodology, starting from a maximum score of 110. Requirements that are not met receive deductions according to the applicable scoring rules. The size of a deduction depends on the requirement; not every unmet requirement carries the same penalty.
Under the established CMMC Level 2 framework, a score of at least 88 may qualify an organization for conditional status if all other eligibility requirements are satisfied and the outstanding requirements are permitted on a Plan of Action and Milestones (POA&M).
A POA&M records the security requirements that remain unmet, the actions needed to address them, responsible parties, and target completion dates. It is not permission to leave any control unresolved indefinitely.
Eligible outstanding requirements must be remediated within 180 days of the conditional status date, followed by the required closeout assessment or self-assessment, as applicable. If the POA&M is not successfully closed within that period, conditional status expires. Some requirements cannot remain open for conditional status.
Do not build your readiness plan around achieving a particular score alone. A high score does not compensate for an ineligible outstanding requirement, an inaccurate assessment of scope, or missing evidence.
Apply the latest CMMC scoring methodology and assessment requirements to determine your eligibility.
How to prepare for CMMC level 2
Starting early gives your team time to remediate weaknesses, coordinate with service providers, and avoid rushing documentation shortly before a contract milestone.
Step 1: Confirm the requirements
Review the relevant contract clauses and customer instructions. Establish whether your work involves CUI and which CMMC status is required.
Step 2: Map CUI and define the boundary
Document where CUI enters, moves through, and leaves your environment. Identify in-scope of assets, connected systems, and external providers.
Step 3: Conduct a gap assessment
Evaluate each of the 110 requirements against actual implementation. Record evidence, deficiencies, dependencies, and remediation priorities.
Step 4: Build your remediation plan
Address gaps based on security impact, assessment of eligibility, implementation effort, and dependencies. Assign owners and target dates rather than relying on a generic checklist.
Step 5: Update documentation
Bring the SSP, policies, procedures, asset records, diagrams, and supporting evidence into alignment with the environment you operate.
Step 6: Validate implementation
Test the safeguards and review evidence before the formal assessment. Resolve discrepancies between written procedures and day-to-day practices.
Step 7: Confirm the assessment route
Learn about the latest DoW guidance and contract language to establish whether a self-assessment or C3PAO certification assessment is required. Submit the required results and affirmations through the appropriate system..
CMMC level 2 vs. level 1 and level 3
| Feature | Level 1 | Level 2 | Level 3 |
|---|---|---|---|
| Primary focus | Basic safeguarding of FCI | Protection of CUI | Enhanced protection against advanced threats |
| Security requirements | 15 CMMC requirements | 110 requirements from NIST SP 800-171 Rev. 2 | 24 selected requirements from NIST SP 800-172, in addition to Level 2 |
| Typical assessment route | Annual self-assessment | Self-assessment or C3PAO assessment, as applicable | Government-led DIBCAC assessment |
| Documentation and evidence | Evidence supporting basic safeguards | Detailed SSP, policies, and implementation evidence | Level 2 foundation plus enhanced security requirements |
| Main consideration | Protecting contract information | Protecting CUI across the defined scope | Meeting enhanced requirements for designated higher-priority work |
The appropriate level depends on the information and contractual requirements, not on which level sounds most comprehensive.
CMMC requirements depend on your contract: Level 2 applies when specified, while Level 1 is insufficient for contracts that require Level 2. Get ready. Find the right CMMC level for your contract with Secure Centric today.
Common reasons organizations fall short
Undefined CUI boundaries
Organizations may know they handle CUI without knowing exactly where it resides or which connected systems fall within scope. Incomplete data flow mapping can lead to omitted assets and assessment delays.
Policies that do not match actual practice
A written policy may describe secure processes that employees do not consistently follow. Assessors look for evidence of implementation, not just documentation.
Incomplete or outdated SSPs
An SSP that omits systems, connections, responsibilities, or security practices can undermine the credibility of the entire assessment. Update it whenever meaningful changes affect the setup or controls.
Missing evidence
A control may be operating, but the organization may be unable to demonstrate it. Establish a repeatable process for collecting, reviewing, retaining, and locating evidence.
Unmanaged external providers
Cloud platforms, managed service providers, and other external services can affect assessment of scope and control responsibilities. Confirm applicable requirements, document shared responsibilities, and ensure provider arrangements to support the necessary safeguards.
Treating remediation as a last minute exercise
Security gaps can involve technical changes, procurement, employee training, and operational adjustments. Leaving them until an assessment date is approaching can increase costs and delay readiness.
Where Secure Centric helps
Secure Centric helps defense supply chains understand CMMC Level 2 requirements and turn them into a practical readiness plan. Our approach focuses on clear assessments, prioritized remediation, documentation, and evidence that supports the applicable requirements.
How Secure Centric supports your CMMC level 2 compliance:
- Identify CMMC Gaps: Assess compliance with NIST SP 800-171.
- Map Your CUI: Identify where CUI is stored, processed, and transmitted.
- Strengthen Your SSP: Document system boundaries and security controls.
- Organize Compliance Evidence: Align policies and documentation with CMMC Level 2 requirements.
- Prepare for Assessment: Build readiness for your required CMMC assessment.
The objective is to make complex requirements easier to understand and act on.
As a cyber–AB Registered Provider Organization (RPO), Secure Centric provides readiness and advisory services within its authorized scope.
Readiness consulting helps you prepare for assessment but doesn’t offer certification or replace an independent C3PAO assessment. Your contract determines the required path.
FAQs about CMMC Level 2
Still have questions regarding your specific CMMC clauses or audit dates? Speak directly with our lead Registered Practitioner.
Ready to take the next step?
Compliance guidance built on trust and clarity
Secure Centric brings in for you practical, step-by-step guidance tailored to your CMMC Level 2 journey. From identifying gaps to organizing evidence, we help you understand what matters, what comes next, and how to prepare with confidence.