[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HDG2GEXJDQNTW8EEZA6KF7":3,"skill-same:01M6HDG2GEXJDQNTW8EEZA6KF7":119},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":65,"repositoryHtmlUrl":66,"repositoryHomepageUrl":6,"ownerHtmlUrl":67,"ownerBlogUrl":6,"ownerDescription":68,"updatedAt":69,"install":70,"resources":83},"01M6HDG2GEXJDQNTW8EEZA6KF7","conducting-post-incident-lessons-learned",null,"Facilitate structured post-incident reviews to identify root causes, document what worked and failed, and produce actionable recommendations to improve future incident response.","HenriqueMC17\u002Fagente-core","HenriqueMC17","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206460478?v=4","01M6HB63HBBF18AC4H09XTB549","Henrique Monteiro Cardoso","01M6HB63NGSQXWKWCFWW2B20W0",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fconducting-post-incident-lessons-learned\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"lessons learned","conducting post incident lessons learned","post","learned","incident","document","improvement","action","reviews","actionable","recommendations","review","process","improve","t1566","t1059","t1078","produce","incident response","cybersecurity","2026-11-10 10:12:30",false,"---\nname: conducting-post-incident-lessons-learned\ndescription: Facilitate structured post-incident reviews to identify root causes, document what worked and failed, and produce actionable recommendations to improve future incident response.\ndomain: cybersecurity\nsubdomain: incident-response\ntags:\n- incident-response\n- lessons-learned\n- post-incident\n- after-action-review\n- process-improvement\nmitre_attack:\n- T1566\n- T1486\n- T1059\n- T1078\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- RS.MA-01\n- RS.MA-02\n- RS.AN-03\n- RC.RP-01\ncategory: conducting-post-incident-lessons-learned\n---\n# Conducting Post-Incident Lessons Learned\n\n## When to Use\n- After any security incident has been fully resolved and recovery completed\n- Following tabletop exercises or IR simulations\n- After significant near-miss events\n- Quarterly review of accumulated incident trends\n- When IR playbooks need updating based on real-world experience\n\n## Prerequisites\n- Incident fully resolved (containment, eradication, recovery complete)\n- Incident timeline and documentation gathered\n- All incident responders available for review session\n- Meeting space for collaborative discussion\n- Incident ticketing system data for metrics analysis\n\n## Workflow\n\n### Step 1: Gather Incident Data\n```bash\n# Export incident timeline from ticketing system\ncurl -s \"https:\u002F\u002Fthehive.local\u002Fapi\u002Fv1\u002Fcase\u002F$CASE_ID\u002Ftimeline\" \\\n  -H \"Authorization: Bearer $THEHIVE_API_KEY\" | jq '.' > incident_timeline.json\n\n# Extract detection and response metrics from SIEM\nindex=notable incident_id=\"IR-2024-042\"\n| stats min(_time) as first_alert, max(_time) as last_alert,\n  count as total_alerts, dc(src) as unique_sources\n\n# Compile all responder actions and timestamps\ngrep -E \"timestamp|action|analyst\" \u002Fvar\u002Flog\u002Fir\u002FIR-2024-042\u002F*.json | \\\n  python3 -m json.tool > compiled_actions.json\n```\n\n### Step 2: Conduct Blameless Post-Mortem Meeting\n```\nStructured Agenda (90 minutes):\n1. Incident summary (5 min) - Factual overview\n2. Timeline walkthrough (20 min) - Chronological events\n3. What worked well (15 min) - Positive outcomes\n4. What needs improvement (15 min) - Gaps and failures\n5. Root cause analysis (15 min) - 5 Whys or fishbone\n6. Action items (10 min) - Specific improvements with owners\n7. Playbook updates (10 min) - Changes to IR procedures\n\nBlameless Principles:\n- Focus on systems and processes, not individuals\n- Assume best intentions with available information\n- Seek to understand, not to blame\n```\n\n### Step 3: Perform Root Cause Analysis\n```bash\n# 5 Whys analysis example:\n# Why 1: Why did ransomware encrypt production servers?\n#   Answer: Attacker had domain admin credentials\n# Why 2: Why did attacker have domain admin credentials?\n#   Answer: Kerberoasted a service account and cracked it\n# Why 3: Why was the service account password crackable?\n#   Answer: Used a 12-character dictionary-based password\n# Why 4: Why was the service account password weak?\n#   Answer: No enforcement of service account password policy\n# Why 5: Why was there no service account password policy?\n#   Answer: PAM was not implemented for service accounts\n# ROOT CAUSE: Lack of privileged access management\n```\n\n### Step 4: Calculate Response Metrics\n```python\nfrom datetime import datetime\nevents = {\n    'compromise': '2024-01-10 14:00:00',\n    'detection': '2024-01-15 08:30:00',\n    'triage': '2024-01-15 08:45:00',\n    'containment': '2024-01-15 09:30:00',\n    'eradication': '2024-01-16 14:00:00',\n    'recovery': '2024-01-18 16:00:00',\n    'closure': '2024-01-25 10:00:00',\n}\nfmt = '%Y-%m-%d %H:%M:%S'\ntimes = {k: datetime.strptime(v, fmt) for k, v in events.items()}\nprint(f\"Dwell Time: {times['detection'] - times['compromise']}\")\nprint(f\"MTTD: {times['triage'] - times['detection']}\")\nprint(f\"MTTC: {times['containment'] - times['detection']}\")\nprint(f\"MTTR: {times['recovery'] - times['eradication']}\")\nprint(f\"Total Duration: {times['closure'] - times['detection']}\")\n```\n\n### Step 5: Document Findings and Create Action Items\n```bash\n# Create tracked action items in project management\ncurl -X POST \"https:\u002F\u002Fjira.local\u002Frest\u002Fapi\u002F2\u002Fissue\" \\\n  -H \"Authorization: Bearer $JIRA_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"fields\": {\n      \"project\": {\"key\": \"SEC\"},\n      \"summary\": \"Implement PAM for service accounts (IR-2024-042)\",\n      \"issuetype\": {\"name\": \"Task\"},\n      \"priority\": {\"name\": \"High\"},\n      \"assignee\": {\"name\": \"security_engineer\"},\n      \"duedate\": \"2024-03-15\"\n    }\n  }'\n```\n\n### Step 6: Update Playbooks and Detection Rules\n```yaml\n# New Sigma detection rule based on incident learnings\ntitle: Kerberoasting Activity Detected\nstatus: stable\ndescription: Detects Kerberoasting based on IR-2024-042 lessons\nlogsource:\n  product: windows\n  service: security\ndetection:\n  selection:\n    EventID: 4769\n    TicketEncryptionType: '0x17'\n  condition: selection\nlevel: high\ntags:\n  - attack.credential_access\n  - attack.t1558.003\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| Blameless Post-Mortem | Reviewing incidents focusing on systems, not blaming individuals |\n| Root Cause Analysis | Identifying the fundamental reason the incident occurred |\n| 5 Whys | Iterative questioning technique to find root cause |\n| MTTD | Mean Time to Detect - time from compromise to detection |\n| MTTC | Mean Time to Contain - time from detection to containment |\n| MTTR | Mean Time to Recover - time from eradication to full recovery |\n| Continuous Improvement | Iterating on IR processes based on real incident data |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| TheHive\u002FServiceNow | Incident timeline and documentation |\n| Jira\u002FAzure DevOps | Action item tracking |\n| Confluence\u002FSharePoint | Lessons learned documentation |\n| Splunk\u002FElastic | Incident metrics and detection improvement |\n| Sigma | Detection rule development |\n\n## Common Scenarios\n\n1. **Ransomware Post-Mortem**: Review entire kill chain from initial access to encryption. Identify detection gaps and backup failures.\n2. **Phishing Campaign Review**: Analyze why users clicked, why email filters missed it, and how to improve training.\n3. **Cloud Misconfiguration Incident**: Review IaC pipeline, CSPM coverage, and change management process.\n4. **Insider Threat Review**: Examine DLP effectiveness, access control gaps, and user monitoring capabilities.\n5. **Third-Party Breach Impact**: Review vendor risk assessment process and data sharing agreements.\n\n## Output Format\n- Post-incident review meeting minutes\n- Root cause analysis document\n- Incident metrics report (MTTD, MTTC, MTTR)\n- Action items list with owners and deadlines\n- Updated IR playbooks and detection rules\n- Executive summary for leadership\n","# Conducting Post-Incident Lessons Learned\n\n## When to Use\n- After any security incident has been fully resolved and recovery completed\n- Following tabletop exercises or IR simulations\n- After significant near-miss events\n- Quarterly review of accumulated incident trends\n- When IR playbooks need updating based on real-world experience\n\n## Prerequisites\n- Incident fully resolved (containment, eradication, recovery complete)\n- Incident timeline and documentation gathered\n- All incident responders available for review session\n- Meeting space for collaborative discussion\n- Incident ticketing system data for metrics analysis\n\n## Workflow\n\n### Step 1: Gather Incident Data\n```bash\n# Export incident timeline from ticketing system\ncurl -s \"https:\u002F\u002Fthehive.local\u002Fapi\u002Fv1\u002Fcase\u002F$CASE_ID\u002Ftimeline\" \\\n  -H \"Authorization: Bearer $THEHIVE_API_KEY\" | jq '.' > incident_timeline.json\n\n# Extract detection and response metrics from SIEM\nindex=notable incident_id=\"IR-2024-042\"\n| stats min(_time) as first_alert, max(_time) as last_alert,\n  count as total_alerts, dc(src) as unique_sources\n\n# Compile all responder actions and timestamps\ngrep -E \"timestamp|action|analyst\" \u002Fvar\u002Flog\u002Fir\u002FIR-2024-042\u002F*.json | \\\n  python3 -m json.tool > compiled_actions.json\n```\n\n### Step 2: Conduct Blameless Post-Mortem Meeting\n```\nStructured Agenda (90 minutes):\n1. Incident summary (5 min) - Factual overview\n2. Timeline walkthrough (20 min) - Chronological events\n3. What worked well (15 min) - Positive outcomes\n4. What needs improvement (15 min) - Gaps and failures\n5. Root cause analysis (15 min) - 5 Whys or fishbone\n6. Action items (10 min) - Specific improvements with owners\n7. Playbook updates (10 min) - Changes to IR procedures\n\nBlameless Principles:\n- Focus on systems and processes, not individuals\n- Assume best intentions with available information\n- Seek to understand, not to blame\n```\n\n### Step 3: Perform Root Cause Analysis\n```bash\n# 5 Whys analysis example:\n# Why 1: Why did ransomware encrypt production servers?\n#   Answer: Attacker had domain admin credentials\n# Why 2: Why did attacker have domain admin credentials?\n#   Answer: Kerberoasted a service account and cracked it\n# Why 3: Why was the service account password crackable?\n#   Answer: Used a 12-character dictionary-based password\n# Why 4: Why was the service account password weak?\n#   Answer: No enforcement of service account password policy\n# Why 5: Why was there no service account password policy?\n#   Answer: PAM was not implemented for service accounts\n# ROOT CAUSE: Lack of privileged access management\n```\n\n### Step 4: Calculate Response Metrics\n```python\nfrom datetime import datetime\nevents = {\n    'compromise': '2024-01-10 14:00:00',\n    'detection': '2024-01-15 08:30:00',\n    'triage': '2024-01-15 08:45:00',\n    'containment': '2024-01-15 09:30:00',\n    'eradication': '2024-01-16 14:00:00',\n    'recovery': '2024-01-18 16:00:00',\n    'closure': '2024-01-25 10:00:00',\n}\nfmt = '%Y-%m-%d %H:%M:%S'\ntimes = {k: datetime.strptime(v, fmt) for k, v in events.items()}\nprint(f\"Dwell Time: {times['detection'] - times['compromise']}\")\nprint(f\"MTTD: {times['triage'] - times['detection']}\")\nprint(f\"MTTC: {times['containment'] - times['detection']}\")\nprint(f\"MTTR: {times['recovery'] - times['eradication']}\")\nprint(f\"Total Duration: {times['closure'] - times['detection']}\")\n```\n\n### Step 5: Document Findings and Create Action Items\n```bash\n# Create tracked action items in project management\ncurl -X POST \"https:\u002F\u002Fjira.local\u002Frest\u002Fapi\u002F2\u002Fissue\" \\\n  -H \"Authorization: Bearer $JIRA_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"fields\": {\n      \"project\": {\"key\": \"SEC\"},\n      \"summary\": \"Implement PAM for service accounts (IR-2024-042)\",\n      \"issuetype\": {\"name\": \"Task\"},\n      \"priority\": {\"name\": \"High\"},\n      \"assignee\": {\"name\": \"security_engineer\"},\n      \"duedate\": \"2024-03-15\"\n    }\n  }'\n```\n\n### Step 6: Update Playbooks and Detection Rules\n```yaml\n# New Sigma detection rule based on incident learnings\ntitle: Kerberoasting Activity Detected\nstatus: stable\ndescription: Detects Kerberoasting based on IR-2024-042 lessons\nlogsource:\n  product: windows\n  service: security\ndetection:\n  selection:\n    EventID: 4769\n    TicketEncryptionType: '0x17'\n  condition: selection\nlevel: high\ntags:\n  - attack.credential_access\n  - attack.t1558.003\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| Blameless Post-Mortem | Reviewing incidents focusing on systems, not blaming individuals |\n| Root Cause Analysis | Identifying the fundamental reason the incident occurred |\n| 5 Whys | Iterative questioning technique to find root cause |\n| MTTD | Mean Time to Detect - time from compromise to detection |\n| MTTC | Mean Time to Contain - time from detection to containment |\n| MTTR | Mean Time to Recover - time from eradication to full recovery |\n| Continuous Improvement | Iterating on IR processes based on real incident data |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| TheHive\u002FServiceNow | Incident timeline and documentation |\n| Jira\u002FAzure DevOps | Action item tracking |\n| Confluence\u002FSharePoint | Lessons learned documentation |\n| Splunk\u002FElastic | Incident metrics and detection improvement |\n| Sigma | Detection rule development |\n\n## Common Scenarios\n\n1. **Ransomware Post-Mortem**: Review entire kill chain from initial access to encryption. Identify detection gaps and backup failures.\n2. **Phishing Campaign Review**: Analyze why users clicked, why email filters missed it, and how to improve training.\n3. **Cloud Misconfiguration Incident**: Review IaC pipeline, CSPM coverage, and change management process.\n4. **Insider Threat Review**: Examine DLP effectiveness, access control gaps, and user monitoring capabilities.\n5. **Third-Party Breach Impact**: Review vendor risk assessment process and data sharing agreements.\n\n## Output Format\n- Post-incident review meeting minutes\n- Root cause analysis document\n- Incident metrics report (MTTD, MTTC, MTTR)\n- Action items list with owners and deadlines\n- Updated IR playbooks and detection rules\n- Executive summary for leadership\n",{"name":5,"tags":44,"author":50,"domain":38,"license":15,"version":51,"category":5,"nist_csf":52,"subdomain":45,"description":7,"mitre_attack":57},[45,46,47,48,49],"incident-response","lessons-learned","post-incident","after-action-review","process-improvement","mahipal","1.0",[53,54,55,56],"RS.MA-01","RS.MA-02","RS.AN-03","RC.RP-01",[58,59,60,61],"T1566","T1486","T1059","T1078","main","5eea5b3296f4673b5f481e8bcc1ba76281149f16","modules\u002Fconducting-post-incident-lessons-learned",0,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core","https:\u002F\u002Fgithub.com\u002FHenriqueMC17","Qualquer tecnologia suficientemente avançada é indistinguível da mágica.","2026-09-28 22:40:38",{"source":8,"skillName":5,"commands":71,"prompt":81,"zipAvailable":82},[72,75,78],{"tool":73,"command":74},"npx","npx skills add HenriqueMC17\u002Fagente-core --skill conducting-post-incident-lessons-learned",{"tool":76,"command":77},"bunx","bunx skills add HenriqueMC17\u002Fagente-core --skill conducting-post-incident-lessons-learned",{"tool":79,"command":80},"pnpm","pnpm dlx skills add HenriqueMC17\u002Fagente-core --skill conducting-post-incident-lessons-learned","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fconducting-post-incident-lessons-learned\u002FSKILL.md",true,[84,90,95,101,105,109,115],{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"assets\u002Ftemplate.md","ASSET","资产文件",2199,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fconducting-post-incident-lessons-learned\u002Fassets\u002Ftemplate.md",{"path":91,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fconducting-post-incident-lessons-learned\u002FLICENSE",{"path":96,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fapi-reference.md","REFERENCE","参考文档",1535,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fconducting-post-incident-lessons-learned\u002Freferences\u002Fapi-reference.md",{"path":102,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fstandards.md",1208,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fconducting-post-incident-lessons-learned\u002Freferences\u002Fstandards.md",{"path":106,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fworkflows.md",1993,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fconducting-post-incident-lessons-learned\u002Freferences\u002Fworkflows.md",{"path":110,"resourceType":111,"resourceTypeDesc":112,"sizeBytes":113,"sourceHtmlUrl":114},"scripts\u002Fagent.py","SCRIPT","脚本",5815,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fconducting-post-incident-lessons-learned\u002Fscripts\u002Fagent.py",{"path":116,"resourceType":111,"resourceTypeDesc":112,"sizeBytes":117,"sourceHtmlUrl":118},"scripts\u002Fprocess.py",9431,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fconducting-post-incident-lessons-learned\u002Fscripts\u002Fprocess.py",[120,148,173,196,212,231],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":131,"publishedAt":39},"01M6HPFF0RCN0X6WT5EBSV71GY","validating-backup-integrity-for-recovery","Validate backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to ensure backups are reliable for disaster recovery and ransomware response scenarios.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[126],{"categoryNo":127,"categoryName":128,"taxonomyType":129,"taxonomyTypeDesc":130},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[132,133,134,135,136,137,38,138,139,140,45,141,142,35,143,144,145,23,146,147],"integrity","backup","recovery","validating backup integrity for recovery","for","testing","validate","verification","hash-verification","ransomware","detection","t1490","disaster-recovery","restore","disaster recovery","ransomware response",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":39},"01M6HPFAWJVFK25Q33K3T7WQ8G","triaging-vulnerabilities-with-ssvc-framework","Triage and prioritize vulnerabilities using CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree framework to produce actionable remediation priorities.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[],[155,156,157,158,159,38,160,161,162,163,164,165,166,167,168,169,170,171,28,172],"vulnerabilities","framework","ssvc","triaging vulnerabilities with ssvc framework","with","triage and prioritize","CISA","vulnerability-management","risk-management","cvss","remediation","vulnerability","prioritization","decision-tree","prioritize","decision","priorities","tree",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":179,"publishedAt":39},"01M6HPF6JS9X72WP59094H3ASQ","triaging-security-incident","Performs initial triage of security incidents to determine severity, scope, and required response actions using the NIST SP 800-61r3 and SANS PICERL frameworks. Classifies incidents by type, assigns priority based on business impact, and routes...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident\u002FSKILL.md",[],[180,181,23,38,182,183,184,35,143,185,186,187,188,189,190,191,192,193,194,195],"security","triaging security incident","actions","soc","NIST","analysis","severity-classification","incident-triage","SANS-PICERL","SOC-operations","picerl","conversion","isolation","scope","impact","consistency",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":202,"publishedAt":39},"01M6HPF2EX6ZYNYYHKBRJN7GEF","triaging-security-incident-with-ir-playbook","Classify and prioritize security incidents using structured IR playbooks to determine severity, assign response teams, and initiate appropriate response procedures.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident-with-ir-playbook\u002FSKILL.md",[],[180,203,204,181,23,159,38,205,183,45,206,207,35,143,208,186,169,209,210,211],"playbook","triaging security incident with ir playbook","teams","IR-playbook","severity","classification","classify","incidents","initiate",{"skillNo":213,"name":214,"nameZh":6,"description":215,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":216,"categories":217,"keywords":218,"publishedAt":39},"01M6HPEY9XPGE7X95AG4XJFQAW","triaging-security-alerts-in-splunk","Triages security alerts in Splunk Enterprise Security by classifying severity, investigating notable events, correlating related telemetry, and making escalation or closure decisions using SPL queries and the Incident Review dashboard. Use when...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-alerts-in-splunk\u002FSKILL.md",[],[180,219,220,221,222,30,38,223,224,225,183,226,35,33,227,228,189,229,23,230],"security alerts","splunk","triaging security alerts in splunk","alerts","siem","dashboard","search","correlation-search","notable-events","incident-review","cm","de",{"skillNo":232,"name":233,"nameZh":6,"description":234,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":235,"categories":236,"keywords":237,"publishedAt":39},"01M6HPET6XGEPEJPN7V032JGZ0","tracking-threat-actor-infrastructure","Threat actor infrastructure tracking involves monitoring and mapping adversary-controlled assets including command-and-control (C2) servers, phishing domains, exploit kit hosts, bulletproof hosting, a","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftracking-threat-actor-infrastructure\u002FSKILL.md",[],[238,239,240,241,38,242,243,244,245,246,247,33,248,249,229,250,230,251,252,253],"infrastructure","tracking threat actor infrastructure","tracking","threat","monitoring","mitre-attack","threat-actor","threat-intelligence","command-and-control","dns","command","exploit","intelligence","domains","kit","hosts"]