[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D72TCFZYYVTZFKS9SAVABF":3,"skill-same:01M7D72TCFZYYVTZFKS9SAVABF":114},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":75,"commitSha":76,"skillDirectory":77,"forksCount":78,"repositoryHtmlUrl":79,"repositoryHomepageUrl":6,"ownerHtmlUrl":80,"ownerBlogUrl":81,"ownerDescription":82,"updatedAt":83,"install":84,"resources":97},"01M7D72TCFZYYVTZFKS9SAVABF","building-soc-playbook-for-ransomware",null,"Builds a structured SOC incident response playbook for ransomware attacks covering detection, containment, eradication, and recovery phases with specific SIEM queries, isolation procedures, and decision trees. Use when SOC teams need formalized response procedures for ransomware incidents aligned to NIST SP 800-61 and MITRE ATT&CK ransomware techniques.","SaiVatsal\u002FSkills-I-Use","SaiVatsal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F242597752?v=4","01M7D5YM1T4VXW9203M0GFAHZ1","SaiVatsalPolimera","01M7D5YM2D61ST39XVR2V7B7ZJ",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fbuilding-soc-playbook-for-ransomware\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fbuilding-soc-playbook-for-ransomware\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: building-soc-playbook-for-ransomware\ndescription: 'Builds a structured SOC incident response playbook for ransomware attacks\n  covering detection, containment, eradication, and recovery phases with specific\n  SIEM queries, isolation procedures, and decision trees. Use when SOC teams need\n  formalized response procedures for ransomware incidents aligned to NIST SP 800-61\n  and MITRE ATT&CK ransomware techniques.\n\n  '\ndomain: cybersecurity\nsubdomain: soc-operations\ntags:\n- soc\n- ransomware\n- incident-response\n- playbook\n- nist\n- mitre-attack\n- containment\nmitre_attack:\n- T1486\n- T1490\n- T1489\n- T1566\n- T1059.001\nmitre_f3:\n  version: '1.1'\n  tactics:\n  - initial-access\n  - monetization\n  techniques:\n  - id: T1660\n    name: Phishing\n    tactic: initial-access\n    source: attack\n  - id: T1110\n    name: Brute Force\n    tactic: initial-access\n    source: attack\n  - id: F1018\n    name: Convert to Cryptocurrency\n    tactic: monetization\n    source: f3\n  - id: F1047\n    name: Transfer of funds\n    tactic: monetization\n    source: f3\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nd3fend_techniques:\n- Platform Hardening\n- Restore Object\n- Restore Configuration\n- Restore Software\n- Software Update\nnist_csf:\n- DE.CM-01\n- DE.AE-02\n- RS.MA-01\n- DE.AE-06\n---\n# Building SOC Playbook for Ransomware\n\n## When to Use\n\nUse this skill when:\n- SOC teams need a standardized ransomware response playbook for Tier 1-3 analysts\n- An organization lacks documented procedures for ransomware containment and recovery\n- Tabletop exercises reveal gaps in ransomware response coordination\n- Compliance requirements (NIST CSF, ISO 27001) mandate documented incident playbooks\n\n**Do not use** during an active ransomware incident as the sole guide — have pre-built playbooks tested and rehearsed before incidents occur.\n\n## Prerequisites\n\n- SIEM platform (Splunk ES, Elastic Security, or Sentinel) with endpoint and network data\n- EDR solution (CrowdStrike, SentinelOne, or Microsoft Defender for Endpoint) with network isolation capability\n- Backup infrastructure with tested recovery procedures and offline\u002Fimmutable backups\n- Communication plan with legal, executive leadership, and external IR retainer contacts\n- MITRE ATT&CK knowledge for ransomware technique chains\n\n## Workflow\n\n### Step 1: Define Detection Triggers\n\nCreate SIEM detection rules for early ransomware indicators:\n\n**Mass File Encryption Detection (Splunk):**\n```spl\nindex=sysmon EventCode=11\n| bin _time span=1m\n| stats dc(TargetFilename) AS unique_files, values(TargetFilename) AS sample_files by Computer, Image, _time\n| where unique_files > 100\n| eval suspicious_extensions = if(match(mvjoin(sample_files, \",\"), \"\\.(encrypted|locked|crypt|enc|ransom)\"), \"YES\", \"NO\")\n| where suspicious_extensions=\"YES\" OR unique_files > 500\n| sort - unique_files\n```\n\n**Shadow Copy Deletion (T1490):**\n```spl\nindex=wineventlog sourcetype=\"WinEventLog:Security\" OR index=sysmon EventCode=1\n(CommandLine=\"*vssadmin*delete*shadows*\" OR CommandLine=\"*wmic*shadowcopy*delete*\"\n OR CommandLine=\"*bcdedit*\u002Fset*recoveryenabled*no*\" OR CommandLine=\"*wbadmin*delete*catalog*\")\n| table _time, Computer, User, ParentImage, Image, CommandLine\n```\n\n**Ransomware Note File Creation:**\n```spl\nindex=sysmon EventCode=11\nTargetFilename IN (\"*README*.txt\", \"*DECRYPT*.txt\", \"*RANSOM*.txt\", \"*RECOVER*.html\", \"*HOW_TO*.txt\")\n| stats count by Computer, Image, TargetFilename\n| where count > 5\n```\n\n**Elastic Security EQL variant:**\n```eql\nsequence by host.name with maxspan=2m\n  [process where event.type == \"start\" and\n    process.args : (\"*vssadmin*\", \"*delete*\", \"*shadows*\")]\n  [file where event.type == \"creation\" and\n    file.name : (\"*README*DECRYPT*\", \"*RANSOM*\", \"*HOW_TO_RECOVER*\")]\n```\n\n### Step 2: Build Triage Decision Tree\n\n```\nRANSOMWARE ALERT TRIAGE\n│\n├── Is encryption actively occurring?\n│   ├── YES → IMMEDIATE: Isolate host from network (Step 3)\n│   │         Do NOT power off (preserve memory for forensics)\n│   └── NO → Is this a pre-encryption indicator?\n│       ├── Shadow copy deletion → HIGH PRIORITY: Isolate and investigate\n│       ├── Known ransomware hash → HIGH PRIORITY: Block hash, scan enterprise\n│       └── Suspicious process behavior → MEDIUM: Investigate, prepare isolation\n│\n├── How many hosts affected?\n│   ├── Single host → Contained incident, follow host isolation procedure\n│   ├── Multiple hosts (2-10) → Escalate to Tier 2, begin enterprise-wide scan\n│   └── Enterprise-wide (>10) → Activate full IR team, engage external retainer\n│\n└── Is data exfiltration confirmed?\n    ├── YES → Double extortion scenario, engage legal for breach notification\n    └── NO\u002FUNKNOWN → Check for Cobalt Strike\u002FC2 beacons, review outbound transfers\n```\n\n### Step 3: Containment Procedures\n\n**Network Isolation via EDR (CrowdStrike Falcon):**\n```bash\n# Isolate host using CrowdStrike Falcon API\ncurl -X POST \"https:\u002F\u002Fapi.crowdstrike.com\u002Fdevices\u002Fentities\u002Fdevices-actions\u002Fv2?action_name=contain\" \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"ids\": [\"device_id_here\"]}'\n```\n\n**Network Isolation via Microsoft Defender for Endpoint:**\n```powershell\n# Isolate machine via MDE API\n$headers = @{Authorization = \"Bearer $token\"}\n$body = @{Comment = \"Ransomware containment - IR-2024-0500\"; IsolationType = \"Full\"} | ConvertTo-Json\nInvoke-RestMethod -Uri \"https:\u002F\u002Fapi.securitycenter.microsoft.com\u002Fapi\u002Fmachines\u002F$machineId\u002Fisolate\" `\n    -Method Post -Headers $headers -Body $body -ContentType \"application\u002Fjson\"\n```\n\n**Firewall Emergency Rules:**\n```\n# Palo Alto — Block SMB lateral spread\nset rulebase security rules RansomwareContainment from Trust to Trust\nset rulebase security rules RansomwareContainment application ms-ds-smb\nset rulebase security rules RansomwareContainment action deny\nset rulebase security rules RansomwareContainment disabled no\ncommit\n```\n\n**Active Directory Emergency Actions:**\n```powershell\n# Disable compromised account\nDisable-ADAccount -Identity \"compromised_user\"\n\n# Reset Kerberos TGT (if domain admin compromised)\n# WARNING: This resets krbtgt and requires two resets 12+ hours apart\nReset-KrbtgtKeys -Server \"DC-PRIMARY\" -Force\n\n# Block lateral movement by disabling remote services\nSet-Service -Name \"RemoteRegistry\" -StartupType Disabled -Status Stopped\n```\n\n### Step 4: Evidence Collection and Preservation\n\nCollect forensic artifacts before remediation:\n\n```powershell\n# Capture running processes and network connections\nGet-Process | Export-Csv \"C:\\IR\\processes_$(hostname).csv\"\nGet-NetTCPConnection | Export-Csv \"C:\\IR\\netstat_$(hostname).csv\"\n\n# Capture memory dump (if host still running)\nwinpmem_mini_x64.exe C:\\IR\\memory_$(hostname).raw\n\n# Collect ransomware artifacts\nCopy-Item \"C:\\Users\\*\\Desktop\\*README*\" \"C:\\IR\\ransom_notes\\\" -Recurse\nCopy-Item \"C:\\Users\\*\\Desktop\\*.encrypted\" \"C:\\IR\\encrypted_samples\\\" -Force\n\n# Capture event logs\nwevtutil epl Security \"C:\\IR\\Security_$(hostname).evtx\"\nwevtutil epl System \"C:\\IR\\System_$(hostname).evtx\"\nwevtutil epl \"Microsoft-Windows-Sysmon\u002FOperational\" \"C:\\IR\\Sysmon_$(hostname).evtx\"\n```\n\n### Step 5: Eradication and Recovery\n\n**Identify ransomware variant:**\n- Upload encrypted sample and ransom note to ID Ransomware (https:\u002F\u002Fid-ransomware.malwarehunterteam.com\u002F)\n- Check No More Ransom Project (https:\u002F\u002Fwww.nomoreransom.org\u002F) for available decryptors\n- Search for ransomware family IOCs in MalwareBazaar\n\n**Enterprise-wide IOC scan in Splunk:**\n```spl\nindex=sysmon (EventCode=1 OR EventCode=11 OR EventCode=3)\n(TargetFilename=\"*ransomware_binary_name*\" OR sha256=\"KNOWN_HASH\"\n OR DestinationIp=\"C2_IP_ADDRESS\" OR CommandLine=\"*malicious_command*\")\n| stats count by Computer, EventCode, Image, CommandLine\n| sort - count\n```\n\n**Recovery from backups:**\n1. Verify backup integrity (offline\u002Fimmutable backups not affected)\n2. Rebuild affected systems from known-good images\n3. Restore data from last clean backup\n4. Validate restored systems before reconnecting to network\n5. Monitor restored systems for 72 hours for reinfection\n\n### Step 6: Post-Incident Documentation\n\nStructure the playbook conclusion with lessons learned:\n\n```\nPOST-INCIDENT REVIEW TEMPLATE\n1. Timeline of events (detection to full recovery)\n2. Initial access vector identification\n3. Dwell time analysis (time from initial compromise to encryption)\n4. Detection gaps identified\n5. Response effectiveness metrics (MTTD, MTTC, MTTR)\n6. Playbook improvements recommended\n7. New detection rules deployed\n8. Backup and recovery procedure updates\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **Double Extortion** | Ransomware tactic combining data encryption with data theft, threatening public release if ransom unpaid |\n| **Dwell Time** | Duration between initial compromise and detection — ransomware operators average 5-9 days before encryption |\n| **MTTC** | Mean Time to Contain — time from detection to successful isolation of affected systems |\n| **Kill Chain** | Ransomware progression: Initial Access -> Execution -> Persistence -> Privilege Escalation -> Lateral Movement -> Collection -> Exfiltration -> Impact |\n| **Immutable Backup** | Backup storage that cannot be modified or deleted for a defined retention period (WORM storage) |\n| **RTO\u002FRPO** | Recovery Time Objective \u002F Recovery Point Objective — maximum acceptable downtime and data loss thresholds |\n\n## Tools & Systems\n\n- **CrowdStrike Falcon \u002F SentinelOne**: EDR platforms with network isolation, process kill, and threat hunting capabilities\n- **Splunk ES \u002F Elastic Security**: SIEM platforms for detection rule deployment and enterprise-wide IOC scanning\n- **ID Ransomware**: Online service identifying ransomware variants from encrypted file samples and ransom notes\n- **No More Ransom Project**: Europol-backed initiative providing free decryption tools for known ransomware families\n- **Veeam \u002F Rubrik**: Enterprise backup solutions with immutable backup support and instant recovery capabilities\n\n## Common Scenarios\n\n- **LockBit Attack**: Detected via SMB lateral movement and mass file encryption — isolate, scan for Cobalt Strike beacons\n- **BlackCat\u002FALPHV**: Detected via ransomware note creation — check for data exfiltration via Rclone or Mega upload\n- **Conti\u002FRoyal**: Detected via shadow copy deletion — check for prior BazarLoader\u002FEmotet initial access\n- **RansomHub**: Detected via anomalous process execution — investigate for compromised VPN or RDP credentials\n- **Play Ransomware**: Detected via service account abuse — audit AD for newly created accounts and group membership changes\n\n## Output Format\n\n```\nRANSOMWARE PLAYBOOK EXECUTION — IR-2024-0500\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nPhase 1 - Detection:\n  Alert:      Mass file encryption detected on FILESERVER-03\n  Variant:    LockBit 3.0 (confirmed via ID Ransomware)\n  MTTD:       12 minutes from first encryption to SOC alert\n\nPhase 2 - Containment:\n  [DONE] FILESERVER-03 isolated via CrowdStrike at 14:35 UTC\n  [DONE] SMB blocked enterprise-wide via firewall emergency rule\n  [DONE] Compromised service account disabled in AD\n  MTTC:       23 minutes\n\nPhase 3 - Eradication:\n  [DONE] 3 additional hosts with C2 beacon identified and isolated\n  [DONE] Cobalt Strike C2 domain (c2[.]evil[.]com) sinkholed\n  [DONE] Enterprise-wide IOC scan completed — no additional infections\n\nPhase 4 - Recovery:\n  [DONE] FILESERVER-03 rebuilt from gold image\n  [DONE] Data restored from immutable Veeam backup (RPO: 4 hours)\n  [DONE] Systems monitored 72 hours — no reinfection\n  MTTR:       18 hours\n\nTotal Affected: 1 server, 3 workstations\nData Loss:      4 hours of file modifications (backup RPO)\nExfiltration:   No evidence of data exfiltration confirmed\n```\n","# Building SOC Playbook for Ransomware\n\n## When to Use\n\nUse this skill when:\n- SOC teams need a standardized ransomware response playbook for Tier 1-3 analysts\n- An organization lacks documented procedures for ransomware containment and recovery\n- Tabletop exercises reveal gaps in ransomware response coordination\n- Compliance requirements (NIST CSF, ISO 27001) mandate documented incident playbooks\n\n**Do not use** during an active ransomware incident as the sole guide — have pre-built playbooks tested and rehearsed before incidents occur.\n\n## Prerequisites\n\n- SIEM platform (Splunk ES, Elastic Security, or Sentinel) with endpoint and network data\n- EDR solution (CrowdStrike, SentinelOne, or Microsoft Defender for Endpoint) with network isolation capability\n- Backup infrastructure with tested recovery procedures and offline\u002Fimmutable backups\n- Communication plan with legal, executive leadership, and external IR retainer contacts\n- MITRE ATT&CK knowledge for ransomware technique chains\n\n## Workflow\n\n### Step 1: Define Detection Triggers\n\nCreate SIEM detection rules for early ransomware indicators:\n\n**Mass File Encryption Detection (Splunk):**\n```spl\nindex=sysmon EventCode=11\n| bin _time span=1m\n| stats dc(TargetFilename) AS unique_files, values(TargetFilename) AS sample_files by Computer, Image, _time\n| where unique_files > 100\n| eval suspicious_extensions = if(match(mvjoin(sample_files, \",\"), \"\\.(encrypted|locked|crypt|enc|ransom)\"), \"YES\", \"NO\")\n| where suspicious_extensions=\"YES\" OR unique_files > 500\n| sort - unique_files\n```\n\n**Shadow Copy Deletion (T1490):**\n```spl\nindex=wineventlog sourcetype=\"WinEventLog:Security\" OR index=sysmon EventCode=1\n(CommandLine=\"*vssadmin*delete*shadows*\" OR CommandLine=\"*wmic*shadowcopy*delete*\"\n OR CommandLine=\"*bcdedit*\u002Fset*recoveryenabled*no*\" OR CommandLine=\"*wbadmin*delete*catalog*\")\n| table _time, Computer, User, ParentImage, Image, CommandLine\n```\n\n**Ransomware Note File Creation:**\n```spl\nindex=sysmon EventCode=11\nTargetFilename IN (\"*README*.txt\", \"*DECRYPT*.txt\", \"*RANSOM*.txt\", \"*RECOVER*.html\", \"*HOW_TO*.txt\")\n| stats count by Computer, Image, TargetFilename\n| where count > 5\n```\n\n**Elastic Security EQL variant:**\n```eql\nsequence by host.name with maxspan=2m\n  [process where event.type == \"start\" and\n    process.args : (\"*vssadmin*\", \"*delete*\", \"*shadows*\")]\n  [file where event.type == \"creation\" and\n    file.name : (\"*README*DECRYPT*\", \"*RANSOM*\", \"*HOW_TO_RECOVER*\")]\n```\n\n### Step 2: Build Triage Decision Tree\n\n```\nRANSOMWARE ALERT TRIAGE\n│\n├── Is encryption actively occurring?\n│   ├── YES → IMMEDIATE: Isolate host from network (Step 3)\n│   │         Do NOT power off (preserve memory for forensics)\n│   └── NO → Is this a pre-encryption indicator?\n│       ├── Shadow copy deletion → HIGH PRIORITY: Isolate and investigate\n│       ├── Known ransomware hash → HIGH PRIORITY: Block hash, scan enterprise\n│       └── Suspicious process behavior → MEDIUM: Investigate, prepare isolation\n│\n├── How many hosts affected?\n│   ├── Single host → Contained incident, follow host isolation procedure\n│   ├── Multiple hosts (2-10) → Escalate to Tier 2, begin enterprise-wide scan\n│   └── Enterprise-wide (>10) → Activate full IR team, engage external retainer\n│\n└── Is data exfiltration confirmed?\n    ├── YES → Double extortion scenario, engage legal for breach notification\n    └── NO\u002FUNKNOWN → Check for Cobalt Strike\u002FC2 beacons, review outbound transfers\n```\n\n### Step 3: Containment Procedures\n\n**Network Isolation via EDR (CrowdStrike Falcon):**\n```bash\n# Isolate host using CrowdStrike Falcon API\ncurl -X POST \"https:\u002F\u002Fapi.crowdstrike.com\u002Fdevices\u002Fentities\u002Fdevices-actions\u002Fv2?action_name=contain\" \\\n  -H \"Authorization: Bearer $TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"ids\": [\"device_id_here\"]}'\n```\n\n**Network Isolation via Microsoft Defender for Endpoint:**\n```powershell\n# Isolate machine via MDE API\n$headers = @{Authorization = \"Bearer $token\"}\n$body = @{Comment = \"Ransomware containment - IR-2024-0500\"; IsolationType = \"Full\"} | ConvertTo-Json\nInvoke-RestMethod -Uri \"https:\u002F\u002Fapi.securitycenter.microsoft.com\u002Fapi\u002Fmachines\u002F$machineId\u002Fisolate\" `\n    -Method Post -Headers $headers -Body $body -ContentType \"application\u002Fjson\"\n```\n\n**Firewall Emergency Rules:**\n```\n# Palo Alto — Block SMB lateral spread\nset rulebase security rules RansomwareContainment from Trust to Trust\nset rulebase security rules RansomwareContainment application ms-ds-smb\nset rulebase security rules RansomwareContainment action deny\nset rulebase security rules RansomwareContainment disabled no\ncommit\n```\n\n**Active Directory Emergency Actions:**\n```powershell\n# Disable compromised account\nDisable-ADAccount -Identity \"compromised_user\"\n\n# Reset Kerberos TGT (if domain admin compromised)\n# WARNING: This resets krbtgt and requires two resets 12+ hours apart\nReset-KrbtgtKeys -Server \"DC-PRIMARY\" -Force\n\n# Block lateral movement by disabling remote services\nSet-Service -Name \"RemoteRegistry\" -StartupType Disabled -Status Stopped\n```\n\n### Step 4: Evidence Collection and Preservation\n\nCollect forensic artifacts before remediation:\n\n```powershell\n# Capture running processes and network connections\nGet-Process | Export-Csv \"C:\\IR\\processes_$(hostname).csv\"\nGet-NetTCPConnection | Export-Csv \"C:\\IR\\netstat_$(hostname).csv\"\n\n# Capture memory dump (if host still running)\nwinpmem_mini_x64.exe C:\\IR\\memory_$(hostname).raw\n\n# Collect ransomware artifacts\nCopy-Item \"C:\\Users\\*\\Desktop\\*README*\" \"C:\\IR\\ransom_notes\\\" -Recurse\nCopy-Item \"C:\\Users\\*\\Desktop\\*.encrypted\" \"C:\\IR\\encrypted_samples\\\" -Force\n\n# Capture event logs\nwevtutil epl Security \"C:\\IR\\Security_$(hostname).evtx\"\nwevtutil epl System \"C:\\IR\\System_$(hostname).evtx\"\nwevtutil epl \"Microsoft-Windows-Sysmon\u002FOperational\" \"C:\\IR\\Sysmon_$(hostname).evtx\"\n```\n\n### Step 5: Eradication and Recovery\n\n**Identify ransomware variant:**\n- Upload encrypted sample and ransom note to ID Ransomware (https:\u002F\u002Fid-ransomware.malwarehunterteam.com\u002F)\n- Check No More Ransom Project (https:\u002F\u002Fwww.nomoreransom.org\u002F) for available decryptors\n- Search for ransomware family IOCs in MalwareBazaar\n\n**Enterprise-wide IOC scan in Splunk:**\n```spl\nindex=sysmon (EventCode=1 OR EventCode=11 OR EventCode=3)\n(TargetFilename=\"*ransomware_binary_name*\" OR sha256=\"KNOWN_HASH\"\n OR DestinationIp=\"C2_IP_ADDRESS\" OR CommandLine=\"*malicious_command*\")\n| stats count by Computer, EventCode, Image, CommandLine\n| sort - count\n```\n\n**Recovery from backups:**\n1. Verify backup integrity (offline\u002Fimmutable backups not affected)\n2. Rebuild affected systems from known-good images\n3. Restore data from last clean backup\n4. Validate restored systems before reconnecting to network\n5. Monitor restored systems for 72 hours for reinfection\n\n### Step 6: Post-Incident Documentation\n\nStructure the playbook conclusion with lessons learned:\n\n```\nPOST-INCIDENT REVIEW TEMPLATE\n1. Timeline of events (detection to full recovery)\n2. Initial access vector identification\n3. Dwell time analysis (time from initial compromise to encryption)\n4. Detection gaps identified\n5. Response effectiveness metrics (MTTD, MTTC, MTTR)\n6. Playbook improvements recommended\n7. New detection rules deployed\n8. Backup and recovery procedure updates\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **Double Extortion** | Ransomware tactic combining data encryption with data theft, threatening public release if ransom unpaid |\n| **Dwell Time** | Duration between initial compromise and detection — ransomware operators average 5-9 days before encryption |\n| **MTTC** | Mean Time to Contain — time from detection to successful isolation of affected systems |\n| **Kill Chain** | Ransomware progression: Initial Access -> Execution -> Persistence -> Privilege Escalation -> Lateral Movement -> Collection -> Exfiltration -> Impact |\n| **Immutable Backup** | Backup storage that cannot be modified or deleted for a defined retention period (WORM storage) |\n| **RTO\u002FRPO** | Recovery Time Objective \u002F Recovery Point Objective — maximum acceptable downtime and data loss thresholds |\n\n## Tools & Systems\n\n- **CrowdStrike Falcon \u002F SentinelOne**: EDR platforms with network isolation, process kill, and threat hunting capabilities\n- **Splunk ES \u002F Elastic Security**: SIEM platforms for detection rule deployment and enterprise-wide IOC scanning\n- **ID Ransomware**: Online service identifying ransomware variants from encrypted file samples and ransom notes\n- **No More Ransom Project**: Europol-backed initiative providing free decryption tools for known ransomware families\n- **Veeam \u002F Rubrik**: Enterprise backup solutions with immutable backup support and instant recovery capabilities\n\n## Common Scenarios\n\n- **LockBit Attack**: Detected via SMB lateral movement and mass file encryption — isolate, scan for Cobalt Strike beacons\n- **BlackCat\u002FALPHV**: Detected via ransomware note creation — check for data exfiltration via Rclone or Mega upload\n- **Conti\u002FRoyal**: Detected via shadow copy deletion — check for prior BazarLoader\u002FEmotet initial access\n- **RansomHub**: Detected via anomalous process execution — investigate for compromised VPN or RDP credentials\n- **Play Ransomware**: Detected via service account abuse — audit AD for newly created accounts and group membership changes\n\n## Output Format\n\n```\nRANSOMWARE PLAYBOOK EXECUTION — IR-2024-0500\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nPhase 1 - Detection:\n  Alert:      Mass file encryption detected on FILESERVER-03\n  Variant:    LockBit 3.0 (confirmed via ID Ransomware)\n  MTTD:       12 minutes from first encryption to SOC alert\n\nPhase 2 - Containment:\n  [DONE] FILESERVER-03 isolated via CrowdStrike at 14:35 UTC\n  [DONE] SMB blocked enterprise-wide via firewall emergency rule\n  [DONE] Compromised service account disabled in AD\n  MTTC:       23 minutes\n\nPhase 3 - Eradication:\n  [DONE] 3 additional hosts with C2 beacon identified and isolated\n  [DONE] Cobalt Strike C2 domain (c2[.]evil[.]com) sinkholed\n  [DONE] Enterprise-wide IOC scan completed — no additional infections\n\nPhase 4 - Recovery:\n  [DONE] FILESERVER-03 rebuilt from gold image\n  [DONE] Data restored from immutable Veeam backup (RPO: 4 hours)\n  [DONE] Systems monitored 72 hours — no reinfection\n  MTTR:       18 hours\n\nTotal Affected: 1 server, 3 workstations\nData Loss:      4 hours of file modifications (backup RPO)\nExfiltration:   No evidence of data exfiltration confirmed\n```\n",{"name":5,"tags":25,"author":33,"domain":34,"license":15,"version":35,"mitre_f3":36,"nist_csf":56,"subdomain":61,"description":62,"mitre_attack":63,"d3fend_techniques":69},[26,27,28,29,30,31,32],"soc","ransomware","incident-response","playbook","nist","mitre-attack","containment","mahipal","cybersecurity","1.0",{"tactics":37,"version":40,"techniques":41},[38,39],"initial-access","monetization","1.1",[42,46,49,53],{"id":43,"name":44,"source":45,"tactic":38},"T1660","Phishing","attack",{"id":47,"name":48,"source":45,"tactic":38},"T1110","Brute Force",{"id":50,"name":51,"source":52,"tactic":39},"F1018","Convert to Cryptocurrency","f3",{"id":54,"name":55,"source":52,"tactic":39},"F1047","Transfer of funds",[57,58,59,60],"DE.CM-01","DE.AE-02","RS.MA-01","DE.AE-06","soc-operations","Builds a structured SOC incident response playbook for ransomware attacks covering detection, containment, eradication, and recovery phases with specific SIEM queries, isolation procedures, and decision trees. Use when SOC teams need formalized response procedures for ransomware incidents aligned to NIST SP 800-61 and MITRE ATT&CK ransomware techniques.\n",[64,65,66,67,68],"T1486","T1490","T1489","T1566","T1059.001",[70,71,72,73,74],"Platform Hardening","Restore Object","Restore Configuration","Restore Software","Software Update","main","8a3b3de73262a4c4db64523949360f3c599c2fb1","Anthropic-Cybersecurity-Skills-main\u002Fskills\u002Fbuilding-soc-playbook-for-ransomware",0,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use","https:\u002F\u002Fgithub.com\u002FSaiVatsal","https:\u002F\u002Fsaivatsal.github.io\u002FPortfolio\u002F","The Longer It Takes The Stronger It Becomes ","2026-09-21 22:45:58",{"source":8,"skillName":5,"commands":85,"prompt":95,"zipAvailable":96},[86,89,92],{"tool":87,"command":88},"npx","npx skills add SaiVatsal\u002FSkills-I-Use --skill building-soc-playbook-for-ransomware",{"tool":90,"command":91},"bunx","bunx skills add SaiVatsal\u002FSkills-I-Use --skill building-soc-playbook-for-ransomware",{"tool":93,"command":94},"pnpm","pnpm dlx skills add SaiVatsal\u002FSkills-I-Use --skill building-soc-playbook-for-ransomware","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fbuilding-soc-playbook-for-ransomware\u002FSKILL.md",true,[98,102,108],{"path":99,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":103,"resourceType":104,"resourceTypeDesc":105,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Fapi-reference.md","REFERENCE","参考文档",2219,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fbuilding-soc-playbook-for-ransomware\u002Freferences\u002Fapi-reference.md",{"path":109,"resourceType":110,"resourceTypeDesc":111,"sizeBytes":112,"sourceHtmlUrl":113},"scripts\u002Fagent.py","SCRIPT","脚本",6001,"https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002FAnthropic-Cybersecurity-Skills-main\u002Fskills\u002Fbuilding-soc-playbook-for-ransomware\u002Fscripts\u002Fagent.py",[115,123,131,140,147,154],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":119,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":20},"01M7DJZP6E6KMBQV4CZSDPZEZ8","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":127,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":20},"01M7DJZFTS5TS06K2TV3MDTE67","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"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":135,"licenseFileUrl":136,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":20},"01M7DJRK4SRQ908F2TJM6EZ7EV","ui-styling","Create beautiful, accessible user interfaces with shadcn\u002Fui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.","MIT","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fui-styling\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fui-styling\u002FSKILL.md",[],[],{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":135,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":20},"01M7DJR902059VEQP23PVM2WA0","design","Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social\u002Fads\u002Fweb\u002Fprint), icon design (15 styles, SVG, Gemini 3.1 Pro), social photos (HTML→screenshot, multi-platform). Actions: design logo, create CIP, generate mockups, build slides, design banner, generate icon, create social photos, social media images, brand identity, design system. Platforms: Facebook, Twitter, LinkedIn, YouTube, Instagram, Pinterest, TikTok, Threads, Google Ads.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fdesign\u002FSKILL.md",[],[],{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":135,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":20},"01M7DJR56QF5N6XYTCPCFHFMNP","design-system","Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing\u002Ftypography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fdesign-system\u002FSKILL.md",[],[],{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":135,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":20},"01M7DJQXB6M0SFF7NX8J5N01AH","banner-design","Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with AI-generated visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter\u002FX, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage. Uses ui-ux-pro-max, frontend-design, ai-artist, ai-multimodal skills.","https:\u002F\u002Fgithub.com\u002FSaiVatsal\u002FSkills-I-Use\u002Fblob\u002Fmain\u002Fui-ux-pro-max-skill-main\u002Fcli\u002Fassets\u002Fskills\u002Fbanner-design\u002FSKILL.md",[],[]]