Cloud Shared Responsibility Mapper
Service model

Hosted AI models and AI platforms: the shared responsibility split

The provider runs the model, its hosting and its patching. You run who may call it, what you send it, what it sends back, how long either is kept on your side, and the application built around it. Whether the provider may train on what you send is set by its terms, which you have to read.

Of the 14 control areas: 2 yours, 10 shared, 2 the provider's, before any category moves the line.

Every control area

AI platform
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 prompts and outputs in transit and at rest within its service; you decide what may be sent at all, and use customer-managed keys where the service offers 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 network the model is served from; you control which of your systems may call the endpoint and whether calls stay on a private path. ISO/IEC 27017 CLD.9.5.1
LOG Logging and monitoringsharedThe provider records usage for its own operation; you log who called the model with what, within your own retention rules.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.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 model service; you set content filters, data settings and the permissions of the keys that call it.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 securitysharedThe provider secures the model endpoint and its filters; you handle what goes in and what comes back in your own application, including injected instructions. 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 model service available; you plan for the service being unavailable and keep what you need of prompts and outputs yourself.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 retains and uses prompts only as its terms allow; you decide what may be sent, set retention where offered and read the terms on training use. ISO/IEC 27018 A.3.1

Service categories delivered this way by default

2