Your CMMC deadline is the date your solicitation or contract requires a current status, not a marketing countdown. The DFARS acquisition change took effect on November 10, 2025. Requirements are being phased into DoD acquisitions; the required level and assessment route must be checked against the actual clauses.
Start with the free CMMC checklist, then confirm your contract requirements with your contracting officer or adviser. For the distinction between FCI and CUI, see CMMC Level 1 vs Level 2.
What deadline applies to your contract?
DFARS 204.7504 provides for use of the CMMC clause through November 9, 2028 when the requiring activity specifies a level. On or after November 10, 2028, the prescription applies more broadly to covered acquisitions using contractor systems to process, store or transmit FCI or CUI, subject to the stated exceptions. That does not mean you can wait until 2028: a solicitation can require a qualifying status before then.
| Contract question | Evidence to obtain | Action |
|---|---|---|
| Which CMMC level is required? | Solicitation and applicable clauses | Record level and assessment route |
| When must status be current? | Award, option or other applicable contract conditions | Work backward from the actual requirement |
| Which systems are covered? | FCI/CUI flows and assessment boundary | Include relevant vendors and external services |
| Are there flow-down obligations? | Prime and subcontract terms | Confirm requirements with each supplier |
There is no blanket October 31, 2026 cutoff requiring every DoD contractor to hold Level 2 certification. Avoid building a schedule around that outdated claim. Review the DFARS CMMC subpart and clause prescription.
Metric
Traditional MSP
Core12 MIP
Approach
Reactive break-fix; wait for tickets
Proactive Managed Intelligence; prevent before impact
Speed
SLA-based response (4+ hrs)
24/7 monitoring, <15 min detection
Security
Basic antivirus & firewall
Zero Trust, CMMC-ready, continuous pen testing
AI & Automation
None or ad-hoc scripts
AI ticket triage, workflow automation, predictive analytics
Advisory
Quarterly reviews (maybe)
Embedded vCTO with roadmap tied to business KPIs
Compliance
Paper-based checklists
Continuous monitoring (NIST 800-171, CMMC, HIPAA)
What should a CMMC cost estimate include?
A ten-person supplier with a small CUI boundary can have a very different scope from a fifty-person supplier with multiple sites and shared cloud services. Employee count alone does not determine the required level or implementation effort. Core12 does not publish a one-size-fits-all certification price.
| Budget line | Scope to confirm | What changes the estimate |
|---|---|---|
| Readiness and scoping | Data flows, gap assessment and remediation roadmap | Boundary complexity and current documentation |
| Technical remediation | Identity, endpoints, encryption, logging and recovery | Existing tools, migrations and open control gaps |
| Documentation and training | SSP, policies, evidence and personnel preparation | Quality of existing records and staff responsibilities |
| Ongoing operations | Monitoring, evidence upkeep and recurring reviews | Systems, vendors and service responsibilities |
| Independent assessment | Required assessment route and assessor fees | Level, boundary and assessment scope |
This is a proposal-comparison framework, not an official fee schedule or a Core12 quote. Request written inclusions, exclusions, dependencies and recurring charges. Ask who owns control maintenance after implementation and whether project work requires separate approval.
How should suppliers sequence readiness work?
First confirm FCI/CUI scope and the required assessment type. Then document the current environment, assess gaps, assign owners and approve remediation. Prepare evidence describing what operates today, not what a template says should operate. Schedule assessment only when the evidence supports the required status.
| Stage | Deliverable | Decision gate |
|---|---|---|
| Scope | Data boundary and contract requirements | Confirm what is included |
| Assess | Gap register and current evidence | Approve priorities and budget |
| Remediate | Implemented controls and documented operations | Verify changes work |
| Prepare | Assessment evidence and responsible owners | Confirm assessment route |
| Maintain | Recurring control and evidence reviews | Keep status and affirmations current |
Timelines depend on actual gaps and assessment availability. A readiness engagement cannot promise a certification result or a fixed completion date. Core12 offers CMMC readiness services and operational support through managed IT or co-managed IT.
What does conditional status mean?
The DFARS definitions limit qualifying conditional Level 2 status to no more than 180 days, with the applicable affirmation and compliance conditions. Conditional status is not a general extension for every unmet requirement, and Level 1 requires final status. Final Level 2 status is generally current for up to three years with a corresponding affirmation no more than one year old. Check the current rule and your assessment route before relying on these periods.
What should leadership do this week?
Name the contract owner, the data-boundary owner and the person responsible for evidence. Put actual award and renewal conditions on the calendar. Request a scoped proposal that separates preparation from assessment and one-time changes from ongoing operations.
Use the CMMC readiness checklist to identify questions to investigate. The IT Risk Report helps frame operational exposure; the AIQ Score is a separate AI-readiness diagnostic, not evidence of CMMC certification.
Sources: DFARS CMMC requirements; November 10, 2025 acquisition change. This guide is readiness information, not legal advice.