Who patches the operating system in IaaS?
The customer. In IaaS the provider secures the facility and virtualization layer, and the customer manages the guest operating system, patches, network rules, and applications.

Exam objectiveCompare and contrast security implications of different architecture models
Objective 3.1 covers how architecture models compare on security: who is responsible for what, how easy each is to patch, how it fails, and what it costs to run and recover.
Cloud and deployment. In the cloud the provider secures the platform and the customer secures what it puts there, as set out in a responsibility matrix; moving to the cloud never transfers accountability for your data. Hybrid designs join different deployment models, and third-party vendors add another party to oversee. Infrastructure as code (IaC) declares servers, networks, and permissions in reviewable, version-controlled files. Serverless removes server administration but not code or access-control duties. Microservices split an application into small services that talk over APIs, which multiplies network paths. Containers share the host kernel, while virtual machines each carry their own OS.
Infrastructure. An air gap gives physical isolation with no network path, logical segmentation gives a controlled path, and software-defined networking (SDN) separates a control plane that decides from a data plane that forwards. On-premises systems, centralized versus decentralized control, and high availability each change the risk and the effort to defend.
Special-purpose systems and trade-offs. IoT, ICS/SCADA, real-time operating systems (RTOS), and embedded systems are often hard to patch and were rarely designed with security first. Models are compared on availability, resilience, cost, responsiveness, scalability, ease of deployment, risk transference, ease of recovery, patch availability or inability to patch, power, and compute.
Exam scenarios describe a business need, such as cheap scaling, an unpatchable controller, or a regulated workload, and ask which model fits or which risk it brings.
This page is the map. Knotch is where you drill it until it sticks.
In both, the provider owns the data center and hardware. With IaaS the customer manages the operating system and up; with PaaS the provider manages the OS and the customer manages its application, data, and access.
A container shares the host kernel, so a kernel flaw can expose every container on the host. A virtual machine carries its own guest kernel, which gives each guest a separate isolation boundary.
Centralized control gives uniform rules and one view, but a single point of failure. Decentralized control adds resilience and local flexibility, but consistent policy and visibility are harder.
An air gap has no network path at all. Segmentation has a controlled path.
The full set of look-alike pairs for this objective is inside Knotch.
A host runs 30 containers. A critical flaw is announced in the Linux kernel on that host. The security lead wants to patch the host before anything else.
Why does one kernel flaw potentially affect all 30 containers?
A shared kernel means a kernel-level flaw can reach every container on that host.
NIST SP 800-190 separates container risk into images, registries, orchestrators, containers, and the host OS. Because the kernel is shared, patching the host is critical, which differs from VMs that each carry a guest kernel.
Why not A: Account sharing is not why a kernel flaw is shared; the shared kernel is.
Why not B: A registry stores images and does not push host kernel flaws into them.
Why not C: Virtual machines carry their own kernel; containers do not.
The customer. In IaaS the provider secures the facility and virtualization layer, and the customer manages the guest operating system, patches, network rules, and applications.
No. Serverless removes server administration, but the customer still owns its code and access-control duties.
No. High availability keeps service running now, while backups restore data after loss. Redundant copies also receive corruption, deletion, and ransomware encryption.
