Ultimate guide to CMMC 2.0 compliance requirements
CMMC 2.0 now applies to all DoD contracts. Are you ready?
The Department of Defence (DoD) developed the Cybersecurity Maturity Model Certification (CMMC) framework to protect the Defence Industrial Base (DIB) from adversarial intelligence collection efforts and corporate proprietary data theft that could compromise U.S. national security. The framework is designed to ensure that defence contractors can meet the cybersecurity requirements built on the National Institute of Standards and Technology (NIST) 800-171 standards.
The DoD issued a final rule amending the Defence Federal Acquisition Regulation Supplement (DFARS) to mandate compliance with CMMC 2.0. Since November 10, 2025, CMMC are included as award criteria in new contracts as well as when exercising option years for existing contracts.
Use the following guide to understand the key components of CMMC 2.0 and get answers to frequently asked questions about the CMMC 2.0 compliance requirements.
What is CMMC 2.0?
The CMMC framework was created to protect the availability, confidentiality, and integrity of Controlled Unclassified Information (CUI) and Federal Contract Information (FCI) throughout the DoD’s extensive contractor supply chain. CMMC 2.0 – an advancement of CMMC 1.0 based on input from stakeholders – was released in October 2024. The revised framework streamlines and simplifies the original one with the goal of increasing the accountability and uniformity of cybersecurity procedures for contractors operating within the DIB.
With the introduction of CMMC 2.0, the DoD is pursuing three objectives:
- Guaranteeing that suitable cybersecurity controls and procedures are in place
- Streamlining certification
- Lowering compliance obstacles and costs for smaller organisations
Effective since December 2024 (32 CFR Final Rule), the revised CMMC Programme is characterised by a tiered model and its assessment requirements aligned to NIST SP 800-171, a set of cybersecurity requirements published by the National Institute of Standards and Technology, and a phased rollout.
The 4 pillars of the revised CMMC 2.0 framework
Tiered model
Businesses entrusted with FCI and CUI are required to implement the progressive cybersecurity standards mandated by CMMC 2.0. The programme also explains the process for mandating information that is flowed down to subcontractors to be protected.
- The new model has been simplified to three maturity levels instead of the previous five.
Assessment requirement
The DoD can confirm the use of precise cybersecurity standards through CMMC evaluations.
- Self-evaluation is sufficient for Level 1, but third-party assessment is required for Level 2, and the Defence Industrial Base Cybersecurity Assessment Centre (DIBCAC) assessment is required for Level 3.
Phased implementation
Certain DoD contractors handling FCI and CUI will need to reach a specific CMMC level as a requirement of contract award once CMMC regulations go into effect.
- CMMC 2.0 has a well-defined implementation schedule; the new requirements will be put into effect over a three-year period, utilising a four-phase implementation plan.
Standard alignment
Unlike the earlier programme, CMMC 2.0 fully aligns with the controls set out in NIST SP 800-171 Revision 2.
Who needs to comply with CMMC 2.0?
To be awarded contracts and for the continuance of contracts, all DoD contractors and subcontractors must have a current CMMC record in the DoD Supplier Performance Risk System (SPRS) or all information systems that process, store, or transmit FCI or CUI during contract performance.
DFARS mandates contractor compliance with the CMMC requirements at the specified level for contract award. Depending on the kind and level of sensitivity of the data that companies may receive, retain, and transmit, the Department of Defence will determine which CMMC level will be applicable to a contract.
As CMMC 2.0 seeks to secure the entire Defence Supply Chain, via the “flow-down” principle, DFARS clauses also apply to subcontractors, making contractors responsible for their enforcement.
- Prime contractors are companies that work directly with the DoD on defence-related contracts
- Subcontractors are third-party businesses that supply prime contractors with goods or services
Contractors and subcontractors must submit a current assessment of their compliance with SPRS prior to contract award.
Understanding Federal Contract Information (FCI) and Controlled Unclassified Information (CUI)
The level of CMMC 2.0 compliance you require is determined by the type of information you handle: Federal Contract Information (FCI) or Controlled Classified Information (CUI). CUI is information that needs to be protected and may also be subject to dissemination regulations, whereas FCI is any information that is "not intended for public release." Title 32 CFR Part 2002 defines CUI, while FAR clause 52.204-21 defines FCI.
Federal Contract Information (FCI)
- Is provided by or generated for the U.S. Government under a contract to develop or deliver a product or service to the Government
- Is not marked as public or for public release
- Examples of FCI can include communication and representation of knowledge, such as facts, data, or opinions in text, numerical, graphical, or audiovisual format
Controlled Unclassified Information (CUI)
- Is created or owned by the U.S. Government or its partners
- Can be critical (CUI with prioritised acquisitions) or non-critical (CUI with non-prioritised acquisitions) – it depends on the specific information’s content, its relation to national security, economic interests, or individual privacy, and requires safeguarding or dissemination controls consistent with applicable laws, regulations, and government policies to protect national security
- Is not classified under Executive Order 13526 or the Atomic Energy Act
- Is marked as CUI
- Examples of CUI include DoD personnel identifiable information, technical specifications for military equipment, critical infrastructure information, and contract performance data
What are the new CMMC 2.0 levels?
The revised CMMC framework includes three levels for a progressive and simplified journey to cybersecurity maturity. Each level is characterised by a set of cybersecurity best practises, standards, and processes as defined in NIST SP 800-171 Revision 2.
CMMC Level 1 requirements (foundational)
This level prioritises safeguarding FCI. It mandates that an organisation’s systems and procedures adhere to 15 fundamental cybersecurity practises specified under 48 CFR 52.204-21, also known as the FAR clause (see FAQ ). This level may be applicable to a subset of programmes that need to meet CMMC Level 2 requirements, if CUI is not involved; however, it is only applicable when the organisation does not receive or hold Controlled Unclassified Information.
CMMC Level 1 assessment
A self-assessment conducted once a year is sufficient at Level 1. Organisations must score their assessment against DoD requirements and report the results to SPRS for the assessment to be considered valid. The yearly submission of self-assessment results serves as an affirmation of continuous compliance.
CMMC Level 2 requirements (advanced)
The protection of CUI is the main focus of this level. At this level, organisations need to document their processes to guide their compliance efforts and follow them as prescribed.
CMMC Level 2 is often referred to as "advanced cyber-hygiene.” It requires the implementation of 110 practises, under the 14 domains specified in NIST SP 800-171 Revision 2 (see FAQ ).
CMMC Level 2 assessment
CMMC Level 2 requires certification and, therefore, third-party assessment, which must be carried out by Certified Third-Party Assessment Organisations (C3PAOs). After initial certification, affirmation of continuous compliance must be made yearly by an organisation official and posted to the Supplier Performance Risk System. Three years after initial certification, a full reassessment must be carried out by a C3PAO.
- Since November 10, 2025, as part of the CMMC 2.0 roll-out phase, new Level 2 contracts and option years require self-assessments. Starting in November 2026, third-party assessments will be required.
CMMC Level 3 requirements (expert)
Concerned with protecting CUI from advanced persistent threats (APTs), this CUI level is also described as "High Value Assets.” CMMC Level 3 requires the implementation of 24 additional controls from NIST SP 800-172 enhanced standards related to greater cybersecurity risk management.
CMMC Level 3 assessment
The certification is only conducted by the DoD via DIBCAC every three years. As a prerequisite for this level, organisations must already be holding a valid Level 2 certification. After initial certification, organisations certified at this level should follow the same process for affirmation of continuous compliance and reassessment as CMMC Level 2 certified organisations.
- Prime contractors and subcontractors may require different degrees of certification depending on their activities and the sensitivity of the information (flow down).
Three-year certification cycles
Once certified at a given NIST revision, organisations remain locked to that revision for the three-year certification cycle. Transition to future revisions (e.g., NIST 800-171 Revision 3) will require new rulemaking, and likely fresh Class deviations for both DFARS 7012 and the 32 CFR CMMC programme.
The CMMC accreditation body is Cyber AB.
How to achieve CMMC 2.0 compliance
Achieving CMMC compliance and certification, especially Levels 2 and 3, takes significant time and resources and is a project that involves the entire organisation. Here is an overview of the steps that you need to follow:
- Determine your CMMC 2.0 certification level
- Perform a gap analysis
- Put the necessary procedures into action
- Select a CMMC-certified C3PAO
- Maintain continuous improvement
- Conditional certification
The certification level you need is driven by the type of information you handle – Federal Contract Information (FCI) or Controlled Classified Information (CUI).
Analyse your current cybersecurity procedures and compare them to the certification level requirements. What are the areas that need improvement to meet the requirements of the CMMC level you are aiming for?
To improve your cybersecurity posture, implement the procedures described in FAR 52.204-21 (Level 1) and NIST SP 800-171 (Level 2), or NIST SP 800-172 (Level 3).
To achieve Level 2 and Level 3 certifications, work with certified third-party assessment organisations (C3PAOs) or with government-led assessors (DIBCAC).
Continuous cybersecurity excellence is emphasised in CMMC 2.0. To handle new risks, make sure you update and enhance your procedures on a regular basis. When working with subcontractors, make sure they have a valid SPRS record and check their scores.
Under the CMMC 2.0 final rule, organisations may achieve “conditional certification” at Level 2 and Level 3. To transition to full certification, they have 180 days to address the gaps identified with the corrective actions plan and road map formally outlined in a POA&M document.
Time and cost of CMMC 2.0 compliance
Achieving certification should typically take 6 to 18 months. However, costs to achieve this vary depending on scope – i.e., volume of CUI and assets that store CUI, the CMMC Level aimed for, and an organization’s cybersecurity maturity at the start of the process. To enhance readiness and prepare your organisation for certification, you can work with a CMMC Registered Provider Organisation (RPO), authorised by the Cyber AB, or a C3PAO (which, in this case, cannot also be your certifying entity).
Learn how Infor supports your compliance requirements in a CMMC 2.0-ready environment.
CMMC 2.0 FAQs
- Limit access to authorised users: Only designated and authorised individuals should have access to information systems.
- Authenticate users: Require users to prove their identity before granting access to systems.
- Limit connections: Restrict connections to external information systems.
- Monitor system use: Audit and log user and system activities to detect suspicious behaviour.
- Limit physical access: Secure access to the physical equipment, facilities, and operating environments of information systems.
- Escort visitors: Supervise and monitor any non-employees within secure areas.
- Sanitise media: Ensure media containing FCI is properly wiped or destroyed before disposal.
- Update software: Install necessary patches and updates to protect against vulnerabilities.
- Whitelist software: Control and restrict which software applications are allowed to run on the system.
- Scan for malware: Use antivirus or endpoint detection and response (EDR) tools to scan systems for malicious code.
- Restrict information flow: Prevent the unauthorised transfer of information from the system.
- Monitor communications: Control and protect communications at the boundaries of the information systems.
- Dispose of devices properly: Ensure media with FCI is destroyed correctly before being disposed of.
- Limit portable storage: Restrict the use of portable storage devices like Universal Serial Buses (USBs) to prevent data loss and malware.
- Train staff: Provide training to employees on handling FCI and following cybersecurity best practises.
NIST SP 800-171 Revision 2 establishes comprehensive guidelines for implementing and managing cybersecurity practises across an organisation, organised in 14 domains, also referred to as the control families.
- Access Control (AC): Limits and manages information systems access to authorised users.
- Audit and Accountability (AU): Ensures the availability and protection of systems audit information.
- Awareness and Training (AT): Mandates security awareness and training to respond to threats.
- Configuration Management (CM): Establishes, documents, and enforces processes and activities to configure and maintain organisational systems, including hardware, software, firmware, and documentation.
- Identification and Authentication (IA): Ensures appropriate and authorised access to an organisation’s systems and data.
- Incident Response (IR): Prepares for cybersecurity incidents, ensuring adequate response and effective mitigation.
- Maintenance (MA): Maintains systems securely.
- Media Protection (MP): Ensures information stored physically or digitally is protected from unauthorised access and exposure.
- Personnel Security (PS): Manages security risk linked to personnel.
- Physical Protection (PE): Protects physical locations and systems.
- Risk Assessment (RA): Assesses risks to systems, operations, and assets and determines how to remediate.
- Security Assessment (CA): Evaluates security controls and identifies vulnerabilities.
- System and Communication Protection (SC): Secures communications and data transmission from unauthorised access.
- System and Information Integrity (SI): Monitors and maintains systems to protect their integrity.
The DoD has outlined a clear timeline for the implementation of CMMC 2.0:
- November 2021: Announcement of CMMC 2.0.
- 2022–2023: Rulemaking process and stakeholder consultations.
- 2024: The 32 CFR CMMC final rule was officially published on October 15, 2024, thereby making the revised CMMC a binding federal regulation. The final rule defines the programme, as well as the ecosystem of third-party assessment organisations (C3PAOs), their credentialing authority (Cyber AB), and the certification assessment process (CAP). The 32 CFR CMMC was approved by Congress on December 16, 2024.
- 2025: Full transition – the 48 CFR CMMC final rule was published on September 10 in the U.S. Federal Register, amending DFARS, to mandate compliance with the final CMMC 2.0 requirements programme rule as a prerequisite to DoD contracts’ eligibility.
A four-phase implementation of the programme is planned over 36 months:
Phase 1: As of November 10, 2025, 60 days after the 48 CFR rule was published as final in the Federal Register, CMMC Level 1 and CMMC Level 2 self-assessments are required for specific contracts.
Phase 2: A year later, on November 10, 2026, CMMC Level 2 certification – third-party assessment – will become mandatory.
Phase 3: One year after Phase 2, CMMC Level 3 certification will become the rule for specific contracts with higher security requirements.
Phase 4: Beginning one year after Phase 3, all DoD contracts will apply CMMC requirements.
Organisations should use this timeline to prepare for compliance, ensuring that necessary cybersecurity measures are in place before the final rollout.