CMMC customer responsibility matrix template
A customer responsibility matrix says, for each cloud service in your CMMC assessment scope, which practices the provider meets, which you meet and which are shared, and who on your side owns each one. The assessor reads it beside your system security plan. This template has the exact columns Cloud Shared Responsibility Mapper reads: fill it in, paste it back, and the mapper draws the split for every control area with the clause behind it.
Who CMMC applies to, and the cloud questions it raises
CMMC applies to the defence industrial base: contractors that handle Federal Contract Information (FCI, Level 1) or Controlled Unclassified Information (CUI, Level 2). A cloud service that stores, processes or transmits CUI is expected to meet FedRAMP Moderate or its equivalent, and an external service provider that is not a cloud service provider is treated differently from one that is. Both are named here, not quoted: the DFARS clause, the DoD equivalency memorandum, the CMMC external service provider guidance and the CMMC assessment guide.
The mapper gives a baseline responsibility map from the service model, to check against your provider's own documentation and your contract. It never connects to a cloud account; recognised identifiers are removed in your browser, so review the cleaned list before you save.
The columns
11 columns| Column | What goes in it |
|---|---|
Service | The service as you name it: "Managed relational database", "File storage for engineering drawings". Names and models only, never an account id or a hostname. |
Provider type | A generic word: public cloud, SaaS vendor, managed service provider. The mapper does not need a brand. |
Model | IaaS, PaaS, SaaS, serverless or AI platform. Leave it blank and the category default is used; a category with no default is flagged. |
CUI | yes if the service stores, processes or transmits CUI. The Level 2 finding fires only on these. |
Accountable owner | The person or team who answers for the service in the system security plan. |
Identity owner, Encryption owner, Logging owner, Backup owner | The control owner who operates that area day to day. Any control area works as a column: "Network owner", "Patch owner", "Configuration owner". A default for every service can go in a first line instead: owner identity: Identity team. |
Split documented | yes, or the areas whose provider and customer split you have written down: "identity, logging". |
Notes | Anything else: customer-managed keys, retention settings, what the MSP runs. |
The five example rows in the file
invented| Service | Provider type | Model | CUI | Accountable owner | Identity owner | Encryption owner | Logging owner | Backup owner | Split documented | Notes |
|---|---|---|---|---|---|---|---|---|---|---|
| Virtual machines for the proposal system | public cloud | IaaS | yes | Platform team | Identity team | Security team | identity, logging | |||
| Managed relational database | public cloud | PaaS | yes | Data team | DBA team | Data team | backup | point-in-time restore tested each quarter | ||
| Email and collaboration suite | SaaS vendor | SaaS | yes | IT operations | Identity team | Security operations | yes | |||
| File storage for engineering drawings | public cloud | IaaS | yes | |||||||
| CI/CD pipelines | SaaS vendor | SaaS | no | Platform team | no CUI in build artefacts |
Replace the example rows with your own services, keep the header row, and paste the whole file into the mapper. Tick CMMC Level 2 and the split is shown with the Level 2 practices behind each area. The CMMC clauses the mapper quotes.