Cloud Shared Responsibility Mapper
Service model

Software as a service: the shared responsibility split

The provider runs the whole application. You still run who has an account and what role it holds, the tenant settings, what data you put in and how long it stays, and your side of every incident.

Of the 14 control areas: 1 yours, 8 shared, 5 the provider's, before any category moves the line.

Every control area

SaaS
Control areaOwnerWhy, and the clause
GOV Governance and policysharedThe provider runs its own security programme for the service and publishes its side of the model; you set which data may go into this service and who may buy it, and keep the allocation in writing. ISO/IEC 27017 6.1.1
IAM Identity and accesssharedThe provider runs the sign-in service, its administrative plane and its staff's privileged access; you decide who holds an account and which role, enforce the second factor and review access. ISO/IEC 27017 9.2.3
DAT Data classification and handlingyoursWhat the data is, how it is labelled and where it may go is yours on every model; the provider only tells you what labelling and location options the service offers. ISO/IEC 27017 8.2.2
KEY Encryption and keysprovider operates, you assureThe provider encrypts the application's data with keys it manages; a key you hold exists only where the service offers one and you turn it on. You assure it: read the provider's assurance report for this area.Providers differ here: Default key custody, and whether customer-managed or customer-held keys are offered, differ by provider and by service. ISO/IEC 27017 10.1.2
NET Network securityprovider operates, you assureThe provider runs the application's network end to end; you control only which addresses and devices may sign in, where the service offers it. You assure it: read the provider's assurance report for this area. ISO/IEC 27017 CLD.9.5.1
LOG Logging and monitoringsharedThe provider logs the application and exposes an audit log of your tenant; you switch the audit log on, keep it long enough and watch it.Providers differ here: Which logs are on by default, how long the provider keeps them and what it takes to keep more differ by provider. ISO/IEC 27017 CLD.12.4.5
VUL Vulnerability and patch managementprovider operates, you assureThe provider patches the application and everything under it; you keep only the devices and integrations that reach it. You assure it: read the provider's assurance report for this area. ISO/IEC 27017 12.6.1
CFG Configuration and hardeningsharedThe provider hardens the application and its defaults; you choose and review the tenant settings, sharing rules and integrations you enable.Providers differ here: Default settings, and which of them the provider enforces or leaves to you, differ by provider. ISO/IEC 27017 CLD.12.1.5
APP Application securityprovider operates, you assureThe application is the provider's to build and test; your side is the integrations and extensions you add to it. You assure it: read the provider's assurance report for this area. ISO/IEC 27017 14.2.1
INC Incident responsesharedThe provider reports incidents affecting your data within the agreed time and handles its own; you detect and handle incidents in what you run, and tell the provider what affects its service. ISO/IEC 27017 16.1.2
BCP Business continuity and backupsharedThe provider keeps the application available and restores it after its own failures; you keep an export or backup of your own data to recover from deletion or corruption.Providers differ here: Whether the provider backs up your data, for how long, and whether you can restore it yourself differ by provider. ISO/IEC 27017 12.3.1
PHY Physical and environmentalprovider operates, you assureThe data centres, power, cooling, access to the floor and the disposal of retired media are the provider's; your evidence is its assurance report, not your own inspection. You assure it: read the provider's assurance report for this area. ISO/IEC 27017 11.2.7
SUP Supplier and subservicesharedThe provider publishes its side of the model and the suppliers behind the service; you hold the matrix for your estate, read the provider's side and keep the agreement that binds both. ISO/IEC 27017 CLD.6.3.1
AIR AI use and data retentionsharedThe provider stores what your users put into the application and follows its terms on use; you choose the retention and AI settings for your tenant and read the terms on how content may be used. ISO/IEC 27018 A.3.1

Service categories delivered this way by default

13