CyberKit

Shared Responsibility Model

The split of security duties between a cloud provider and its customer.

What it is

A framework that divides security obligations between the cloud provider, who secures the underlying infrastructure, and the customer, who secures their data, identities, and configurations. Where the line falls shifts with the service model, from infrastructure to platform to fully managed offerings.

Why it matters

Most cloud breaches stem from the customer side of the line, so knowing exactly which controls you own determines what you can detect, log, and investigate after an incident.

In practice

A responder traces a leaked customer database back to a bucket the team left world-readable, squarely on the customer's half of the model rather than the provider's.

What to look for

  • Findings that sit in the customer's half, such as open storage, weak IAM or unpatched guest OS.
  • Gaps where each side assumed the other handled logging, backup or encryption.
  • Different splits for IaaS, PaaS and SaaS in the same environment.

Common mistake

Assuming the provider secures your data. The provider runs the platform; configuration, identities and data stay your job.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Amazon GuardDuty Cloud service

    AWS threat detection that analyzes CloudTrail, VPC flow logs and DNS logs.

  • Microsoft Defender for Cloud Commercial

    Posture and threat protection for Azure, AWS and Google Cloud.

  • Wiz Commercial

    Maps cloud resources, identities and exposures into one graph of risk.

  • Prowler Open source

    An open source tool that checks cloud accounts against benchmarks such as CIS.

Read next

Sources