Skip to content

5. Cloud Security Basics

Cloud security runs on the shared responsibility model: the provider secures everything underneath your layer (Lesson 3), and you secure everything you put on top of it. Nobody secures 100% of the stack alone.

Layer Who's responsible
Physical hardware, the hypervisor itself The provider, always
Your OS, your software, your configuration You, always
Your data, your access credentials You, always

Where cloud breaches actually come from

Almost every major "cloud hack" headline turns out to be a misconfiguration on the customer's side, not the provider's infrastructure being broken into — a storage bucket left open to the public internet, a weak or reused password, an access key accidentally committed somewhere public. The provider's half of the shared responsibility model rarely fails; the customer's half is where things usually go wrong.

Try it

Using hermes as the example: name one thing that's the provider's responsibility to secure, and one thing that's clearly the user's responsibility instead.

Tip

"The cloud got hacked" is almost always more accurately "someone misconfigured their own part of it" — a healthy habit is to assume that's the cause first, and look for an actual provider-side failure only after ruling it out.

Play it

Open the Virtualization and Cloud Lab and use the Cloud security tab. Once you've been through all five lessons, try the Quiz tab for a review drawing from everything in this module.

Watch along

From the CompTIA A+ 220-1201 Full Course: Cloud security (4:25:04)