Skip to content
Ransomware Readiness Assessment

Checked

Ransomware readiness assessment: score your controls, see the gaps, and plan the response

Readiness score

0%

Critical gaps

0 to 29 percent

0 of 234 points0 of 36 answered

0gaps

Scripts are off, so this is the printable checklist: tick one answer per control, multiply its points by the weight, and add up with the scoring rules on this page.

GVGovernance: Who decides, what is written down, and whether it has been rehearsed.

GV1GovernanceWeight 3, up to 9 pointsIs one named executive accountable for ransomware decisions, with written authority to order systems isolated?

Why GV1 matters, and its source

GV2GovernanceWeight 3, up to 9 pointsDoes your incident response plan carry ransomware and data-extortion procedures, approved in writing by the CEO or equivalent?

Why GV2 matters, and its source

GV3GovernanceWeight 2, up to 6 pointsWas the plan exercised against a ransomware scenario in the last 12 months, with executives in the room?

Why GV3 matters, and its source

GV4GovernanceWeight 2, up to 6 pointsAre your legal reporting duties for a ransomware event written down, with the clock, the recipient and the owner for each?

Why GV4 matters, and its source

IDIdentity and access: How attackers get credentials and how far a stolen one reaches.

ID1Identity and accessWeight 3, up to 9 pointsIs phishing-resistant multifactor authentication required for email, remote access, administrator accounts and cloud consoles?

Why ID1 matters, and its source

ID2Identity and accessWeight 3, up to 9 pointsDo administrators use separate accounts from their daily email and web accounts, and are privileges reviewed at least quarterly?

Why ID2 matters, and its source

ID3Identity and accessWeight 2, up to 6 pointsAre domain controllers and the identity platform hardened, restricted to a small admin group and kept off the internet?

Why ID3 matters, and its source

ID4Identity and accessWeight 1, up to 3 pointsAre default passwords changed, passwords unique and long, failed logins alerted on, and leavers cut off promptly?

Why ID4 matters, and its source

BRBackups and recovery: Whether you can restore without paying, and how fast.

BR1Backups and recoveryWeight 3, up to 9 pointsAre encrypted backups of critical systems kept offline or immutable, out of reach of your domain administrator credentials?

Why BR1 matters, and its source

BR2Backups and recoveryWeight 3, up to 9 pointsHas a full restore of your critical systems been tested in the last 12 months, with the elapsed time recorded?

Why BR2 matters, and its source

BR3Backups and recoveryWeight 2, up to 6 pointsDo you hold golden images, infrastructure-as-code templates and installers with license keys, stored offline?

Why BR3 matters, and its source

BR4Backups and recoveryWeight 2, up to 6 pointsIs there a ranked list of systems to restore, with their dependencies, and identity at the front of it?

Why BR4 matters, and its source

DTDetection: Whether someone sees the precursors before the encryption starts.

DT1DetectionWeight 3, up to 9 pointsIs endpoint detection or centrally managed anti-malware on servers and endpoints, with alerts that reach a person at any hour?

Why DT1 matters, and its source

DT2DetectionWeight 2, up to 6 pointsAre logs from critical systems, firewalls, VPN and identity collected centrally and kept for at least a year?

Why DT2 matters, and its source

DT3DetectionWeight 2, up to 6 pointsDo you alert on ransomware precursors: new privileged accounts, backup or shadow-copy deletion, unexpected remote management tools, large outbound transfers?

Why DT3 matters, and its source

DT4DetectionWeight 2, up to 6 pointsDoes the on-call route reach a person with authority to isolate systems outside business hours?

Why DT4 matters, and its source

SGSegmentation and platform: How far an intruder can travel and what they can reach from the internet.

SG1Segmentation and platformWeight 2, up to 6 pointsIs the network segmented so that a compromised workstation cannot reach servers, backups and management interfaces directly?

Why SG1 matters, and its source

SG2Segmentation and platformWeight 3, up to 9 pointsIs every internet-facing service inventoried, with remote desktop closed to the internet and VPN and edge devices patched?

Why SG2 matters, and its source

SG3Segmentation and platformWeight 2, up to 6 pointsDo you patch known exploited vulnerabilities on internet-facing systems within a time limit you set, and scan for gaps?

Why SG3 matters, and its source

SG4Segmentation and platformWeight 1, up to 3 pointsIs software execution restricted by allowlisting, and are hypervisors, PowerShell and remote tools hardened and logged?

Why SG4 matters, and its source

EEEmail and edge: Phishing, social engineering and web filtering in front of users.

EE1Email and edgeWeight 2, up to 6 pointsDoes email filtering block risky attachments, flag external senders and disable macros by default?

Why EE1 matters, and its source

EE2Email and edgeWeight 1, up to 3 pointsAre SPF, DKIM and DMARC set on all mail domains, with DMARC at reject?

Why EE2 matters, and its source

EE3Email and edgeWeight 2, up to 6 pointsDoes training cover phishing and advanced social engineering such as help desk impersonation, and do staff report without blame?

Why EE3 matters, and its source

EE4Email and edgeWeight 1, up to 3 pointsIs protective DNS or web filtering in place, with remote management tool ports blocked at the perimeter?

Why EE4 matters, and its source

RRResponse readiness: Contacts, authority and evidence handling on the day.

RR1Response readinessWeight 3, up to 9 pointsIs there an out-of-band way to reach responders and staff, and a paper contact list with 24-hour numbers?

Why RR1 matters, and its source

RR2Response readinessWeight 2, up to 6 pointsDo you have an incident response firm and breach counsel on retainer or pre-agreed terms, and does your insurer know the process?

Why RR2 matters, and its source

RR3Response readinessWeight 2, up to 6 pointsIs there a written path for a ransom payment decision, including a sanctions screening step and contact with law enforcement first?

Why RR3 matters, and its source

RR4Response readinessWeight 1, up to 3 pointsCan responders capture memory and disk images and keep a time-stamped decision log from the first hour?

Why RR4 matters, and its source

TPThird parties: Vendors and managed service providers who hold access or backups.

TP1Third partiesWeight 2, up to 6 pointsDo vendor and service provider contracts require incident notice within a set time?

Why TP1 matters, and its source

TP2Third partiesWeight 3, up to 9 pointsIs managed service provider access limited by least privilege, MFA and logging, and do you audit remote management tools?

Why TP2 matters, and its source

TP3Third partiesWeight 2, up to 6 pointsIf a provider keeps your backups or runs your systems, does the contract require the same backup practices you use?

Why TP3 matters, and its source

TP4Third partiesWeight 1, up to 3 pointsAre key providers on your contact list and in your exercises, and is cyber insurance in place?

Why TP4 matters, and its source

OTOperational technology: For sites with plants, pipelines, building systems or lab equipment. Mark the whole group not applicable if you run none.

OT1Operational technologyWeight 3, up to 9 pointsAre IT and OT networks separated by a demilitarized zone, with industrial protocols barred from the IT network?

Why OT1 matters, and its source

OT2Operational technologyWeight 3, up to 9 pointsHave you tested running the plant manually, and isolating OT from IT, within the last 12 months?

Why OT2 matters, and its source

OT3Operational technologyWeight 2, up to 6 pointsIs there a current inventory of OT assets and a network topology diagram, stored offline?

Why OT3 matters, and its source

OT4Operational technologyWeight 2, up to 6 pointsAre backups and gold images of controllers, HMIs and engineering workstations kept offline and restore-tested?

Why OT4 matters, and its source

Score your ransomware readiness, one control at a time

Question 1 of 36

Your gaps 0

Scoring rules

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.

Round the percent down to a whole number before reading the band. Points available: 234 with the OT group, 204 without it. An unanswered control scores zero.

  • 0 to 29Critical gapsBasic protections are missing. A ransomware event would likely stop the business until rebuilt.
  • 30 to 54PartialSome controls are in place, but one or more of the main routes in or the route back is open.
  • 55 to 79EstablishedMost controls exist. The remaining work is testing, written authority and coverage of edge cases.
  • 80 to 100TestedControls exist and have been exercised. Keep the evidence and repeat the test each year.

Any control with weight 3 that scores 0 points is listed as a priority gap, whatever the band. Weights and the reason for each are on the scoring method page.

Your gaps

Any control answered with 1 or 0 points is a gap. Any control with weight 3 that scores 0 points is listed as a priority gap, whatever the band. With scripts on, the list builds here as you answer.

    Your answers are kept in this browser only (localStorage on this device). Nothing is sent anywhere. The files are made on your device from your answers.

    See the control mapping

    Reporting clocks after an attack

    The dates to know once an incident is confirmed, quoted from the reporting duties page. Duties read at source. Contracts and insurance policies may add others.

    1. 4 business days

      SEC Form 8-K Item 1.05

      Four business days after the materiality determination.

      Status: In force since the rule took effect on 5 September 2023. 8-K page

    2. 60 calendar days

      HIPAA breach notification

      Individuals: without unreasonable delay and within 60 calendar days of discovery; HHS: with individual notice for 500 or more, otherwise within 60 days of year end; media: within 60 days when more than 500 residents of a State are affected.

      Status: In force (45 CFR 164.404, 164.406, 164.408, 164.410). HIPAA page

    3. 72 h and 24 h

      CIRCIA covered incident and ransom payment reports

      72 hours for covered incidents and 24 hours for ransom payments, as the statute directs.

      Status: Not required until the final rule takes effect. CIRCIA page

    4. By state

      State breach notification

      Set by each state.

      Status: Laws in all 50 states, DC, Guam, Puerto Rico and the Virgin Islands, per NCSL. State laws page

    5. As soon as possible

      Voluntary reports to CISA, FBI IC3, Secret Service

      As soon as possible, per OFAC and CISA.

      Status: Encouraged. Reporting duties

    Dated items, newest first

    1. Coveware Q3 2026: median ransom payment $400,000, most data-theft cases unpaid
    2. CISA holds four CIRCIA town halls; the final rule is still pending
    3. NIST finalizes IR 8374 Rev. 1, its ransomware profile for CSF 2.0

    Templates to download

    Each file below is free under CC BY 4.0. Print any template page straight from the browser.

    What is ransomware readiness?

    Ransomware readiness is the ability to prevent, detect, respond to and recover from a ransomware event. NIST IR 8374 Rev. 1, finalized in June 2026, says its profile helps gauge that readiness and deal with the consequences of events. The definition page sets out the wording used by NIST and CISA.

    The two original assets

    Questions people ask about scoring, the mapping and reporting are answered on the FAQ page.

    Sources

    Read 16 November 2026, the day this page was last reviewed, unless a line shows another date.

    1. NIST IR 8374 Rev. 1, Ransomware Risk Management: A Cybersecurity Framework 2.0 Community Profile (CSRC record)
    2. CISA, MS-ISAC, FBI and NSA: #StopRansomware Guide (September 2023 edition, page read 16 November 2026)
    3. CISA: Cybersecurity Performance Goals 2.0 (CPG 2.0) goal list

    Last reviewed 16 November 2026.