Glossary
Shared responsibility model
Definition
The shared responsibility model explains which security tasks a service provider handles and which remain with the customer.
It separates the provider's security duties from the customer's. Confirm the practical boundary for the service rather than relying on a generic diagram.
A customer may include “Shared responsibility model” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.
A shared responsibility model describes the division of security work between a provider and its customer. It is commonly used for cloud services, where the provider operates some layers of technology and the customer controls others.
The boundary changes with the service model. A provider of a ready-made application may maintain its operating systems, while a customer renting virtual servers may need to maintain those operating systems themselves. Account permissions and the customer's use of data usually remain decisions the customer must manage.
Imagine a small retailer using a hosted sales application. The supplier may patch the platform, but the retailer still decides whether a former employee keeps access and which staff may export customer records. Assuming the supplier owns both jobs creates a gap.
A generic diagram is a starting point rather than a substitute for the actual service arrangement. Map who configures each control, who checks it is operating and what happens when it fails. Backup and recovery are especially important. Shared responsibility should assign work clearly; it should not leave each party assuming the other is doing it.