# Cloud risk register template: 15 columns, a gap score and a named owner

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

The cloud risk register template is an XLSX made in your browser from the assessment answers. It has 15 columns, from risk ID and check ID to gap, owner, due date and evidence link. The assessment fills 8 and calculates one; you add the risk ID, owner, due date, status, evidence link and review date.

## The register has 15 columns, 8 of them filled from your answers

After you finish the [assessment](/), the export button builds the XLSX in the browser. Nothing is uploaded. Each answer that scores below yes becomes a row, so a team with 12 gaps gets 12 rows.

The columns are listed below. The risk ID, owner, due date, status, evidence link and review date columns are blank on purpose, because only your team can fill them.

| Column | What goes in it | Filled from |
| --- | --- | --- |
| Risk ID | A short stable id such as R-001 | You |
| Check ID | The question id, for example id-03 | Assessment |
| Domain | One of the six domains | Assessment |
| Risk statement | The gap in one sentence, written as the question reversed | Assessment |
| Answer | Yes, partly or no or not known, with its value 1, 0.5 or 0 | Assessment |
| Weight | 1 to 3, from the question | Assessment |
| Gap | Weight times (1 minus value) | Calculated |
| Fix | The imperative sentence from the question page | Assessment |
| Effort | Low, medium or high | Assessment |
| Control | The framework, reference and short title cited by the question | Assessment |
| Owner | One named person or team | You |
| Due date | The date of the recheck | You |
| Status | Open, in progress, accepted or closed | You |
| Evidence link | Where the dated artifact is stored | You |
| Review date | The next date the answer will be tested again | You |

## The gap column ranks the rows

Gap is weight times one minus the answer value. A no on a weight 3 question is a gap of 3, and a partly on a weight 2 question is a gap of 1. Sort the sheet by gap, descending, and the top rows are the fixes the assessment would give. The tool shows five; the register keeps all of them.

Where two rows tie, order them by effort, low first, then by question order, the same rule as in the [methodology](/methodology/).

## Every row needs one owner and one date

A register without owners is a list of worries. Put one named person on each row, a team name if the person is not known yet, and a due date that is a recheck of the test, not a hope. Link the dated artifact in the evidence column, such as the credential report that shows a key was deleted.

Rows with a status of accepted need a reason and an end date. That follows the [exceptions expire](/questions/exceptions-expire/) check: an accepted risk with no end date is an exception with no expiry.

## Add likelihood only if your method needs it

Many risk methods score impact and likelihood. The register carries impact in the weight and the gap, and leaves likelihood out. If your process needs it, add a column and say how you set it, then keep the assessment gap as the first sort key so the order stays reproducible.

The [cloud risk assessment](/cloud-risk-assessment/) guide shows a worked score. The register is how that result becomes tracked work.

## One filled row shows the shape

Row R-001 could read: check id-03, domain identities, risk statement "Long-lived access keys exist and are older than 90 days", answer no (0), weight 3, gap 3, fix "Replace static keys with short-lived credentials, and delete every key older than 90 days or unused for 90 days", effort medium, owner the platform team, due date the next recheck, status in progress. The [long-lived keys](/questions/long-lived-keys/) page gives the AWS, Azure and Google Cloud test for the evidence link.

## Update the register on every run

Run the assessment again after the fixes. Rows whose answer moved to yes are closed with the date; new gaps are added; rows that did not move keep their owners and get a new review date. Keep each export, since two exports show a trend that one cannot. The [maturity model](/cloud-security-maturity-model/) turns the domain scores into levels for reporting, and the [options](/options/) page lists tools that report on some of the same checks.

## Related pages

- [Cloud Security Checklist: 15 Items for a New Account](/cloud-security-checklist/)
- [Cloud Security Assessment Checklist: 40 Checks](/cloud-security-assessment-checklist/)
- [AWS Security Checklist for the Access Layer](/aws-security-checklist/)
- [All of them](/guides/)

## Sources

- NIST SP 800-53 Rev. 5: https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final (read 16 Nov 2026)
- NIST SP 800-221 Rev. 1 initial public draft: https://csrc.nist.gov/pubs/sp/800/221/r1/ipd (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudsecurityriskassessment.com/risk-register-template/
