SESK: Stuff Everyone Should Know · sesk.info/secplus-lessons-learned-meeting
What is the purpose of a lessons learned meeting after a major security incident?
To review how the response went and identify improvements to controls and practices.
- Review the response and identify improvements ✔
- Assign blame to one person
- Delete all evidence of the incident
Why: Lessons learned closes the loop. The team reviews what worked, what failed and what to change. The results feed back into preparation for the next incident.
Huh, didn't know that: NIST's 2025 guidance says lessons learned should often be shared as soon as they are found, not held until recovery ends.
Our lessons learned meeting lasted two hours. The main lesson: don't hold two-hour meetings.
Like this card?
References
Answer: Review the response and identify improvements. Lessons learned closes the loop. The team reviews what worked, what failed and what to change. The results feed back into preparation for the next incident.
- NIST SP 800-61 Rev. 2, Computer Security Incident Handling Guide nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-61r2.pdf
the organization should hold a lessons learned meeting to review the effectiveness of the incident handling process
Checked 2026-10-10. - NIST SP 800-61 Rev. 3, Incident Response Recommendations and Considerations for Cybersecurity Risk Management nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-61r3.pdf
should often be shared as soon as they are identified, not delayed until after recovery concludes
Checked 2026-10-10.
Think this answer is wrong? Tap "Challenge this answer" on the card in the game and tell us why.
More stuff everyone should know
That's stuff everyone should know.