Skip to content

Cloud Security

Cloud adoption introduces a shared responsibility model where the cloud provider secures the underlying infrastructure and the customer is responsible for what they deploy on top of it. The boundary of that responsibility shifts depending on the service model used.

Topics in this section

Shared responsibility model

ResponsibilityIaaSPaaSSaaS
Physical infrastructureProviderProviderProvider
Network controlsSharedProviderProvider
Operating systemCustomerProviderProvider
Runtime / middlewareCustomerSharedProvider
Application codeCustomerCustomerProvider
Data & identityCustomerCustomerCustomer

The customer always owns data and identity, regardless of service model. Misconfiguring access to data stored in a cloud service is the customer's responsibility to prevent and detect.

Cloud security domains

  • Identity and access — IAM policies, service account permissions, federation with on-premises directories
  • Data protection — encryption at rest and in transit; key management; data residency
  • Network security — VPC design, security groups, NACLs, private endpoints, firewall rules
  • Posture management — continuous compliance scanning (CSPM); detecting misconfigurations before they are exploited
  • Workload protection — securing VMs, containers, and serverless functions at runtime (CWPP)
  • Logging and detection — cloud-native audit logs (CloudTrail, Azure Monitor, GCP Cloud Audit Logs) fed into SIEM
  • Supply chain — IaC scanning; image signing; dependency management

See also

Released under the MIT Licence.