[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADZ4T9F4DX5KBQWS13BXEN":3,"skill-same:01M6ADZ4T9F4DX5KBQWS13BXEN":130},{"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":23,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":62,"repositoryHtmlUrl":63,"repositoryHomepageUrl":64,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":67,"updatedAt":68,"install":69,"resources":82},"01M6ADZ4T9F4DX5KBQWS13BXEN","building-malware-incident-communication-template",null,"Build structured communication templates for malware incidents (ransomware, wiper, trojan, worm), covering internal stakeholder notifications, executive briefings, technical advisories for IT teams, customer notifications, and regulatory disclosures, with severity-based escalation procedures. Use when drafting or standardizing incident communications and notification workflows for a malware outbreak.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",36078,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-malware-incident-communication-template\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"communication","malware","building malware incident communication template","cybersecurity","customer","workflows","teams","notifications","incident-response","ransomware","incident-communication","malware-response","stakeholder-notification","crisis-communication","executive-briefing","regulatory-disclosure","2026-11-10 10:12:30",false,"---\nname: building-malware-incident-communication-template\ndescription: Build structured communication templates for malware incidents (ransomware,\n  wiper, trojan, worm), covering internal stakeholder notifications, executive briefings,\n  technical advisories for IT teams, customer notifications, and regulatory disclosures,\n  with severity-based escalation procedures. Use when drafting or standardizing incident\n  communications and notification workflows for a malware outbreak.\ndomain: cybersecurity\nsubdomain: incident-response\ntags:\n- incident-communication\n- malware-response\n- stakeholder-notification\n- crisis-communication\n- executive-briefing\n- regulatory-disclosure\nmitre_attack:\n- T1486\n- T1490\n- T1657\n- T1041\n- T1566\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\n---\n\n# Building Malware Incident Communication Template\n\n## Overview\n\nEffective communication during malware incidents is critical for coordinated response, stakeholder management, and regulatory compliance. A structured communication framework ensures the right people receive appropriate information at the right time, preventing panic while maintaining transparency. Communication templates should cover internal escalation, executive briefings, technical advisories for IT teams, customer notifications, regulatory disclosures, and media statements. The framework must account for different malware types (ransomware, wiper, trojan, worm) and severity levels that drive escalation speed and audience.\n\n\n## When to Use\n\n- When deploying or configuring building malware incident communication template capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Familiarity with incident response concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Communication Framework\n\n### Severity Classification\n\n| Severity | Description | Notification Timeline | Audience |\n|----------|-------------|----------------------|----------|\n| P1 - Critical | Ransomware, wiper, or widespread infection affecting business operations | Within 15 minutes | CISO, CEO, Legal, Board (if applicable) |\n| P2 - High | Targeted malware on critical systems, data exfiltration suspected | Within 1 hour | CISO, IT Director, Legal |\n| P3 - Medium | Contained malware infection, limited spread | Within 4 hours | Security Manager, IT Director |\n| P4 - Low | Single endpoint infection, quickly contained | Within 24 hours | Security Team Lead |\n\n### Communication Channels\n\n| Channel | Use Case | Security Level |\n|---------|----------|---------------|\n| Out-of-band phone calls | Initial critical notifications | Highest |\n| Encrypted messaging (Signal) | Real-time IR team coordination | High |\n| Secure email (encrypted) | Formal notifications, documentation | High |\n| War room (physical\u002Fvirtual) | Ongoing incident coordination | Medium |\n| Incident ticketing system | Status tracking and documentation | Medium |\n| Company intranet | Broad employee communication | Standard |\n\n## Template 1: Initial Incident Notification (Internal)\n\n```\nSUBJECT: [SEVERITY] Malware Incident - Initial Notification - [DATE\u002FTIME UTC]\n\nCLASSIFICATION: CONFIDENTIAL - IR TEAM ONLY\n\nINCIDENT ID: IR-[YEAR]-[NUMBER]\nDETECTION TIME: [YYYY-MM-DD HH:MM UTC]\nNOTIFICATION TIME: [YYYY-MM-DD HH:MM UTC]\nSEVERITY: [P1\u002FP2\u002FP3\u002FP4]\n\nSUMMARY:\nA malware incident has been detected affecting [NUMBER] systems in\n[DEPARTMENT\u002FLOCATION]. The malware has been identified as [TYPE] with\n[KNOWN\u002FUNKNOWN] characteristics.\n\nCURRENT IMPACT:\n- Systems affected: [COUNT and DESCRIPTION]\n- Business functions impacted: [LIST]\n- Data at risk: [DESCRIPTION]\n- Current spread status: [CONTAINED\u002FSPREADING\u002FUNKNOWN]\n\nIMMEDIATE ACTIONS TAKEN:\n1. [ACTION - e.g., Affected endpoints isolated from network]\n2. [ACTION - e.g., EDR containment policies activated]\n3. [ACTION - e.g., Security team mobilized]\n\nNEXT STEPS:\n1. [PLANNED ACTION with TIMELINE]\n2. [PLANNED ACTION with TIMELINE]\n\nINCIDENT COMMANDER: [NAME]\nCONTACT: [PHONE\u002FENCRYPTED CHANNEL]\n\nNEXT UPDATE: [TIME] or sooner if situation changes\n\n---\nDo not forward this notification outside the IR team.\n```\n\n## Template 2: Executive Briefing\n\n```\nSUBJECT: Executive Briefing - Malware Incident IR-[YEAR]-[NUMBER]\n\nFOR: [CEO \u002F CISO \u002F CIO \u002F Board]\nFROM: [Incident Commander]\nDATE: [DATE]\nUPDATE: [#]\n\nSITUATION SUMMARY:\n[2-3 sentences describing the incident in business terms]\n\nBUSINESS IMPACT:\n- Revenue impact: [ESTIMATED\u002FNONE\u002FUNDER ASSESSMENT]\n- Operational impact: [DESCRIPTION]\n- Customer impact: [DESCRIPTION]\n- Regulatory implications: [DESCRIPTION]\n\nCURRENT STATUS: [DETECTED \u002F CONTAINED \u002F ERADICATING \u002F RECOVERING]\n\nKEY DECISIONS NEEDED:\n1. [DECISION with context and recommendation]\n2. [DECISION with context and recommendation]\n\nTIMELINE:\n- [TIME]: Incident detected\n- [TIME]: Containment initiated\n- [TIME]: [MILESTONE]\n- [TIME]: Estimated recovery (if known)\n\nEXTERNAL COMMUNICATION STATUS:\n- Regulatory notification: [REQUIRED\u002FSUBMITTED\u002FNOT REQUIRED]\n- Customer notification: [REQUIRED\u002FPLANNED\u002FNOT REQUIRED]\n- Law enforcement: [ENGAGED\u002FPLANNED\u002FNOT APPLICABLE]\n\nRESOURCE REQUIREMENTS:\n- [RESOURCE NEED - e.g., External IR firm engagement]\n- [RESOURCE NEED - e.g., Additional hardware for rebuild]\n\nNEXT UPDATE: [TIME]\n```\n\n## Template 3: Technical Advisory for IT Teams\n\n```\nSUBJECT: TECHNICAL ADVISORY - [MALWARE NAME] - Immediate Action Required\n\nSEVERITY: [CRITICAL\u002FHIGH\u002FMEDIUM]\nDATE: [DATE\u002FTIME UTC]\nADVISORY ID: TA-[YEAR]-[NUMBER]\n\nTHREAT DESCRIPTION:\n[Technical description of the malware, behavior, and indicators]\n\nAFFECTED SYSTEMS:\n- Operating Systems: [LIST]\n- Applications: [LIST]\n- Network segments: [LIST]\n\nINDICATORS OF COMPROMISE (IOCs):\nFile Hashes:\n  MD5: [HASH]\n  SHA256: [HASH]\n\nFile Names:\n  [FILENAME]\n\nNetwork Indicators:\n  C2 Domains: [DOMAIN]\n  C2 IPs: [IP ADDRESS]\n  User-Agent: [STRING]\n\nRegistry Keys:\n  [REGISTRY PATH]\n\nDETECTION METHODS:\n- EDR: [DETECTION RULE\u002FSIGNATURE]\n- SIEM: [CORRELATION RULE]\n- Network: [IDS\u002FIPS SIGNATURE]\n\nREQUIRED ACTIONS:\nPriority 1 (Immediate):\n  [ ] Block IOCs at firewall\u002Fproxy\n  [ ] Push EDR containment rules\n  [ ] Scan all endpoints for IOCs\n\nPriority 2 (Within 4 hours):\n  [ ] Apply patches [KB\u002FCVE NUMBER]\n  [ ] Update antivirus signatures\n  [ ] Review logs for historical indicators\n\nPriority 3 (Within 24 hours):\n  [ ] Conduct enterprise-wide hunt\n  [ ] Validate backup integrity\n  [ ] Update detection rules\n\nCONTACT: SOC - [PHONE] | Security Engineering - [PHONE]\n```\n\n## Template 4: Regulatory Notification\n\n```\n[ORGANIZATION LETTERHEAD]\n\n[REGULATORY BODY]\n[ADDRESS]\n\nDate: [DATE]\n\nRE: Data Security Incident Notification - [REFERENCE NUMBER]\n\nDear [TITLE\u002FNAME],\n\nPursuant to [REGULATION - e.g., GDPR Article 33, State Breach Notification Law],\n[ORGANIZATION] is providing notification of a data security incident.\n\nINCIDENT SUMMARY:\nOn [DATE], [ORGANIZATION] detected a malware incident affecting systems containing\n[TYPE OF DATA]. The incident was detected through [DETECTION METHOD].\n\nDATA POTENTIALLY AFFECTED:\n- Types of data: [PERSONAL DATA, FINANCIAL, HEALTH, etc.]\n- Number of individuals: [COUNT or ESTIMATE]\n- Categories of individuals: [CUSTOMERS, EMPLOYEES, etc.]\n\nTIMELINE:\n- [DATE]: Incident occurred (estimated)\n- [DATE]: Incident detected\n- [DATE]: Containment achieved\n- [DATE]: This notification\n\nMEASURES TAKEN:\n1. [CONTAINMENT ACTION]\n2. [INVESTIGATION ACTION]\n3. [REMEDIATION ACTION]\n\nMEASURES TO MITIGATE ADVERSE EFFECTS:\n1. [MITIGATION - e.g., Credit monitoring offered]\n2. [MITIGATION - e.g., Password resets enforced]\n\nCONTACT INFORMATION:\n[DPO\u002FPRIVACY OFFICER NAME]\n[TITLE]\n[EMAIL]\n[PHONE]\n\nRespectfully,\n[SIGNATORY]\n[TITLE]\n```\n\n## Template 5: Customer\u002FPublic Notification\n\n```\nSUBJECT: Important Security Notice from [ORGANIZATION]\n\nDear [CUSTOMER\u002FUSER],\n\nWe are writing to inform you of a security incident that may have affected\nyour information.\n\nWHAT HAPPENED:\nOn [DATE], we detected unauthorized activity on our systems involving\nmalicious software. We immediately activated our incident response procedures\nand engaged leading cybersecurity experts to investigate.\n\nWHAT INFORMATION WAS INVOLVED:\nBased on our investigation, the following types of information may have\nbeen affected: [LIST - e.g., names, email addresses, etc.]\n\nWHAT WE ARE DOING:\n- We have contained the incident and removed the malicious software\n- We have engaged [FORENSIC FIRM] to conduct a thorough investigation\n- We have enhanced our security controls to prevent similar incidents\n- We have notified relevant regulatory authorities\n\nWHAT YOU CAN DO:\n- Change your password for your [ORGANIZATION] account\n- Enable multi-factor authentication if not already active\n- Monitor your accounts for unusual activity\n- [Additional specific recommendations]\n\nADDITIONAL RESOURCES:\n- [DEDICATED SUPPORT LINE]\n- [FAQ PAGE URL]\n- [CREDIT MONITORING ENROLLMENT - if applicable]\n\nWe sincerely apologize for any concern this may cause and remain committed\nto protecting your information.\n\n[SIGNATORY]\n[TITLE]\n```\n\n## Communication Workflow\n\n### Escalation Matrix\n```\nMalware Detected\n  |\n  v\n[Classify Severity: P1\u002FP2\u002FP3\u002FP4]\n  |\n  |-- P1: Notify within 15 min\n  |     |-- Incident Commander\n  |     |-- CISO (phone call)\n  |     |-- CEO (phone call)\n  |     |-- Legal Counsel\n  |     |-- External IR firm\n  |     |-- Law enforcement (if applicable)\n  |\n  |-- P2: Notify within 1 hour\n  |     |-- CISO\n  |     |-- IT Director\n  |     |-- Legal Counsel\n  |\n  |-- P3: Notify within 4 hours\n  |     |-- Security Manager\n  |     |-- IT Director\n  |\n  |-- P4: Notify within 24 hours\n        |-- Security Team Lead\n```\n\n## References\n\n- NIST SP 800-61 Rev 2: Incident Communication Guidelines\n- GDPR Article 33: Data Breach Notification Requirements\n- SANS Incident Handler's Handbook: Communication Best Practices\n- CISA Incident Reporting Guidelines\n","# Building Malware Incident Communication Template\n\n## Overview\n\nEffective communication during malware incidents is critical for coordinated response, stakeholder management, and regulatory compliance. A structured communication framework ensures the right people receive appropriate information at the right time, preventing panic while maintaining transparency. Communication templates should cover internal escalation, executive briefings, technical advisories for IT teams, customer notifications, regulatory disclosures, and media statements. The framework must account for different malware types (ransomware, wiper, trojan, worm) and severity levels that drive escalation speed and audience.\n\n\n## When to Use\n\n- When deploying or configuring building malware incident communication template capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Familiarity with incident response concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Communication Framework\n\n### Severity Classification\n\n| Severity | Description | Notification Timeline | Audience |\n|----------|-------------|----------------------|----------|\n| P1 - Critical | Ransomware, wiper, or widespread infection affecting business operations | Within 15 minutes | CISO, CEO, Legal, Board (if applicable) |\n| P2 - High | Targeted malware on critical systems, data exfiltration suspected | Within 1 hour | CISO, IT Director, Legal |\n| P3 - Medium | Contained malware infection, limited spread | Within 4 hours | Security Manager, IT Director |\n| P4 - Low | Single endpoint infection, quickly contained | Within 24 hours | Security Team Lead |\n\n### Communication Channels\n\n| Channel | Use Case | Security Level |\n|---------|----------|---------------|\n| Out-of-band phone calls | Initial critical notifications | Highest |\n| Encrypted messaging (Signal) | Real-time IR team coordination | High |\n| Secure email (encrypted) | Formal notifications, documentation | High |\n| War room (physical\u002Fvirtual) | Ongoing incident coordination | Medium |\n| Incident ticketing system | Status tracking and documentation | Medium |\n| Company intranet | Broad employee communication | Standard |\n\n## Template 1: Initial Incident Notification (Internal)\n\n```\nSUBJECT: [SEVERITY] Malware Incident - Initial Notification - [DATE\u002FTIME UTC]\n\nCLASSIFICATION: CONFIDENTIAL - IR TEAM ONLY\n\nINCIDENT ID: IR-[YEAR]-[NUMBER]\nDETECTION TIME: [YYYY-MM-DD HH:MM UTC]\nNOTIFICATION TIME: [YYYY-MM-DD HH:MM UTC]\nSEVERITY: [P1\u002FP2\u002FP3\u002FP4]\n\nSUMMARY:\nA malware incident has been detected affecting [NUMBER] systems in\n[DEPARTMENT\u002FLOCATION]. The malware has been identified as [TYPE] with\n[KNOWN\u002FUNKNOWN] characteristics.\n\nCURRENT IMPACT:\n- Systems affected: [COUNT and DESCRIPTION]\n- Business functions impacted: [LIST]\n- Data at risk: [DESCRIPTION]\n- Current spread status: [CONTAINED\u002FSPREADING\u002FUNKNOWN]\n\nIMMEDIATE ACTIONS TAKEN:\n1. [ACTION - e.g., Affected endpoints isolated from network]\n2. [ACTION - e.g., EDR containment policies activated]\n3. [ACTION - e.g., Security team mobilized]\n\nNEXT STEPS:\n1. [PLANNED ACTION with TIMELINE]\n2. [PLANNED ACTION with TIMELINE]\n\nINCIDENT COMMANDER: [NAME]\nCONTACT: [PHONE\u002FENCRYPTED CHANNEL]\n\nNEXT UPDATE: [TIME] or sooner if situation changes\n\n---\nDo not forward this notification outside the IR team.\n```\n\n## Template 2: Executive Briefing\n\n```\nSUBJECT: Executive Briefing - Malware Incident IR-[YEAR]-[NUMBER]\n\nFOR: [CEO \u002F CISO \u002F CIO \u002F Board]\nFROM: [Incident Commander]\nDATE: [DATE]\nUPDATE: [#]\n\nSITUATION SUMMARY:\n[2-3 sentences describing the incident in business terms]\n\nBUSINESS IMPACT:\n- Revenue impact: [ESTIMATED\u002FNONE\u002FUNDER ASSESSMENT]\n- Operational impact: [DESCRIPTION]\n- Customer impact: [DESCRIPTION]\n- Regulatory implications: [DESCRIPTION]\n\nCURRENT STATUS: [DETECTED \u002F CONTAINED \u002F ERADICATING \u002F RECOVERING]\n\nKEY DECISIONS NEEDED:\n1. [DECISION with context and recommendation]\n2. [DECISION with context and recommendation]\n\nTIMELINE:\n- [TIME]: Incident detected\n- [TIME]: Containment initiated\n- [TIME]: [MILESTONE]\n- [TIME]: Estimated recovery (if known)\n\nEXTERNAL COMMUNICATION STATUS:\n- Regulatory notification: [REQUIRED\u002FSUBMITTED\u002FNOT REQUIRED]\n- Customer notification: [REQUIRED\u002FPLANNED\u002FNOT REQUIRED]\n- Law enforcement: [ENGAGED\u002FPLANNED\u002FNOT APPLICABLE]\n\nRESOURCE REQUIREMENTS:\n- [RESOURCE NEED - e.g., External IR firm engagement]\n- [RESOURCE NEED - e.g., Additional hardware for rebuild]\n\nNEXT UPDATE: [TIME]\n```\n\n## Template 3: Technical Advisory for IT Teams\n\n```\nSUBJECT: TECHNICAL ADVISORY - [MALWARE NAME] - Immediate Action Required\n\nSEVERITY: [CRITICAL\u002FHIGH\u002FMEDIUM]\nDATE: [DATE\u002FTIME UTC]\nADVISORY ID: TA-[YEAR]-[NUMBER]\n\nTHREAT DESCRIPTION:\n[Technical description of the malware, behavior, and indicators]\n\nAFFECTED SYSTEMS:\n- Operating Systems: [LIST]\n- Applications: [LIST]\n- Network segments: [LIST]\n\nINDICATORS OF COMPROMISE (IOCs):\nFile Hashes:\n  MD5: [HASH]\n  SHA256: [HASH]\n\nFile Names:\n  [FILENAME]\n\nNetwork Indicators:\n  C2 Domains: [DOMAIN]\n  C2 IPs: [IP ADDRESS]\n  User-Agent: [STRING]\n\nRegistry Keys:\n  [REGISTRY PATH]\n\nDETECTION METHODS:\n- EDR: [DETECTION RULE\u002FSIGNATURE]\n- SIEM: [CORRELATION RULE]\n- Network: [IDS\u002FIPS SIGNATURE]\n\nREQUIRED ACTIONS:\nPriority 1 (Immediate):\n  [ ] Block IOCs at firewall\u002Fproxy\n  [ ] Push EDR containment rules\n  [ ] Scan all endpoints for IOCs\n\nPriority 2 (Within 4 hours):\n  [ ] Apply patches [KB\u002FCVE NUMBER]\n  [ ] Update antivirus signatures\n  [ ] Review logs for historical indicators\n\nPriority 3 (Within 24 hours):\n  [ ] Conduct enterprise-wide hunt\n  [ ] Validate backup integrity\n  [ ] Update detection rules\n\nCONTACT: SOC - [PHONE] | Security Engineering - [PHONE]\n```\n\n## Template 4: Regulatory Notification\n\n```\n[ORGANIZATION LETTERHEAD]\n\n[REGULATORY BODY]\n[ADDRESS]\n\nDate: [DATE]\n\nRE: Data Security Incident Notification - [REFERENCE NUMBER]\n\nDear [TITLE\u002FNAME],\n\nPursuant to [REGULATION - e.g., GDPR Article 33, State Breach Notification Law],\n[ORGANIZATION] is providing notification of a data security incident.\n\nINCIDENT SUMMARY:\nOn [DATE], [ORGANIZATION] detected a malware incident affecting systems containing\n[TYPE OF DATA]. The incident was detected through [DETECTION METHOD].\n\nDATA POTENTIALLY AFFECTED:\n- Types of data: [PERSONAL DATA, FINANCIAL, HEALTH, etc.]\n- Number of individuals: [COUNT or ESTIMATE]\n- Categories of individuals: [CUSTOMERS, EMPLOYEES, etc.]\n\nTIMELINE:\n- [DATE]: Incident occurred (estimated)\n- [DATE]: Incident detected\n- [DATE]: Containment achieved\n- [DATE]: This notification\n\nMEASURES TAKEN:\n1. [CONTAINMENT ACTION]\n2. [INVESTIGATION ACTION]\n3. [REMEDIATION ACTION]\n\nMEASURES TO MITIGATE ADVERSE EFFECTS:\n1. [MITIGATION - e.g., Credit monitoring offered]\n2. [MITIGATION - e.g., Password resets enforced]\n\nCONTACT INFORMATION:\n[DPO\u002FPRIVACY OFFICER NAME]\n[TITLE]\n[EMAIL]\n[PHONE]\n\nRespectfully,\n[SIGNATORY]\n[TITLE]\n```\n\n## Template 5: Customer\u002FPublic Notification\n\n```\nSUBJECT: Important Security Notice from [ORGANIZATION]\n\nDear [CUSTOMER\u002FUSER],\n\nWe are writing to inform you of a security incident that may have affected\nyour information.\n\nWHAT HAPPENED:\nOn [DATE], we detected unauthorized activity on our systems involving\nmalicious software. We immediately activated our incident response procedures\nand engaged leading cybersecurity experts to investigate.\n\nWHAT INFORMATION WAS INVOLVED:\nBased on our investigation, the following types of information may have\nbeen affected: [LIST - e.g., names, email addresses, etc.]\n\nWHAT WE ARE DOING:\n- We have contained the incident and removed the malicious software\n- We have engaged [FORENSIC FIRM] to conduct a thorough investigation\n- We have enhanced our security controls to prevent similar incidents\n- We have notified relevant regulatory authorities\n\nWHAT YOU CAN DO:\n- Change your password for your [ORGANIZATION] account\n- Enable multi-factor authentication if not already active\n- Monitor your accounts for unusual activity\n- [Additional specific recommendations]\n\nADDITIONAL RESOURCES:\n- [DEDICATED SUPPORT LINE]\n- [FAQ PAGE URL]\n- [CREDIT MONITORING ENROLLMENT - if applicable]\n\nWe sincerely apologize for any concern this may cause and remain committed\nto protecting your information.\n\n[SIGNATORY]\n[TITLE]\n```\n\n## Communication Workflow\n\n### Escalation Matrix\n```\nMalware Detected\n  |\n  v\n[Classify Severity: P1\u002FP2\u002FP3\u002FP4]\n  |\n  |-- P1: Notify within 15 min\n  |     |-- Incident Commander\n  |     |-- CISO (phone call)\n  |     |-- CEO (phone call)\n  |     |-- Legal Counsel\n  |     |-- External IR firm\n  |     |-- Law enforcement (if applicable)\n  |\n  |-- P2: Notify within 1 hour\n  |     |-- CISO\n  |     |-- IT Director\n  |     |-- Legal Counsel\n  |\n  |-- P3: Notify within 4 hours\n  |     |-- Security Manager\n  |     |-- IT Director\n  |\n  |-- P4: Notify within 24 hours\n        |-- Security Team Lead\n```\n\n## References\n\n- NIST SP 800-61 Rev 2: Incident Communication Guidelines\n- GDPR Article 33: Data Breach Notification Requirements\n- SANS Incident Handler's Handbook: Communication Best Practices\n- CISA Incident Reporting Guidelines\n",{"name":5,"tags":45,"author":46,"domain":27,"license":15,"version":47,"nist_csf":48,"subdomain":32,"description":7,"mitre_attack":53},[34,35,36,37,38,39],"mahipal","1.0",[49,50,51,52],"RS.MA-01","RS.MA-02","RS.AN-03","RC.RP-01",[54,55,56,57,58],"T1486","T1490","T1657","T1041","T1566","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fbuilding-malware-incident-communication-template",4414,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","https:\u002F\u002Fmahipal.engineer\u002FAnthropic-Cybersecurity-Skills\u002F","https:\u002F\u002Fgithub.com\u002Fmukul975","Mahipal.engineer","🔐 Cybersecurity | 💻 Dev | 📷 Street Photographer\r\n🎓 MSc | 📚 Research & AI Security","2026-08-31 12:32:44",{"source":8,"skillName":5,"commands":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill building-malware-incident-communication-template",{"tool":75,"command":76},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill building-malware-incident-communication-template",{"tool":78,"command":79},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill building-malware-incident-communication-template","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-malware-incident-communication-template\u002FSKILL.md",true,[83,89,93,98,104,108,112,116,122,126],{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"assets\u002Fexample_asset.txt","ASSET","资产文件",865,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fquality-documentation-manager\u002Fassets\u002Fexample_asset.txt",{"path":90,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":91,"sourceHtmlUrl":92},"assets\u002Ftemplate.md",1354,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-malware-incident-communication-template\u002Fassets\u002Ftemplate.md",{"path":94,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-malware-incident-communication-template\u002FLICENSE",{"path":99,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fapi_reference.md","REFERENCE","参考文档",980,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fquality-documentation-manager\u002Freferences\u002Fapi_reference.md",{"path":105,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Fapi-reference.md",2204,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-malware-incident-communication-template\u002Freferences\u002Fapi-reference.md",{"path":109,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":110,"sourceHtmlUrl":111},"references\u002Fstandards.md",1204,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-malware-incident-communication-template\u002Freferences\u002Fstandards.md",{"path":113,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":114,"sourceHtmlUrl":115},"references\u002Fworkflows.md",2388,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-malware-incident-communication-template\u002Freferences\u002Fworkflows.md",{"path":117,"resourceType":118,"resourceTypeDesc":119,"sizeBytes":120,"sourceHtmlUrl":121},"scripts\u002Fagent.py","SCRIPT","脚本",8774,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-malware-incident-communication-template\u002Fscripts\u002Fagent.py",{"path":123,"resourceType":118,"resourceTypeDesc":119,"sizeBytes":124,"sourceHtmlUrl":125},"scripts\u002Fexample.py",617,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fquality-documentation-manager\u002Fscripts\u002Fexample.py",{"path":127,"resourceType":118,"resourceTypeDesc":119,"sizeBytes":128,"sourceHtmlUrl":129},"scripts\u002Fprocess.py",10488,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-malware-incident-communication-template\u002Fscripts\u002Fprocess.py",[131,158,182,208,234,261],{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":138,"publishedAt":40},"01M6AGDM3HJXTKXX15ZZ0ZVCJ3","verifying-build-provenance-with-slsa-sigstore","Verifies artifact signatures and SLSA provenance using Sigstore's cosign (verify, verify-attestation, verify-blob-attestation) and slsa-verifier (verify-artifact), enforcing keyless OIDC builder identity and source repo against SLSA Build levels. Use in CI\u002FCD before deploying artifacts, when consuming third-party attestations, establishing a SLSA Build L3 pipeline, or confirming provenance during incident response or admission control.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fverifying-build-provenance-with-slsa-sigstore\u002FSKILL.md",[137],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[139,140,141,142,143,27,144,145,146,147,148,149,150,151,152,153,154,155,156,157],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","security","incident response","identity","pr","code","artifacts","ci","supply-chain","pipeline","supply-chain-security","t1195","attestation","code-signing","cosign","keyless",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":165,"publishedAt":40},"01M6AGDGBPWYVZ2F11GFKJ4HZ9","validating-tpm-measured-boot-attestation","Verifies TPM 2.0 measured-boot integrity and remote attestation with tpm2-tools -- reading PCRs (tpm2_pcrread), replaying the boot event log, generating and checking signed quotes (tpm2_quote\u002Ftpm2_checkquote), and sealing secrets to a PCR policy. Use to confirm a system booted trusted firmware\u002Fkernel for Zero Trust device posture, detect boot-chain tampering via PCR drift, or build a golden-value baseline for fleet attestation.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-tpm-measured-boot-attestation\u002FSKILL.md",[164],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[166,154,167,168,143,169,27,146,170,171,172,173,174,175,176,177,178,179,180,181],"boot","TPM","validating tpm measured boot attestation","policy","verification","ZeRO","firmware","Tools","measured-boot","PCR","integrity","secrets","remote-attestation","tpm2-tools","integrity-verification","trusted-computing",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":192,"publishedAt":40},"01M6AGDCW0Y4FXZ3362GT1941M","validating-backup-integrity-for-recovery","Validates backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to confirm backups are reliable for disaster recovery and ransomware response. Use before relying on backups for recovery, when building post-backup validation pipelines, auditing backup infrastructure for compliance, or checking immutable\u002Fair-gapped backups for silent corruption or tampering.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[188,191],{"categoryNo":189,"categoryName":190,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[176,193,194,195,196,27,197,198,170,199,200,32,33,201,202,203,204,205,206,207],"backup","recovery","validating backup integrity for recovery","testing","infrastructure","validation","compliance","hash-verification","cryptocurrency","detection","t1078","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":212,"categories":213,"keywords":215,"publishedAt":40},"01M6AGD9GBG2KZ336AE763J3WH","triaging-windows-with-kape","Runs KAPE (Kroll Artifact Parser and Extractor) to collect targeted forensic artifacts (registry hives, $MFT, event logs, prefetch, browser data) via Targets and parse them with Modules wrapping Eric Zimmerman's EZ Tools (PECmd, MFTECmd, RECmd). Use during early incident containment\u002Ftriage when full disk imaging is impractical but a defensible, parseable Windows artifact set is needed quickly, including at-scale remote collection.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-windows-with-kape\u002FSKILL.md",[214],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[216,217,218,27,219,220,221,222,223,224,225,226,227,228,229,230,173,231,232,233],"windows","kape","triaging windows with kape","registry","browser","logs","windows-forensics","dfir","mft","mftecmd","data","prefetch","eric-zimmerman","digital-forensics","SET","collection","pecmd","artifact-collection",{"skillNo":235,"name":236,"nameZh":6,"description":237,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":238,"categories":239,"keywords":241,"publishedAt":40},"01M6AGD5PW5J4EVZM958WD74ZQ","triaging-vulnerabilities-with-ssvc-framework","Triages and prioritizes vulnerabilities with CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree, weighing exploitation status (via the CISA KEV catalog and FIRST EPSS API), technical impact, automatability, and mission prevalence to output Track\u002FTrack*\u002FAttend\u002FAct decisions. Use when prioritizing vulnerability scan results (OpenVAS, Nessus, Qualys) for remediation planning beyond raw CVSS scores.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[240],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[242,243,244,27,245,246,247,248,249,250,251,252,253,254,255,256,257,258,259,260],"vulnerabilities","framework","triaging vulnerabilities with ssvc framework","status","planning","CISA","vulnerability-management","risk-management","nessus","qualys","openvas","cvss","remediation","risk","vulnerability","api","prioritization","ssvc","decision-tree",{"skillNo":262,"name":263,"nameZh":6,"description":264,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":265,"categories":266,"keywords":268,"publishedAt":40},"01M6AGD24TTQQM4CXG69E3B9TJ","triaging-security-incident","Performs initial triage of security incidents using the NIST SP 800-61r3 and SANS PICERL frameworks, classifying incident type, assigning priority by business impact, and routing to the appropriate response team. Use when a SIEM\u002FEDR alert needs human classification, concurrent alerts must be prioritized, or a user report or threat-intel IOC match requires initial incident categorization.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-security-incident\u002FSKILL.md",[267],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[143,269,27,270,271,272,273,274,275,276,277,203,278,204,279,280,281,282,283,284],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]