Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A lessons learned review is the structured session after an incident where a team establishes what actually happened, where detection and response fell short, and what will change as a result.

What Is a Lessons Learned Review?
The last phase of incident response is the one most often skipped. Systems are back, everyone is exhausted, and the review slips until the details have faded. That is a costly habit, because the review is where an incident stops being a loss and becomes the reason the next one is caught in an hour rather than a month.
Within two weeks of closure is the usual guidance, and it holds. Invite everyone who was involved rather than only the technical responders: the service desk analyst who took the first call, the communications lead, legal, the business owner whose system was affected, and the external provider if one was engaged. Each of them saw a different part of the incident, and the gaps between those views are usually where the real findings sit.
Appoint a facilitator who was not running the response. An incident lead chairing a review of their own decisions produces a polite meeting and a thin action list.
Start by agreeing the facts before anyone discusses them. Put the full sequence on a wall or a shared document: when the attacker gained access, when the first signal appeared somewhere in the environment, when a human noticed it, when the incident was declared, when containment began, when eradication completed, and when service was restored.
The intervals are the findings. The distance between first signal and human noticing is a detection problem. The distance between noticing and declaring is a triage or confidence problem. The distance between declaring and containing is usually an authority or access problem. Each one has a different fix, and a timeline makes the distinction obvious in a way that discussion alone does not.
If people expect to be blamed, they will present a version of events in which nothing could have been done differently, and the review produces nothing. The useful framing is that systems let people make mistakes: the engineer who clicked the link was not the cause, the absence of attachment sandboxing and the lack of a quick reporting route were. Say so explicitly at the start, and make sure senior attendees behave accordingly.
Every finding needs an owner, a date, and a measure of done. Four tracked actions that are completed beat twenty recommendations that are filed. Route them into the normal change and risk processes rather than a private spreadsheet, and report progress to the same executives who were briefed during the incident — visibility is what keeps remediation funded after the urgency fades.
Track a small set of metrics across incidents: time to detect, time to contain, how often initial severity was wrong, and how many actions from previous reviews were still open when this incident began. That last figure is uncomfortable and more predictive than any other. Mandiant’s M-Trends research has shown global median dwell time falling to around ten days, driven largely by better detection and by third-party notification — comparing your own figure with that is a sharper benchmark than a maturity score.
Feed the output back into detections, playbooks, the incident response plan, and the next tabletop exercise. At Privia Security, we facilitate post-incident reviews through our investigation and incident response services, and an external chair usually produces a more candid conversation than an internal one.
Everyone who touched the incident, not just the technical team. That includes the person who first reported it, service desk staff, the incident lead, system owners, communications, legal or the data protection officer, and any external provider engaged. Different participants saw different parts of the sequence, and the disagreements between their accounts are usually where the most useful findings are.
Within two weeks of closure. Earlier and the team is still recovering and the facts are incomplete; later and memory degrades, people move on, and the urgency that funds remediation disappears. For long-running incidents, hold an interim review once containment is complete rather than waiting for full recovery weeks later.
Three things above all: a chair who ran the response, a culture where people expect blame, and actions with no owner or deadline. The first produces defensiveness, the second produces a sanitised account, and the third produces a document nobody revisits. Measuring how many previous actions were still open at the start of the new incident exposes all three.
Take legal advice before writing it, because the document may be disclosable. That is a reason to be careful with speculative language, not a reason to avoid candour about facts. Regulators generally respond well to evidence of a structured review with tracked remediation, and clients asking supplier assurance questions increasingly want to see that the process exists.
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.