Skip to content
Cloud Security Risk Assessment

Cloud security assessment checklist: 40 checks for the cloud access layer

The cloud security assessment checklist lists 40 checks in six domains: identities and entitlements (8), network reachability (7), data perimeter (7), AI workloads (6), guardrails and drift (6) and evidence (6). Each applies to AWS, Azure and Google Cloud and weighs 1 to 3 in the score. Edition 16 Nov 2026.

Start the assessment ยท All guides

Forty checks sit in six domains, and the domains carry unequal weight

The checklist has 40 checks. Each is a yes, partly or no question about the cloud access layer, and each applies to AWS, Azure and Google Cloud. A check weighs 1, 2 or 3 depending on how far a wrong answer moves risk. The 40 weights add up to 84, and 12 checks weigh 3.

Domain weights are set apart from the check weights: identities and entitlements 25, network reachability 20, data perimeter 20, AI workloads 15, guardrails and drift 10, evidence 10. The domain weights add up to 100.

DomainChecksDomain weightSum of check weights
Identities and entitlements82519
Network reachability72014
Data perimeter72015
AI workloads61514
Guardrails and drift61011
Evidence61011

Eight identity checks cover who holds power and for how long

People and workloads that hold standing power over the cloud account are the most common route from one stolen credential to a full breach.

Seven network checks decide what an attacker can touch without a credential

Reachability decides which of your services an attacker can touch before any credential is needed.

Seven data perimeter checks limit who reads data and from where

A data perimeter limits who can reach your data and from where, even when an identity or a policy is wrong.

Six AI checks treat each agent as an identity with a reach

AI services and agents act with cloud credentials, so what they can call and read is an access question.

Six guardrail checks stop bad changes and catch the ones that slip past

Preventive controls stop a bad change before it lands, and drift checks catch the ones that slip past.

Six evidence checks let you prove access and cut it off

Logs and records are what let you prove who had access, detect misuse and respond.

The checklist is also a Word file you can edit

The Word version, cloud-security-assessment-checklist, lists the same 40 checks with columns for the answer, the owner and the evidence. Use it when a team wants to review the checks in a meeting before anyone opens the scored tool.

To get a score, answer the same checks in the assessment. The scoring is explained in the methodology, and the risk register template turns the five fixes into tracked work. Providers publish more checks than these 40, as the options page shows.

Each check names the control it comes from

Every check cites one primary control: a CIS Benchmark, the Microsoft cloud security benchmark, a provider guide or NIST SP 800-53 Rev. 5. CIS says it publishes more than 100 Benchmarks across 25 or more vendor product families (CIS Benchmarks page, read 16 Nov 2026). The checklist refers to CIS and CSA controls by number and short title only, because those texts are licensed.

Download

Sources

  1. CIS Benchmarks, read 16 Nov 2026
  2. NIST SP 800-53 Rev. 5, read 16 Nov 2026
  3. Microsoft cloud security benchmark overview, read 16 Nov 2026
  4. AWS Well-Architected Security Pillar, read 16 Nov 2026

Last reviewed 16 Nov 2026.