A security architect is developing a cloud security matrix to clarify operational responsibilities across multi-cloud environments. Match each security operational task to the corresponding cloud service model where the customer is primarily responsible for performing that specific task.
- Configuring user role permissions and single sign-on (SSO) integration within a fully vendor-managed applicationInfrastructure as a Service (IaaS)
- Hardening source code and managing database schemas while the vendor maintains the execution runtime and middlewarePlatform as a Service (PaaS)
- Securing custom function trigger logic and API endpoints while the provider manages event orchestration and container executionFunction as a Service (FaaS / Serverless)
Answer
Guest OS patching and firewalling matches Infrastructure as a Service (IaaS); configuring user role permissions matches Software as a Service (SaaS); source code and schema security matches Platform as a Service (PaaS); securing function logic and API endpoints matches Function as a Service (FaaS / Serverless).
Each service model transfers specific operational responsibilities to the cloud provider. In IaaS, the customer retains control down to the guest OS level. In PaaS, the provider handles the OS and runtime, leaving application code to the customer. In SaaS, the provider manages the entire application stack, leaving access control to the customer. In FaaS, short-lived function code and trigger handling are the customer's focus.
Step-by-Step Solution
Key Concept
Cloud Shared Responsibility Model across Service Delivery Models
Estimated Time:1m 30s