CMMC Compliance Services for Defense Suppliers
CMMC clauses have been in DoD contracts since November 10, 2025. On July 13, 2026 the Department of War (the Defense Department’s secondary name since September 2025) suspended the Phase 2 third-party assessment phase-in pending a program review — but DFARS 252.204-7012 still requires NIST SP 800-171, and Level 1 or Level 2 (Self) contracts still require the self-assessment and its annual affirmation. The calendar paused. The obligation did not.
We get Southern California machine shops, manufacturers and subcontractors ready: scoping your controlled unclassified information (CUI), the 110 NIST 800-171 controls, and the evidence an assessor asks for. We prepare you for the authorized assessor (C3PAO) — we are not one, and we don’t certify anyone.
What CMMC 2.0 actually demands
Update — July 13, 2026: the Department of War suspended CMMC Phase 2 and paused the Phase 3 and 4 milestones, ordering a program review. Where an existing contract carries a Level 2 (C3PAO) or Level 3 (DIBCAC, the Defense Department’s own assessors) requirement, contracting officers are to remove that requirement by modification before the next option period or administrative modification; Level 1 (Self) and Level 2 (Self) remain, with no waivers during the review. Status as of October 5, 2026: the review window closed on September 11, 2026, no outcome has been published, and the suspension stands — the temporary acquisition-rule change DoD issued as class deviation 2026-O0025 (Revision 3, September 3, 2026) carries it until further notice.
What did not change: DFARS 252.204-7012 still requires NIST SP 800-171; where a contract carries a CMMC Level 1 or Level 2 (Self) requirement, you must still post your self-assessment in SPRS and affirm continuing compliance every year (32 CFR 170.22; DFARS 252.204-7021); Phase 1 self-assessments remain in force; and the Department still runs select government-led assessments. A suspended phase-in is not a repealed rule. Read the suspension memorandum →
The program rule (32 CFR) took effect December 16, 2024; the acquisition rule (48 CFR) followed on November 10, 2025, putting CMMC requirements into contracts. Three levels, keyed to the data you handle:
| Level | Data | Requirements | How it’s assessed |
|---|---|---|---|
| Level 1 — Foundational | Federal contract information (FCI) | 15 basic safeguarding requirements | Annual self-assessment + executive affirmation |
| Level 2 — Advanced | Controlled unclassified information (CUI) | The 110 requirements of NIST SP 800-171 Revision 2 | C3PAO assessment every three years for most contracts (that third-party phase-in is suspended — see the update above); self-assessment for a smaller set — plus affirmations |
| Level 3 — Expert | CUI on the most sensitive programs | 110 from NIST SP 800-171 + 24 from NIST SP 800-172 | Government-led assessment |
Want the full rulemaking story, timeline, and prep sequence? Read our deep dive: CMMC 2.0 — what defense suppliers need to do now.
IT-as-usual is not CMMC-ready IT
Most suppliers we meet have working IT and real gaps against NIST 800-171 — not because anyone was careless, but because ordinary business IT was never asked to evidence itself. The pattern repeats:
- Nobody can say precisely where CUI lives — it is in email threads, quoting folders, and a shared drive named Engineering
- No System Security Plan, no POA&M, and an SPRS score nobody wants to sign
- MFA on some logins, logging nobody reviews, backup copies of CUI nobody has encrypted
Closing that gap is the same discipline as managed security done properly — plus documentation that proves it. That second half is where preparation lives or dies.
We prepare you. Your C3PAO assesses you.
CMMC deliberately separates the people who get you ready from the people who judge the result — the same reason your accountant doesn’t audit their own books. So here is our lane, stated plainly: CRC Cloud prepares defense suppliers for their C3PAO assessment. We are not a C3PAO, we do not conduct certification assessments, and we never promise a certificate. Anyone who promises one is selling something the rules don’t allow.
The pressure is real either way: primes are asking subcontractors for SPRS scores and remediation plans ahead of contract deadlines, the SPRS posting and annual affirmation still apply wherever a contract calls for Level 1 or Level 2 (Self), and that affirmation is a signed legal statement the Department of Justice enforces under the False Claims Act. Preparation done honestly — scoped, implemented, documented — is what turns that pressure back into ordinary work.
How CRC Cloud gets you assessment-ready
Four moves, in order. Scope first — because every control you don’t need to apply everywhere is money saved.
1 · Scope the CUI
Find where FCI and CUI actually live, then shrink the footprint — often with an enclave strategy that concentrates CUI into one contained, hardened environment instead of 110 controls across the whole company.
2 · Implement 800-171 controls
Help you close the gap assessment findings, as everyday support or as project work quoted in writing: MFA and access control, hardening, encryption, logging, media and remote-work rules — mapped requirement by requirement.
3 · Document & evidence
System Security Plan input, IT procedures, training records, and the artifacts assessors ask for — so your SPRS score is one your senior official can affirm truthfully. We track every POA&M item until it is closed; the rules allow only a narrow set, for 180 days. Your customer responsibility matrix — which of the 110 requirements we own, which you own, which are shared — is a deliverable of the engagement, not something we assemble the week the assessor arrives.
4 · Operate & monitor
24/7 SOC monitoring, SIEM, and managed detection and response keep the monitoring, response, and audit-log requirements operating between assessments — not just written down. The annual vendor risk review ranks the outside companies that touch your data by risk and sends security questionnaires to the three most critical.
For CUI itself, be aware of the boundary: DFARS 252.204-7012 requires a cloud service provider at FedRAMP Moderate (or equivalent) before covered defense information may be stored or processed there — SOC 2, ISO 27001 and a concurrently maintainable design do not satisfy that test, and CRC Cloud does not hold a FedRAMP authorization. We keep CUI workloads scoped to systems that meet the requirement and align everything around them.
Built for Southern California’s defense ecosystem
Southern California’s supplier base is exactly who CMMC lands on hardest: machine shops, precision and aerospace manufacturers, engineering firms, and government contractors with real DoD-adjacent work and a two-person (or zero-person) IT department. We support that supply chain across Orange County, Los Angeles and the South Bay’s aerospace corridor, San Diego’s Navy and defense-technology suppliers, and the Inland Empire, out to the high desert — including Yucca Valley, Joshua Tree, and the contractors around the Twentynine Palms Marine base.
We act as an external service provider that handles security data, never CUI. You get a service description and a customer responsibility matrix, and incident notice within 24 hours. Time with your assessor is billed as project work. We don’t hold a CMMC certification.
CMMC is one of twelve frameworks we align IT to — if your work spans more than defense, start at the compliance overview or the foundation itself, NIST CSF 2.0.
CMMC, asked and answered
Is CRC Cloud a C3PAO? Can you certify us?
No, and no MSP can. Level 2 certification comes only from an assessment by an authorized C3PAO (CMMC Third-Party Assessment Organization), and Level 3 assessments are government-led. Our role is everything before and after that visit: scoping, gap assessment against NIST 800-171, remediation, documentation, and the managed security that keeps you assessment-ready. The separation between preparers and assessors is deliberate — be wary of anyone who blurs it.
Do you help defense suppliers in Los Angeles, San Diego and the Inland Empire with CMMC?
Yes. On-site support is included within 175 driving miles of our Newport Beach headquarters, which covers Orange County, Los Angeles and the South Bay, San Diego and North County, the Inland Empire and the high desert. Most CMMC preparation happens remotely: scoping, the gap assessment against NIST SP 800-171, remediation and documentation. We come on-site for the work that needs hands on your hardware and premises, such as network segmentation, workstation builds and physical-protection controls. The price is the same everywhere: CMMC work starts on Secure IT, at the published Secure IT rate plus the published 25% CMMC uplift.
What CMMC level do we need?
The data decides. Federal contract information (FCI) generally means Level 1 — 15 basic safeguarding requirements with an annual self-assessment and executive affirmation. Controlled unclassified information (CUI) generally means Level 2 — the 110 requirements of NIST SP 800-171 Revision 2 (the version CMMC uses), with C3PAO assessment for most contracts (that third-party phase-in is suspended pending the program review) and self-assessment allowed for a smaller set. Level 3 adds 24 requirements from NIST SP 800-172 with government-led assessment, for the most sensitive programs. Your solicitation states the required level.
How long does CMMC Level 2 preparation take?
For most small suppliers, the honest answer is quarters, not weeks. The 110 requirements include policy, documentation, and evidence work as well as technical fixes — and while the November 2026 third-party phase-in was suspended in July 2026, the underlying NIST 800-171 obligation under DFARS 252.204-7012 never paused. Starting after a solicitation names CMMC is usually starting late.
What does CMMC readiness cost?
It depends almost entirely on scope — which is why scoping comes first. Many suppliers save real money with an enclave strategy: concentrating CUI into a contained, hardened environment so the 110 controls apply to one enclave instead of the whole company. The managed-security base is Secure IT at $250 per user per month, and CMMC/DFARS work carries a published +25% uplift on the per-user plan and per-server management — $312.50 per user. That covers the customer responsibility matrix, input for your system security plan and POA&M, the evidence for the controls we run, and assessment preparation.
Time with your assessor is quoted project work. The one-time 800-171 gap assessment and remediation projects are quoted in writing after the initial gap read.
What is an SSP, and why does everyone keep asking for it?
The System Security Plan is the document that explains how your environment meets each of the 110 requirements — it is the artifact your assessor works from, alongside a plan of action for open items (POA&M) and your SPRS score. That score carries a senior official’s affirmation, which is a legal statement the Department of Justice enforces under the False Claims Act. We keep our part of all three accurate: the responsibility matrix, our control descriptions and the tracking of fixes. Your firm owns the plan, the POA&M and the score.
We’re two tiers below the prime. Does CMMC really reach us?
If FCI or CUI flows down to you, yes. Primes are required to flow CMMC requirements to subcontractors, and many are already asking for SPRS scores and remediation plans ahead of contract deadlines because their own awards depend on the answers. A machine shop with one drawing of CUI on a shared drive is in scope.
Can our CUI systems live in your private cloud?
Short answer: no. Under DFARS 252.204-7012, a cloud that stores, processes or transmits CUI must be FedRAMP Moderate authorized, or validated as FedRAMP Moderate equivalent by a third-party assessor. CRC Cloud’s private cloud is neither. Datacenter credentials like SOC 2 and ISO 27001 are facility facts. They do not satisfy that rule, and a provider who implies otherwise is setting you up to fail. CUI belongs in an environment built for it, such as Microsoft 365 GCC High.
We help you prepare and secure that environment as an outside service provider that handles security data, never CUI, with our access limited as your service order records. We track every gap until it is closed, quote the fixes in writing, and organize the evidence. The goal is that the assessment becomes a confirmation rather than a discovery exercise — but it is an independent judgment, and we will never call it a formality.
If the assessor still flags something, fixing it is quoted project work, and so is our time with the assessor. Our private cloud is the right home for everything that never touches CUI. Splitting the two is usually the cheapest way to shrink your scope.
Can we just put the gaps on a POA&M and fix them later?
Only a few — far fewer than most suppliers assume, and the rule is specific. Under 32 CFR 170.21, a plan of action and milestones is not permitted at all for a Level 1 self-assessment. At Level 2 you may only carry one if your assessment score is at least 0.8 of the total — a score of 88 out of 110 — and nothing on the plan is worth more than 1 point under the CMMC scoring methodology. Since 3-point and 5-point requirements make up most of the hard ones, they must be genuinely met before the assessor scores them.
There is one narrow exception: CUI encryption (SC.L2-3.13.11) may go on the plan if you are encrypting but not yet with a FIPS-validated module. Six requirements are barred outright — external connections, control of public information, escorting visitors, physical access logs and managing physical access (each worth 1 point), and the System Security Plan itself, which has no point value because without one the assessment cannot be completed. And a plan only earns you Conditional status: a closeout assessment must confirm the items are closed within 180 days of the conditional status date, or that status expires.
For a certification assessment the closeout must be done by an authorized C3PAO. In practice this means the plan is for the last few loose ends, not a way to defer the work.
You manage our IT. Does that put you inside our assessment?
Yes, and you should expect that of any provider worth hiring. Under 32 CFR 170, an external service provider is in scope when controlled unclassified information or security protection data is processed, stored or transmitted on its systems. Security protection data is the second trigger people miss — the logs, alerts, vulnerability findings, backup metadata and identity records that our monitoring and management tools hold. That means we are usually in scope even on engagements where no CUI ever reaches us.
The rule requires our relationship and the services we provide to be described in your System Security Plan, and it requires us to give you a customer responsibility matrix: a line-by-line statement of which of the 110 requirements we implement, which you implement, and which are shared and how. We give you that matrix and a description of our services, keep both current as the environment changes, and cooperate with your assessment; time with your assessor is project work. If a provider cannot give you one, they are not ready to support a CMMC assessment.
Priced openly, like everything else we do. CMMC / DFARS work carries a published uplift of +25% on the per-user plan and per-server management fee, so the documentation and evidence work is priced instead of hidden in a quote. Secure IT is the starting point for compliance work — Core IT is not an option for a regulated environment, because the frameworks lean on the monitored layer Secure IT adds. On Secure IT that is $312.50 per user per month, covering the customer responsibility matrix, input for your system security plan and POA&M, the evidence for the controls we run, an enclave design recommendation (building it is quoted project work) and assessment preparation. Time with your assessor is quoted project work. Backup, private cloud resources and add-ons stay at their flat published rates. See the full compliance uplift table →