Cloud risk assessment: weight each gap by how much a wrong answer moves risk
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
A cloud risk assessment lists the gaps in your cloud controls and ranks them by impact. This site scores the access layer with 40 questions: each answer is worth 1, 0.5 or 0, each question weighs 1 to 3, and the five fixes come from the largest weight times the missing share of the answer.
Start the assessment ยท All guides
The score is a weighted share of yes answers
Each question has three answers: yes, partly and no or not known. Their values are 1, 0.5 and 0. The weight of a question runs from 1 to 3 and records how much a wrong answer moves risk. The domain score is the sum of value times weight, divided by the sum of weights, times 100.
Unknown counts as no. A team that cannot show the control has the same exposure as a team without it, and the score should say so.
A worked example scores the identities domain at 50
The eight identity questions weigh 3, 3, 3, 2, 2, 3, 2 and 1, a total of 19. Suppose the answers are yes, partly, no, partly, yes, no, partly and yes in question order. The sum of value times weight is 3 + 1.5 + 0 + 1 + 2 + 0 + 1 + 1 = 9.5, and 9.5 divided by 19 is 0.5, so the domain scores 50.
| Question | Weight | Answer value | Gap (weight x (1 - value)) |
|---|---|---|---|
| People sign in through single sign-on with MFA | 3 | 0.5 | 1.5 |
| Long-lived keys removed or rotated every 90 days | 3 | 0 | 3 |
| Workloads use platform-issued identities | 2 | 0.5 | 1 |
| Privileged roles are granted for a limited time | 3 | 0 | 3 |
| Permissions reviewed every 90 days | 2 | 0.5 | 1 |
The largest gaps become the fixes, with ties broken by effort
In the example, long-lived keys and no standing privilege tie at a gap of 3. Keys are rated medium effort and standing privilege high effort, so keys come first. Next comes workforce SSO at 1.5, then access reviews before workload identity at 1 each, again on lower effort.
Across all six domains the tool takes the five largest gaps, breaking ties by lower effort and then by question order.
Likelihood stays outside the arithmetic
The weight captures impact if the control is missing. It does not estimate how likely an attacker is to try. Add likelihood in the risk register template if your risk method needs both, and record the reason.
NIST publishes a draft revision of SP 800-221, on governing ICT risk programs within enterprise risk, with comments due 7 December 2026 (NIST, read 16 Nov 2026). Teams that run an enterprise risk process can use the register to carry the fixes upward.
Domain weights record how much of the exposure each domain holds
The domain weights are chosen by this site and stated, not measured. Identities and entitlements takes 25 because standing power over the account is the common route from one stolen credential to a full breach. Network reachability and data perimeter take 20 each. AI workloads takes 15, and guardrails and evidence take 10 each.
A team that disagrees can read the domain scores directly and ignore the weights. The domain score never uses the domain weight; only an overall figure does.
Partly answers need a rule
The middle answer is worth 0.5 and means the control is in place in some accounts or for some identities. Use it when the control exists but does not cover everything you own. Do not use it for plans or pilots, which count as no until they are running.
Record in the register which accounts are covered, so the next run can show the gap closing.
What a risk assessment of the access layer leaves out
It does not scan workloads for vulnerabilities, check every configuration setting or rank security platforms. Those are separate jobs. For the 20-minute version of this one, see the assessment, and for the full scope see the cloud security assessment guide.
Related pages
Sources
- NIST SP 800-221 Rev. 1 initial public draft, read 16 Nov 2026
- NIST SP 800-53 Rev. 5, read 16 Nov 2026
- AWS Well-Architected Security Pillar, read 16 Nov 2026
Last reviewed 16 Nov 2026.