NIST updates its ransomware risk management profile, mapping governance through recovery to CSF 2.0

NIST published IR 8374r1, a revised ransomware risk management report mapping relevant security outcomes to CSF 2.0 across Govern, Identify, Protect, Detect, Respond and Recover. It can support readiness planning and incident response playbooks; inclusion does not constitute certification.

Original illustration of colleagues rehearsing business recovery using a printed checklist and a backup drive
Illustration · Source ↗ · About this image ↗

Source Facts

NIST published IR 8374r1 on 11 June, providing a CSF 2.0 Community Profile for ransomware risk management. The report identifies cybersecurity objectives relevant to ransomware, covering governance and asset identification through prevention, detection, response and recovery.

The official summary says organisations can use the profile to assess readiness for ransomware threats and their possible consequences, then develop ransomware playbooks. It is a risk management reference, not a guarantee that adoption will prevent all attacks or ensure recovery.

Next Steps for Businesses / Editorial Observations

Start with one critical business function. Record owners, existing measures and evidence for each item, address gaps in backup restoration and incident responsibilities first, then expand across the organisation.

Next steps you can take

  • Choose one critical business function and list owners, existing measures and missing evidence across governance through recovery.
  • Turn inventory findings into an incident response checklist, run a restoration drill and record the time required and unresolved dependencies.

Original sources

NIST IR 8374r1 Ransomware Risk Management: A Cybersecurity Framework 2.0 Community Profile

Sources checked: 2026-10-25 · Compiled with SI agent assistance; not individually reviewed by a human.

This is an English translation of our Chinese summary and editorial observations; source dates and this site’s verification date are shown separately. If an original advisory changes, refer to the source.

Back to news ←