[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFDQ3ZJFN48H9C7A1QXNRR":3,"skill-same:01M6AFDQ3ZJFN48H9C7A1QXNRR":124},{"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":83,"commitSha":84,"skillDirectory":85,"forksCount":86,"repositoryHtmlUrl":87,"repositoryHomepageUrl":88,"ownerHtmlUrl":89,"ownerBlogUrl":90,"ownerDescription":91,"updatedAt":92,"install":93,"resources":106},"01M6AFDQ3ZJFN48H9C7A1QXNRR","implementing-soar-playbook-for-phishing",null,"Automates phishing incident response by calling the Splunk SOAR (Phantom) REST API to create containers, attach artifacts (emails, URLs, attachments), and trigger response playbooks. Use when building or wiring up a Splunk SOAR phishing playbook, ingesting a suspected phishing report into SOAR, or automating containment and triage for phishing incidents.","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\u002Fimplementing-soar-playbook-for-phishing\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"implementing soar playbook for phishing","soar","playbook","phishing","security-operations","t1566","initial-access","t1059","t1078","containment","splunk","containers","email","website","create","development","official","incident response","cybersecurity","security","2026-11-10 10:12:30",false,"---\nname: implementing-soar-playbook-for-phishing\ndescription: Automates phishing incident response by calling the Splunk SOAR (Phantom)\n  REST API to create containers, attach artifacts (emails, URLs, attachments), and\n  trigger response playbooks. Use when building or wiring up a Splunk SOAR phishing\n  playbook, ingesting a suspected phishing report into SOAR, or automating containment\n  and triage for phishing incidents.\ndomain: cybersecurity\nsubdomain: security-operations\ntags:\n- soar\n- splunk-phantom\n- phishing\n- incident-response\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- DE.CM-01\n- RS.MA-01\n- GV.OV-01\n- DE.AE-02\nmitre_attack:\n- T1078\n- T1190\n- T1059\n- T1566\n- T1598\nmitre_f3:\n  version: '1.1'\n  tactics:\n  - reconnaissance\n  - resource-development\n  - initial-access\n  - stealth\n  techniques:\n  - id: T1598\n    name: Phishing for Information\n    tactic: reconnaissance\n    source: attack\n  - id: T1660\n    name: Phishing\n    tactic: initial-access\n    source: attack\n  - id: T1672\n    name: Email Spoofing\n    tactic: stealth\n    source: attack\n  - id: F1020.002\n    name: 'Create Fake Materials: Fake Website'\n    tactic: resource-development\n    source: f3\n  - id: F1032\n    name: Impersonate Official\n    tactic: initial-access\n    source: f3\n---\n\n\n# Implementing SOAR Playbook for Phishing\n\n## Overview\n\nThis skill implements a phishing incident response workflow using the Splunk SOAR (formerly Phantom) REST API. When a suspected phishing email is reported, the agent parses email headers and body, creates a SOAR container representing the incident, attaches artifacts containing indicators of compromise (sender address, URLs, IP addresses, file hashes), triggers an automated investigation playbook, and polls for action results.\n\nSplunk SOAR orchestrates and automates security operations through playbooks that chain together investigative and response actions. The REST API at `\u002Frest\u002Fcontainer`, `\u002Frest\u002Fartifact`, and `\u002Frest\u002Fplaybook_run` enables programmatic incident creation and automation triggering from external tools, email gateways, and SIEM alerts.\n\n\n## When to Use\n\n- When deploying or configuring implementing soar playbook for phishing 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- Python 3.9 or later with `requests` and `email` modules\n- Splunk SOAR instance (Cloud or On-Premises) with REST API access\n- SOAR API token with permissions to create containers and trigger playbooks\n- Network connectivity to SOAR instance on port 443\n- A configured phishing investigation playbook in SOAR\n\n## Steps\n\n1. **Parse the phishing email**: Read the email file (.eml format) and extract headers including From, To, Subject, Reply-To, Return-Path, Received, Message-ID, X-Mailer, and authentication results (SPF, DKIM, DMARC). Extract URLs and IP addresses from the email body.\n\n2. **Authenticate to SOAR REST API**: Use the API token in the `ph-auth-token` header to authenticate all REST API requests to the SOAR instance.\n\n3. **Create a container**: POST to `\u002Frest\u002Fcontainer` with the incident label, name, description, severity, and status. The container represents the phishing incident and receives a container ID in the response.\n\n4. **Add email header artifacts**: POST to `\u002Frest\u002Fartifact` with `container_id` and CEF (Common Event Format) fields containing sender address (`fromAddress`), recipient (`toAddress`), subject, originating IP (`sourceAddress`), and Message-ID. Set `run_automation` to False for all but the last artifact.\n\n5. **Add URL artifacts**: For each URL extracted from the email body, create an artifact with CEF field `requestURL` and type `url`. These artifacts feed into URL reputation checks in the playbook.\n\n6. **Trigger the playbook**: POST to `\u002Frest\u002Fplaybook_run` with the playbook ID or name and the container ID. This initiates the automated investigation workflow.\n\n7. **Poll action results**: GET `\u002Frest\u002Faction_run` filtered by container ID to monitor playbook progress. Poll until all actions reach a terminal state (success, failed, or cancelled).\n\n8. **Compile response report**: Aggregate playbook action results into a summary report with verdicts from URL reputation, domain reputation, IP geolocation, and email header analysis.\n\n## Expected Output\n\n```json\n{\n  \"incident\": {\n    \"container_id\": 1542,\n    \"status\": \"new\",\n    \"severity\": \"high\",\n    \"artifacts_created\": 5\n  },\n  \"playbook\": {\n    \"name\": \"phishing_investigate\",\n    \"run_id\": 892,\n    \"status\": \"success\",\n    \"actions_completed\": 8\n  },\n  \"verdict\": \"malicious\",\n  \"indicators\": {\n    \"sender_domain_reputation\": \"malicious\",\n    \"urls_flagged\": 2,\n    \"spf_result\": \"fail\",\n    \"dkim_result\": \"fail\"\n  }\n}\n```\n","# Implementing SOAR Playbook for Phishing\n\n## Overview\n\nThis skill implements a phishing incident response workflow using the Splunk SOAR (formerly Phantom) REST API. When a suspected phishing email is reported, the agent parses email headers and body, creates a SOAR container representing the incident, attaches artifacts containing indicators of compromise (sender address, URLs, IP addresses, file hashes), triggers an automated investigation playbook, and polls for action results.\n\nSplunk SOAR orchestrates and automates security operations through playbooks that chain together investigative and response actions. The REST API at `\u002Frest\u002Fcontainer`, `\u002Frest\u002Fartifact`, and `\u002Frest\u002Fplaybook_run` enables programmatic incident creation and automation triggering from external tools, email gateways, and SIEM alerts.\n\n\n## When to Use\n\n- When deploying or configuring implementing soar playbook for phishing 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- Python 3.9 or later with `requests` and `email` modules\n- Splunk SOAR instance (Cloud or On-Premises) with REST API access\n- SOAR API token with permissions to create containers and trigger playbooks\n- Network connectivity to SOAR instance on port 443\n- A configured phishing investigation playbook in SOAR\n\n## Steps\n\n1. **Parse the phishing email**: Read the email file (.eml format) and extract headers including From, To, Subject, Reply-To, Return-Path, Received, Message-ID, X-Mailer, and authentication results (SPF, DKIM, DMARC). Extract URLs and IP addresses from the email body.\n\n2. **Authenticate to SOAR REST API**: Use the API token in the `ph-auth-token` header to authenticate all REST API requests to the SOAR instance.\n\n3. **Create a container**: POST to `\u002Frest\u002Fcontainer` with the incident label, name, description, severity, and status. The container represents the phishing incident and receives a container ID in the response.\n\n4. **Add email header artifacts**: POST to `\u002Frest\u002Fartifact` with `container_id` and CEF (Common Event Format) fields containing sender address (`fromAddress`), recipient (`toAddress`), subject, originating IP (`sourceAddress`), and Message-ID. Set `run_automation` to False for all but the last artifact.\n\n5. **Add URL artifacts**: For each URL extracted from the email body, create an artifact with CEF field `requestURL` and type `url`. These artifacts feed into URL reputation checks in the playbook.\n\n6. **Trigger the playbook**: POST to `\u002Frest\u002Fplaybook_run` with the playbook ID or name and the container ID. This initiates the automated investigation workflow.\n\n7. **Poll action results**: GET `\u002Frest\u002Faction_run` filtered by container ID to monitor playbook progress. Poll until all actions reach a terminal state (success, failed, or cancelled).\n\n8. **Compile response report**: Aggregate playbook action results into a summary report with verdicts from URL reputation, domain reputation, IP geolocation, and email header analysis.\n\n## Expected Output\n\n```json\n{\n  \"incident\": {\n    \"container_id\": 1542,\n    \"status\": \"new\",\n    \"severity\": \"high\",\n    \"artifacts_created\": 5\n  },\n  \"playbook\": {\n    \"name\": \"phishing_investigate\",\n    \"run_id\": 892,\n    \"status\": \"success\",\n    \"actions_completed\": 8\n  },\n  \"verdict\": \"malicious\",\n  \"indicators\": {\n    \"sender_domain_reputation\": \"malicious\",\n    \"urls_flagged\": 2,\n    \"spf_result\": \"fail\",\n    \"dkim_result\": \"fail\"\n  }\n}\n```\n",{"name":5,"tags":44,"author":47,"domain":37,"license":15,"version":48,"mitre_f3":49,"nist_csf":73,"subdomain":23,"description":7,"mitre_attack":78},[20,45,22,46],"splunk-phantom","incident-response","mahipal","1.0",{"tactics":50,"version":54,"techniques":55},[51,52,25,53],"reconnaissance","resource-development","stealth","1.1",[56,60,63,66,70],{"id":57,"name":58,"source":59,"tactic":51},"T1598","Phishing for Information","attack",{"id":61,"name":62,"source":59,"tactic":25},"T1660","Phishing",{"id":64,"name":65,"source":59,"tactic":53},"T1672","Email Spoofing",{"id":67,"name":68,"source":69,"tactic":52},"F1020.002","Create Fake Materials: Fake Website","f3",{"id":71,"name":72,"source":69,"tactic":25},"F1032","Impersonate Official",[74,75,76,77],"DE.CM-01","RS.MA-01","GV.OV-01","DE.AE-02",[79,80,81,82,57],"T1078","T1190","T1059","T1566","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fimplementing-soar-playbook-for-phishing",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":94,"prompt":104,"zipAvailable":105},[95,98,101],{"tool":96,"command":97},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-soar-playbook-for-phishing",{"tool":99,"command":100},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-soar-playbook-for-phishing",{"tool":102,"command":103},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-soar-playbook-for-phishing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-soar-playbook-for-phishing\u002FSKILL.md",true,[107,112,118],{"path":108,"resourceType":108,"resourceTypeDesc":109,"sizeBytes":110,"sourceHtmlUrl":111},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-soar-playbook-for-phishing\u002FLICENSE",{"path":113,"resourceType":114,"resourceTypeDesc":115,"sizeBytes":116,"sourceHtmlUrl":117},"references\u002Fapi-reference.md","REFERENCE","参考文档",2586,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-soar-playbook-for-phishing\u002Freferences\u002Fapi-reference.md",{"path":119,"resourceType":120,"resourceTypeDesc":121,"sizeBytes":122,"sourceHtmlUrl":123},"scripts\u002Fagent.py","SCRIPT","脚本",8856,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-soar-playbook-for-phishing\u002Fscripts\u002Fagent.py",[125,154,178,204,230,257],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":136,"publishedAt":39},"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",[131],{"categoryNo":132,"categoryName":133,"taxonomyType":134,"taxonomyTypeDesc":135},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[137,138,139,140,38,37,36,141,142,143,144,145,146,147,148,149,150,151,152,153],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","identity","pr","code","artifacts","ci","supply-chain","pipeline","supply-chain-security","t1195","attestation","code-signing","cosign","keyless",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":161,"publishedAt":39},"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",[160],{"categoryNo":132,"categoryName":133,"taxonomyType":134,"taxonomyTypeDesc":135},[162,150,163,164,38,165,37,142,166,167,168,169,170,171,172,173,174,175,176,177],"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":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":188,"publishedAt":39},"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",[184,187],{"categoryNo":185,"categoryName":186,"taxonomyType":134,"taxonomyTypeDesc":135},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":132,"categoryName":133,"taxonomyType":134,"taxonomyTypeDesc":135},[172,189,190,191,192,37,193,194,166,195,196,46,197,198,199,27,200,201,202,203],"backup","recovery","validating backup integrity for recovery","testing","infrastructure","validation","compliance","hash-verification","ransomware","cryptocurrency","detection","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":208,"categories":209,"keywords":211,"publishedAt":39},"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",[210],{"categoryNo":132,"categoryName":133,"taxonomyType":134,"taxonomyTypeDesc":135},[212,213,214,37,215,216,217,218,219,220,221,222,223,224,225,226,169,227,228,229],"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":231,"name":232,"nameZh":6,"description":233,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":234,"categories":235,"keywords":237,"publishedAt":39},"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",[236],{"categoryNo":132,"categoryName":133,"taxonomyType":134,"taxonomyTypeDesc":135},[238,239,240,37,241,242,243,244,245,246,247,248,249,250,251,252,253,254,255,256],"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":258,"name":259,"nameZh":6,"description":260,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":261,"categories":262,"keywords":264,"publishedAt":39},"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",[263],{"categoryNo":132,"categoryName":133,"taxonomyType":134,"taxonomyTypeDesc":135},[38,265,37,266,267,268,269,270,271,272,273,27,274,200,275,276,277,278,279,280],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]