Cloud Shared Responsibility Mapper
Service model

Serverless functions and event services: the shared responsibility split

The provider runs the servers, the runtime and the scaling. You run the function code and its dependencies, the permissions each function holds, the triggers that reach it and the data it touches.

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

Every control area

Serverless
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 the function's storage and environment with keys it holds; you encrypt the secrets and data the function handles and choose who holds those keys.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 network the functions execute in; you control the triggers and endpoints that reach each function and any private network it attaches to. ISO/IEC 27017 CLD.9.5.1
LOG Logging and monitoringsharedThe provider records invocations and platform events; you log what your code does, keep the logs and alert on 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 runtime and the servers under it; you keep your function code and its dependencies free of known flaws.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 runtime and its hosts; you set each function's permissions, timeouts, environment and triggers 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 runtime available across its zones; you back up the data the functions write and keep the code and configuration to redeploy.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

1