top of page

CMMC Level 2 Requirements: What Government Contractors Need to Prepare

11 minutes ago
6 min read
Business meeting close-up: hands signing a contract beside a laptop on a wooden table, calm and professional.

Government contractors that work with Controlled Unclassified Information (CUI) must protect it wherever it is used, stored, or shared. CMMC Level 2 is a way for the Department of Defense to check whether a contractor has put the required safeguards in place. Preparing for it means understanding which information and systems are covered, fixing security gaps, keeping clear records, and following the assessment rules that apply to the contract. The DoD changed its rollout plans in July 2026, so contractors should check the latest instructions before deciding what assessment is require.


What Are the CMMC Level 2 Requirements?


CMMC Level 2 is based on 110 security requirements in NIST SP 800-171 Revision 2. They cover everyday areas of information security, such as who can access company systems, how accounts are protected, how activity is recorded, how devices are maintained, and how the organization responds to an incident. The DoD's CMMC 101 overview confirms the 110 security requirements in NIST SP 800-171 Revision 2. Contractors should use the official assessment guidance and their contract instructions when checking what applies to them..


Who Needs to Prepare for CMMC Level 2?


Level 2 may apply to prime contractors and subcontractors whose DoD contracts involve CUI and specify this requirement. The important question is whether the contract work requires the company to create, receive, use, store, or send CUI. If it does, the contractor must identify the people, computers, applications, locations, and outside providers that handle or support that information. This helps establish what needs to be included when preparing for an assessment..


A 2025 DoD Inspector General audit found weaknesses in the process used to authorize organizations that conduct CMMC assessments. The audit identified 12 authorization requirements for C3PAOs and called for stronger quality checks. If a contract requires an outside assessment, contractors should confirm that the assessment organization is currently authorized and understand what it is responsible for. Choosing a cybersecurity provider that understands the contractor's environment can also help support informed preparation.


How to Prepare for CMMC Level 2


Begin with the contract. Look for references to CUI, review any handling instructions, and ask the contracting officer or prime contractor to clarify anything uncertain. Then follow the information: where does it come from, who works with it, which computers or applications store it, and how is it shared? Include outside companies and cloud services when they help handle or protect that information. This gives the organization a practical picture of which parts of its environment need to be considered..


Next, compare current security practices with the applicable NIST requirements. For each one, note whether it is in place, partly in place, or still needs work. Record what shows that the safeguard is working. For example, a written rule about who can access company systems should be supported by current user lists, approval records, and regular account reviews. Having a policy is not enough if everyday practice does not follow it.


Not every gap has the same level of urgency. Start with issues that could expose CUI or affect important systems, then consider how much effort each fix will take and who needs to be involved. Give every action an owner and a target date. A clear cybersecurity risk prioritization process helps the team decide what to address first and what can be scheduled for later..


Key Documents and Evidence for CMMC Level 2


A System Security Plan (SSP) is a written description of the systems that handle CUI and the safeguards used to protect them. It should explain what is included, how the environment works, who is responsible, and how the required protections are carried out. Keep it current when systems, applications, providers, or the way information moves through the business changes. The SSP should describe the real environment, not an ideal version of it..


A Plan of Action and Milestones (POA&M) records security gaps that the organization is allowed to address after an assessment. It should explain what remains to be done, who will do it, and when the work is expected to be finished. Not every gap can be placed on a POA&M. Where the rules allow it, eligible Level 2 items must be completed within the applicable 180-day period. Check the current program rules before relying on this option..


Keep records that show how security practices work day to day. These may include approved user access, account reviews, multi-factor authentication settings, software updates, system logs, staff training, incident exercises, supplier agreements, and records of important system changes. Give someone responsibility for keeping each set of records current and store them where the team can find them when needed..


People are part of the security process, too. Make sure employees who handle CUI understand what they can share, where they can store it, and how to report a concern. Review the access given to outside providers and make responsibilities clear. For smaller contractors, cybersecurity services for small businesses can help connect everyday IT protection with the processes and records needed for CMMC preparation..


Assessment, SPRS, and Current DoD Requirements


The assessment a contractor needs depends on the current DoD program instructions and the wording of its contract. On July 13, 2026, the Department of War announced that the planned Phase II rollout was suspended, while Phase I self-assessment requirements remained in place. This changed the expected timing for some third-party assessments. Contractors should review the latest announcement and check their own contract or any amendments before making plans.


Current DoD guidance says Level 2 self-assessments remain in place, with an assessment every three years and an annual confirmation that the information remains accurate. Results and confirmations are recorded in the Supplier Performance Risk System (SPRS). The Phase II suspension does not remove a contractor's responsibility to protect CUI under applicable contract terms, including DFARS 252.204-7012. Check the official CMMC guidance and contract instructions to confirm what your organization must do.


A 2025 survey of 209 senior leaders from defense industry organizations found that 46% said they were ready to seek CMMC Level 2 certification, while 57% had not completed a full review of their gaps against NIST SP 800-171. These results describe the people who took part in the survey, not every defense contractor. They do, however, show why it is useful to check current practices early and keep a clear record of what still needs attention.


CMMC Level 2 Readiness Planning Matrix


Use this matrix to organize readiness work and make ownership and evidence expectations visible.

Readiness Area

What to Establish

Evidence to Retain

CUI scope

Contracts, CUI data flows, facilities, users, systems, and service providers

Scope statement, data-flow diagrams, asset inventory

Security requirements

Applicability and implementation status for each requirement

Assessment results, control narratives, configuration records

System Security Plan

Boundary, environment, responsibilities, and implemented safeguards

Current SSP, network diagrams, system descriptions

Remediation

Prioritized corrective actions and accountable owners

POA&M where permitted, tickets, change records, closure evidence

Operational safeguards

Access, MFA, logging, training, incident response, supplier controls

Account reviews, logs, training records, incident exercises, agreements

Assessment and affirmation

Current assessment route and contract-specific obligations

SPRS records, affirmation confirmation, contract amendments



Build a More Defensible CMMC Readiness Process


A practical CMMC plan starts with knowing where CUI is handled and understanding which safeguards are already in place. From there, contractors can address the most important gaps, keep their System Security Plan accurate, and maintain records that show how security works in practice. Since DoD instructions and contract terms can change, check the current requirements before making assessment decisions. SinglePoint Global can help discuss the broader IT and cybersecurity priorities that support a well-managed environment.


Frequently Asked Questions


1. Does CMMC Level 2 include 110 security requirements?


Yes. Level 2 aligns with the 110 security requirements in NIST SP 800-171 Revision 2. Contractors should use the current DoD assessment guide and applicable contract language when evaluating implementation.


2. Does every contractor need a C3PAO assessment?


Not under every current contract. The required assessment route depends on applicable CMMC direction and the contract or solicitation. The DoD announced the suspension of planned Phase II requirements in July 2026, while Phase I self-assessment requirements remain in place.


3. What is the purpose of a System Security Plan?


An SSP describes the system boundary, operating environment, security responsibilities, and how applicable requirements are implemented. It should reflect the actual environment and be updated when relevant systems or processes change.


4. Can every unmet requirement be placed on a POA&M?


No. Only eligible requirements may be included, and current rules define closeout conditions and timelines. Contractors should verify eligibility and deadlines before relying on a POA&M.


5. Does the Phase II suspension remove the requirement to protect CUI?


No. The DoD has stated that Phase I requirements remain in place and that applicable contractual safeguarding obligations continue. Contractors must follow their current contract clauses and official DoD guidance.


 
 
 

Comments


bottom of page