← Back to Resources
DCG Blog

CMMC Compliance vs. Certification: Why Close Isn’t Good Enough

Two-column editorial graphic comparing compliance and certification.

We have personally seen an organization fail its Cybersecurity Maturity Model Certification (CMMC) assessment for missing one half of one assessment objective, despite the rest of its program being in good shape. That is a rough outcome, but it reflects an important reality within the CMMC ecosystem: compliance and certification are not the same thing. With the CMMC Reform Task Force evaluating the program, aspects of the zero-defect approach could change, but organizations seeking certification will still need to pay close attention to the details. This is not like many other certification regimes in industry, where being close can still be good enough.

Many contractors treat CMMC compliance, CMMC assessment, and CMMC certification as one idea said three different ways. They are related concepts, but they are not interchangeable. Understanding the distinction matters because the space between them is where organizations often misunderstand their risk, underestimate their obligations, and find themselves surprised by assessment results.

A compliant contractor can go unassessed for a period of time and hold no certification. A contractor that would fail an assessment, however, was never compliant, regardless of what it believed about its program. That distinction sits at the center of the entire CMMC ecosystem.

So, what is the difference?

The CMMC is the Department’s program for verifying that contractors protect the information they are entrusted to handle across the Defense Industrial Base (DIB). The program establishes a mechanism for evaluating whether an organization has implemented the safeguards required by its contracts and by the information it handles.

Within that framework, compliance is a condition. It means the organization has implemented the applicable requirements, documented how those requirements are being met, and produced evidence demonstrating that the requirements are operating as intended. An assessment is a review of that condition. Certification is a status resulting from that review. Stated simply, compliance is what the organization does, while certification is an external determination that the organization has done it successfully.

Which status a contractor needs depends on its contract and the level specified in that contract. Regardless of the status required, nearly every contractor in the DIB will ultimately be subject to either a self-assessment or a certification assessment. Many organizations overlook the importance of the CMMC Level 1 self-assessment, but the assessment requirements must still be met, and the assessment must still be conducted correctly.

  • CMMC Level 1 covers the fifteen basic safeguarding requirements for Federal Contract Information (FCI) and relies on an annual self-assessment.
  • CMMC Level 2 applies to organizations handling Controlled Unclassified Information (CUI). It includes 110 requirements aligned to NIST SP 800-171 and is measured through 320 assessment objectives. Depending on contract requirements, Level 2 may be verified through a self-assessment or a third-party assessment conducted by a C3PAO.
  • CMMC Level 3 adds enhanced requirements derived from NIST SP 800-172 for organizations supporting the most sensitive programs.

The requirements themselves do not bend to company size, budget constraints, or good intentions.

A Final Level 2 or Level 3 status lasts three years and requires annual affirmation during that period. That requirement provides perhaps the clearest illustration of the difference between compliance and certification.

Compliance is something you do every day of those three years.
Certification is something you hold during those three years.

An organization earns a certification on a particular date, but it demonstrates compliance continuously between those dates. Certification recognizes compliance; it does not replace it.

That distinction works in both directions. An organization can be compliant and not currently hold a certification. An organization can also lose or jeopardize its certification status despite maintaining its technical controls. A contractor that fails to meet a required affirmation deadline can create certification problems even if its implementation of NIST SP 800-171 remains intact.

Does a moving deadline change anything?

The Defense Federal Acquisition Regulation Supplement (DFARS) is where CMMC reaches contractors through their contracts. The rule incorporating CMMC took effect on November 10, 2025, and implementation is phased over multiple years. Level 1 and Level 2 self-assessments arrive first, followed by third-party Level 2 assessments. The Department has already demonstrated a willingness to adjust implementation timelines, as seen in the July 13, 2026, pause while the CMMC Reform Task Force evaluates the program.

Contractors often interpret schedule changes as permission to wait, and the instinct is understandable. A delayed requirement is, after all, a delayed requirement. What those schedule adjustments do not change, however, are the cybersecurity obligations that already exist elsewhere in the contracting framework.

DFARS 252.204-7012 has required contractors handling CUI to implement the NIST SP 800-171 controls for years. CMMC did not create those safeguarding requirements. It created an assessment mechanism for verifying that organizations are meeting cybersecurity standards and requirements that already exist.

A Level 1 or Level 2 self-assessment is submitted to the Supplier Performance Risk System and affirmed annually by a senior official. In practical terms, that is a signed statement to the government regarding the organization’s cybersecurity posture. The Department of Justice has already pursued false claims cases involving cybersecurity representations that proved inaccurate. This is not a theoretical risk or a marketing talking point. It is an established area of enforcement.

Dates move. The bar stays where it is.

Put differently, a schedule pause does not change the contractual requirement to comply with the applicable controls and report the required self-assessment results into SPRS.

Why doesn't close count?

This is where the word “compliant” becomes dangerous.

A Conditional status can be achieved with a score of 88 out of 110, and some contractors interpret that provision as evidence that near compliance is acceptable. At first glance, the question seems fair: if the program allows a shortfall, why insist on complete implementation?

Because the allowance is narrow, temporary, and intended to lead to full compliance.

In addition to meeting the scoring threshold, the organization must close every POA&M item within 180 days. Furthermore, a handful of requirements cannot be placed on a POA&M at all. Those requirements include the System Security Plan (SSP) itself and most of the three- and five-point requirements. The Conditional pathway is intended to provide a limited remediation period, not a permanent operating model.

More importantly, certification decisions are ultimately based on whether applicable requirements and their corresponding assessment objectives are met.

This is where organizations frequently get into trouble.

Assessors do not simply review whether an organization has addressed the 110 requirements at a high level. They evaluate the associated 320 assessment objectives that provide evidence those requirements are actually being satisfied. If an assessment objective under a requirement is not met, the requirement itself may not be met.

We see this frequently with documentation-related objectives, particularly those requiring information to be identified, documented, or formally maintained. An organization may believe it has implemented a control because the underlying activity occurs. The assessment may reach a different conclusion when the documentation or evidence supporting that activity is incomplete.

That is how an organization can address all 110 NIST SP 800-171 requirements in principle and still fail an assessment. The company in the opening story did not fail because it ignored cybersecurity. It failed because one assessment objective remained unfinished.

That distinction is the difference between believing you are compliant and being able to demonstrate it.

What does a defensible program look like?

First, start with the documentation. To avoid missing an assessment objective and to ensure you have a fully defensible and compliant CMMC program, begin with the SSP, the policies, the procedures, and the evidence that allows someone outside your organization to reach the same conclusion you reached. Roughly 70 percent of CMMC compliance lives there. The technology must exist, but technology alone is not what gets an organization through an assessment. We call the discipline that ties all of these pieces together Real Compliance, and our post on what we mean by Real Compliance explains why it must operate as a program rather than a project.

Next, determine where you stand before you build anything. A CMMC gap assessment measures your current state against the assessment objectives, allowing resources to be directed toward actual deficiencies rather than assumed ones. If you are still determining which level applies to your organization, our guide to what CMMC Level 2 actually requires provides a more detailed look at the CMMC requirements and assessment expectations contractors face.

Finally, build the program so that it survives the next change on the calendar, because there will be another one. A contractor with a defensible compliance program loses very little when a date moves. A contractor without one is gambling that the next delay arrives before its next obligation. A watch that ends when the calendar slips was never truly a watch.

The company in the opening story had put in the effort. Most of the program was in place. What it lacked was the last half of one assessment objective.

That was enough.

Compliance and certification are not the same thing. A contractor can be compliant without holding a certification. A contractor can also come very close to certification and still fail to achieve it. The difference is found in the details that organizations assume will not matter.

In CMMC, those details matter more than in other programs.

Approached is “Not Met.” “Met” is Met.

Whatever date the Department ultimately settles on, the work of standing the watch starts today.

← All posts
Ready to Talk?

The First Conversation Is Free.
And It Will Tell You the Truth.

If this raised a question about your specific situation, the next step is a conversation with DCG. We will tell you honestly what we see before we tell you anything about our services.

Book a Free Consultation