CMMC Demystified

Update, September 2026: What the CMMC Suspension Means

On July 13, 2026, the Department of War suspended new CMMC certification requirements, and a class deviation issued September 3, 2026 made that suspension binding on contracting officers. Phase 2, which would have required third-party Level 2 assessments starting November 10, 2026, is on hold while a reform task force reviews the program.

Where things stand in late September 2026: The reform task force delivered its recommendations to the Department of War’s chief information officer on September 11. They have not been made public yet, and reporting points to a release in late September or October. The department has said it is weighing both rollbacks of planned requirements and possible expansions, such as security for operational technology. Until then, Phase 1 stays in effect, so Level 1 and Level 2 self-assessments and affirmations are still required.

Several obligations did not pause. DFARS 252.204-7012 cybersecurity requirements, NIST SP 800-171 self-assessments and the SPRS scores built on them, and annual affirmations all still apply. An affirmation is a legally binding statement, and the False Claims Act still covers it.

CMMC is a moving target, and it is not going away. Companies that keep working toward compliance now will be ready when the requirements return, and they won’t be low-hanging fruit for attackers in the meantime. For the full breakdown, read Is CMMC Paused? What the Phase 2 Suspension Changed and What You Still Owe.

 


 

Manufacturers who sell to the Department of Defense and larger DoD contractors will soon be required to comply with CMMC or else they will lose federal government contracts. The CMMC model was recently updated to better protect controlled unclassified information (CUI) that’s stored or created by private companies like manufacturers. CMMC is a response to concerns that criminal actors or hostile nation-states could steal CUI from an unprotected manufacturer and use the data to exploit weaknesses in our country’s defense systems.

CUI is an umbrella term used to identify data that is not classified but requires protection. Some examples include:

  • Personally Identifiable Information (PII)
  • Sensitive Personally Identifiable Information (SPII)
  • Proprietary Business Information (PBI) Confidential Business Information (CBI)
  • Unclassified Controlled Technical Information (UCTI)
  • Sensitive but Unclassified (SBU)
  • For Official Use Only (FOUO)
  • Law Enforcement Sensitive (LES)
  • And more…

 

If you store CUI on your computer systems, CMMC requirements apply to the DoD contracts your organization pursues. The rollout is phased over several years and prioritizes the most sensitive contracts, and the timeline has shifted more than once, most recently with the 2026 suspension described above. It’s unknown which DoD contracts will require CMMC compliance first or what level they will require, but you can probably make a few educated guesses with this information.

  • Level 1 is “Foundational” CMMC and requires 17 checkboxes. It’s completed via self-assessment.
  • Level 2 is “Advanced” CMMC. It aligns with the existing NIST 800-171 standard and needs 110 checkboxes. It requires third-party assessment in most cases.
  • Level 3 is “Expert” CMMC, requiring over 110 checkboxes based on NIST 800-172. It can only be achieved with the federal government’s assessment.

CMMC Level 2 is expected to be the most common requirement for DoD manufacturers and contractors. Its 110 checkboxes follow the NIST 800-171 requirements, which are organized into 14 groups. NIST 800-171 was initially required in 2017, so it’s a relatively well-understood standard by security professionals. The checklist items must be implemented and enforced. To give you an idea of what the 110 checklist items contain, the 14 groups are:

1. Access Control

Devices automatically lock after a period of inactivity, excessive unauthorized login attempts are blocked, data is encrypted in transit and at rest, and access control adheres to the least privileged access principle, meaning accounts are given no more authorization than necessary to perform required functions.

2. Awareness and Training

Everyone is trained and assessed security risks and related cybersecurity procedures, and appropriate employees are trained to complete security-related roles.

3. Audit and Accountability

Event logs are recorded, analyzed, and audited to observe cybersecurity incidents. SNAP-Defense works well for this.

4. Configuration Management

Device access is limited. Approved devices restrict unauthorized software and accessories and are kept up-to-date on available security patches.

5. Identification and Authentication

Multifactor authentication and password policies are enabled and enforced.

6. Incident Response

Capabilities for cybersecurity event detection, analysis, containment, recovery, and response must be present. Typically this requires a Security Operations Center (SOC) service, which is included in SNAP-Defense.

7. Maintenance

Ensure maintenance is formally scheduled and performed by authorized parties.

8. Media Protection

Storage containing CUI is marked, secured, and securely wiped.

9. Personnel Security

Make sure HR & IT is in sync for active and terminated employees and people with access to CUI pass appropriate background checks.

10. Physical Protection

Physical access to sensitive devices and areas is limited to authorized personnel.

11. Risk Assessment

Conduct routine vulnerability scans and correct problems.

12. Security Assessment

Conduct routine penetration tests, audit logs for computer system misuse, and correct problems.

13. System and Communications Protection

Block “shadow-IT” by prohibiting unauthorized remote control of systems and data uploads to other systems.

14. System and Information Integrity

Install the latest critical security patches on all devices within five days of release. Scan for traditional malware, unusual patterns of activity, and evidence of breach with next-generation antivirus services like EDR, and MDR. MDR is included with SNAP-Defense.

Compliance is more than a simple implementation of security technologies. It’s also secure operating procedures and a compliance documentation package. Required documentation includes a System Security Plan (SSP) and associated documents, its policies, and its procedures, as well as a Plan of Action and Milestones (POA&M). The entire compliance journey typically takes 9-12 months, not including the actual assessment.

Assessor capacity is still a bottleneck. Roughly 100 authorized third-party assessment organizations (C3PAOs) serve more than 100,000 companies, so companies that wait until the last minute will be waiting in line for an audit.

After full compliance is certified, an ongoing maintenance phase must be present that includes annual risk assessments, penetration tests, vulnerability assessments, and updates to the SSP and other relevant compliance documentation.

Certification is typically good for three years, assuming ongoing maintenance is completed.

Pegasus Technologies helps a variety of companies, including:

The reality is that even if the DoD contracts a manufacturer works on today do not require CMMC compliance, adhering to NIST 800-171 standards drastically increases the effectiveness of an organization’s cybersecurity defense systems and paves the way for future compliance should a contract require CMMC in the coming years. Because achieving full compliance is not an overnight process, there are many reasons to start the CMMC journey today and take advantage of the superior cyberdefenses NIST 800-171 provides against ransomware, insider threats, and cybercriminals. Manufacturers need all the help they can get to preserve their efficiency and reputation, and we stand ready to assist.

Contact us today to discuss how Pegasus can help your organization continue to win DoD manufacturing contracts as CMMC requirements return to DoD contracts.

The complete guide: Penetration Testing Explained covers the seven stages of a real test, the black, grey and white box types, how a test differs from a vulnerability scan, what the report should contain, and what moves the price.