# 30 questions, answered from the data

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

Answers to common questions about the 40-question cloud access assessment: how long it takes, what it covers, how the score and the five fixes are calculated, where answers go and how it differs from an audit. Each answer is short, names its source and links to the page behind it.

**How long does the cloud security risk assessment take?**

About 20 minutes to answer the 40 questions for a team that knows its estate. Verifying each answer against a console takes longer, and depends on the number of accounts. Each [question page](/questions/root-account-mfa/) gives the AWS, Azure and Google Cloud test.

**What does the assessment cover?**

It covers the cloud access layer in six domains: identities and entitlements, network reachability, data perimeter, AI workloads, guardrails and drift, and evidence. Workload vulnerabilities and posture scanning are outside it. See the [checklist](/cloud-security-assessment-checklist/) for all 40 checks.

**Does the assessment rank anything?**

No. It scores your own answers and ranks no provider, tool or vendor. The [options](/options/) page lists assessment tools in alphabetical order within each kind, with each maker's own description and the date it was read.

**Where do my answers go?**

Nowhere. Answers stay in the browser, the page sets no cookies and runs no analytics, and the PDF and XLSX exports are made in the browser. Closing the tab ends the session unless you saved an export.

**How is the domain score calculated?**

The sum of answer value times question weight, divided by the sum of weights, times 100. Values are 1 for yes, 0.5 for partly and 0 for no or not known. The [methodology](/methodology/) and the [cloud risk assessment](/cloud-risk-assessment/) guide show a worked example.

**How are the five fixes chosen?**

The tool takes the questions with the highest weight times one minus the answer value. Ties go to lower effort first, then to question order. The result is a short list one team can finish, with each fix written as one imperative sentence.

**Why are there 40 questions?**

Forty keeps the run near 20 minutes while giving each of six domains six to eight checks. Domain sizes are 8, 7, 7, 6, 6 and 6. The count is a design choice stated on the [methodology](/methodology/) page, not a standard.

**What do the weights mean?**

A weight from 1 to 3 records how much a wrong answer moves risk. Twelve of the 40 questions weigh 3, and the weights sum to 84. Domain weights are separate: 25, 20, 20, 15, 10 and 10, which sum to 100.

**Why does not known score as no?**

A control nobody can show offers the same exposure as a missing one. Scoring unknown as no keeps the result honest and puts the missing evidence on the fix list, where an owner can close it.

**Does it work for AWS, Azure and Google Cloud?**

Yes. Every question applies to all three, and each question page gives one test per cloud. The [AWS](/aws-security-checklist/), [Azure](/azure-security-checklist/) and [Google Cloud](/google-cloud-security-checklist/) checklists pick the checks with the most direct tests.

**Which controls do the questions come from?**

From CIS Benchmarks, the Microsoft cloud security benchmark, NIST SP 800-53 Rev. 5 and provider guidance from AWS and Google Cloud. CIS and CSA texts are referenced by number and short title only, because they are licensed. NIST may be quoted.

**Why include AI workloads?**

AI agents and pipelines act with cloud credentials, so what they can call and read is an access question. The domain has six checks and a weight of 15, covering identity, permissions, approved models, data reach, human approval and logging.

**Is this a vulnerability scan?**

No. It does not scan workloads for vulnerabilities or posture settings. Those jobs use other tools, and general security platform rankings are not covered here. The assessment asks about access: who can sign in, what they can reach and what is logged.

**How is an assessment different from an audit?**

An assessment estimates risk and ranks gaps. An audit tests whether a control operated and keeps dated evidence. The [cloud security audit](/cloud-security-audit/) guide and the [audit checklist](/cloud-security-audit-checklist/) cover the second.

**How often should we run it?**

After each batch of fixes and at least every quarter. Two runs show a trend, and each export is a dated record. Keep the same scope each time so scores compare.

**Who should answer the questions?**

One person each from identity, network and data or platform, so no domain is answered by guesswork. A single security lead can start the run, but the owners should confirm answers in their own area.

**What is a good score?**

This site sets no pass mark. Read each domain score against the [maturity model](/cloud-security-maturity-model/) bands and decide a target per domain. A high score in evidence does not offset a low one in identities.

**What is in the risk register?**

The XLSX has 15 columns, from risk ID and check ID to gap, owner, due date and evidence link. The assessment fills 8 and calculates the gap; you add the rest. See the [register template](/risk-register-template/).

**Can I cite the assessment?**

Yes. The cite line on the method page reads: Cloud Security Risk Assessment, the 40-question assessment, edition 16 Nov 2026, with the methodology address. Cite the edition date, since questions change between editions.

**What does phishing-resistant MFA mean here?**

Authentication where the credential is bound to the real site or device, such as passkeys, FIDO2 security keys or certificates. Microsoft lists these under its authentication methods (read 16 Nov 2026). Text message and app codes can be phished.

**Why check the metadata service?**

On AWS, a request-forgery bug can read credentials from the instance metadata address. Requiring IMDSv2 blocks many of those. Azure and Google Cloud have equivalent concerns, which the [question page](/questions/metadata-service-hardened/) covers.

**What is a break-glass account?**

An emergency administrator account for when normal sign-in fails. Microsoft calls it an emergency access account. It needs long unique credentials, alerting on every use and a test at least twice a year.

**Are free provider tools enough?**

They answer part of the questions. AWS Trusted Advisor, Defender for Cloud and Security Command Center each report on a subset of checks, and each has plan conditions listed on the [options](/options/) page. None covers every domain.

**Does Act offer an assessment?**

Yes. Act's page, read 16 Nov 2026, describes a free access attack simulation that is read-only and deployed in under 5 minutes. It is listed on the [options](/options/) page beside the other assessments.

**What is the CIS Benchmark version?**

CIS announced AWS Foundations Benchmark v7.1.0 in its November 2026 update (read 16 Nov 2026). Question pages cite control numbers from the edition named on each page, so confirm against the edition you hold.

**Can I use it for a small team?**

Yes. A team with one account can answer all 40 and verify most in an afternoon. Start with the [15-item list](/cloud-security-checklist/) if the account is new.

**What counts as partly?**

The control is in place in some accounts or for some identities, but not all. Do not use it for plans or pilots, which count as no. Record which accounts are covered in the register.

**How do I fix the lowest domain first?**

Sort the fixes by gap and start with the low-effort ones that weigh 3, such as root account MFA, open admin ports, public storage and audit logging. Then move to the high-effort items on the list.

**Where are corrections reported?**

Write to editor@cloudsecurityriskassessment.com with the page, the sentence and the source. Confirmed errors are fixed on the page and logged with the date.

**How current are the facts?**

Provider facts carry the date they were read, 16 Nov 2026 for this edition. The news page lists dated changes from AWS, Microsoft, Google, CIS, NIST and CSA that affect the checks.

## Related pages

- [The 40-question assessment: the data, downloadable](/datasets/)
- [About](/about/)
- [Editorial policy](/editorial-policy/)

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