--- name: conducting-post-incident-lessons-learned description: Facilitate structured post-incident reviews to identify root causes, document what worked and failed, and produce actionable recommendations to improve future incident response. domain: cybersecurity subdomain: incident-response tags: [incident-response, lessons-learned, post-incident, after-action-review, process-improvement] version: "1.0" author: mahipal license: Apache-2.0 --- # Conducting Post-Incident Lessons Learned ## When to Use - After any security incident has been fully resolved and recovery completed - Following tabletop exercises or IR simulations - After significant near-miss events - Quarterly review of accumulated incident trends - When IR playbooks need updating based on real-world experience ## Prerequisites - Incident fully resolved (containment, eradication, recovery complete) - Incident timeline and documentation gathered - All incident responders available for review session - Meeting space for collaborative discussion - Incident ticketing system data for metrics analysis ## Workflow ### Step 1: Gather Incident Data ```bash # Export incident timeline from ticketing system curl -s "https://thehive.local/api/v1/case/$CASE_ID/timeline" \ -H "Authorization: Bearer $THEHIVE_API_KEY" | jq '.' > incident_timeline.json # Extract detection and response metrics from SIEM index=notable incident_id="IR-2024-042" | stats min(_time) as first_alert, max(_time) as last_alert, count as total_alerts, dc(src) as unique_sources # Compile all responder actions and timestamps grep -E "timestamp|action|analyst" /var/log/ir/IR-2024-042/*.json | \ python3 -m json.tool > compiled_actions.json ``` ### Step 2: Conduct Blameless Post-Mortem Meeting ``` Structured Agenda (90 minutes): 1. Incident summary (5 min) - Factual overview 2. Timeline walkthrough (20 min) - Chronological events 3. What worked well (15 min) - Positive outcomes 4. What needs improvement (15 min) - Gaps and failures 5. Root cause analysis (15 min) - 5 Whys or fishbone 6. Action items (10 min) - Specific improvements with owners 7. Playbook updates (10 min) - Changes to IR procedures Blameless Principles: - Focus on systems and processes, not individuals - Assume best intentions with available information - Seek to understand, not to blame ``` ### Step 3: Perform Root Cause Analysis ```bash # 5 Whys analysis example: # Why 1: Why did ransomware encrypt production servers? # Answer: Attacker had domain admin credentials # Why 2: Why did attacker have domain admin credentials? # Answer: Kerberoasted a service account and cracked it # Why 3: Why was the service account password crackable? # Answer: Used a 12-character dictionary-based password # Why 4: Why was the service account password weak? # Answer: No enforcement of service account password policy # Why 5: Why was there no service account password policy? # Answer: PAM was not implemented for service accounts # ROOT CAUSE: Lack of privileged access management ``` ### Step 4: Calculate Response Metrics ```python from datetime import datetime events = { 'compromise': '2024-01-10 14:00:00', 'detection': '2024-01-15 08:30:00', 'triage': '2024-01-15 08:45:00', 'containment': '2024-01-15 09:30:00', 'eradication': '2024-01-16 14:00:00', 'recovery': '2024-01-18 16:00:00', 'closure': '2024-01-25 10:00:00', } fmt = '%Y-%m-%d %H:%M:%S' times = {k: datetime.strptime(v, fmt) for k, v in events.items()} print(f"Dwell Time: {times['detection'] - times['compromise']}") print(f"MTTD: {times['triage'] - times['detection']}") print(f"MTTC: {times['containment'] - times['detection']}") print(f"MTTR: {times['recovery'] - times['eradication']}") print(f"Total Duration: {times['closure'] - times['detection']}") ``` ### Step 5: Document Findings and Create Action Items ```bash # Create tracked action items in project management curl -X POST "https://jira.local/rest/api/2/issue" \ -H "Authorization: Bearer $JIRA_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "fields": { "project": {"key": "SEC"}, "summary": "Implement PAM for service accounts (IR-2024-042)", "issuetype": {"name": "Task"}, "priority": {"name": "High"}, "assignee": {"name": "security_engineer"}, "duedate": "2024-03-15" } }' ``` ### Step 6: Update Playbooks and Detection Rules ```yaml # New Sigma detection rule based on incident learnings title: Kerberoasting Activity Detected status: stable description: Detects Kerberoasting based on IR-2024-042 lessons logsource: product: windows service: security detection: selection: EventID: 4769 TicketEncryptionType: '0x17' condition: selection level: high tags: - attack.credential_access - attack.t1558.003 ``` ## Key Concepts | Concept | Description | |---------|-------------| | Blameless Post-Mortem | Reviewing incidents focusing on systems, not blaming individuals | | Root Cause Analysis | Identifying the fundamental reason the incident occurred | | 5 Whys | Iterative questioning technique to find root cause | | MTTD | Mean Time to Detect - time from compromise to detection | | MTTC | Mean Time to Contain - time from detection to containment | | MTTR | Mean Time to Recover - time from eradication to full recovery | | Continuous Improvement | Iterating on IR processes based on real incident data | ## Tools & Systems | Tool | Purpose | |------|---------| | TheHive/ServiceNow | Incident timeline and documentation | | Jira/Azure DevOps | Action item tracking | | Confluence/SharePoint | Lessons learned documentation | | Splunk/Elastic | Incident metrics and detection improvement | | Sigma | Detection rule development | ## Common Scenarios 1. **Ransomware Post-Mortem**: Review entire kill chain from initial access to encryption. Identify detection gaps and backup failures. 2. **Phishing Campaign Review**: Analyze why users clicked, why email filters missed it, and how to improve training. 3. **Cloud Misconfiguration Incident**: Review IaC pipeline, CSPM coverage, and change management process. 4. **Insider Threat Review**: Examine DLP effectiveness, access control gaps, and user monitoring capabilities. 5. **Third-Party Breach Impact**: Review vendor risk assessment process and data sharing agreements. ## Output Format - Post-incident review meeting minutes - Root cause analysis document - Incident metrics report (MTTD, MTTC, MTTR) - Action items list with owners and deadlines - Updated IR playbooks and detection rules - Executive summary for leadership --- Source attribution: pinkpixel-dev Original project: https://github.com/pinkpixel-dev/skills-collection-1/blob/dc709653773653302e333a45d3b6f3b70fdff8f8/SKILLS/conducting-post-incident-lessons-learned/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by the Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding any notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. Please do not remove or change the license header comment from a contributed file except when necessary. Copyright 2026 mukul975 Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: pinkpixel-dev Original project: https://github.com/pinkpixel-dev/skills-collection-1/blob/dc709653773653302e333a45d3b6f3b70fdff8f8/SKILLS/conducting-post-incident-lessons-learned/SKILL.md Attribution basis: Source repository record Fields of work: Operations, Sales, Customer Support Roles: Business Development, Customer Success Manager, Operations Manager, Sales Development Rep (SDR), Technical Support Specialties: API Tools: Jira Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 3c517a10be048e33336d829249cef121bc74f4cd15740148fd424cd547591a44