“Moving to the cloud” can mean very different things: renting virtual servers, running your own applications on a ready-made platform, or simply using email and documents in a browser. NIST describes three cloud service models — SaaS, PaaS and IaaS. They differ in what you get from the provider and what you manage yourself.
In short: SaaS is a ready-made application you use in a browser on a subscription (Microsoft 365, for example); PaaS is a platform to run your own applications; IaaS is rented virtual servers, storage and networks.
Below: each model in plain words, with examples, who is responsible for what, and how to choose a model for your systems.
In short
| What you get | What you manage | Examples | |
|---|---|---|---|
| SaaS | A ready-made application | Data, users, application settings | Microsoft 365, CRM, online accounting |
| PaaS | A platform to run your own applications and databases | Applications, data, access | Azure App Service, Azure Functions, Azure SQL Database |
| IaaS | Virtual servers, storage, networks | Operating systems, applications, data, part of the network | Azure Virtual Machines, virtual servers from cloud providers |
For comparison: in your own server room, everything — from the building and power to the applications — is on you.
What SaaS is
SaaS (Software as a Service), as NIST defines it, is the capability to use the provider’s applications running on a cloud infrastructure. Access is through a browser or a program interface. You do not manage servers, operating systems or even the application’s capabilities — apart, possibly, from limited user-specific settings.
Examples: Microsoft 365, CRM systems, online accounting, electronic document management services.
- Pros: a quick start, subscription pricing, updates and infrastructure are on the provider.
- What to consider: limited customisation, dependence on the provider, where exactly the data is stored and how to take it out.
What PaaS is
PaaS (Platform as a Service) is the capability to deploy your own or acquired applications to the cloud, created using programming languages, libraries, services and tools supported by the provider. You do not manage the network, servers, operating systems or storage, but you control the deployed applications and possibly the settings of the environment they run in.
Examples: Azure App Service, Azure Functions, Azure SQL Database.
- Fits when you develop your own web applications, APIs or services and do not want to administer servers.
- What to consider: the application becomes tied to a specific platform’s tools, so moving to another provider takes rework.
What IaaS is
IaaS (Infrastructure as a Service) is the capability to provision processing, storage, networks and other fundamental computing resources where you can run arbitrary software, including operating systems. The provider manages the physical infrastructure, and you control the operating systems, storage, deployed applications and, to a limited extent, network settings such as host firewalls.
Examples: Azure Virtual Machines, virtual servers from Ukrainian and international cloud providers.
- Fits moving existing servers and applications with few changes, a backup site and disaster recovery, temporary capacity.
- What to consider: updating, protecting and backing up the servers stays with you. How to plan the move is covered in “Cloud migration: a step-by-step plan for business”.
Who is responsible for what
The higher the model — from IaaS to SaaS — the more the provider takes on. This is how Microsoft divides responsibility:
| Area | Own server room | IaaS | PaaS | SaaS |
|---|---|---|---|---|
| Data | You | You | You | You |
| Configurations and settings | You | You | You | You |
| Identities and users | You | You | You | You |
| Client devices | You | You | You | Shared |
| Applications | You | You | Shared | Shared |
| Network controls | You | You | Shared | Provider |
| Operating system | You | You | Provider | Provider |
| Physical hosts, network, datacentre | You | Provider | Provider | Provider |
The key point: in any model, your data, accounts and access are your responsibility. That is why multi-factor authentication, access control and data backups are needed even for SaaS — see “3-2-1 backup rule: protecting business data”. A specific provider may divide things differently — check the contract.
Public, private or hybrid cloud
The service model is what you get. The deployment model is where and for whom the infrastructure runs. NIST distinguishes, among others:
- public cloud — infrastructure for open use, on the provider’s premises;
- private cloud — infrastructure for a single organisation, which may be on or off its premises and managed by the organisation or a third party;
- hybrid cloud — a combination of separate infrastructures between which data and applications can be moved.
IaaS can run in a public or a private cloud. Critical or regulated systems can stay in a private cloud, while flexible workloads move to a public one. How to build such a setup — see “Hybrid cloud: what it is and when you need it”.
How to choose
| What you need | What fits |
|---|---|
| Email, documents, CRM without administering servers | SaaS |
| Your own web applications or APIs without looking after servers and OS | PaaS |
| Move existing servers and applications and keep control over the OS | IaaS |
| Critical or regulated data, requirements for data location and control | Private cloud or hybrid |
Before choosing, ask the provider a few questions:
- In which country will the data be physically stored?
- What availability commitments are written into the contract?
- Who on the provider’s side has access to your data?
- How is data backed up, and who is responsible for recovery?
- How do you take your data out and move to another provider?
Some industries have their own requirements: for banks — NBU Resolution No. 99 (see “NBU Resolution 99: cloud for banks and fintech”), for state information resources — the cloud provider list, and if you process personal data of people in the EU — the GDPR.
Checklist
- There is a list of systems, and a model is chosen for each: SaaS, PaaS, IaaS or keep on premises
- It is known where the data will be physically stored
- The split of responsibility with the provider is set out in the contract
- Multi-factor authentication is on for all accounts
- Cloud data is backed up, and recovery has been tested
- There is an exit plan: how to take the data out and move to another provider
- Your industry’s regulatory requirements have been checked
How Bereg-IT can help
We help you choose a cloud platform that meets your business goals: we inventory systems and the dependencies between them, record availability and security requirements, and compare options by requirements, budget and risks. We draw up a migration plan — order, maintenance windows and a rollback plan — move the workloads and support you after the move.
If some systems have to stay under full control, we build a private cloud and connect it with a public one.
The first consultation is free. Send a request and an IT engineer will get in touch.
Sources
- NIST SP 800-145, The NIST Definition of Cloud Computing (September 2011): https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-145.pdf
- Microsoft Learn, Shared responsibility in the cloud — division of responsibility and service examples: https://learn.microsoft.com/en-us/azure/security/fundamentals/shared-responsibility