Course contentsShow
← Security
Lesson 1678 of 3,05234. Cloud Security - Shared ResponsibilityFree lesson

PaaS Security Boundaries

Understand the security division in Platform as a Service offerings like App Engine, Heroku, and Azure App Service.

PaaS Security Boundaries

What you'll learn: How security responsibilities shift when using Platform as a Service offerings like Google App Engine, Heroku, and Azure App Service.

The Core Idea

In Platform as a Service (PaaS), the cloud provider manages significantly more of the infrastructure than in IaaS. You deploy your application code and sometimes configure runtime settings, but the provider handles the operating system, middleware, runtime environment, and underlying servers. This convenience creates a security boundary where responsibilities split differently than IaaS.

Think of PaaS like renting a fully-equipped commercial kitchen: the landlord maintains the building, utilities, ventilation, and major appliances. You're responsible for your recipes, ingredients, food safety practices, and what you serve customers—but you can't modify the oven's wiring or the building's fire suppression system.

Where the Boundary Falls

The provider secures:

  • Physical infrastructure and hypervisor
  • Operating system patches and hardening
  • Runtime environment (Node.js, Python, Java versions)
  • Platform components (load balancers, databases-as-a-service)
  • Network infrastructure and DDoS protection

You secure:

  • Your application code and dependencies
  • Application-level authentication and authorization
  • Data encryption (in transit and at rest where configurable)
  • API keys, secrets, and credentials management
  • Application logging and monitoring
  • User data privacy and compliance
  • Configuration of platform features (firewall rules, access policies)

The Grey Area

Some responsibilities are shared. For example, the provider patches the platform, but you must redeploy to newer runtime versions. The provider offers identity services, but you configure them correctly. The provider encrypts data, but you manage encryption keys in some models.

Key Takeaway: PaaS security boundaries place infrastructure and platform security on the provider, while you remain fully responsible for application code security, secrets management, access controls, and proper platform configuration—understand your provider's specific shared responsibility model documentation.