Skip to content
Cloud Security Risk Assessment

Cloud security assessment: what it covers at the access layer and how long it takes

A cloud security assessment at the access layer scores who and what can reach your cloud accounts and data. This site's version has 40 questions in six domains, takes about 20 minutes to answer and returns a score per domain, five fixes and a PDF and XLSX export made in the browser.

Start the assessment ยท All guides

The assessment covers six domains of access

The scope is the access layer: identities and entitlements, network reachability, data perimeter, AI workloads, guardrails and drift, and evidence. It matches the 40-check list. Workload vulnerabilities and posture scanning sit outside it and use other tools.

It takes about 20 minutes to answer and longer to verify

Answering the 40 questions takes about 20 minutes for a team that knows its estate. Verifying each answer against the console takes longer and depends on the number of accounts, so treat the first run as a fast screen. Each question page gives the AWS, Azure and Google Cloud steps to confirm an answer, starting with root account MFA.

Answers stay in the browser. Nothing is sent to a server, and the PDF and XLSX exports are made in the browser.

The output is a score, five fixes and a register

  • A score per domain from 0 to 100, as in the method.
  • The five fixes with the largest weight times missing share, each with an effort rating.
  • A PDF for the report and an XLSX to load into a risk register, described on the register template page.

Other published self-assessments exist

Wiz publishes a Cloud Security Self Assessment with 9 domains: it asks 9 introductory questions, shows a checklist for each domain answered yes and then returns a risk score (Wiz page, read 16 Nov 2026). Act offers a free access attack simulation (Act page, read 16 Nov 2026). The options page lists these and the provider tools, in alphabetical order and unranked.

Prepare four things before starting

  • The list of accounts, subscriptions and projects, with an owner for each.
  • Read access to the identity provider and to the audit log destination.
  • One person from identity, one from network and one from data or platform, so no domain is answered by guesswork.
  • A place to store the exports, such as a ticket or a shared folder, with the date in the name.

The five fixes read like a work order

Each fix is one imperative sentence with an effort rating of low, medium or high. For example, the fix for root account MFA is to register a hardware or passkey MFA device on every root or top administrator identity and delete any root access keys, and it is rated low effort.

Low-effort fixes with a weight of 3 come first when gaps tie. The result is a short list that one team can finish in a sprint, instead of a long report that nobody owns.

Scope choices change the verification time, not the 20 minutes

The 20 minutes covers answering. Verification grows with the number of accounts and the number of clouds, because each question page lists one test per cloud. A single AWS account with one pipeline can be verified in an afternoon; an organization with hundreds of accounts needs a script for the credential report and the policy lists.

Decide the scope first: the whole organization, one business unit or the accounts that hold regulated data. Write it on the first page of the export so a later run uses the same scope.

Who reads the result

The domain scores go to the security lead, who decides which domain to work on. The five fixes go to the teams that own them. The register goes to whoever tracks risk. Share the PDF with leadership only after the owners have seen their fixes, so nobody meets a finding in a meeting for the first time.

What an assessment is not

An access-layer assessment is not a vulnerability scan of workloads, a posture scan of every configuration setting or a ranking of security platforms. Each of those is a separate job. The audit guide covers the evidence step that follows an assessment.

Run the assessment on a schedule

A single run shows a state. Two runs show a trend. Repeat after each batch of fixes, or every quarter, and keep each export. The maturity model turns the domain scores into levels you can report. A new account should first pass the short cloud security checklist.

Sources

  1. Wiz Cloud Security Self Assessment, read 16 Nov 2026
  2. Act free assessment, read 16 Nov 2026
  3. NIST SP 800-53 Rev. 5, read 16 Nov 2026
  4. AWS Well-Architected Security Pillar, read 16 Nov 2026

Last reviewed 16 Nov 2026.