Skip to content
Ransomware Readiness Assessment

TemplateChecked

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

Take the assessmentSee the control mapping

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?

Blank log. Print several copies and keep them with the plan.
Time (UTC)DecisionDeciderAdvice receivedOptions not takenEvidence or log referenceNext review
[ ][ ][ ][ ][ ][ ][ ]Blank row to fill in on the printed copy: Time (UTC), Decision, Decider, Advice received, Options not taken, Evidence or log reference, Next review.
[ ][ ][ ][ ][ ][ ][ ]Blank row to fill in on the printed copy: Time (UTC), Decision, Decider, Advice received, Options not taken, Evidence or log reference, Next review.
[ ][ ][ ][ ][ ][ ][ ]Blank row to fill in on the printed copy: Time (UTC), Decision, Decider, Advice received, Options not taken, Evidence or log reference, Next review.
[ ][ ][ ][ ][ ][ ][ ]Blank row to fill in on the printed copy: Time (UTC), Decision, Decider, Advice received, Options not taken, Evidence or log reference, Next review.
[ ][ ][ ][ ][ ][ ][ ]Blank row to fill in on the printed copy: Time (UTC), Decision, Decider, Advice received, Options not taken, Evidence or log reference, Next review.

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, sections 3 and 8.

Sources

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

  1. NIST IR 8374r1, full text (June 2026)
  2. Federal Register: SEC final rule on cybersecurity risk management, strategy, governance and incident reporting (4 August 2023)
  3. OFAC: Updated Advisory on Potential Sanctions Risks for Facilitating Ransomware Payments, 21 September 2021

Last reviewed 16 November 2026.