BiTree
  • Search For Lessons
  • Curriculum
  • Pricing
  • For Educators
  • Become a Tutor
  • About
  • Contact
Log InGet Started

Questions, concerns, bug reports, or suggestions? We read every message, write to us at [email protected].

More ways to reach us →
BiTree

Live coding lessons for aspiring developers and security professionals.

[email protected]

(201) 785-7951

Mon–Fri, 9 AM–5 PM EST

Learn

  • Search For Lessons
  • Curriculum
  • Pricing

Company

  • About
  • For Educators & Schools
  • Become a Tutor
  • Contact Us

Legal

  • Terms of Service
  • Privacy Policy
© 2026 BiTree. All rights reserved.
Curriculum/Cybersecurity/Cloud Security/Cloud Security and the Shared Responsibility Model
20 minBeginner

Cloud Security and the Shared Responsibility Model

After this lesson, you will be able to: Understand the shared responsibility model in depth: what the cloud provider secures versus what you secure, and how it differs across IaaS, PaaS, and SaaS.

Most companies run in the cloud, and most cloud breaches come from customer misconfiguration, not provider failure. This subtrack covers the shared responsibility model, IAM misconfigurations, cloud attack techniques, security tooling, and secrets, with a hands-on CloudGoat scenario.

This is a free introductory lesson. No purchase required.

💡 Authorization first

Only test cloud environments you own. The labs use CloudGoat, a deliberately vulnerable AWS environment you deploy into your own account (free-tier eligible). Never probe accounts you do not control.

The shared responsibility model

The provider secures the cloud (physical data centers, hardware, the hypervisor, managed-service internals); you secure what you put in the cloud (your data, IAM configuration, network rules, application code, and OS patching where applicable). The line moves with the service type: with IaaS (EC2) you patch the OS and configure everything; with PaaS (App Service) the provider handles the OS; with SaaS the provider handles almost everything except your data and access settings. Misunderstanding where the line sits is the root of many breaches.

Why cloud breaches happen

The headline cloud breaches were misconfigurations: public S3 buckets exposing millions of records, overly permissive IAM roles, and exposed metadata services. The provider's infrastructure was not breached; the customer's configuration was wrong. This subtrack focuses on exactly those customer-side mistakes because that is where the risk and the jobs are.

Back to Cloud Security
IAM Misconfigurations and Least Privilege→