[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AEHZ4CYEYTCB2MY5MJY0NX":3,"skill-same:01M6AEHZ4CYEYTCB2MY5MJY0NX":153},{"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":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":94,"commitSha":95,"skillDirectory":96,"forksCount":97,"repositoryHtmlUrl":98,"repositoryHomepageUrl":99,"ownerHtmlUrl":100,"ownerBlogUrl":101,"ownerDescription":102,"updatedAt":103,"install":104,"resources":117},"01M6AEHZ4CYEYTCB2MY5MJY0NX","detecting-spearphishing-with-email-gateway",null,"Detect and block spearphishing emails that use personalized, researched content to evade generic spam filters, by configuring email security gateway (SEG) impersonation protection, URL rewriting, attachment sandboxing, and custom detection rules in Microsoft Defender for Office 365, Proofpoint, Mimecast, or Barracuda. Use when hardening a mail gateway against targeted phishing or investigating a suspected spearphishing campaign.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",35990,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdetecting-spearphishing-with-email-gateway\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"email","detecting spearphishing with email gateway","spearphishing","gateway","pr","development","create","website","defender","office","security","phishing","dmarc","email-security","social-engineering","awareness","official","defense","email-gateway","cybersecurity","2026-11-10 10:12:30",false,"---\nname: detecting-spearphishing-with-email-gateway\ndescription: Detect and block spearphishing emails that use personalized, researched\n  content to evade generic spam filters, by configuring email security gateway\n  (SEG) impersonation protection, URL rewriting, attachment sandboxing, and\n  custom detection rules in Microsoft Defender for Office 365, Proofpoint,\n  Mimecast, or Barracuda. Use when hardening a mail gateway against targeted\n  phishing or investigating a suspected spearphishing campaign.\ndomain: cybersecurity\nsubdomain: phishing-defense\ntags:\n- phishing\n- email-security\n- social-engineering\n- dmarc\n- awareness\n- spearphishing\n- email-gateway\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.AT-01\n- DE.CM-09\n- RS.CO-02\n- DE.AE-02\nmitre_attack:\n- T1566.001\n- T1566.002\n- T1204.001\n- T1204.002\nmitre_f3:\n  version: '1.1'\n  tactics:\n  - reconnaissance\n  - initial-access\n  - stealth\n  - resource-development\n  techniques:\n  - id: T1660\n    name: Phishing\n    tactic: initial-access\n    source: attack\n  - id: T1598\n    name: Phishing for Information\n    tactic: reconnaissance\n    source: attack\n  - id: T1672\n    name: Email Spoofing\n    tactic: stealth\n    source: attack\n  - id: F1032\n    name: Impersonate Official\n    tactic: initial-access\n    source: f3\n  - id: F1031\n    name: Impersonate Account Holder\n    tactic: initial-access\n    source: f3\n  - id: F1020.002\n    name: 'Create Fake Materials: Fake Website'\n    tactic: resource-development\n    source: f3\n---\n# Detecting Spearphishing with Email Gateway\n\n## Overview\nSpearphishing targets specific individuals using personalized, researched content that bypasses generic spam filters. Email security gateways (SEGs) like Microsoft Defender for Office 365, Proofpoint, Mimecast, and Barracuda provide advanced detection capabilities including behavioral analysis, URL detonation, attachment sandboxing, and impersonation detection. This skill covers configuring these gateways to detect and block targeted phishing attacks.\n\n\n## When to Use\n\n- When investigating security incidents that require detecting spearphishing with email gateway\n- When building detection rules or threat hunting queries for this domain\n- When SOC analysts need structured procedures for this analysis type\n- When validating security monitoring coverage for related attack techniques\n\n## Prerequisites\n- Access to email security gateway admin console\n- Understanding of email flow architecture (MX records, transport rules)\n- Familiarity with SPF\u002FDKIM\u002FDMARC authentication\n- Knowledge of common spearphishing techniques and pretexts\n\n## Key Concepts\n\n### Spearphishing Characteristics\n- **Targeted recipients**: Specific individuals, often executives or finance staff\n- **Researched pretexts**: References to real projects, colleagues, or events\n- **Impersonation**: Spoofs trusted senders (CEO, vendor, partner)\n- **Low volume**: Few emails to avoid pattern-based detection\n- **Urgent tone**: Creates pressure to act quickly\n\n### Gateway Detection Layers\n1. **Reputation filtering**: IP\u002Fdomain\u002FURL reputation scoring\n2. **Authentication checks**: SPF, DKIM, DMARC validation\n3. **Content analysis**: NLP-based analysis of email body\n4. **Impersonation detection**: Display name and domain similarity matching\n5. **URL analysis**: Real-time URL detonation and redirect following\n6. **Attachment sandboxing**: Behavioral analysis of attachments in isolated environments\n7. **Behavioral analytics**: Anomaly detection in communication patterns\n\n## Workflow\n\n### Step 1: Configure Impersonation Protection\n```\nMicrosoft Defender for Office 365:\n  Security > Anti-phishing policies > Impersonation settings\n  - Enable user impersonation protection for VIPs\n  - Enable domain impersonation protection\n  - Add protected users (CEO, CFO, HR Director)\n  - Set action: Quarantine message\n\nProofpoint:\n  Email Protection > Impostor Classifier\n  - Enable display name spoofing detection\n  - Configure lookalike domain detection\n  - Set Impostor threshold sensitivity\n```\n\n### Step 2: Configure URL Protection\n- Enable Safe Links \u002F URL rewriting\n- Enable time-of-click URL detonation\n- Block newly registered domains (\u003C 30 days)\n- Enable URL redirect chain following\n\n### Step 3: Configure Attachment Sandboxing\n- Enable Safe Attachments \u002F attachment sandboxing\n- Configure dynamic delivery (deliver body, hold attachments)\n- Set sandbox detonation timeout to 60+ seconds\n- Block macro-enabled Office documents from external senders\n\n### Step 4: Create Custom Detection Rules\nUse the `scripts\u002Fprocess.py` to analyze email gateway logs, identify spearphishing patterns, and generate custom detection rules.\n\n### Step 5: Configure Alert and Response Actions\n- Real-time alerts for impersonation attempts\n- Automatic quarantine for high-confidence detections\n- User notification with safety tips\n- Integration with SIEM for correlation\n\n## Tools & Resources\n- **Microsoft Defender for Office 365**: https:\u002F\u002Fsecurity.microsoft.com\n- **Proofpoint Email Protection**: https:\u002F\u002Fwww.proofpoint.com\u002Fus\u002Fproducts\u002Femail-security\n- **Mimecast Email Security**: https:\u002F\u002Fwww.mimecast.com\u002Fproducts\u002Femail-security\u002F\n- **Barracuda Email Protection**: https:\u002F\u002Fwww.barracuda.com\u002Fproducts\u002Femail-protection\n\n## Validation\n- Impersonation protection correctly identifies spoofed VIP display names\n- URL detonation catches malicious links in test phishing emails\n- Attachment sandboxing detects weaponized documents\n- Custom rules trigger on known spearphishing patterns\n- SIEM integration receives gateway alerts\n","# Detecting Spearphishing with Email Gateway\n\n## Overview\nSpearphishing targets specific individuals using personalized, researched content that bypasses generic spam filters. Email security gateways (SEGs) like Microsoft Defender for Office 365, Proofpoint, Mimecast, and Barracuda provide advanced detection capabilities including behavioral analysis, URL detonation, attachment sandboxing, and impersonation detection. This skill covers configuring these gateways to detect and block targeted phishing attacks.\n\n\n## When to Use\n\n- When investigating security incidents that require detecting spearphishing with email gateway\n- When building detection rules or threat hunting queries for this domain\n- When SOC analysts need structured procedures for this analysis type\n- When validating security monitoring coverage for related attack techniques\n\n## Prerequisites\n- Access to email security gateway admin console\n- Understanding of email flow architecture (MX records, transport rules)\n- Familiarity with SPF\u002FDKIM\u002FDMARC authentication\n- Knowledge of common spearphishing techniques and pretexts\n\n## Key Concepts\n\n### Spearphishing Characteristics\n- **Targeted recipients**: Specific individuals, often executives or finance staff\n- **Researched pretexts**: References to real projects, colleagues, or events\n- **Impersonation**: Spoofs trusted senders (CEO, vendor, partner)\n- **Low volume**: Few emails to avoid pattern-based detection\n- **Urgent tone**: Creates pressure to act quickly\n\n### Gateway Detection Layers\n1. **Reputation filtering**: IP\u002Fdomain\u002FURL reputation scoring\n2. **Authentication checks**: SPF, DKIM, DMARC validation\n3. **Content analysis**: NLP-based analysis of email body\n4. **Impersonation detection**: Display name and domain similarity matching\n5. **URL analysis**: Real-time URL detonation and redirect following\n6. **Attachment sandboxing**: Behavioral analysis of attachments in isolated environments\n7. **Behavioral analytics**: Anomaly detection in communication patterns\n\n## Workflow\n\n### Step 1: Configure Impersonation Protection\n```\nMicrosoft Defender for Office 365:\n  Security > Anti-phishing policies > Impersonation settings\n  - Enable user impersonation protection for VIPs\n  - Enable domain impersonation protection\n  - Add protected users (CEO, CFO, HR Director)\n  - Set action: Quarantine message\n\nProofpoint:\n  Email Protection > Impostor Classifier\n  - Enable display name spoofing detection\n  - Configure lookalike domain detection\n  - Set Impostor threshold sensitivity\n```\n\n### Step 2: Configure URL Protection\n- Enable Safe Links \u002F URL rewriting\n- Enable time-of-click URL detonation\n- Block newly registered domains (\u003C 30 days)\n- Enable URL redirect chain following\n\n### Step 3: Configure Attachment Sandboxing\n- Enable Safe Attachments \u002F attachment sandboxing\n- Configure dynamic delivery (deliver body, hold attachments)\n- Set sandbox detonation timeout to 60+ seconds\n- Block macro-enabled Office documents from external senders\n\n### Step 4: Create Custom Detection Rules\nUse the `scripts\u002Fprocess.py` to analyze email gateway logs, identify spearphishing patterns, and generate custom detection rules.\n\n### Step 5: Configure Alert and Response Actions\n- Real-time alerts for impersonation attempts\n- Automatic quarantine for high-confidence detections\n- User notification with safety tips\n- Integration with SIEM for correlation\n\n## Tools & Resources\n- **Microsoft Defender for Office 365**: https:\u002F\u002Fsecurity.microsoft.com\n- **Proofpoint Email Protection**: https:\u002F\u002Fwww.proofpoint.com\u002Fus\u002Fproducts\u002Femail-security\n- **Mimecast Email Security**: https:\u002F\u002Fwww.mimecast.com\u002Fproducts\u002Femail-security\u002F\n- **Barracuda Email Protection**: https:\u002F\u002Fwww.barracuda.com\u002Fproducts\u002Femail-protection\n\n## Validation\n- Impersonation protection correctly identifies spoofed VIP display names\n- URL detonation catches malicious links in test phishing emails\n- Attachment sandboxing detects weaponized documents\n- Custom rules trigger on known spearphishing patterns\n- SIEM integration receives gateway alerts\n",{"name":5,"tags":52,"author":53,"domain":46,"license":15,"version":54,"mitre_f3":55,"nist_csf":83,"subdomain":88,"description":7,"mitre_attack":89},[38,40,41,39,42,29,45],"mahipal","1.0",{"tactics":56,"version":61,"techniques":62},[57,58,59,60],"reconnaissance","initial-access","stealth","resource-development","1.1",[63,67,70,73,77,80],{"id":64,"name":65,"source":66,"tactic":58},"T1660","Phishing","attack",{"id":68,"name":69,"source":66,"tactic":57},"T1598","Phishing for Information",{"id":71,"name":72,"source":66,"tactic":59},"T1672","Email Spoofing",{"id":74,"name":75,"source":76,"tactic":58},"F1032","Impersonate Official","f3",{"id":78,"name":79,"source":76,"tactic":58},"F1031","Impersonate Account Holder",{"id":81,"name":82,"source":76,"tactic":60},"F1020.002","Create Fake Materials: Fake Website",[84,85,86,87],"PR.AT-01","DE.CM-09","RS.CO-02","DE.AE-02","phishing-defense",[90,91,92,93],"T1566.001","T1566.002","T1204.001","T1204.002","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fdetecting-spearphishing-with-email-gateway",4395,"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":105,"prompt":115,"zipAvailable":116},[106,109,112],{"tool":107,"command":108},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill detecting-spearphishing-with-email-gateway",{"tool":110,"command":111},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill detecting-spearphishing-with-email-gateway",{"tool":113,"command":114},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill detecting-spearphishing-with-email-gateway","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdetecting-spearphishing-with-email-gateway\u002FSKILL.md",true,[118,124,129,135,139,143,149],{"path":119,"resourceType":120,"resourceTypeDesc":121,"sizeBytes":122,"sourceHtmlUrl":123},"assets\u002Ftemplate.md","ASSET","资产文件",1928,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdetecting-spearphishing-with-email-gateway\u002Fassets\u002Ftemplate.md",{"path":125,"resourceType":125,"resourceTypeDesc":126,"sizeBytes":127,"sourceHtmlUrl":128},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdetecting-spearphishing-with-email-gateway\u002FLICENSE",{"path":130,"resourceType":131,"resourceTypeDesc":132,"sizeBytes":133,"sourceHtmlUrl":134},"references\u002Fapi-reference.md","REFERENCE","参考文档",2296,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdetecting-spearphishing-with-email-gateway\u002Freferences\u002Fapi-reference.md",{"path":136,"resourceType":131,"resourceTypeDesc":132,"sizeBytes":137,"sourceHtmlUrl":138},"references\u002Fstandards.md",2489,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdetecting-spearphishing-with-email-gateway\u002Freferences\u002Fstandards.md",{"path":140,"resourceType":131,"resourceTypeDesc":132,"sizeBytes":141,"sourceHtmlUrl":142},"references\u002Fworkflows.md",3813,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdetecting-spearphishing-with-email-gateway\u002Freferences\u002Fworkflows.md",{"path":144,"resourceType":145,"resourceTypeDesc":146,"sizeBytes":147,"sourceHtmlUrl":148},"scripts\u002Fagent.py","SCRIPT","脚本",5768,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdetecting-spearphishing-with-email-gateway\u002Fscripts\u002Fagent.py",{"path":150,"resourceType":145,"resourceTypeDesc":146,"sizeBytes":151,"sourceHtmlUrl":152},"scripts\u002Fprocess.py",21603,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdetecting-spearphishing-with-email-gateway\u002Fscripts\u002Fprocess.py",[154,179,203,231,257,284],{"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":47},"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",[160],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[162,163,164,165,37,46,166,167,31,168,169,170,171,172,173,174,175,176,177,178],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","incident response","identity","code","artifacts","ci","supply-chain","pipeline","supply-chain-security","t1195","attestation","code-signing","cosign","keyless",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":186,"publishedAt":47},"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",[185],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[187,175,188,189,37,190,46,31,191,192,193,194,195,196,197,198,199,200,201,202],"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":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":213,"publishedAt":47},"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",[209,212],{"categoryNo":210,"categoryName":211,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[197,214,215,216,217,46,218,219,191,220,221,222,223,224,225,226,227,228,229,230],"backup","recovery","validating backup integrity for recovery","testing","infrastructure","validation","compliance","hash-verification","incident-response","ransomware","cryptocurrency","detection","t1078","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":232,"name":233,"nameZh":6,"description":234,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":235,"categories":236,"keywords":238,"publishedAt":47},"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",[237],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[239,240,241,46,242,243,244,245,246,247,248,249,250,251,252,253,194,254,255,256],"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":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":47},"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",[263],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[265,266,267,46,268,269,270,271,272,273,274,275,276,277,278,279,280,281,282,283],"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":285,"name":286,"nameZh":6,"description":287,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":288,"categories":289,"keywords":291,"publishedAt":47},"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",[290],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[37,292,46,293,294,295,296,297,298,299,300,226,301,227,302,303,304,305,306,307],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]