1. National Institute of Standards and Technology (NIST). (2012). SP 800-61 Rev. 2, Computer Security Incident Handling Guide. Section 3.4, "Post-Incident Activity," and Section 3.4.2, "Lessons Learned," pp. 43-44. This section explicitly states that this phase involves "learning and improving" and holding a "lessons learned meeting" to discuss what happened and how to improve. The creation of a final report for management is a key output.
2. Wilson, M., & Hash, J. (2003). CSIRT Development, Establishing a Computer Security Incident Response Team. Carnegie Mellon University, Software Engineering Institute. CMU/SEI-2003-TN-001. Section 4.3, "Post-Incident Analysis," p. 19. This document describes the post-incident phase as the time to "review all available information... to determine exactly what happened, why it happened, and what can be done to prevent it from happening again."
3. University of Washington. (n.d.). T INFO 442: Information Assurance and Cybersecurity - Incident Response. Courseware. The curriculum outlines the incident response process based on the NIST framework, identifying "Post-Incident Activity (Lessons Learned)" as the final, critical phase for review and reporting.