Cloud Shared Responsibility Mapper
Service model

Platform as a service: the shared responsibility split

The provider runs the platform and its runtime and patches both. You run the identities that reach it, the configuration you choose, the code and data you put on it, and the half of each shared control the platform hands back to you.

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

Every control area

PaaS
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 accessyoursThe accounts, roles and second factors inside your tenancy are yours to grant, review and remove; the provider secures only its own staff's privileged 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 keyssharedThe provider encrypts stored data by default with keys it holds and runs the key service; you choose customer-managed keys where the data needs them, set rotation and decide who may use or revoke them.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 securitysharedThe provider runs the platform network and keeps tenants apart; you decide which endpoints are public, add private connections and set the rules on them. ISO/IEC 27017 CLD.13.1.4
LOG Logging and monitoringsharedThe provider logs the platform and offers activity and diagnostic logs; you turn those logs on, send them where you keep them and review them.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 managementsharedThe provider patches the platform, the runtime and the managed engine; you scan and patch the code, libraries and images you deploy onto it.Providers differ here: Which runtime, image and dependency patches the provider applies, and on what schedule, differ by provider. ISO/IEC 27017 12.6.1
CFG Configuration and hardeningsharedThe provider hardens the platform to its own baseline; you set every tenant option, close public defaults and hold your settings to a baseline.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 securityyoursThe code you deploy is yours to build and test securely; the provider has no view of it. 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 platform available and may keep its own backups; you decide whether those backups are enough, keep your own copy where needed and test a restore.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 retentionyoursWhat data goes into the service, for what purpose and how long it is kept is yours to decide and delete; the provider stores what you give it. ISO/IEC 27017 CLD.8.1.5

Service categories delivered this way by default

20