# Cloud security risk assessment: score your cloud access layer in 20 minutes

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

The cloud security risk assessment asks 40 questions about the cloud access layer of AWS, Azure and Google Cloud, in six domains, and takes about 20 minutes. It returns a score per domain, the five fixes that matter most, and a PDF and XLSX export made in your browser. Answers never leave the page.

1. Does the root user (or Global Administrator, or Organization Admin) of every account have phishing-resistant MFA and no access keys? (CIS AWS Foundations Benchmark v5.0 1.4 and 1.5)
2. Do all people reach the cloud through central single sign-on with MFA, with no local IAM users or standalone cloud passwords? (Microsoft cloud security benchmark IM-6)
3. Are long-lived access keys and service account keys absent, or rotated at least every 90 days and unused ones deleted? (Google Cloud security best practices Service account keys)
4. Do workloads get cloud access through attached roles, managed identities or workload identity federation instead of stored secrets? (Microsoft cloud security benchmark IM-3)
5. Is the number of people with administrator-level roles small, named and separate from their daily accounts? (Microsoft cloud security benchmark PA-1)
6. Are privileged roles granted only for a limited time, on request, instead of held permanently? (Microsoft cloud security benchmark PA-2)
7. Are permissions reviewed at least every 90 days and unused ones removed? (Microsoft cloud security benchmark PA-4)
8. Are emergency (break-glass) accounts in place, protected, monitored and tested at least twice a year? (Microsoft cloud security benchmark PA-5)
9. Is every SSH, RDP and database port closed to the whole internet (0.0.0.0/0 and ::/0)? (Google Cloud security best practices VPC firewall rules)
10. Do your data stores and platform services (storage, databases, secrets, AI) accept traffic only through private endpoints? (Microsoft cloud security benchmark NS-2)
11. Do new compute instances and databases get no public IP address by default? (Microsoft cloud security benchmark NS-1)
12. Do administrators reach servers through a brokered, logged service (Session Manager, Bastion, Identity-Aware Proxy) with no inbound admin ports? (Microsoft cloud security benchmark PA-6)
13. Is the instance metadata service hardened (IMDSv2 required on AWS, managed identity endpoint protected on Azure, metadata concealment on GKE)? (AWS documentation Instance metadata)
14. Is outbound traffic from production workloads filtered to known destinations? (Microsoft cloud security benchmark NS-3)
15. Do you analyze which resources are reachable from the internet and from other networks (peering, transit, cross-account) at least monthly? (Microsoft cloud security benchmark NS-7)
16. Is public access to object storage blocked at the organization level, not just per bucket? (AWS documentation S3 Block Public Access)
17. Do your resource policies and sharing rules limit access to identities in your own organization? (AWS documentation Data perimeter)
18. Can your most sensitive data be read only from trusted networks or endpoints (VPC endpoints, service perimeters, private links)? (Google Cloud security best practices VPC Service Controls)
19. Do you review findings about resources shared outside your organization at least weekly? (AWS documentation IAM Access Analyzer)
20. Are sensitive data encrypted with customer-managed keys whose use is limited to named identities and services? (Microsoft cloud security benchmark DP-5)
21. Do you know which storage locations hold regulated or sensitive data, and is that list up to date? (Microsoft cloud security benchmark DP-1)
22. Is every third-party and cross-account role protected by an external ID or condition, with an owner and an end date? (AWS documentation IAM best practices)
23. Does each AI agent, pipeline and application have its own cloud identity, not a shared one or a person's credentials? (Microsoft cloud security benchmark AI-4)
24. Is the list of actions each AI agent can perform limited to what its task needs, and written down? (Microsoft cloud security benchmark AI-4)
25. Can only approved models and AI services be used in your accounts, enforced by policy? (Microsoft cloud security benchmark AI-1)
26. Is the data an AI system can read (retrieval stores, training data, tool outputs) limited to what its users may see? (Google Cloud security best practices AI and ML security)
27. Do destructive or high-impact agent actions (delete, grant access, pay, send externally) need a human approval? (Microsoft cloud security benchmark AI-5)
28. Are model calls, tool calls and the identity behind each logged and kept? (Microsoft cloud security benchmark AI-6)
29. Do organization-level policies block the riskiest actions before they happen (SCPs, Azure Policy deny effects, organization policy constraints)? (AWS documentation Service control policies)
30. Do infrastructure changes go through code review and pipelines, with console changes in production flagged? (Microsoft cloud security benchmark PV-1)
31. Does a continuous check compare live configuration against your rules and report differences within a day? (AWS documentation AWS Config)
32. Do you test a new guardrail in audit or report-only mode and see what it would block before you enforce it? (Microsoft documentation Azure Policy)
33. Does every guardrail exception have an owner, a reason and an expiry date? (Microsoft cloud security benchmark PV-2)
34. Can administrators inside a workload account not turn off logging, guardrails or security services? (Microsoft cloud security benchmark PV-2)
35. Are control-plane audit logs on in every account, subscription and project, in every region, including data access logs for sensitive stores? (Microsoft cloud security benchmark LT-3)
36. Are audit logs stored in a separate, restricted account where workload administrators cannot change or delete them? (Microsoft cloud security benchmark LT-5)
37. Do you keep audit logs for at least 365 days, with the most recent 90 days searchable? (Microsoft cloud security benchmark LT-6)
38. Do alerts fire, and reach a person, for root or global administrator sign-ins, policy changes, new keys and disabled logging? (Microsoft cloud security benchmark LT-2)
39. Within one working day, can you produce a list of who can access a given sensitive data store and how they got that access? (Microsoft cloud security benchmark PA-4)
40. Have you practiced cutting off all access of one compromised identity within one hour, and written down the steps? (NIST SP 800-53 Rev. 5 IR-4)

## The six domains

| Domain | Weight | Questions | Why it is weighted |
| --- | --- | --- | --- |
| Identities and entitlements | 25 | 8 | People and workloads that hold standing power over the cloud account are the most common route from one stolen credential to a full breach. |
| Network reachability | 20 | 7 | Reachability decides which of your services an attacker can touch before any credential is needed. |
| Data perimeter | 20 | 7 | A data perimeter limits who can reach your data and from where, even when an identity or a policy is wrong. |
| AI workloads | 15 | 6 | AI services and agents act with cloud credentials, so what they can call and read is an access question. |
| Guardrails and drift | 10 | 6 | Preventive controls stop a bad change before it lands, and drift checks catch the ones that slip past. |
| Evidence | 10 | 6 | Logs and records are what let you prove who had access, detect misuse and respond. |

Workload vulnerabilities and posture scanning are outside this assessment: it scores who and what can reach your cloud resources, not the software running on them.

## Other ways to assess

The [directory of assessment options](/options/) lists 15 provider tools, open source scanners and vendor-run assessments by the same fields, in alphabetical order.

## Sources

- CIS AWS Foundations Benchmark v5.0 1.4 and 1.5: https://www.cisecurity.org/benchmark/amazon_web_services (read 16 Nov 2026)
- Microsoft cloud security benchmark IM-6: https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-v2-identity-management (read 16 Nov 2026)
- Google Cloud security best practices Service account keys: https://cloud.google.com/iam/docs/best-practices-for-managing-service-account-keys (read 16 Nov 2026)
- Microsoft cloud security benchmark IM-3: https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-v2-identity-management (read 16 Nov 2026)
- Microsoft cloud security benchmark PA-1: https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-v2-privileged-access (read 16 Nov 2026)
- Microsoft cloud security benchmark PA-2: https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-v2-privileged-access (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudsecurityriskassessment.com/
