# A ransomware decision log records each decision, who took it, on what advice and with which alternatives

Template, read 16 November 2026

**The short answer.** A ransomware decision log is a time-stamped record of each decision taken during an incident: what was decided, by whom, on whose advice, with what options considered. It supports later reporting, insurance and review. The SEC final rule treats delay in a materiality determination as a compliance risk, which makes timing records useful. Read on 16 November 2026.

## What is a ransomware decision log?

A ransomware decision log is a running table kept by a scribe from the first hour. It records the time of each decision, the decision, the decider, the advice received, the options not taken and the next review time.

The first reason to keep one is clarity. NIST says estimating the impact and scope of an event informs response and recovery priorities and supports a cost-benefit analysis when deciding whether a ransom should be paid. The log shows what was known when the choice was made.

## Why does timing matter in the log?

For companies filing under SEC rules, the final rule requires a materiality determination "without unreasonable delay" and says that deferring a board committee meeting past the normal time to convene would be unreasonable delay. The release adds that revising incident response policies to delay a determination would also be unreasonable. A log with times shows the determination followed normal practice.

OFAC also considers the timing and completeness of reporting and cooperation with law enforcement as significant mitigating factors, so log the time of each report.

## What columns should the log have?

| Time (UTC) | Decision | Decider | Advice received | Options not taken | Evidence or log reference | Next review |
| --- | --- | --- | --- | --- | --- | --- |
| [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |

Blank log. Print several copies and keep them with the plan.

Always log these decisions: isolation, any power-down, outside help engaged, insurer and law enforcement contact, every reporting clock started, any contact with the actor, any payment decision and its screening, and the declaration that the incident is over. See the [plan template](/plan/ransomware-response-plan-template/), sections 3 and 8.

## Related pages

- [Ransomware response plan: what it holds and who signs](/plan/ransomware-response-plan/)
- [Ransomware response roles: who does what](/plan/ransomware-response-roles/)
- [Ransomware communications plan: staff, customers, press](/plan/ransomware-communications-plan/)
- [Ransomware response plan template: full text and .docx](/plan/ransomware-response-plan-template/)
- [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)
- OFAC: Updated Advisory on Potential Sanctions Risks for Facilitating Ransomware Payments, 21 September 2021: https://ofac.treasury.gov/media/912981/download?inline (read 16 November 2026)

Last reviewed 16 November 2026. Canonical: https://ransomwarereadinessassessment.com/plan/ransomware-decision-log/
