...field notes
Insight on CMMC, DoD contracting, and the path to certification

CMMC Isn’t Optional Anymore, It’s Your Ticket to Stay in the Defense Supply Chain

The LinkedIn posts are starting to pile up. Defense tech founders and cybersecurity consultants all saying the same thing: CMMC is no longer just another compliance checkbox, it’s becoming the gatekeeper for who gets to play in the defense industrial base.

They’re not wrong. But for small-to-medium DIB contractors handling CUI, the real question isn’t whether CMMC matters. It’s whether you understand what’s actually required before you’re too deep into contracts to pivot.

The Shift From “Should” to “Must”

Here’s what’s changed: proving security isn’t optional anymore. The days of self-attestation through SPRS scoring are ending. When CMMC Level 2 hits your contracts, you’ll need either a self-assessment with affirmation (for non-prioritized acquisitions) or a full C3PAO assessment (for prioritized acquisitions).

The key word there? Proving.

This isn’t about having good intentions or even having decent security. It’s about demonstrating conformity with all 110 practices from NIST SP 800-171, documented, implemented, and assessable.

What This Actually Means for Your Contracts

Paul George S.’s recent post frames this as unlocking “defense partnerships” and “high-value opportunities.” But let’s be more specific about what’s at stake:

1. Current contracts with DFARS 252.204-7012, These already require NIST 800-171 compliance. CMMC Level 2 doesn’t add new technical requirements; it adds verification.

2. Future contract eligibility, Once CMMC clauses start flowing down from primes, no certification means no bid. Period.

3. Subcontractor relationships, Your prime contractors will mandate CMMC compliance before contract award. They have no choice, their own certifications depend on it.

The Real Risk: Waiting Too Long

The mistake we see repeatedly: companies treat CMMC like they treated NIST 800-171, something to figure out “when we need it.”

Here’s why that fails:

  • Scoping takes time, Defining your assessment boundary using the Level 2 Scoping Guide isn’t trivial. Every CUI asset, security protection asset, and specialized asset must be categorized correctly.
  • Remediation can’t be rushed, If your gap assessment reveals 50+ findings across the 14 domains (typical for first-timers), you’re looking at months of implementation.
  • POA&Ms have limits, You can only carry a limited score reduction into conditional certification. Major gaps must be closed before assessment.

The Competitive Reality

Yes, early CMMC preparation gives you an edge, but not the way most people think. It’s not about being “first to certify.” It’s about understanding your actual compliance burden before you’re locked into contracts you can’t fulfill.

Consider:

  • How much of your infrastructure actually touches CUI?
  • Can you architect a reduced-scope enclave?
  • What would virtualization or cloud migration cost versus securing everything in place?

These aren’t questions to answer during Phase 1. They’re questions that determine whether Phase 1 even makes sense yet.

Your Move

Don’t wait until CMMC clauses appear in your contracts to figure out where you stand. The worst time to discover you’ve been thinking about scope incorrectly is after you’ve committed to an approach, or worse, during a C3PAO assessment.

Before you budget for compliance or engage any services, validate your assumptions about what’s actually in scope. That early clarity determines everything: timeline, cost, and whether you can realistically meet your contract obligations.

Need to understand your real CMMC scope before making compliance decisions? Start with a scoping conversation, it’s built to catch these issues before they become expensive problems.

Ready to assess your CMMC readiness?

Track all 110 NIST 800-171 requirements and prepare for your Level 2 assessment with our free compliance tracker.

CMMC Level 1 Requires 17 Safeguards 15 Controls

The official FAR clause lists 15 safeguards, but CMMC documentation often references 17 practices. Here is why: 

CMMC inherited the DoD’s earlier mapping from the DFARS 252.204-21 “Basic Safeguarding” table, where two of the FAR requirements were split into multiple CMMC practice IDs during modeling. They are not additional requirements—just a structural carryover from the original DoD-to-NIST mapping exercise.