DEV Community

TiltedLunar123
TiltedLunar123

Posted on Originally published at secplusmastery.com

Security+ Cloud Shared Responsibility: Who Owns It

Objective 3.1 on SY0-701 focuses on cloud architecture, and the key question is often "whose responsibility is this?" instead of asking for a definition. The question presents a scenario of a security breach or a missing control in a cloud setup, followed by four real-world security tasks. Just one of these tasks fits the party the question is inquiring about. Knowing the responsibilities for each service model makes these questions particularly quick to answer.

The line moves up the stack

Picture the stack as layers. At the bottom is the physical stuff (the buildings and the hardware in them). Above that is the hypervisor that carves the hardware into virtual machines. Then comes the guest operating system and the runtime it hosts. Your application sits on that, and at the very top is your data and the list of who can reach it.

In the cloud, the provider always owns the bottom of that stack and you always own the top. Where the handoff happens depends on the service model you pick.

With IaaS, you rent virtual machines, storage and networks. The provider handles the facility, the hardware and the hypervisor. Everything from the guest OS up is yours. That means patching the OS and hardening the image. The firewall rules and security groups are yours too, along with whatever you install.

With PaaS, the provider also runs the operating system and the runtime. You deploy code and the platform runs it. Your job shrinks to the application, the libraries it pulls in, and the data it handles.

With SaaS, the provider handles the entire application. You're getting a complete product. Your data and your account and sharing setup remain yours.

Two things never move

This decides most questions. Whatever the model, the customer bears the responsibility for the data and for identity and access. The provider can encrypt the disks, but it does not choose who in your company gets read access to the customer list. It cannot detect that a former employee still has a working account. It will not realize that someone shared a folder with "anyone with the link".

So, when a stem says a SaaS tenant leaked records because a storage bucket or a shared drive was public, the blame falls on the customer, even though the provider runs everything else. The same applies to weak passwords, missing MFA on cloud admin accounts, and over-permissioned roles. These are setup and identity issues. In every model, they land on you.

How to read the stem

Find two things before you look at the answers: the service model and the layer that failed.

  1. Name the model. Words like "virtual machines" or "instances" point to IaaS. "Deploys code to a managed platform" or "the developers only push their application" points to PaaS. A product the company signs into, like an email suite or a CRM, is SaaS.
  2. Name the layer. Is the problem down in the hardware or hypervisor, in the OS, or up in the code and the access settings?
  3. Put the layer against the line for that model and read off the owner.

An example. A company runs its web servers on IaaS instances, and an attacker gets in through an OS vulnerability that had a patch available for months. Who was responsible for applying it? The customer. On IaaS the guest OS is yours, so an unpatched guest is your incident. Move the same app to PaaS and the OS patch becomes the provider's job, but a vulnerable library inside your code is still yours.

Another one. A firm relies on a SaaS file-sharing service, but sensitive documents get exposed due to a publicly shared link. The service provider manages the application, the servers, and the storage. The sharing setting is a choice the customer made, so it is the customer's problem.

The distractors

The wrong answers are typically correct statements about the other party. A question regarding an unpatched hypervisor on a public cloud host will include "the customer should patch their virtual machines" as a misleading option. This is practical advice, yet the wrong answer, since the customer doesn't have access to the hypervisor. If the issue lies beneath the customer's control, the provider is responsible, and the customer's options are constrained: review the provider's audit reports and rely on the contract terms. Watch for "the cloud provider is responsible for security" phrased as a blanket claim. On this exam, it's never entirely accurate. The provider secures the cloud itself, and you secure what you put in it.

Practice it

This objective rewards drilling more than reading, since the scenarios alter their wording but maintain their core logic. The Security+ objectives list highlights where 3.1 is positioned within Domain 3. The free practice questions combine cloud scenarios with the other objectives, similar to how they appear on the actual exam. If you continue to struggle with these, try saying the model and the layer out loud before reviewing the options; the answer often becomes clear on its own.

Originally published on secplusmastery.com.

Top comments (0)