Skip to content
Tutorials Center
My learning

Topics

Lesson 2 of 38 ยท Getting Started

Cloud Service and Deployment Models

Understand IaaS, PaaS, SaaS, FaaS and public, private, hybrid and multi-cloud deployments, and what each choice means for who secures what.

Before you can secure a cloud system you need to know what kind of cloud service you are using. A virtual machine, a managed database and a hosted email service are all "the cloud", but they leave you with very different amounts of security work. The industry describes this with service models (how much the provider manages for you) and deployment models (where and for whom the cloud runs).

This lesson gives you the vocabulary you will use in every later chapter, and ends with a small program that shows how responsibility moves between you and the provider.

Service models

Think of a stack of layers: physical facilities, hardware, virtualization, operating system, runtime, application, data and identity. A service model decides which layers the provider runs.

Four service models

IaaS You get virtual machines and networks
PaaS You get a platform to run code
FaaS You deploy single functions
SaaS You just use the app

More provider control means less for you to patch.

1 / 2
  • IaaS (Infrastructure as a Service). You rent virtual machines, disks and virtual networks. You install and patch the operating system, runtime and applications. Examples: a generic virtual machine, a virtual network, block storage.
  • PaaS (Platform as a Service). The provider runs the operating system and runtime; you deploy code or use a managed database. You still configure access, networking, and your application's own security.
  • FaaS / serverless. You upload small functions that run on demand. The provider manages servers entirely, but your code, its permissions and the events that trigger it are your responsibility.
  • SaaS (Software as a Service). A finished application such as email, a CRM or a file-sharing tool. You manage users, sharing settings and the data you put in.
  • CaaS (Containers as a Service). A managed way to run containers, between IaaS and PaaS. We cover it in the container chapter.

Deployment models

  • Public cloud. Shared infrastructure operated by a provider for many customers, logically isolated from each other.
  • Private cloud. Cloud-style infrastructure used by a single organization, in its own data center or a dedicated hosted one. More control, more work.
  • Hybrid cloud. A mix of private infrastructure and public cloud, connected by VPN or dedicated links. Security teams must protect the connection and keep policies consistent on both sides.
  • Community cloud. Shared by several organizations with common needs (for example a group of hospitals).
  • Multi-cloud. Using more than one public provider. It reduces dependence on a vendor but multiplies the number of consoles, identity systems and rule sets to keep aligned.
flowchart TB
    subgraph Hybrid["Hybrid cloud"]
        OnPrem["Private data center"] <-->|"VPN / private link"| Pub["Public cloud"]
    end
    Pub --> SaaS["SaaS apps"]
    Pub --> IaaS["IaaS and PaaS workloads"]

A hybrid setup: the link between the two sides is itself something to secure and monitor.

Security consequences of each choice

Choice Security upside Watch out for
IaaS Full control of OS and network You patch everything; easy to leave ports open
PaaS Less patching Default settings, over-broad service identities
FaaS No servers to harden Over-privileged function roles, injection through event data
SaaS Provider secures the app Weak sharing settings, no MFA, shadow IT
Multi-cloud No single vendor lock Inconsistent policy, more places to misconfigure

Runnable example: who patches what?

The program below stores which layers each model leaves to you (customer) and which to the provider. It then prints your checklist. The data is a simplified teaching model, not any provider's official table.

Python Responsibility by service model

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Notice that "data" and "identities and access" appear for every model. Moving to a higher-level service removes patching work, not accountability.

Choosing a model with security in mind

Ask these questions when you pick a service:

  1. What can I configure, and what are the secure defaults?
  2. Which logs does the service produce, and can I send them to my own storage?
  3. How does it encrypt data, and can I control the keys?
  4. How do I give access to it: individual users, roles, or shared secrets?
  5. Where does the data physically live, and does that matter for the law (see compliance later in the course)?

Rule of thumb. Prefer the most managed service that meets your need. Every layer the provider runs is a layer you do not have to patch, as long as you keep the settings you control tight.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. In which service model do you patch the operating system yourself?

    With IaaS you rent virtual machines and manage the OS, runtime and everything above it.
  2. 2. What do you always remain responsible for, whatever the model?

    Data and identity/access configuration stay with the customer in every model.
  3. 3. What is a hybrid cloud?

    Hybrid means private infrastructure plus public cloud, linked together. Using two public providers is multi-cloud.
  4. 4. Which extra challenge is typical of multi-cloud?

    Each provider has its own tools and terminology, so policy drift and inconsistent configuration are common.

Summary

  • Service models (IaaS, PaaS, FaaS, SaaS) decide how many layers you manage.
  • Deployment models (public, private, hybrid, community, multi-cloud) decide where the cloud runs and who shares it.
  • Higher-level services reduce patching but never remove responsibility for data, identity and configuration.
  • Choose the most managed service that fits, and check its defaults, logs and key options.

Next: Security Principles: CIA, Defense in Depth and Zero Trust