Shared Responsibility in PaaS
What you'll learn: How platform-as-a-service (PaaS) shifts infrastructure security to the provider while you remain responsible for application and data protection.
The PaaS Security Balance
In PaaS environments like Azure App Service, Google App Engine, or AWS Elastic Beanstalk, the provider assumes significantly more security responsibilities than in IaaS. Think of it like renting a fully managed apartment building versus building your own house—the landlord handles structural integrity, utility security, and building maintenance, but you're still responsible for locking your door and protecting your belongings.
What the Provider Secures
The cloud provider handles:
- Operating system patching and hardening
- Runtime environment security (language runtimes, middleware)
- Platform infrastructure and networking
- Physical security and hypervisor management
- Database engine security (in managed database services)
You deploy your application and the provider ensures the platform beneath it remains secure and available.
What You Must Secure
Your responsibilities focus on the application layer:
- Application code security – preventing SQL injection, XSS, and other vulnerabilities
- Data security – encryption, classification, and access controls
- Authentication and authorization – identity management and user permissions
- Application configuration – secure settings, connection strings, API keys
- Dependency management – third-party libraries and packages
- Access policies – who can deploy or modify your applications
The Critical Boundary
The dividing line sits at the application runtime. The provider secures the platform and everything below; you secure everything you build, deploy, and store on that platform. Misconfigurations in environment variables, exposed secrets, or vulnerable application code remain your responsibility even though you don't manage the underlying servers.
Key Takeaway: PaaS dramatically reduces your infrastructure security burden, but application security, data protection, and proper configuration remain squarely in your hands—secure what you build, trust the provider to secure what runs it.