# A board briefing on ransomware readiness should show six things, each backed by a test or a document

Briefing guide, read 16 November 2026

**The short answer.** A board briefing on ransomware readiness should show who may order isolation, the date of the last restore test, the date of the last exercise, the written reporting duties, third-party access and insurance. Each maps to a published expectation. SEC rules add board-level duties for public companies. Read on 16 November 2026.

## What should a board ask about ransomware readiness?

A board should ask six questions and expect a date or a document in reply. Who may order systems isolated, and is that written down? When was a full restore last tested, and how long did it take? When was the response plan last exercised with executives present? Which legal reporting duties apply and who owns each clock? Which third parties hold access or backups? Is there cyber insurance, and who calls the insurer?

The questions map to controls GV1, BR2, GV3, GV4, TP2 and TP4 on the [assessment](/assessment/).

## What does NIST say about governance for ransomware?

NIST places ransomware risk inside enterprise risk management. Its profile says ransomware risks must be factored into organizational risk management governance, including factors that might transfer risk such as cyber insurance (GV.RM-03), and that a documented risk appetite helps make clear and justifiable decisions during response and recovery (GV.RM-02).

## Do public company boards have extra duties?

For companies subject to SEC rules, the final rule adopted in 2023 requires annual reporting on the board's oversight of risks from cybersecurity threats and on management's role in assessing them, plus a Form 8-K Item 1.05 filing for material incidents. The [8-K page](/reporting/sec-form-8-k-item-1-05/) sets out the filing clock.

A one-page summary for directors can use the [leadership checklist](/readiness/ransomware-readiness-checklist/).

## Related pages

- [Ransomware readiness: what it covers and how to test it](/readiness/ransomware-readiness/)
- [Ransomware preparedness checklist for IT teams](/readiness/ransomware-preparedness-checklist/)
- [Ransomware readiness for a small business](/readiness/ransomware-readiness-for-small-business/)
- [Ransomware readiness assessment cost: what drives it](/readiness/ransomware-readiness-assessment-cost/)
- [Backup and Active Directory recovery readiness](/readiness/ransomware-backup-and-identity-recovery-readiness/)
- [The ransomware readiness assessment](/assessment/)
- [The control mapping](/mapping/)

## Sources

- NIST IR 8374r1, full text (June 2026): https://nvlpubs.nist.gov/nistpubs/ir/2026/NIST.IR.8374r1.pdf (read 16 November 2026)
- Federal Register: SEC final rule on cybersecurity risk management, strategy, governance and incident reporting (4 August 2023): https://www.federalregister.gov/documents/2023/08/04/2023-16194/cybersecurity-risk-management-strategy-governance-and-incident-disclosure (read 16 November 2026)
- 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)
- 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/readiness/ransomware-readiness-board-briefing/
