# A ransomware incident report template has ten sections and one block for the fields law enforcement asks for

Template, read 16 November 2026

**The short answer.** A ransomware incident report states what happened, what was affected, what was done, what has been reported and what comes next. This template has ten sections and includes the fields the FBI Internet Crime Complaint Center asks for: variant, file extension, wallet details, attacker email, ransom demand and whether anything was paid. Read on 16 November 2026.

## Is there a ransomware incident report template?

Yes. The ten sections below can be pasted into a document. Write facts and mark unknowns as unknown, because the first report is usually revised.

1. Summary: date and time of discovery, current status, business impact in one paragraph.
2. Timeline: time-stamped events from the decision log.
3. Systems and services affected, and those confirmed unaffected.
4. Data affected: types, volumes, and whether theft is confirmed, suspected or ruled out.
5. Actions taken: isolation, evidence preserved, outside help engaged.
6. Entry route and attacker activity, as far as known.
7. Demand and contact: whether a demand was made, what, and who has been in contact.
8. Notifications made and due: regulators, individuals, customers, insurer, law enforcement, with the clock for each.
9. Recovery status: restore order, progress and next milestones.
10. Open decisions and who owns them.

## What does law enforcement ask a victim to provide?

The FBI Internet Crime Complaint Center says a complaint should contain all required data in its fields, including the ransomware variant name if known; the file extension of encrypted files; cryptocurrency type and address; the email address used by the attackers; websites or URLs provided by the attackers; the ransom demand amount; and whether the ransom was paid and, if so, the amount. Collect these in one block of the report so one person can file once.

The FBI also states that it does not support paying a ransom. The [reporting page](/reporting/ransomware-reporting-duties/) covers other recipients.

## Who should receive the report?

Send the executive version to the executive decider and board, the insurer version to the insurer under the policy terms, and the regulator version only after counsel has reviewed it. Keep a single source of facts, the decision log, and derive each version from it.

## Related pages

- [Ransomware playbook: steps for the first 72 hours](/playbook/ransomware-playbook/)
- [Ransomware playbook flowchart: the decision paths](/playbook/ransomware-playbook-flowchart/)
- [Ransomware playbook keyed to NIST IR 8374 Rev. 1](/playbook/ransomware-playbook-nist/)
- [What is a ransomware playbook, and who holds it?](/playbook/what-is-a-ransomware-playbook/)
- [The ransomware readiness assessment](/assessment/)
- [The control mapping](/mapping/)

## Sources

- FBI Internet Crime Complaint Center: Ransomware: https://www.ic3.gov/CrimeInfo/Ransomware (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)
- 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/playbook/ransomware-incident-report-template/
