# How the ransomware readiness assessment is scored: points, weights and bands

Method, read 16 November 2026

**In short.** Each control has four answers worth 3, 2, 1 or 0 points. Points are multiplied by the control weight, 1 to 3, and summed. The sum divided by the points available gives a percent, read in four bands. A weight-3 control scored zero is a priority gap. Weights are editorial choices, published here. Edition 16 November 2026.

## How is the ransomware readiness score worked out?

Points earned for a control = option points x control weight. Total earned / total available = percent. For the OT group, a site with no operational technology marks all four controls not applicable: they are left out of both the earned and the available total. Points earned for a control equal the points of the answer you ticked (3, 2, 1 or 0) times the control weight.

Any control with weight 3 that scores 0 points is listed as a priority gap, whatever the band.

| Band | From percent | To percent | Reading |
| --- | --- | --- | --- |
| Critical gaps | 0 | 29 | Basic protections are missing. A ransomware event would likely stop the business until rebuilt. |
| Partial | 30 | 54 | Some controls are in place, but one or more of the main routes in or the route back is open. |
| Established | 55 | 79 | Most controls exist. The remaining work is testing, written authority and coverage of edge cases. |
| Tested | 80 | 100 | Controls exist and have been exercised. Keep the evidence and repeat the test each year. |

Round the percent down to a whole number before reading the band. Points available are 234 with all four OT controls and 204 without them.

## What does each control weigh?

Each control carries a weight of 1, 2 or 3. The table lists the weight and the most points the control can earn.

| Control | Group | Weight | Points available |
| --- | --- | --- | --- |
| GV1 | Governance | 3 | 9 |
| GV2 | Governance | 3 | 9 |
| GV3 | Governance | 2 | 6 |
| GV4 | Governance | 2 | 6 |
| ID1 | Identity and access | 3 | 9 |
| ID2 | Identity and access | 3 | 9 |
| ID3 | Identity and access | 2 | 6 |
| ID4 | Identity and access | 1 | 3 |
| BR1 | Backups and recovery | 3 | 9 |
| BR2 | Backups and recovery | 3 | 9 |
| BR3 | Backups and recovery | 2 | 6 |
| BR4 | Backups and recovery | 2 | 6 |
| DT1 | Detection | 3 | 9 |
| DT2 | Detection | 2 | 6 |
| DT3 | Detection | 2 | 6 |
| DT4 | Detection | 2 | 6 |
| SG1 | Segmentation and platform | 2 | 6 |
| SG2 | Segmentation and platform | 3 | 9 |
| SG3 | Segmentation and platform | 2 | 6 |
| SG4 | Segmentation and platform | 1 | 3 |
| EE1 | Email and edge | 2 | 6 |
| EE2 | Email and edge | 1 | 3 |
| EE3 | Email and edge | 2 | 6 |
| EE4 | Email and edge | 1 | 3 |
| RR1 | Response readiness | 3 | 9 |
| RR2 | Response readiness | 2 | 6 |
| RR3 | Response readiness | 2 | 6 |
| RR4 | Response readiness | 1 | 3 |
| TP1 | Third parties | 2 | 6 |
| TP2 | Third parties | 3 | 9 |
| TP3 | Third parties | 2 | 6 |
| TP4 | Third parties | 1 | 3 |
| OT1 | Operational technology | 3 | 9 |
| OT2 | Operational technology | 3 | 9 |
| OT3 | Operational technology | 2 | 6 |
| OT4 | Operational technology | 2 | 6 |

Weights and maximums for all 36 controls. The same data is in the scoring dataset.

## Why these weights?

Weights are editorial judgments, not statistics. They are not derived from incident data and carry no claim of precision. Each is set by one test, applied the same way to every control.

- Weight 3: a source read for this site singles out the control as a route in (credentials, exposed services, unmonitored endpoints), as the way back (offline backups and tested restores), or as the authority needed in the first hour (decision rights, contacts).
- Weight 2: a source asks for the control and its absence widens the damage or slows recovery, but the control is not a first-line route in or out.
- Weight 1: a source asks for the control and it is cheap, or it refines another control.

You may disagree. Edit the weights in the JSON file and recompute; the formula is one line.

## What do the answers mean?

The top answer (3 points) means the control exists, is enforced or written, and has been tested or evidenced. Two points means it exists with a gap. One point means partial or informal. Zero means absent or unknown. Unknown scores zero, because an attacker also does not wait for you to find out.

## What can the score not tell you?

A self-assessed score is not an audit, a certification or a benchmark against other organizations. Bands are interpretive labels. The value is the list of gaps and the dated evidence behind each answer. Re-run it after every major change and each year.

## What changed between editions?

First edition, 16 November 2026: 36 controls in 9 groups, weights as above.

## Cite this

Ransomware Readiness Assessment, "Scoring rules and weights", edition 16 November 2026, https://ransomwarereadinessassessment.com/assessment/method/ (CC BY 4.0).

## Related pages

- [The assessment](/assessment/)
- [The control mapping](/mapping/)
- [Download the scoring data](/datasets/)
- [How sources are read](/method/)
- [Ransomware readiness](/readiness/ransomware-readiness/)
- [Ransomware Readiness Assessment: home](/)

## Sources

- CISA, MS-ISAC, FBI and NSA: #StopRansomware Guide (September 2023 edition, page read 16 November 2026): https://www.cisa.gov/stopransomware/ransomware-guide (read 16 November 2026)
- NIST IR 8374r1, full text (June 2026): https://nvlpubs.nist.gov/nistpubs/ir/2026/NIST.IR.8374r1.pdf (read 16 November 2026)
- CISA: Cybersecurity Performance Goals 2.0 (CPG 2.0) goal list: https://www.cisa.gov/cybersecurity-performance-goals-2-0-cpg-2-0 (read 16 November 2026)

Last reviewed 16 November 2026. Canonical: https://ransomwarereadinessassessment.com/assessment/method/
