Skip to content
(787)-476-7950 Hormigueros, PR 00660

Mon – Fri 7:00 am – 5:00 pm OPEN Saturday-Sunday CLOSED

Person working on a laptop with a grid of digital documents and a checklist icon, representing document management software

Guide

CMMC Explained: Levels, Self-Assessment, SPRS and Current Status

The Cybersecurity Maturity Model Certification (CMMC), set out in 32 CFR part 170, is how the U.S. Department of Defense (DoD) checks that contractors and subcontractors protect contract information on their own systems. The level follows the information: a company that handles only Federal Contract Information (FCI) needs Level 1, the 15 requirements of FAR 52.204-21, self-assessed every year; a company that handles Controlled Unclassified Information (CUI) needs Level 2, the 110 requirements of NIST SP 800-171 Rev. 2, assessed every three years. Level 3 adds 24 requirements from NIST SP 800-172. As of November 2026 the rollout is paused in Phase 1, so new contract requirements are limited to a self-assessment (Level 1 or Level 2), with results and an annual affirmation in SPRS.

Updated November 2026

Who needs CMMC: the type of information decides

Under 32 CFR 170.3, CMMC applies to DoD contracts and subcontracts under which a company will process, store or transmit FCI or CUI on its own information systems. Contracts solely for commercially available off-the-shelf (COTS) items are left out (32 CFR 170.3(c) and DFARS 204.7504).

  • FCI is information not intended for public release that is provided by or generated for the government under a contract (FAR 4.1901). Public information and simple transactional data, such as what is needed to process payments, are excluded.
  • CUI is information the government creates or possesses, or that an entity creates or possesses on its behalf, that a law, regulation or government-wide policy requires or permits to be handled with safeguarding or dissemination controls (32 CFR 2002.4(h)).

The DoD program manager or requiring activity chooses the level for each contract (32 CFR 170.3(d)), and DFARS clause 252.204-7021 makes it binding. If the contract or the document markings do not make clear what you will receive, ask the contracting officer or the prime contractor before you scope anything.

The three CMMC levels and what each one requires

  • Level 1 (Self): the 15 basic safeguarding requirements of FAR 52.204-21, such as limiting system access to authorized users, sanitizing media before disposal, escorting visitors and scanning for malicious code. All 15 must be met. Self-assessment and affirmation every year. Solicitations issued under a FAR overhaul class deviation may carry the same 15 controls as clause FAR 52.240-93.
  • Level 2: the 110 requirements of NIST SP 800-171 Rev. 2, assessed every three years either by the company, Level 2 (Self), or by an authorized third-party assessment organization, Level 2 (C3PAO), with an affirmation every year.
  • Level 3 (DIBCAC): Level 2 plus 24 requirements selected from NIST SP 800-172 (February 2021), including a security operations center capability, threat hunting and penetration testing at least once a year. It requires Final Level 2 (C3PAO) status first and is assessed every three years by DCMA DIBCAC, a government team.

NIST has since superseded both documents, with SP 800-171 Rev. 3 (May 2024) and SP 800-172 Rev. 3 (May 2026), but the CMMC rule still names the older editions, and those are the ones you are assessed against.

Self-assessment, scoring, SPRS and the annual affirmation

Each requirement is scored MET, NOT MET or not applicable against the assessment objectives of NIST SP 800-171A, and only evidence in final form counts: drafts and unapproved policies do not (32 CFR 170.24). At Level 2 the score starts at 110 and each unmet requirement subtracts 1, 3 or 5 points according to its weight.

Results go into the Supplier Performance Risk System (SPRS), where contracting officers check for a current status before award or before exercising an option (DFARS 204.7503). A Level 2 entry shows the score, for example 105 out of 110, and any POA&M. Each assessment receives a CMMC unique identifier (CMMC UID) that the contractor reports to the contracting officer.

After every assessment, and every year after that, the affirming official, a senior person responsible for the company's compliance, affirms in SPRS that the requirements are in place and will be maintained. The DoD CIO states that a Level 2 status lapses without the annual affirmation.

POA&M limits: what may wait 180 days and what may not

A plan of action and milestones (POA&M) lists the requirements still NOT MET and the dates to fix them. 32 CFR 170.21 sets narrow limits:

  • Level 1: no POA&M at any time.
  • Level 2: a conditional status needs a score of at least 80 percent of the requirements (88 of 110), and only 1-point items may be deferred. The one exception is CUI encryption (SC.L2-3.13.11) when encryption is used but not FIPS-validated.
  • Never deferrable at Level 2: the system security plan (CA.L2-3.12.4), external connections (AC.L2-3.1.20), control of public information (AC.L2-3.1.22) and three physical access requirements (PE.L2-3.10.3, 3.10.4 and 3.10.5).
  • Open items must be closed and confirmed by a closeout assessment within 180 days of the conditional status date, or that status expires.

A POA&M bridges a few low-weight gaps; it does not postpone the core work.

The four-phase calendar and its status in November 2026

32 CFR 170.3(e) brings CMMC into contracts in four phases, each one calendar year after the previous:

  1. Phase 1, from November 10, 2025, the effective date of the DFARS acquisition rule: Level 1 (Self) or Level 2 (Self) as a condition of award, with Level 2 (C3PAO) at the department's discretion.
  2. Phase 2, scheduled for November 10, 2026: Level 2 (C3PAO) as a condition of award for applicable contracts.
  3. Phase 3: Level 2 (C3PAO) for all applicable contracts, plus Level 3 (DIBCAC).
  4. Phase 4: full implementation, including option periods on older contracts.

Status as of November 2026: the Department of Defense, which now also calls itself the Department of War, suspended Phase 2 and the later implementation milestones on July 13, 2026 and set up a CMMC reform task force. Its About CMMC page states that the program is paused in Phase 1, may only require self-assessments at Level 1 and Level 2, and keeps every Phase 1 self-assessment requirement in place; during the review the department enforces NIST SP 800-171 Rev. 2 through self-assessments and select government-led assessments. On November 17, 2026 the page gave no new start date for Phase 2. Rules and dates can change after that check, so look at dodcio.defense.gov/CMMC, the official CMMC page of the DoD Chief Information Officer, before you plan.

How the requirement reaches subcontractors and service providers

CMMC applies at every tier of the supply chain where FCI or CUI travels (32 CFR 170.23). Before awarding a subcontract, the prime must confirm that the subcontractor holds a current status at the right level, and subcontractors affirm every year as primes do (DFARS 252.204-7021). The subcontractor's minimum follows the information it receives:

  • FCI only: Level 1 (Self).
  • CUI: at least Level 2 (Self).
  • CUI under a prime contract that requires Level 2 (C3PAO) or Level 3: Level 2 (C3PAO).

Sharing with each supplier only what the job needs keeps its level as low as the rule allows. An IT or security provider whose systems handle CUI or security protection data, such as logs and configuration data, is an external service provider (ESP) under 32 CFR 170.4. Its services fall inside the client's assessment scope, and their use must be documented in the client's system security plan and described in the provider's service description and customer responsibility matrix (32 CFR 170.19). A cloud service that stores, processes or transmits CUI must reach security equivalent to the FedRAMP Moderate baseline (DFARS 252.204-7012).

Steps to get ready: a practical checklist

  1. Read the solicitation: which CMMC level does it name, and does it include DFARS 252.204-7012, DFARS 252.204-7021 and FAR 52.204-21 (or FAR 52.240-93)?
  2. Map where FCI and CUI arrive, where they are stored and who handles them: e-mail, file shares, laptops, cloud services, paper and shop-floor machines.
  3. Define the assessment scope. A smaller, separate CUI environment means fewer assets to bring up to the 110 requirements.
  4. Run a gap review against FAR 52.204-21 or NIST SP 800-171 Rev. 2, scored as described in 32 CFR 170.24.
  5. Fix first what no POA&M can cover: the six requirements listed in the POA&M section and every requirement worth 3 or 5 points, apart from the FIPS exception for CUI encryption. The cybersecurity baseline guide gives an order of work for general controls such as MFA, patching and logging; it does not replace the 110 requirements.
  6. Collect final evidence, run the self-assessment, enter the results in SPRS and have the affirming official review the evidence before affirming.
  7. Put the cycle on a calendar (Level 1 every year, Level 2 every three years, affirmations every year), ask service providers for their responsibility matrix and flow the correct level down to your own subcontractors.

Frequently Asked Questions

Does the Phase 2 suspension mean CMMC no longer applies?

No. The suspension stopped the move to mandatory third-party assessments, not the program. As of November 2026, Phase 1 is in force: new contracts may require Level 1 (Self) or Level 2 (Self), with results and affirmations in SPRS; if an older contract still names Level 2 (C3PAO), ask the contracting officer how the suspension applies. The DoD CIO also states that the pause does not remove the duty to protect information under DFARS 252.204-7012, which includes reporting cyber incidents within 72 hours of discovery.

Can an IT provider or consultant certify my company for CMMC?

No. A Level 2 certification assessment can only be performed by an authorized or accredited C3PAO, and Level 3 only by DCMA DIBCAC. A self-assessment is affirmed by your own affirming official, not by an outside firm. Consultants and managed service providers can help you prepare, implement controls and organize evidence, but none of that is a certification.

Should we implement NIST SP 800-171 Revision 3 instead of Revision 2?

Not for CMMC. 32 CFR 170.14 states that the Level 2 requirements are identical to those in NIST SP 800-171 R2, and the DoD CIO's About CMMC page refers to the 110 requirements of Revision 2. NIST withdrew Revision 2 on May 14, 2024, when Revision 3 superseded it, but the CMMC rule has not adopted the newer text. Check the official page before you redesign controls around Revision 3.

Does CMMC apply to suppliers outside the United States?

32 CFR part 170 defines its reach by the contract and the information, not by where the supplier is located: it applies to DoD contract and subcontract awardees that process, store or transmit FCI or CUI on their own systems. A supplier in any country that receives such information under a DoD contract or subcontract should read the clauses in its agreement and confirm the required level with its customer.

About this guide

GlobalTech Corp., the cybersecurity and IT company based in Hormigueros, Puerto Rico, compiled this guide, backed by over 25 years of experience. It works with organizations throughout Puerto Rico; with those in Florida it works remotely or on site, as a project requires. It holds HUBZone Certified Small Business status, is a SonicWall Certified MSSP for Puerto Rico and supports HIPAA, NIST and CMMC readiness: it helps organizations prepare, but it is not a C3PAO or a CMMC assessor and issues no certifications. See its CMMC readiness service and the page on CMMC help for contractors in Puerto Rico. Program facts are as of November 2026; confirm the current status on the official CMMC page.

More guides: Technology Guides.