[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AEAKFH3HQXTCCS3P5EMDCM":3,"skill-same:01M6AEAKFH3HQXTCCS3P5EMDCM":176},{"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":34,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":117,"commitSha":118,"skillDirectory":119,"forksCount":120,"repositoryHtmlUrl":121,"repositoryHomepageUrl":122,"ownerHtmlUrl":123,"ownerBlogUrl":124,"ownerDescription":125,"updatedAt":126,"install":127,"resources":140},"01M6AEAKFH3HQXTCCS3P5EMDCM","detecting-business-email-compromise",null,"Detect Business Email Compromise (BEC) fraud, where attackers impersonate executives or vendors to trick employees into wire transfers or data disclosure without malicious links, using email gateway rules, behavioral analytics, and financial process controls. Use when investigating a suspected executive\u002Fvendor impersonation email or building detection rules for social-engineering fund-transfer fraud.","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\u002Fdetecting-business-email-compromise\u002FSKILL.md",[18,23,26,29],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"detecting business email compromise","email","phishing","impersonation","defense","BEC","data","awareness","social-engineering","email-security","dmarc","malicious","gateway","delete","pr","official","analytics","change","cybersecurity","security","2026-11-10 10:12:30",false,"---\nname: detecting-business-email-compromise\ndescription: Detect Business Email Compromise (BEC) fraud, where attackers impersonate\n  executives or vendors to trick employees into wire transfers or data disclosure without\n  malicious links, using email gateway rules, behavioral analytics, and financial process\n  controls. Use when investigating a suspected executive\u002Fvendor impersonation email or\n  building detection rules for social-engineering fund-transfer fraud.\ndomain: cybersecurity\nsubdomain: phishing-defense\ntags:\n- phishing\n- email-security\n- social-engineering\n- dmarc\n- awareness\n- bec\n- fraud\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\natlas_techniques:\n- AML.T0052\n- AML.T0088\nnist_ai_rmf:\n- GOVERN-6.2\n- MAP-5.2\nd3fend_techniques:\n- Restore Object\n- Restore Configuration\n- Application Configuration Hardening\n- Application Hardening\n- Disable Remote Access\nnist_csf:\n- PR.AT-01\n- DE.CM-09\n- RS.CO-02\n- DE.AE-02\nmitre_attack:\n- T1566.002\n- T1534\n- T1114.002\n- T1657\n- T1078.004\nmitre_f3:\n  version: '1.1'\n  tactics:\n  - initial-access\n  - positioning\n  - monetization\n  - stealth\n  techniques:\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: F1036\n    name: New Vendor Setup\n    tactic: positioning\n    source: f3\n  - id: F1005.006\n    name: 'Account Manipulation: Change of Payment Details'\n    tactic: positioning\n    source: f3\n  - id: F1025.003\n    name: 'Electronic Funds Transfer: Wire Transfer'\n    tactic: monetization\n    source: f3\n  - id: F1022\n    name: Delete Relevant Emails\n    tactic: stealth\n    source: f3\n---\n# Detecting Business Email Compromise\n\n## Overview\nBusiness Email Compromise (BEC) is a sophisticated fraud scheme where attackers impersonate executives, vendors, or trusted partners to trick employees into transferring funds, sharing sensitive data, or changing payment details. Unlike traditional phishing, BEC often contains no malicious links or attachments, relying purely on social engineering. This skill covers detection techniques using email gateway rules, behavioral analytics, and financial process controls.\n\n\n## When to Use\n\n- When investigating security incidents that require detecting business email compromise\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- Email security gateway with BEC detection capabilities\n- Understanding of organizational financial processes and approval chains\n- Access to email logs and SIEM platform\n- Knowledge of social engineering tactics\n\n## Key Concepts\n\n### BEC Attack Types (FBI IC3 Classification)\n1. **CEO Fraud**: Attacker impersonates CEO, requests urgent wire transfer\n2. **Account Compromise**: Employee email compromised, used to request payments from vendors\n3. **False Invoice Scheme**: Fake invoices from \"vendor\" with changed bank details\n4. **Attorney Impersonation**: Impersonates legal counsel for urgent confidential transfers\n5. **Data Theft**: Requests W-2, tax forms, or PII from HR\n\n### Detection Indicators\n- Urgency and secrecy language (\"confidential\", \"do not discuss with others\")\n- New or changed payment instructions\n- Executive communication outside normal patterns\n- Display name matches executive but email domain differs\n- Reply-to address differs from From address\n- First-time communication pattern between sender and recipient\n- Request for gift cards or cryptocurrency\n\n## Workflow\n\n### Step 1: Configure BEC-Specific Email Rules\n- Flag emails with VIP display names from external domains\n- Detect financial keywords combined with urgency language\n- Alert on first-time sender to finance\u002Faccounting staff\n- Check for Reply-To domain mismatch\n\n### Step 2: Deploy Behavioral Analytics\n- Baseline normal communication patterns per user\n- Detect anomalous requests (unusual recipient, unusual time, unusual request type)\n- Monitor for email forwarding rule changes (T1114.003)\n\n### Step 3: Implement Financial Controls\n- Dual-authorization for wire transfers above threshold\n- Out-of-band verification for payment detail changes (phone callback)\n- Vendor payment change verification process\n- Finance team training on BEC red flags\n\n### Step 4: Monitor for Account Compromise\n- Detect impossible travel in email login locations\n- Alert on email forwarding rule creation\n- Monitor for mailbox delegation changes\n- Check for inbox rules hiding BEC-related emails\n\n## Tools & Resources\n- **Microsoft Defender for O365 Anti-BEC**: Built-in BEC detection\n- **Proofpoint Email Fraud Defense**: BEC-specific solution\n- **Abnormal Security**: AI-driven BEC detection\n- **FBI IC3 BEC Advisory**: https:\u002F\u002Fwww.ic3.gov\u002F\n- **FinCEN BEC Advisory**: Financial institution guidance\n\n## Validation\n- BEC detection rules trigger on test scenarios\n- Financial controls prevent unauthorized transfers in drills\n- Account compromise detection catches simulated attacks\n- Reduced BEC susceptibility in awareness assessments\n","# Detecting Business Email Compromise\n\n## Overview\nBusiness Email Compromise (BEC) is a sophisticated fraud scheme where attackers impersonate executives, vendors, or trusted partners to trick employees into transferring funds, sharing sensitive data, or changing payment details. Unlike traditional phishing, BEC often contains no malicious links or attachments, relying purely on social engineering. This skill covers detection techniques using email gateway rules, behavioral analytics, and financial process controls.\n\n\n## When to Use\n\n- When investigating security incidents that require detecting business email compromise\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- Email security gateway with BEC detection capabilities\n- Understanding of organizational financial processes and approval chains\n- Access to email logs and SIEM platform\n- Knowledge of social engineering tactics\n\n## Key Concepts\n\n### BEC Attack Types (FBI IC3 Classification)\n1. **CEO Fraud**: Attacker impersonates CEO, requests urgent wire transfer\n2. **Account Compromise**: Employee email compromised, used to request payments from vendors\n3. **False Invoice Scheme**: Fake invoices from \"vendor\" with changed bank details\n4. **Attorney Impersonation**: Impersonates legal counsel for urgent confidential transfers\n5. **Data Theft**: Requests W-2, tax forms, or PII from HR\n\n### Detection Indicators\n- Urgency and secrecy language (\"confidential\", \"do not discuss with others\")\n- New or changed payment instructions\n- Executive communication outside normal patterns\n- Display name matches executive but email domain differs\n- Reply-to address differs from From address\n- First-time communication pattern between sender and recipient\n- Request for gift cards or cryptocurrency\n\n## Workflow\n\n### Step 1: Configure BEC-Specific Email Rules\n- Flag emails with VIP display names from external domains\n- Detect financial keywords combined with urgency language\n- Alert on first-time sender to finance\u002Faccounting staff\n- Check for Reply-To domain mismatch\n\n### Step 2: Deploy Behavioral Analytics\n- Baseline normal communication patterns per user\n- Detect anomalous requests (unusual recipient, unusual time, unusual request type)\n- Monitor for email forwarding rule changes (T1114.003)\n\n### Step 3: Implement Financial Controls\n- Dual-authorization for wire transfers above threshold\n- Out-of-band verification for payment detail changes (phone callback)\n- Vendor payment change verification process\n- Finance team training on BEC red flags\n\n### Step 4: Monitor for Account Compromise\n- Detect impossible travel in email login locations\n- Alert on email forwarding rule creation\n- Monitor for mailbox delegation changes\n- Check for inbox rules hiding BEC-related emails\n\n## Tools & Resources\n- **Microsoft Defender for O365 Anti-BEC**: Built-in BEC detection\n- **Proofpoint Email Fraud Defense**: BEC-specific solution\n- **Abnormal Security**: AI-driven BEC detection\n- **FBI IC3 BEC Advisory**: https:\u002F\u002Fwww.ic3.gov\u002F\n- **FinCEN BEC Advisory**: Financial institution guidance\n\n## Validation\n- BEC detection rules trigger on test scenarios\n- Financial controls prevent unauthorized transfers in drills\n- Account compromise detection catches simulated attacks\n- Reduced BEC susceptibility in awareness assessments\n",{"name":5,"tags":60,"author":63,"domain":53,"license":15,"version":64,"mitre_f3":65,"nist_csf":93,"subdomain":98,"description":7,"nist_ai_rmf":99,"mitre_attack":102,"atlas_techniques":108,"d3fend_techniques":111},[37,44,43,45,42,61,62],"bec","fraud","mahipal","1.0",{"tactics":66,"version":71,"techniques":72},[67,68,69,70],"initial-access","positioning","monetization","stealth","1.1",[73,77,81,84,87,90],{"id":74,"name":75,"source":76,"tactic":70},"T1672","Email Spoofing","attack",{"id":78,"name":79,"source":80,"tactic":67},"F1032","Impersonate Official","f3",{"id":82,"name":83,"source":80,"tactic":68},"F1036","New Vendor Setup",{"id":85,"name":86,"source":80,"tactic":68},"F1005.006","Account Manipulation: Change of Payment Details",{"id":88,"name":89,"source":80,"tactic":69},"F1025.003","Electronic Funds Transfer: Wire Transfer",{"id":91,"name":92,"source":80,"tactic":70},"F1022","Delete Relevant Emails",[94,95,96,97],"PR.AT-01","DE.CM-09","RS.CO-02","DE.AE-02","phishing-defense",[100,101],"GOVERN-6.2","MAP-5.2",[103,104,105,106,107],"T1566.002","T1534","T1114.002","T1657","T1078.004",[109,110],"AML.T0052","AML.T0088",[112,113,114,115,116],"Restore Object","Restore Configuration","Application Configuration Hardening","Application Hardening","Disable Remote Access","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fdetecting-business-email-compromise",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":128,"prompt":138,"zipAvailable":139},[129,132,135],{"tool":130,"command":131},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill detecting-business-email-compromise",{"tool":133,"command":134},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill detecting-business-email-compromise",{"tool":136,"command":137},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill detecting-business-email-compromise","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdetecting-business-email-compromise\u002FSKILL.md",true,[141,147,152,158,162,166,172],{"path":142,"resourceType":143,"resourceTypeDesc":144,"sizeBytes":145,"sourceHtmlUrl":146},"assets\u002Ftemplate.md","ASSET","资产文件",1173,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdetecting-business-email-compromise\u002Fassets\u002Ftemplate.md",{"path":148,"resourceType":148,"resourceTypeDesc":149,"sizeBytes":150,"sourceHtmlUrl":151},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdetecting-business-email-compromise\u002FLICENSE",{"path":153,"resourceType":154,"resourceTypeDesc":155,"sizeBytes":156,"sourceHtmlUrl":157},"references\u002Fapi-reference.md","REFERENCE","参考文档",1966,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdetecting-business-email-compromise\u002Freferences\u002Fapi-reference.md",{"path":159,"resourceType":154,"resourceTypeDesc":155,"sizeBytes":160,"sourceHtmlUrl":161},"references\u002Fstandards.md",1427,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdetecting-business-email-compromise\u002Freferences\u002Fstandards.md",{"path":163,"resourceType":154,"resourceTypeDesc":155,"sizeBytes":164,"sourceHtmlUrl":165},"references\u002Fworkflows.md",2376,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdetecting-business-email-compromise\u002Freferences\u002Fworkflows.md",{"path":167,"resourceType":168,"resourceTypeDesc":169,"sizeBytes":170,"sourceHtmlUrl":171},"scripts\u002Fagent.py","SCRIPT","脚本",5582,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdetecting-business-email-compromise\u002Fscripts\u002Fagent.py",{"path":173,"resourceType":168,"resourceTypeDesc":169,"sizeBytes":174,"sourceHtmlUrl":175},"scripts\u002Fprocess.py",11965,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdetecting-business-email-compromise\u002Fscripts\u002Fprocess.py",[177,202,226,254,279,306],{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":184,"publishedAt":55},"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",[183],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[185,186,187,188,54,53,189,190,49,191,192,193,194,195,196,197,198,199,200,201],"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":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":209,"publishedAt":55},"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",[208],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[210,198,211,212,54,213,53,49,214,215,216,217,218,219,220,221,222,223,224,225],"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":227,"name":228,"nameZh":6,"description":229,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":230,"categories":231,"keywords":236,"publishedAt":55},"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",[232,235],{"categoryNo":233,"categoryName":234,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[220,237,238,239,240,53,241,242,214,243,244,245,246,247,248,249,250,251,252,253],"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":255,"name":256,"nameZh":6,"description":257,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":258,"categories":259,"keywords":261,"publishedAt":55},"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",[260],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[262,263,264,53,265,266,267,268,269,270,271,41,272,273,274,275,217,276,277,278],"windows","kape","triaging windows with kape","registry","browser","logs","windows-forensics","dfir","mft","mftecmd","prefetch","eric-zimmerman","digital-forensics","SET","collection","pecmd","artifact-collection",{"skillNo":280,"name":281,"nameZh":6,"description":282,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":283,"categories":284,"keywords":286,"publishedAt":55},"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",[285],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[287,288,289,53,290,291,292,293,294,295,296,297,298,299,300,301,302,303,304,305],"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":307,"name":308,"nameZh":6,"description":309,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":310,"categories":311,"keywords":313,"publishedAt":55},"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",[312],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[54,314,53,315,316,317,318,319,320,321,322,249,323,250,324,325,326,327,328,329],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]