An enterprise security architect is mapping security governance duties across various cloud service models during a multi-cloud initiative. Match each cloud service model on the left with the customer's primary security responsibility on the right.
- Infrastructure as a Service (IaaS)Configuring guest operating system security patches, virtual machine firewalls, and installed middleware applications.
- Platform as a Service (PaaS)Managing application code and database schemas while relying on the provider to maintain the operating system and runtime framework.
- Software as a Service (SaaS)Configuring user identity access permissions and monitoring data access policies while the provider maintains all application code, runtime, and infrastructure.
- Function as a Service (FaaS)Managing event trigger permissions and stateless code execution logic while the provider completely abstracts infrastructure host provisioning and scaling.
Answer
Infrastructure as a Service (IaaS) matches with configuring guest operating system security patches, virtual machine firewalls, and installed middleware applications. Platform as a Service (PaaS) matches with managing application code and database schemas while relying on the provider to maintain the operating system and runtime framework. Software as a Service (SaaS) matches with configuring user identity access permissions and monitoring data access policies while the provider maintains all application code, runtime, and infrastructure. Function as a Service (FaaS) matches with managing event trigger permissions and stateless code execution logic while the provider completely abstracts infrastructure host provisioning and scaling.
Each cloud service model defines a distinct boundary of ownership under the shared responsibility framework. In Infrastructure as a Service (IaaS), customer responsibility extends from the guest OS upward (including OS patching and virtual network security). Platform as a Service (PaaS) shifts OS and runtime maintenance to the provider, leaving code and database management to the customer. Software as a Service (SaaS) shifts application code management to the provider, leaving identity governance and data access to the customer. Function as a Service (FaaS) abstracts server infrastructure entirely, limiting customer responsibility to discrete event-driven function code.
Step-by-Step Solution
Key Concept
Cloud Shared Responsibility Model across Service Delivery Architecture Types