Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A post-incident report is the authoritative written record of a security incident: what happened, in what order, why it was possible, and what changes follow from it.

What Is a Post-Incident Report?
A post-incident report is the document the organisation will still be reading in three years, when a regulator asks about the 2026 intrusion or a new security lead wants to know why the network is segmented the way it is. It records what happened, in what order, why it was possible, how the response went, and what changes follow. Written well, it is the most valuable artefact the whole response produces. Written as a formality, it is four pages nobody opens twice.
One document usually has to serve three audiences, which is why the structure matters more than the prose.
Write the executive summary last, keep it to a single page, and resist the temptation to soften it. A summary that omits the fact that an administrator account had no second factor is a summary that will be contradicted by the timeline four pages later.
Everything else hangs off an accurate chronology. Record every entry in UTC with the source that supports it, and distinguish clearly between when something happened and when you found out about it. Those two columns, placed side by side, produce the single most useful number in the report: dwell time.
A usable timeline entry names the evidence. “08:42 UTC — first malicious PowerShell execution on FIN-WS-114 (Event ID 4104, script block log)” can be checked by a reader two years later. “Attacker gained access in the morning” cannot. Where times are inferred rather than observed, say so, because an investigator who later finds earlier activity needs to know which entries were estimates.
Separate the root cause from the contributing factors, and keep both away from individuals. An intrusion that began when a member of staff entered credentials into a convincing phishing page has a root cause of single-factor remote access, not of one person’s judgement under time pressure. Phrasing it the other way guarantees the next person says nothing when they realise they have clicked something.
Where a control failed, state whether it was absent, misconfigured, or working as designed but insufficient. Those three answers lead to completely different remediation, and conflating them is how organisations buy a product to fix a process problem.
Track these across incidents and they become the most honest security metrics you have, because they are measured against real adversaries rather than exercises.
The report ends with actions, not observations. Each one needs an owner, a date, and a link to the hardening checklist that tracks it. An action written as “improve monitoring” will not be completed; “deploy endpoint detection to the 61 servers listed in Appendix C by 31 March” will.
Treat distribution deliberately. The report may contain personal data about staff, unremediated weaknesses, and material that solicitors will want handled under legal privilege, so agree the circulation list and classification before it is written rather than after it has been forwarded. Where a personal data breach occurred, UK GDPR requires notification to the ICO within 72 hours of becoming aware, which always precedes a finished report — the regulator expects an initial notification followed by fuller detail, and the post-incident report is what supplies that detail. Incidents affecting UK essential services or digital service providers carry separate duties under the NIS Regulations, and the NCSC asks for reports of significant incidents through its own channels.
At Privia Security, our digital forensic incident response services deliver the evidence-backed timeline that makes a report like this defensible.
Length follows the incident. A contained phishing attempt affecting one mailbox may need three pages; a ransomware event across an estate will run to forty with appendices. What stays constant is the structure: a one-page executive summary, an evidence-backed timeline, root cause and contributing factors, response assessment, and actions with owners and dates.
The incident lead, drawing on the analysts who did the work, with technical review from whoever performed the forensics and editorial review from someone outside the response. That outside reader is valuable: they catch the assumptions the team no longer notices and the jargon an executive will not follow. Never delegate the writing to someone who was not in the response.
Rarely in full. The internal report contains unremediated weaknesses and personal data that should not circulate. Produce a separate external summary covering what happened, what data was affected, what you have done, and what the recipient should do. Where UK GDPR requires notifying data subjects of a high-risk breach, that communication has its own required content and plain-language standard.
Longer than most retention schedules assume. Reports are referenced during later incidents, regulatory enquiries, insurance claims, and litigation that can begin years afterwards. Several years is typical, with the supporting evidence retained alongside under the same classification. Agree the period with legal and information governance, and store reports somewhere that survives a future compromise of the production estate.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.