Paste the cloud services you use. See which controls are yours, the provider's, or shared.
Paste the cloud services you use. See which controls are yours, the provider
Swipe sideways for all 14 areas.
| Service | GOV | IAM | DAT | KEY | NET | LOG | VUL | CFG | APP | INC | BCP | PHY | SUP | AIR |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| S1 Virtual machines for the claims API | shared | yours | yours, service owner only | yours | yours, service owner only | yours | yours, service owner only | yours, service owner only | yours, service owner only | shared | yours, service owner only | provider operates, you assure | shared | yours, service owner only |
| S2 Virtual machines for batch reporting | shared | yours | no owner | yours | no owner | yours | no owner | no owner | no owner | shared | no owner | provider operates, you assure | shared | no owner |
| S7 Object storage buckets holding customer files | shared | yours | yours, service owner only | yours | shared | yours | yours, service owner only | yours, service owner only | yours, service owner only | shared | yours, service owner only | provider operates, you assure | shared | yours, service owner only |
| S10 Managed relational database | shared | yours | yours, service owner only | shared, providers differ here | shared | shared, providers differ here | shared, providers differ here | shared, providers differ here | yours, service owner only | shared | shared, providers differ here | provider operates, you assure | shared | yours, service owner only |
| S16 Hosted LLM API for the support chatbot | shared | yours | yours, service owner only | shared, providers differ here | shared | shared, providers differ here | provider operates, you assure, providers differ here | shared, providers differ here | shared | shared | shared, providers differ here | provider operates, you assure | shared | yours, service owner only |
| S19 Identity provider (SSO) | shared | yours | yours, service owner only | provider operates, you assure, providers differ here | provider operates, you assure | shared, providers differ here | provider operates, you assure | shared, providers differ here | provider operates, you assure | shared | shared, providers differ here | provider operates, you assure | shared | shared |
| S22 Managed firewall | shared | yours | no owner | shared, providers differ here | run by the MSP | shared, providers differ here | shared, providers differ here | shared, providers differ here | no owner | shared | shared, providers differ here | provider operates, you assure | shared | no owner |
| S30 CRM | shared | shared | yours, service owner only | provider operates, you assure, providers differ here | provider operates, you assure | shared, providers differ here | provider operates, you assure | shared, providers differ here | provider operates, you assure | shared | shared, providers differ here | provider operates, you assure | shared | shared |
36 services, 27 controls nobody owns.
504 bays: 159 yours (88 service owner only, 27 nobody), 67 provider operates, 246 shared, 4 MSP, 28 not drawn. A baseline from the service model.
Cloud Shared Responsibility Mapper, for SOC 2, ISO/IEC 27001 and CMMC assessments, reads your list of cloud services and maps the shared responsibility model onto it, service by service and control area by control area. Paste the cloud services you use. Get a shared responsibility map per service and control area, what the provider owns, what you own and what is shared, with the Cloud Controls Matrix, ISO/IEC 27017 and 27018 clauses behind each split, and the customer-owned controls nobody has named.
Paste service names and service models only: no account ids, no architecture, nothing from inside your cloud. The list is read in your browser and nothing is stored until you save.
Pick your frameworks and, for CMMC, your level: the split is shown for what you are assessed against.
The split follows the published shared responsibility model for each service model, with the clause behind it. Check it against your provider's own documentation before you hand it to an assessor.

Paste the service list you already keep
One service per line: the name alone, or with any of provider, service model, data classification, CUI, the accountable owner, a control owner per area, MSP, split documented and notes. Each is placed on one of 48 published service categories; a line that matches none is marked unplaced and never guessed. Recognised identifiers (account and subscription ids, resource names, IP addresses, hostnames, access keys) are removed in your browser; review the cleaned list before you save.
Read the responsibility plan
Every service a strip, every control area a bay: edged red where it is yours and a control owner is named, a red corner where only the service owner is named, filled red where nobody is: the orphaned control an assessor finds first. Shaded where the provider operates it and you assure it, hatched where it is shared, a dot where providers commonly differ from the baseline.
Hand over the customer responsibility matrix
Eleven findings in fixed order, each with the services it names, the clause quoted from the Cloud Controls Matrix, ISO/IEC 27017 and 27018, SOC 2, CMMC, C5 or ISO/IEC 27001, and the question to take to the platform owner. The matrix exports in the columns an assessor expects.
The Cloud Controls Matrix, ISO/IEC 27017 and the STAR shared responsibility disclosure are always shown: they are the cloud-specific codes that allocate each control.
Why a responsibility plan and not a consultant's workshop
Every provider publishes its side of the shared responsibility model, and every assessor asks for yours: a customer responsibility matrix that names who owns each control on each service. Most estates keep that as a spreadsheet of services with no column for control ownership, so the orphaned control, the one the model makes yours and nobody on your side runs, is found in the assessment. This draws the SSRM over the list you already have, in your browser, with the clause behind every split, and names every orphaned control before the assessor does.
Shared responsibility in the cloud: the questions assessors ask
What does Cloud Shared Responsibility Mapper do?
It reads your list of cloud services and maps the shared responsibility model onto it, service by service and control area by control area. You get a map showing what the provider owns, what you own and what is shared, with the Cloud Controls Matrix, ISO/IEC 27017 and 27018 clauses behind each split. It also names the customer-owned controls nobody has named.
What is a customer responsibility matrix?
Every provider publishes its side of the shared responsibility model, and every assessor asks for yours: a customer responsibility matrix that names who owns each control on each service. This tool draws a baseline responsibility map from the service model, to check against your provider's own documentation and your contract. The matrix exports in the columns an assessor expects.
Which frameworks can I map against?
You can pick SOC 2, ISO/IEC 27001, CMMC Level 1, CMMC Level 2, FedRAMP Moderate, C5, and ISO/IEC 27018 for personal data. The Cloud Controls Matrix, ISO/IEC 27017 and the STAR shared responsibility disclosure are always shown, as the cloud-specific codes that allocate each control. For CMMC, you also pick your level.
Do I have to give it access to my cloud account?
No. You paste service names and service models only: no account ids, no architecture, and nothing from inside your cloud. It never connects to a cloud account, and the list is read in your browser with nothing stored until you save.
What is an orphaned control?
An orphaned control is a customer-owned control that nobody on your side runs, which an assessor finds first. The map shows a control area filled where nobody is named, and a specimen run can report a count such as 27 controls nobody owns. It reads labels only, so the gap is a question for the platform or service owner.
What should I do with the result?
Use it as a baseline responsibility map from the service model, built in minutes from the service list you already keep. Check it against your provider's own documentation and your contract before you hand it to an assessor. It never reproduces a provider's own matrix.
Is it free to map my services?
Eight services can be mapped free with no account. A published dictionary of 48 service categories, 14 control areas and the clause text loads with the page, and every split is drawn in your browser.
What exactly can I paste?
One service per line: the name alone, or with any of provider, service model, data classification, CUI, the accountable owner, a control owner per area, MSP, split documented and notes. You can also paste a CSV export with a header row. Each line is placed on one of 48 published service categories, and a line that matches none is marked unplaced and never guessed.
What are the control areas it maps?
There are fourteen control areas, shown as columns, covering areas such as governance, identity, data, keys, network, logging, vulnerability, configuration, application, incident, continuity, physical, supplier and AI. Every service is a strip and every control area a bay. Recognised identifiers such as account and subscription ids, resource names, IP addresses, hostnames and access keys are removed in your browser before you save.
For a CMMC assessment, where do I start?
Start from the CMMC customer responsibility matrix template, then map your services for CMMC Level 1 or Level 2. The split is shown for what you are assessed against, with the CMMC clauses beside each split. It gives you a named owner against every control your cloud leaves to you.
Does it tell me I am compliant?
No. It does arithmetic on your rows and states each obligation in our words, citing its clause; it never rules on you. It is a baseline from the service model, not a verdict, and you check it against your provider's documentation and your contract.
What is the providers-differ marker?
A dot marks a bay where providers commonly differ from the baseline, such as key management or logging on a managed database. It flags where the published model is not enough, and the provider's own documentation decides. That is a question to take to the platform owner, not a ruling.
What this does, and what a spreadsheet, a consultant or an AI assistant does better
A spreadsheet is better for keeping the service list and the matrix as your own working document, with the owners, tabs and history you maintain, and it needs no dictionary. A consultant or an assessor is better on whether a control is truly in place and on how your provider's own shared responsibility model applies, which this tool only baselines. A general AI assistant is better for drafting the matrix commentary or the evidence narrative an assessor reads. What this does that they do not is draw the published shared responsibility model over each pasted service and control area, mark what is yours, the provider's or shared with the Cloud Controls Matrix, ISO/IEC 27017 and 27018 clause behind each split, and name the customer-owned controls nobody has; it never connects to your cloud account and never reproduces a provider's own matrix, and is a baseline to check against the provider's documentation and your contract.
Primary source: Cloud Controls Matrix