Public cloud providers secure the underlying infrastructure, but customers remain responsible for much of what runs on it. Understanding this split prevents gaps that attackers look for.

Every major cloud provider describes security with a shared responsibility model. The provider secures the physical data centres, hardware and core platform. The customer secures what it builds and configures on top. Where the line falls depends on the type of service.

How the split changes by service type

  • Infrastructure as a service (virtual machines, virtual networks): you manage the operating system, patches, installed software, network rules and data.
  • Platform as a service (managed databases, application hosting): the provider manages the operating system and runtime; you manage configuration, access, application code and data.
  • Software as a service: the provider runs the application; you manage users, access policies and the data you put into it.

What customers always own

  1. Identities and access. Who can sign in, with which permissions, and whether multi-factor authentication is enforced.
  2. Data. Classification, encryption choices, retention and backups.
  3. Configuration. Public endpoints, storage access settings, firewall and network rules.
  4. Monitoring and response. Reviewing alerts and acting on them.

Common gaps we see

  • Storage containers or buckets left open to anonymous access after testing.
  • Management ports such as SSH or RDP open to the whole internet.
  • Administrator accounts without multi-factor authentication, or shared between staff.
  • Security recommendations generated by the platform but never reviewed.
  • Backups configured but never tested with a restore.

Practical next steps

  • Enable the built-in security posture tools each provider offers and review their recommendations monthly.
  • Define a baseline for new accounts: logging enabled, public access blocked by default, MFA enforced for administrators.
  • Assign an owner for every recommendation, and record a reason when a risk is accepted rather than fixed.
A cloud provider's certifications cover its part of the model. Your own controls and evidence cover yours.

This article is general information and not legal, tax or financial advice. Service features, regions and prices change; confirm current details with each provider before making decisions.