Cloud basics: AWS, Azure and Google Cloud

Cloud means renting computers, storage and services from a provider, who secures their half while you secure yours.

// TECH FOR GRC

Most companies no longer run their own servers. They rent them from a cloud provider. AWS, Microsoft Azure and Google Cloud are the three you will meet most.

The words you will see on every screen

  • Account, subscription or project: the container everything sits in. AWS calls it an account, Azure a subscription, Google Cloud a project. Companies keep production in a separate one from development and testing.
  • Region: where the data physically is, such as Mumbai (ap-south-1) or Frankfurt.
  • Availability zone: a separate data centre inside a region. Spreading across zones keeps a service running if one fails.
  • Console: the website you click around in. The same actions can also be done by code, which is how most engineers work.

The shared responsibility model

The provider secures the cloud itself: buildings, hardware, the network underneath. The customer secures what it puts in the cloud: who can log in, how data is encrypted, which ports are open.

This is why a company's SOC 2 report often carves out the cloud provider. The provider has its own SOC 2 and ISO 27001 reports, which customers download from AWS Artifact, the Microsoft Service Trust Portal or Google Cloud's compliance reports manager.

What this means for evidence

Every cloud screenshot should show which account and which region it came from, and when it was taken. A setting proven in the development account proves nothing about production.

// WHAT IT LOOKS LIKE AS EVIDENCE
CloudTrail on in every region and accountAWS CloudTrail · proves CC7.2, A.8.15, A.5.33
AWS CloudTrailSAMPLE
CloudTrail › Trails › org-audit-trail

org-audit-trail

complyoo-org management (7710 2284 0051)Viewed 2026-10-01 09:22 UTC1
  • LoggingOn2
  • Multi-region trailYes3
  • Apply trail to my organizationEnabled for all accounts
  • Log file validationEnabled4
  • S3 bucketcomplyoo-audit-logs (Object Lock: Compliance, 400 days)
  • Management eventsRead and write
  1. 1Date of capture. For a Type II, take this more than once across the period, or show it was never turned off.
  2. 2Logging is on. This is the control itself.
  3. 3Multi-region. A single-region trail leaves gaps attackers use.
  4. 4Log file validation and Object Lock show the logs are protected from tampering.

Weak version: Single region, in one account only. The auditor will ask about every other region and account, and logging gaps there are a finding.

// FROM A REAL ACCOUNTAWS console, CloudTrail · identifiers blurred
This account has no trail. Event history still shows 90 days of management events, but nothing is kept longer and data events are not recorded. Against a twelve month SOC 2 period, that is a gap.
WeakThis account has no trail. Event history still shows 90 days of management events, but nothing is kept longer and data events are not recorded. Against a twelve month SOC 2 period, that is a gap.
Event history from the same account while these screenshots were made. Every change was made as root. An auditor would ask why the root user does daily work, which is an access question before it is a logging one.
Worth knowingEvent history from the same account while these screenshots were made. Every change was made as root. An auditor would ask why the root user does daily work, which is an access question before it is a logging one.
Organisation guardrails enforcedGoogle Cloud Organization Policy · proves CC6.1, A.8.9, A.5.17
Google Cloud Organization PolicySAMPLE
IAM & Admin › Organization Policies

Organization policies: complyoo.com

Organization: complyoo.comViewed 2026-10-03 11:25 IST1
  • Disable service account key creationEnforced2
  • Domain restricted sharingEnforced: complyoo.com only3
  • Enforce uniform bucket-level accessEnforced
  • Restrict public IP access on Cloud SQLEnforced
  1. 1Date and organisation. Org-level policies cover every project.
  2. 2No long-lived service account keys, a common source of leaks.
  3. 3Data cannot be shared outside the company domain.

Weak version: Policies set on one project only. Other projects are unprotected.

// FROM A REAL ACCOUNTGoogle Cloud console, Organization policies · identifiers replaced
26 policies active on this project, all inherited from the organisation, including a block on service account API key bindings. The baseline bar shows 60% of Google's recommended constraints switched on. The other 40% is the conversation to have with the auditor.
Strong26 policies active on this project, all inherited from the organisation, including a block on service account API key bindings. The baseline bar shows 60% of Google's recommended constraints switched on. The other 40% is the conversation to have with the auditor.
// REMEMBER THIS

The provider secures the cloud. You secure what you put in it.

// CHECK YOURSELF

1. Who is responsible for configuring who can log in to a company's AWS account?

2. Evidence shows MFA is on in the development account. Does that prove it for production?

3. Where would a customer get AWS's own SOC 2 report?