A CMMC external service provider (ESP) is any outside company whose people, technology, or facilities run IT or security services for you and hold your Controlled Unclassified Information (CUI) or your security data while doing it. Your cloud email, your managed service provider (MSP), your outsourced security monitoring, and your offsite backup vendor are the usual candidates.
Two questions decide what the rule asks of each one. Is the provider a cloud service provider? And does it hold CUI, security data only, or neither? A cloud provider that holds CUI must meet the FedRAMP Moderate baseline or its equivalent. Every other ESP falls inside your own assessment scope. None of them is required by the rule to hold its own CMMC certification. This is explanatory content, not legal advice, so read your contract and your prime's flowdown terms for anything stricter.
What counts as a CMMC external service provider
The definition is in 32 CFR 170.4. An ESP is "external people, technology, or facilities that an organization utilizes for provision and management of IT and/or cybersecurity services on behalf of the organization." The next sentence narrows it: CUI or Security Protection Data must be processed, stored, or transmitted on the provider's assets for it to be considered an ESP.
Security Protection Data is the part most small shops miss. The same section describes it as security relevant information, including configuration data needed to run a security tool, log files, data about the configuration or vulnerability status of in-scope assets, and passwords that grant access to the in-scope environment. An MSP that never opens a drawing but keeps your firewall configuration, your logs, and your administrator passwords in its own tools holds Security Protection Data.
That leaves a clear exit. A vendor that holds neither kind of data does not meet the CMMC definition of an ESP. Your payroll service, your marketing agency, and the company that hosts a public website with no contract data are vendors, not ESPs.
The table that sorts every provider
Table 4 in 32 CFR 170.19(c)(2) sets the Level 2 rule. It is short enough to restate in full.
| The provider holds | If it is a cloud service provider | If it is not a cloud service provider |
|---|---|---|
| CUI, with or without security data | It must meet the FedRAMP requirements in DFARS 252.204-7012. | Its services are in your assessment scope and are assessed as part of your assessment. |
| Security data only, no CUI | Its services are in your scope and are assessed as Security Protection Assets. | Its services are in your scope and are assessed as Security Protection Assets. |
| Neither | Not an ESP under CMMC. | Not an ESP under CMMC. |
CMMC Phase 2 and third-party assessments are suspended for now, so "your assessment" today means your Level 2 self-assessment and the SPRS score that comes out of it. The scoping rule is the same either way. If a provider's service is in scope and you cannot show how a requirement is met there, you cannot honestly mark that requirement as met.
Cloud providers that hold CUI: FedRAMP Moderate or equivalent
The cloud rule comes from the contract clause. DFARS 252.204-7012 says that if you use an external cloud service provider to store, process, or transmit covered defense information, you must require and ensure that the provider meets security requirements equivalent to the FedRAMP Moderate baseline and complies with paragraphs (c) through (g) of the clause, which cover incident reporting, malicious software, media preservation, forensic access, and damage assessment.
The CMMC rule gives two ways to satisfy this for a Level 2 self-assessment, in 32 CFR 170.16(c)(2):
- FedRAMP Authorized. The product or service is listed on the FedRAMP Marketplace at the Moderate baseline or higher. This is the simple route. You check the listing, confirm that the exact service you bought is the one listed, and keep a copy.
- FedRAMP Moderate equivalent. The product is not authorized but meets equivalent security requirements "in accordance with DoD Policy." That policy is a DoD CIO memo dated December 21, 2023. It expects the provider to show full compliance with the Moderate baseline through an assessment by a FedRAMP-recognized third-party assessor, and to hand you the resulting body of evidence. The memo puts the job of checking that evidence on you, the contractor.
For a small shop the practical reading is this: prefer an authorized service. If a vendor says "equivalent," ask for the assessor's report and the full evidence package before you sign, and expect that reviewing it will take someone with FedRAMP experience. A sales page that says "FedRAMP ready" or "built on a FedRAMP cloud" is not either route. Our posts on Google Workspace and Microsoft GCC High walk through the two most common platforms.
MSPs and other providers that are not cloud services
An MSP that administers your systems, a consultant with a standing admin account, or a help desk firm with remote access is an ESP but usually not a cloud provider. For these, 32 CFR 170.16(c)(3) sets three conditions:
- The use of the ESP, its relationship to you, and the services it provides are documented in your System Security Plan (SSP) and described in the ESP's service description and customer responsibility matrix.
- The ESP services you rely on to meet requirements are assessed within the scope of your assessment against all Level 2 security requirements.
- Your own infrastructure that connects to the ESP's service is part of the scope too.
Notice what is missing. The rule does not say the MSP must be certified. It says the ESP "may voluntarily undergo a CMMC certification assessment to reduce the ESP's effort required" during yours. A provider that has done the work is easier to rely on, but the question to ask is not "are you certified?" It is "can you give me the evidence for the requirements you perform for me?" Our MSP guide lists what to ask for.
Watch for an MSP that is quietly both kinds. If it hosts your files, mail, or backups on its own multi-customer platform, that part of the service may be a cloud offering, and the FedRAMP row of the table applies to it.
Providers that hold only security data
A managed security provider that collects your logs, or a remote monitoring tool that stores device inventories and patch status, usually holds Security Protection Data without CUI. Those services are in scope as Security Protection Assets. Table 3 of 32 CFR 170.19 says such assets are assessed against the Level 2 requirements "that are relevant to the capabilities provided." A log service is judged on the audit and access requirements it performs, not on all 110.
The risk is drift. A monitoring agent that starts capturing file contents or full network traffic has moved the provider into the CUI row. Ask what the tool collects, in writing, and look again whenever the provider changes tools.
The customer responsibility matrix
The rule names one document in every ESP scenario: the customer responsibility matrix, or CRM. It "describes the responsibilities of the OSA and ESP with respect to the services provided." OSA means the organization seeking assessment, which is you. Some vendors call the same thing a shared responsibility matrix.
A useful CRM lists each NIST SP 800-171 Rev 2 requirement the service touches and says who does what:
- Provider. The provider meets it fully. You keep its evidence or its authorization on file.
- Shared. The provider supplies the capability and you configure or operate it. Multi-factor authentication is the classic case: the platform offers it, and you have to turn it on for everyone.
- Customer. It is yours. Training your people, screening them, and locking the office door never transfer to a vendor.
Your SSP must document these responsibilities or refer to the matrix. Then check the matrix against reality. A row marked "provider" that the provider cannot back with evidence is an unmet requirement in your score, not theirs.
What about Level 1?
The Level 1 scoping paragraph in 32 CFR 170.19 tells you to consider the people, technology, facilities, and ESPs that process, store, or transmit Federal Contract Information (FCI). There is no ESP table and no FedRAMP requirement at Level 1, because FAR 52.204-21 does not set one. You still answer for the 15 basic safeguards wherever your FCI sits, including a provider's systems.
What to do this week
- List every outside company with access to your systems or data: cloud services, MSP, security monitoring, backup, copier and phone vendors with remote access.
- For each one, write down what it holds: CUI, security data only, FCI only, or none of these.
- Mark which are cloud services. For those that hold CUI, find the FedRAMP Marketplace listing or ask for the equivalency evidence.
- Ask every ESP for its service description and customer responsibility matrix.
- Record each provider and what it does in your SSP, and place it in your scoping diagram and asset inventory.
- Where a provider cannot produce evidence, score that requirement as not met and put it on your plan of action. The free SPRS calculator shows what each one costs.
CMMC Map, CMMC compliance software for small defense contractors, gives you a free assessment of all 110 requirements where you can note which provider covers each one. The paid plan generates the SSP and plan of action from those answers, so the provider relationships you record end up in the documents a prime or assessor will read.
See which requirements your providers leave to you
The free CMMC Map assessment covers all 110 requirements and the Level 1 safeguards, so you can mark what each provider handles and see what is still yours.
Start free in CMMC Map