Updated:
Get Form Now
A cybersecurity incident response report is a written account of a cyberattack. It shows what happened, which systems and data were affected, and how your team responded. Security teams use this free template, especially right after a breach or ransomware attack.
A cyber security incident report is the single document where a security team writes down a security incident, from the first alert to the final fix, so IT staff, managers, and outside advisers work from the same facts.
A good report answers four plain questions:
Because every incident is written up in the same format, it is easy to compare one security incident with another and to spot patterns over time.
The record is useful long after the incident ends. A new team member can read an old entry and see how a similar problem was handled, which systems were involved, and which choices helped.
The names overlap in everyday use. A cyber incident report, a computer security incident report, and a cyber attack report describe the same kind of document, and this template works under any of those names.
A finished incident report is read by the security team, IT managers, senior management, and auditors, and each of them looks for something different in it. Clear and complete entries save everyone time. The usual readers include:
Start a cyber incident response report as soon as your team spots a possible security threat, such as unauthorized access, a malware infection, or a phishing email that someone answered, so every detail is captured from the start.
Scenarios where this form is helpful include:
The template helps structure the investigation and remediation efforts, ensuring a thorough approach to managing the incident.
A completed report is a big help in post-incident reviews and audits. For example, if a company experiences a data breach, the team can review the finished form to improve its security measures and response strategies. It also works as a training document, because it shows how the incident was handled and how similar incidents can be handled better in the future.
Your organization's incident response plan decides which events count as reportable incidents inside the company, and a plan can name suspected breaches, malware alerts, phishing clicks, and lost devices that hold company data.
Whether a regulator, a customer, or an outside agency gets a notice is a separate question for your attorney, and this template does not answer it.
Cybersecurity incidents that security teams often see include phishing, ransomware, malware, unauthorized access, data breaches, denial of service, lost or stolen devices, and insider misuse, and this form works for each of them.
Knowing the name of the incident type makes the form easier to fill in and easier to search later.
Before you start the incident report, gather the response lead's contact details, the time the incident was noticed, a list of affected systems, log excerpts or screenshots, and notes on any exposed data.
Each item below feeds a part of the form, and you can add more as the response moves forward:
Filling out the template takes six short steps, and each one matches a part of the form. Work through them in order while the facts are fresh. Keep your wording factual so anyone who reads the report later can follow what happened and why the team acted as it did.
Enter the name, job title, phone number, and email address of the person handling the incident response. This gives everyone a clear point of contact for follow-up actions.
Record a unique incident ID and note whether the source was internal or external. Then fill in these details, using the exact times from your logs when you can:
List every system, application, network segment, and data set the incident touched. A complete list shows how far the incident reached and helps the team decide where to act first.
Write a clear account of what happened, in the order it happened, including the likely entry point and the first effects your team noticed. Stick to facts and leave out guesses.
For example: At 9:14 a.m., Anna Baker in Accounting opened a link in an email that looked like a bank notice. At 9:20 a.m., her laptop began showing a lock screen, and the helpdesk was called.
Write down each action your team took to limit the damage, along with the time of each one. Cover both technical steps, such as isolating a device from the network, and communication steps, such as alerting staff.
Add any other observations, lessons learned, or ideas that may help with future responses or investigations. These notes feed straight into your post-incident review.
The cyber security incident report example below shows how a filled-in form reads for a phishing email that led to ransomware on a laptop. Every name, time, and detail in it is made up.
| Part of the form | Example entry |
|---|---|
| Contact information | Jordan Reyes, IT Security Manager, (555) 010-4477, jreyes@example.com |
| Incident ID and source | IR-0142, external |
| Incident type | Phishing email leading to ransomware |
| Started and found | Started 9:14 a.m., found 9:20 a.m., March 3, Eastern Time |
| Location | Accounting office, second floor |
| Severity and impact | High: one laptop locked, invoicing paused for four hours |
| Sensitive data | Under review: the laptop held vendor bank details |
| Systems and services impacted | Laptop ACCT-07, the finance shared drive, Anna Baker's email account |
| Description | At 9:14 a.m., Anna Baker in Accounting opened a link in an email that looked like a bank notice. At 9:20 a.m., her laptop began showing a lock screen, and the helpdesk was called. |
| Mitigation steps | 9:25 a.m., helpdesk unplugged the laptop from the network. 9:40 a.m., IT reset Anna Baker's password and signed out her sessions. 10:05 a.m., the IT Security Manager warned staff about the fake bank notice. 1:30 p.m., IT restored the laptop from a clean backup. |
| Comments and lessons learned | The fake notice passed the email filter. Add a warning banner for outside senders and run a phishing exercise next quarter. |
Notice what the example leaves out: guesses about who sent the email, opinions about the person who clicked, and any passwords. Those stay out of a real report too.
The incident response report runs alongside the whole response: it starts during detection and analysis, grows through containment and recovery, and is finished in the post-incident review.
Many teams still describe the response in the phases of the older NIST SP 800-61 Rev. 2 life cycle: preparation; detection and analysis; containment, eradication and recovery; and post-incident activity. Here is how the form connects to each phase:
The current federal guidance, NIST SP 800-61 Rev. 3, was published in April 2025 and supersedes Rev. 2 of 2012. Rev. 3 does not use that phase list: it ties incident response to cybersecurity risk management as described by the NIST Cybersecurity Framework (CSF) 2.0.
Preparing your team before an incident means agreeing on a response plan, a contact list, and a place to keep finished reports, so the team can act with less confusion when an alert arrives. A few simple habits help:
Practice also shows where your own standards for naming files and writing times need to be clearer, so that entries from different people look alike.
Report a cyber attack inside your organization first, through the channel your incident response plan names, such as the help desk or the security team, and then decide with management who outside the company needs to know.
The FBI Internet Crime Complaint Center (IC3) describes itself as the central hub for reporting cyber-enabled crime. The FBI Internet Crime Complaint Center (IC3) takes complaints ranging from cyber-enabled frauds and scams to cybercrime, asks people to file even when they are unsure a complaint qualifies, and says it cannot respond directly to every submission.
A completed incident report makes that complaint easier to write, because the times, systems, and actions are already set down in order.
This page does not cover notices to regulators, customers, or insurers. Ask your attorney or insurer before sending one.
A clear incident report uses plain words, a single time format with the time zone, and a name for every action, so the next reader can follow it without calling you. These habits keep your cyber incident notes short, accurate, and easy to follow, whether they are read tomorrow or a year from now:
After you complete the report, check that the dates, system names, and incident ID match your logs, then share it with the people who took part in the response so they can add anything that is missing.
Store your own copy with the other security files, and bring the lessons learned back to your incident response plan so the team can respond faster next time.
Responding well does not end when systems are back online. Follow-up activities help the organization restore normal operations and become more secure. Common follow-up activities include:
Completed incident reports show which cyberattacks happen most often, which parts of the network are hit first, and which security controls work. That analysis of past events helps technology and operations leaders manage risk, plan improvements, schedule testing, and decide where a strategic investment will make the business more secure.
Timely and accurate entries make the analysis far more reliable. Managing risk effectively starts with knowing exactly what occurred, so the details you record today become the evidence behind tomorrow's security decisions.
Teams often ask the same few questions when they first use this template. The short answers below point back to the steps above, so you can find the right part of the form quickly.
Usually the person leading the response fills it out, with input from IT, security, and any manager involved. Their details go in Step 1.
A reportable cyber security incident is any event your organization's incident response plan tells staff to report, such as a suspected breach, a malware alert, a phishing click, or a lost laptop. Notice to people outside the company is a separate question for your attorney.
Use the channel your organization's policy names, such as the help desk, the security team, or an internal reporting form, and report early rather than waiting until you are sure. The person leading the response then starts this form.
They overlap, but they are not the same. An IT incident report covers technical problems in general, such as an outage or a failed update. This form focuses on security incidents. If your event was a technical problem rather than an attack, the cybersecurity IT incident report may fit better.
Yes. A suspected event can be recorded too. Mark clearly what is confirmed and what is still being checked, and update the entry as the facts become clear.
Start as early as you can, even if some fields are blank. You can complete the rest as the facts come in and the incident is understood.
Share it with the response team, review the lessons learned, and keep a signed copy with your security records.
General information, not legal or tax advice.
