Table of Contents
Most MSPs serving the defense industrial base spent the last year treating CMMC as their clients' problem. The client signs the contract, the client posts the score in SPRS, and the client takes the risk. That framing stopped holding on November 10, 2026. Phase 2 of the CMMC rollout now lets the Department of Defense require third-party Level 2 certification from a C3PAO (CMMC Third-Party Assessment Organization) on applicable contracts, where self-assessment used to be enough. Once an outside assessor walks into a client's environment, the services you deliver are examined right along with it. This article explains the CMMC Phase 2 MSP requirements in practical terms: which of your managed assets get assessed, what documentation your clients will ask for, and how to get ready in 60 days against NIST SP 800-171.
What Changed on November 10, 2026?
CMMC is being phased in over several years under 32 CFR Part 170 and the matching DFARS clause. Phase 1 started in November 2025 and mostly called for Level 1 and Level 2 self-assessments. Phase 2 is the step that adds independent verification.
| Phase | Start Date | What It Introduced |
|---|---|---|
| Phase 1 | November 10, 2025 | Level 1 and Level 2 self-assessments in applicable solicitations |
| Phase 2 | November 10, 2026 | Level 2 certification assessments by a C3PAO in applicable solicitations |
| Phase 3 | November 2027 | Level 3 assessments by DoD's DIBCAC |
| Phase 4 | November 2028 | Full implementation across applicable contracts |
This matters because a self-assessment is a document your client controls, while a C3PAO assessment is evidence-driven and adversarial in the healthy sense. The assessor tests the 110 security requirements of NIST SP 800-171 Rev. 2 using the 320 assessment objectives in SP 800-171A. They interview the people who run the controls. If the people running access control, logging, patching, and endpoint protection work for you, you'll be the ones interviewed.
Where MSPs Fit: The External Service Provider Role
The CMMC rule defines an External Service Provider (ESP) as an outside person or organization that provides services to the contractor's environment. As the name suggests, that covers most of what an MSP or MSSP does. The rule then splits ESPs into two groups, and the split determines how much scrutiny you get.
- Cloud Service Providers (CSPs) that store, process, or transmit CUI. These must meet the FedRAMP Moderate baseline or an equivalent. If you host a client's CUI in your own multi-tenant cloud, this is where you sit, and it's a heavy lift.
- Non-CSP ESPs. This is where most MSPs land. You don't need your own CMMC certificate, but the services and assets you provide that touch the client's CMMC scope are assessed as part of their assessment. Some MSPs choose to get voluntarily assessed to reduce friction across their client base. A growing number of primes are asking for it.
Put plainly, your client's certification depends partly on how you operate, whether or not your logo is on the certificate.
Which MSP-Managed Assets Get Assessed?
CMMC Level 2 scoping sorts every asset into categories. For MSPs, two of them carry most of the weight.
Security Protection Assets
Security Protection Assets (SPAs) provide security functions or capabilities to the CUI environment, whether or not they handle CUI themselves. They're assessed against the requirements that apply to them. For a typical MSP, that includes:
- Remote monitoring and management (RMM) platforms and agents
- PSA and ticketing systems that hold configuration details, credentials, or remote session links
- Identity providers, privileged access management, and password vaults
- SIEM, log collectors, and the SOC that watches them
- EDR/XDR consoles and policy management
- Backup consoles, and the backup repositories themselves if they hold CUI
- Firewalls, VPN concentrators, and edge routers you manage
A common mistake is assuming the RMM is out of scope because it "doesn't store CUI." It can push scripts to every endpoint in the enclave. An assessor will treat it as part of the protection layer, because that's what it is.
CUI Assets and the Spillover Problem
If CUI lands anywhere in your environment, those systems become CUI assets. That can happen through a ticket attachment containing a drawing, a screenshot in a remote session recording, or a backup copy stored in your tenant. It's one of the most frequent and least intentional ways MSPs widen their own scope. Trace where client data actually goes, not where your runbook says it goes.
Why This Week's Vulnerabilities Matter Here
The assets in scope are exactly the ones attackers aim for. Three items from this week's intel map directly to defense-client environments:
- CVE-2026-129453 (CVSS 9.9), DrayTek Vigor2960 1.5.1.6. A heap-based buffer overflow in the
check_file_existfunction of/cgi-bin/mainfunction.cgi, triggered through theupload_nameargument, can be exploited remotely. A public exploit is available. Remediation: upgrade to firmware 1.5.1.7 and restrict management interfaces from the internet. If you manage edge devices for defense clients, this falls under 3.14.1 (flaw remediation) and 3.4 (configuration management). - CVE-2026-19732 and CVE-2026-77033 (CVSS 9.9) and CVE-2026-93664 (CVSS 10), Dassault 3DEXPERIENCE Station Launcher App, R2023x through R2026x. Two OS command injection flaws allow arbitrary command execution on the server, and a deserialization flaw allows unauthenticated remote code execution. Defense manufacturers use PLM and CAD platforms like this to hold controlled technical data, which is CUI at its most valuable. Remediation: apply Dassault's vendor fix for the affected releases, and until then limit network access to the Station Launcher component to trusted hosts only.
- CVE-2026-129483 (CVSS 9.1), Cyrus SASL through 2.1.28. The SRP server mechanism doesn't reject client public values that are multiples of N. An attacker can send A equal to N, force a zero shared secret, and authenticate as any existing user without a password. Remediation: disable the SRP mechanism on mail and directory services that use Cyrus SASL until a patched build is deployed.
An assessor will expect to see that you found these, rated them, and fixed them within the timelines your client's SSP commits to. That evidence comes from continuous vulnerability assessment. A quarterly scan PDF won't show it.
The Shared-Responsibility Documentation Clients Will Request
Expect your defense clients' compliance leads to send you a list. Here's what's going to be on it.
- A Customer Responsibility Matrix (CRM). For each of the 110 requirements, it states whether the control is met by the MSP, by the client, or shared, and how. A requirement marked "shared" with no explanation will fail an interview. Be specific: "MSP enforces MFA for all privileged access via [IdP]; client approves new privileged accounts via ticket."
- Your sections of their System Security Plan (SSP). Clients need text describing how your services implement controls, which tools you use, and where evidence lives.
- Network and data-flow diagrams that show your connection paths into the enclave: remote access, agent communication, log forwarding, and backup replication.
- Asset inventory with CMMC categories for everything you manage, so the client can draw an accurate boundary.
- Evidence artifacts: audit log retention settings (3.3.1), baseline configurations (3.4.1), MFA enforcement (3.5.3), FIPS-validated cryptography for CUI in transit and at rest (3.13.11), nonlocal maintenance controls (3.7.5), and personnel screening for your technicians (3.9.1).
- Incident response commitments. DFARS 252.204-7012 requires reporting cyber incidents to DoD within 72 hours, and preserving images and data for 90 days. Your contract needs to say who detects, who preserves, and who notifies. We explored that question in our post Who Notifies When a Client Gets Breached?, and under CMMC it gets sharper.
If you support twenty defense clients, writing twenty bespoke CRMs by hand is a recipe for contradictions. Build one master CRM per service offering. Then adjust only the client-specific deltas.
Scoring Reality: What Happens If You Fall Short
Level 2 uses a weighted scoring model: 110 points if every requirement is met, with deductions of 1, 3, or 5 points per gap. A client can receive Conditional status with a score of at least 88 and a Plan of Action and Milestones (POA&M). Those open items must close within 180 days. Not every requirement can go on a POA&M, though. Higher-weighted controls like MFA and FIPS-validated encryption generally must be met at the time of assessment.
The practical consequence is blunt. If your RMM lacks MFA, or your remote sessions don't use validated cryptography, the gap belongs to your client's score. That's the moment your client starts looking at other MSPs.
A 60-Day CMMC Readiness Checklist for MSPs
This plan assumes you already support at least one client pursuing Level 2. Each phase ties back to NIST SP 800-171 families.
| Days | Focus | Key Actions | 800-171 Families |
|---|---|---|---|
| 1–15 | Scope and inventory | Map every tool and connection into each client enclave; categorize assets; find CUI spillover in tickets, recordings, and backups | 3.4, 3.13 |
| 16–30 | Identity and access | Enforce MFA on RMM, PSA, IdP, and vaults; remove shared admin accounts; set up session timeouts and least privilege for technicians | 3.1, 3.5, 3.7 |
| 31–45 | Monitoring and vulnerability management | Centralize logs with defined retention; document alert triage; scan SPAs and managed edge devices continuously; patch criticals like the DrayTek and 3DEXPERIENCE flaws | 3.3, 3.6, 3.11, 3.14 |
| 46–60 | Documentation and validation | Finalize the master CRM and SSP language; run a mock interview with your technicians; commission an independent test of your access paths | 3.12, 3.6, 3.2 |
A few details that tend to decide outcomes:
- Train the people who'll be interviewed. Assessors ask technicians how they actually perform a control. If your tier-two engineer describes a process that differs from the SSP, that's a finding.
- Test your access paths the way an attacker would. A focused penetration test against your RMM, VPN, and jump hosts shows whether the boundary in your diagrams matches reality.
- Check cloud tenants holding client data. If any CUI sits in a cloud you administer, confirm the provider's FedRAMP Moderate status or equivalent. Review the configuration through a cloud security lens, not just a checkbox.
- Version-control your evidence. Screenshots dated six months ago don't prove a control operates today.
Making It Repeatable Across Clients
The hardest part of CMMC for an MSP isn't any single control. It's consistency across dozens of client environments when each one runs on a different mix of point tools. That's where most practices break down. Evidence lives in five consoles, the CRM lives in a spreadsheet, and nobody can answer "are all twenty enclaves enforcing MFA on privileged access right now?"
We built our approach around that problem. Rogue Logics runs governance and GRC mapping across 36 frameworks, including NIST SP 800-171, on the same platform as our 24/7 SOC monitoring, attack-surface scanning, and threat intelligence. Control status and evidence stay current instead of being rebuilt before each assessment. Our US-based vCISOs work with MSPs to standardize a CRM per service line, then roll it across client environments. The same posture can carry your other contractual obligations, such as SOC 2 and CIS Controls, so you aren't running parallel programs.
The Takeaway
Phase 2 shifts CMMC from a statement your clients make to a test your clients take, with you sitting in the room. For MSPs, that's both an exposure and an opening. The practices that document their shared responsibilities clearly will become the default choice for defense contractors. So will the ones that secure their own management plane and can show continuous evidence on demand. The ones that can't will find their clients' assessment findings turning into their own contract terminations. The 60 days to get ready start now, and they start with your own tools.