
IaaS, PaaS and SaaS: who manages what, and what always stays yours
The textbook answer on IaaS, PaaS and SaaS fits on a beer mat: the further up the stack you go, the more the provider does for you. What the beer mat leaves out is where it goes wrong in practice: the tasks that stay with you while everyone assumes the cloud has taken them over.
With IaaS you rent infrastructure and manage everything from the operating system up; with PaaS the provider also runs the platform; with SaaS you use finished software.
In all three models your data, your user accounts and access rights, and the devices people sign in from remain your responsibility.
The most expensive misconception is that a SaaS service backs up your data for you. The provider keeps the service running; what you delete or what gets encrypted is your problem.
IaaS, PaaS and SaaS in three paragraphs
IaaS (Infrastructure as a Service) is rented infrastructure: compute, storage and network in a provider’s data centre. You get a virtual server, and whatever runs on it is yours. The operating system, its updates, the security settings and the applications are yours to manage, or to have managed by someone you appoint.
PaaS (Platform as a Service) goes one layer further. The provider also manages the operating system and the platform your application runs on: a database, a web environment, an integration service. You bring the application or the data and decide how it is configured, but you no longer patch a server.
SaaS (Software as a Service) is finished software used through a browser or an app: mail and collaboration in Microsoft 365, an accounting package, a CRM, a ticketing system. You manage no server and no platform, only the configuration, the users and what you put in.
Most organisations use all three at once, often without ever calling them that. That is why “which model should we choose” is a less useful question than “who does what, for each service we already have”.
The shared responsibility model, layer by layer
Every major cloud provider publishes a shared responsibility model: the provider is responsible for the security of the cloud, you for what you do in it. Where that line sits moves with the model. From the bottom up:
- Data centre, power, cooling and physical security: always the provider.
- Hardware, storage and network: always the provider.
- Virtualisation: always the provider.
- Operating system and its patches: you with IaaS, the provider with PaaS and SaaS.
- Middleware, database engine and runtime: you with IaaS, the provider with PaaS and SaaS.
- The application itself: you (or the software vendor) with IaaS and PaaS, the provider with SaaS.
- Configuration and settings of the service: always you.
- Users, permissions and sign-in: always you.
- Data: always you.
- The devices people sign in from: always you.
Hold that list against your own services. In most organisations there is no name next to “configuration” and “users”, because everyone assumed the provider had it.
What your organisation keeps in every model
Four things never move to the provider, however far up the stack you go.
- Your data. What is in it, who may see it, how long you keep it and whether you can get it back. The provider stores it; control and accountability stay with you, including under UK GDPR. For personal data there should be a data processing agreement with the provider.
- Identities and access. Who has an account, with which rights, and whether multi-factor authentication is on. Most cloud incidents start with a compromised account, and that account is yours.
- Devices. A SaaS service is as secure as the laptop or phone someone signs in from. Updates, encryption and management of those devices are in no cloud contract.
- Settings. External sharing, mail forwarding, retention periods, logging on or off. The provider supplies the switches; their position is your choice, and the default is not always the safe one.
The NCSC’s cloud security guidance makes the same point from the other side: it asks you to understand which security principles the provider meets and which ones remain with you.
Patching, backup and licences in each model
Three tasks cause most of the confusion in practice. This is where they sit.
Patching. With IaaS you patch the operating system and all software on the server yourself, exactly as with your own hardware. With PaaS the provider patches the platform, but your own code and the components you bring with it remain yours. With SaaS the provider handles the software; you keep the devices and browsers used to reach it up to date.
Backup. With IaaS you arrange it yourself: a virtual server is not backed up by default, and a snapshot in the same environment is not a backup somewhere else. With PaaS providers often include a built-in backup, with a retention period you need to check. With SaaS the provider keeps the service running through a failure on its side, but that is not a restore of what you or an attacker delete. That is why a separate Microsoft 365 backup exists.
Licences. SaaS is usually charged per user, and the management is in joiners and leavers: a former employee who keeps a licence costs money and is an open door. IaaS and PaaS often run on consumption, so you also pay for what is switched on and unused. Software you install on an IaaS server carries its own licence terms, and they do not always apply in the cloud as they do on your own server.
Where it goes wrong in practice
- “It’s in the cloud, so it’s backed up.” The most common assumption, and with SaaS the one most often untrue in the sense people mean it.
- A virtual server nobody manages. Set up once for a project, never patched again, and still reachable from the internet. With IaaS that is your server, even if it is not in your own rack.
- Admin accounts without extra protection. One administrator account without multi-factor authentication opens up the entire environment.
- SaaS bought outside IT. A department signs up with a company card, business data lands in a service nobody knows about, and nobody cancels it.
- No way out. How you get your data back when you switch, in which format and within what period, is rarely asked until it is needed.
The question to ask for each service
Which model fits depends less on technology than on what you want to manage and can manage. Three questions make it concrete.
- How much customisation do you really need? Standard processes such as mail, documents and accounting are best served by SaaS. If you need something bespoke, you end up with PaaS or IaaS, and take on management with it.
- Who manages the layers that stay with you? An IaaS server needs the same care as your own server. If there is no internal time or expertise for that, it is a task to assign before you switch the server on, not after.
- What happens if the service or the provider disappears? How long you can do without, where the second copy of your data lives, and how you move.
Which provider you pick is a separate question from which model, and it is best answered once you know which layers you want to keep.
What to ask a provider or managed service partner
- Which layers do you manage, and is that written into the contract per layer?
- What does your backup cover, how long is it kept, and can I restore something I deleted myself?
- How and when are updates applied, and am I told beforehand?
- Where is my data stored, and which data processing agreement applies?
- How do I take my data with me when I leave, in which format and within what period?
- Which admin accounts do you hold in my environment, and can I revoke them myself?
“The cloud takes care of that” is not an answer to any of these. Ask who actually does it.
Where our work stops
What we do. We manage the layers that stay with you: virtual servers under IaaS, the configuration of Microsoft 365 and other SaaS services, users and permissions, multi-factor authentication, devices and the backup of your cloud data. We record for each service who does what, so every layer has a name next to it.
What we don’t do. We are not a cloud provider and have no say over the data centre, the hardware or the availability of Microsoft’s or any other provider’s service; their terms and service levels are theirs. Nor are we lawyers: whether a data processing agreement or an international data transfer is in order for your situation is for your own legal adviser or data protection officer to assess.
Questions we get about this
The five that come up most.
What is the difference between IaaS, PaaS and SaaS?
The difference is how much the provider manages. With IaaS you rent infrastructure and manage the operating system and everything above it. With PaaS the provider also runs the platform and you bring the application. With SaaS you use finished software and manage only the configuration, the users and your data.
Is Microsoft 365 SaaS?
Yes. Microsoft manages the software, the servers and the data centre. You manage the users, permissions, sharing and security settings, the devices people sign in from and the data stored in it.
Do you need to back up SaaS data yourself?
In most cases, yes. A SaaS provider keeps the service running through a failure on its side, but does not always restore what a user or attacker deletes or encrypts, and not indefinitely back in time. Check what the provider keeps and for how long, and arrange your own backup elsewhere for the rest.
Who is responsible for security in the cloud?
Both parties, each for their own layers. The provider secures the data centre, the hardware and, depending on the model, the operating system and the software. Your organisation remains responsible in every model for data, user accounts and access, settings and the devices used to sign in.
Are you a cloud provider?
No. We manage the layers that stay with the customer, such as virtual servers, Microsoft 365 configuration, accounts, devices and backup, but we run no data centre of our own and have no say over a provider’s availability or terms. Legal questions about data processing agreements are for your lawyer.
Further reading
Where this model connects.
Shall we put a name next to every layer?
Send us the list of cloud and SaaS services you use. We will tell you, per service, which layers sit with you, who manages them today and where a backup or an admin account is missing.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.