Service Model Selection for Security Requirements
What you'll learn: How to match cloud service models (IaaS, PaaS, SaaS, etc.) to your organization's security needs and compliance obligations.
The Selection Challenge
Choosing the right cloud service model isn't just about features or cost—it's fundamentally a security decision. Each model (IaaS, PaaS, SaaS, FaaS, CaaS) represents a different division of responsibility between you and the cloud provider. The question is: where do you need control, and where can you safely delegate?
Matching Models to Requirements
When to choose IaaS:
- You need granular control over OS hardening, patching, and configurations
- Compliance mandates require custom security controls or specific encryption implementations
- Your security team must manage network segmentation, firewalls, and monitoring at the infrastructure level
When PaaS makes sense:
- Your team focuses on application security, not infrastructure management
- You trust the provider's patching and runtime security posture
- Compliance requirements don't demand infrastructure-level control
When SaaS is appropriate:
- Your organization lacks deep security expertise
- The provider's certifications (SOC 2, ISO 27001) align with your needs
- Data sensitivity is low to moderate, or provider encryption meets your standards
Hybrid considerations:
- High-security workloads on IaaS with tight control
- Development environments on PaaS for speed
- Productivity tools on SaaS for ease
The Decision Framework
Ask yourself:
- What must we control? (encryption keys, network topology, OS hardening)
- What expertise do we have? (Can we secure Kubernetes? Patch at scale?)
- What does compliance require? (Specific controls, audit trails, data residency)
- What's our acceptable risk? (Provider breaches, supply chain attacks)
Key Takeaway: Choose your cloud service model based on where you need security control versus where you can accept provider-managed security—align the shared responsibility boundary with your team's capabilities and compliance requirements.