[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADZCB66Q698SCYXJWWD8FR":3,"skill-same:01M6ADZCB66Q698SCYXJWWD8FR":166},{"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":91,"commitSha":92,"skillDirectory":93,"forksCount":94,"repositoryHtmlUrl":95,"repositoryHomepageUrl":96,"ownerHtmlUrl":97,"ownerBlogUrl":98,"ownerDescription":99,"updatedAt":100,"install":101,"resources":114},"01M6ADZCB66Q698SCYXJWWD8FR","building-phishing-reporting-button-workflow",null,"Implement a phishing report button (Microsoft 365 built-in Report button or third-party like KnowBe4\u002FCofense) in email clients with a SOAR-driven automated triage workflow that classifies reported emails, extracts IOCs, takes remediation actions, and gives feedback to reporters. Use when deploying user-reported phishing intake or automating triage of the resulting reporting mailbox.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",36078,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-phishing-reporting-button-workflow\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],"building phishing reporting button workflow","workflow","phishing","reporting","actions","microsoft-365","security-awareness","phishing-reporting","awareness","email-security","email","security","website","intake","create","development","pr","implement","soar","cybersecurity","2026-11-10 10:12:30",false,"---\nname: building-phishing-reporting-button-workflow\ndescription: Implement a phishing report button (Microsoft 365 built-in Report button\n  or third-party like KnowBe4\u002FCofense) in email clients with a SOAR-driven automated\n  triage workflow that classifies reported emails, extracts IOCs, takes remediation\n  actions, and gives feedback to reporters. Use when deploying user-reported phishing\n  intake or automating triage of the resulting reporting mailbox.\ndomain: cybersecurity\nsubdomain: phishing-defense\ntags:\n- phishing-reporting\n- email-security\n- incident-response\n- security-awareness\n- outlook\n- microsoft-365\n- soar\nmitre_attack:\n- T1566.001\n- T1566.002\n- T1598.003\n- T1204.001\n- T1534\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\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\n---\n# Building Phishing Reporting Button Workflow\n\n## Overview\nA phishing reporting button empowers users to flag suspicious emails directly from their email client, creating a critical feedback loop between end users and the security operations center. Microsoft's built-in Report button is now the recommended approach, replacing the deprecated Report Message and Report Phishing add-ins. When combined with automated triage using SOAR platforms, reported emails can be classified, IOCs extracted, and remediation actions taken within minutes. Organizations with effective phishing reporting programs see 70%+ report rates in phishing simulations.\n\n\n## When to Use\n\n- When deploying or configuring building phishing reporting button workflow 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- Microsoft 365 or Google Workspace with administrative access\n- SOAR platform or automation capability (Microsoft Sentinel, Splunk SOAR, Cortex XSOAR)\n- Dedicated reporting mailbox for phishing submissions\n- Email security gateway with message retraction capability\n- Security awareness training platform for feedback loop\n\n## Workflow\n\n### Step 1: Deploy Phishing Report Button\n- Enable Microsoft built-in Report button via Security & Compliance Center\n- Configure user reported settings: route to reporting mailbox and Microsoft\n- For third-party: deploy KnowBe4 Phish Alert Button or Cofense Reporter\n- Verify button appears in Outlook desktop, web, and mobile clients\n- Configure report options: Report Phishing, Report Junk, Report Not Junk\n\n### Step 2: Build Automated Triage Pipeline\n- Configure reporting mailbox monitored by SOAR platform\n- Auto-extract IOCs from reported emails: URLs, attachments, sender info, headers\n- Submit URLs to VirusTotal, URLScan.io for reputation check\n- Submit attachments to sandbox for dynamic analysis\n- Check sender against known threat intelligence feeds\n- Auto-classify: confirmed phishing, spam, simulation, legitimate\n\n### Step 3: Implement Response Actions\n- Confirmed phishing: auto-retract from all inboxes, block sender domain\n- Confirmed spam: move to junk for all recipients\n- Simulation email: mark as correctly reported, credit user\n- Legitimate email: return to inbox, notify reporter\n- Generate IOC report for threat intelligence team\n\n### Step 4: Create Feedback Loop\n- Send automated thank-you response to reporter within 5 minutes\n- Include classification result when analysis completes\n- Track reporter accuracy and engagement metrics\n- Recognize top reporters in monthly security newsletter\n- Feed reporting metrics into security awareness training program\n\n### Step 5: Measure and Optimize\n- Track mean time to triage (target: under 10 minutes automated)\n- Monitor report volume trends and false positive rates\n- Measure user reporting rate in phishing simulations\n- Report on confirmed threats caught by user reports vs. gateway\n- Optimize automation rules based on classification accuracy\n\n## Tools & Resources\n- **Microsoft Report Button**: Built-in Outlook phishing reporting\n- **Cofense Reporter + Triage**: Enterprise phishing reporting and automated analysis\n- **KnowBe4 Phish Alert Button**: Integrated reporting with simulation platform\n- **Microsoft Sentinel**: SOAR automation for triage workflow\n- **Proofpoint CLEAR**: Closed-loop email analysis and response\n\n## Validation\n- Report button visible and functional across all Outlook platforms\n- Reported email arrives in dedicated mailbox within 60 seconds\n- Automated triage classifies test phishing email correctly\n- Auto-retraction removes confirmed phishing from all inboxes\n- Reporter receives feedback notification with classification\n- Metrics dashboard shows report volume and accuracy trends\n","# Building Phishing Reporting Button Workflow\n\n## Overview\nA phishing reporting button empowers users to flag suspicious emails directly from their email client, creating a critical feedback loop between end users and the security operations center. Microsoft's built-in Report button is now the recommended approach, replacing the deprecated Report Message and Report Phishing add-ins. When combined with automated triage using SOAR platforms, reported emails can be classified, IOCs extracted, and remediation actions taken within minutes. Organizations with effective phishing reporting programs see 70%+ report rates in phishing simulations.\n\n\n## When to Use\n\n- When deploying or configuring building phishing reporting button workflow 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- Microsoft 365 or Google Workspace with administrative access\n- SOAR platform or automation capability (Microsoft Sentinel, Splunk SOAR, Cortex XSOAR)\n- Dedicated reporting mailbox for phishing submissions\n- Email security gateway with message retraction capability\n- Security awareness training platform for feedback loop\n\n## Workflow\n\n### Step 1: Deploy Phishing Report Button\n- Enable Microsoft built-in Report button via Security & Compliance Center\n- Configure user reported settings: route to reporting mailbox and Microsoft\n- For third-party: deploy KnowBe4 Phish Alert Button or Cofense Reporter\n- Verify button appears in Outlook desktop, web, and mobile clients\n- Configure report options: Report Phishing, Report Junk, Report Not Junk\n\n### Step 2: Build Automated Triage Pipeline\n- Configure reporting mailbox monitored by SOAR platform\n- Auto-extract IOCs from reported emails: URLs, attachments, sender info, headers\n- Submit URLs to VirusTotal, URLScan.io for reputation check\n- Submit attachments to sandbox for dynamic analysis\n- Check sender against known threat intelligence feeds\n- Auto-classify: confirmed phishing, spam, simulation, legitimate\n\n### Step 3: Implement Response Actions\n- Confirmed phishing: auto-retract from all inboxes, block sender domain\n- Confirmed spam: move to junk for all recipients\n- Simulation email: mark as correctly reported, credit user\n- Legitimate email: return to inbox, notify reporter\n- Generate IOC report for threat intelligence team\n\n### Step 4: Create Feedback Loop\n- Send automated thank-you response to reporter within 5 minutes\n- Include classification result when analysis completes\n- Track reporter accuracy and engagement metrics\n- Recognize top reporters in monthly security newsletter\n- Feed reporting metrics into security awareness training program\n\n### Step 5: Measure and Optimize\n- Track mean time to triage (target: under 10 minutes automated)\n- Monitor report volume trends and false positive rates\n- Measure user reporting rate in phishing simulations\n- Report on confirmed threats caught by user reports vs. gateway\n- Optimize automation rules based on classification accuracy\n\n## Tools & Resources\n- **Microsoft Report Button**: Built-in Outlook phishing reporting\n- **Cofense Reporter + Triage**: Enterprise phishing reporting and automated analysis\n- **KnowBe4 Phish Alert Button**: Integrated reporting with simulation platform\n- **Microsoft Sentinel**: SOAR automation for triage workflow\n- **Proofpoint CLEAR**: Closed-loop email analysis and response\n\n## Validation\n- Report button visible and functional across all Outlook platforms\n- Reported email arrives in dedicated mailbox within 60 seconds\n- Automated triage classifies test phishing email correctly\n- Auto-retraction removes confirmed phishing from all inboxes\n- Reporter receives feedback notification with classification\n- Metrics dashboard shows report volume and accuracy trends\n",{"name":5,"tags":52,"author":55,"domain":46,"license":15,"version":56,"mitre_f3":57,"nist_csf":79,"subdomain":84,"description":7,"mitre_attack":85},[34,36,53,33,54,32,45],"incident-response","outlook","mahipal","1.0",{"tactics":58,"version":63,"techniques":64},[59,60,61,62],"reconnaissance","resource-development","initial-access","stealth","1.1",[65,69,72,75],{"id":66,"name":67,"source":68,"tactic":59},"T1598","Phishing for Information","attack",{"id":70,"name":71,"source":68,"tactic":61},"T1660","Phishing",{"id":73,"name":74,"source":68,"tactic":62},"T1672","Email Spoofing",{"id":76,"name":77,"source":78,"tactic":60},"F1020.002","Create Fake Materials: Fake Website","f3",[80,81,82,83],"PR.AT-01","DE.CM-09","RS.CO-02","DE.AE-02","phishing-defense",[86,87,88,89,90],"T1566.001","T1566.002","T1598.003","T1204.001","T1534","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fbuilding-phishing-reporting-button-workflow",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":102,"prompt":112,"zipAvailable":113},[103,106,109],{"tool":104,"command":105},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill building-phishing-reporting-button-workflow",{"tool":107,"command":108},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill building-phishing-reporting-button-workflow",{"tool":110,"command":111},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill building-phishing-reporting-button-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-phishing-reporting-button-workflow\u002FSKILL.md",true,[115,121,125,130,136,140,144,148,152,158,162],{"path":116,"resourceType":117,"resourceTypeDesc":118,"sizeBytes":119,"sourceHtmlUrl":120},"assets\u002Fexample_asset.txt","ASSET","资产文件",865,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fregulatory-affairs-head\u002Fassets\u002Fexample_asset.txt",{"path":122,"resourceType":117,"resourceTypeDesc":118,"sizeBytes":123,"sourceHtmlUrl":124},"assets\u002Ftemplate.md",945,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-phishing-reporting-button-workflow\u002Fassets\u002Ftemplate.md",{"path":126,"resourceType":126,"resourceTypeDesc":127,"sizeBytes":128,"sourceHtmlUrl":129},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-phishing-reporting-button-workflow\u002FLICENSE",{"path":131,"resourceType":132,"resourceTypeDesc":133,"sizeBytes":134,"sourceHtmlUrl":135},"references\u002Fapi-reference.md","REFERENCE","参考文档",1835,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-phishing-reporting-button-workflow\u002Freferences\u002Fapi-reference.md",{"path":137,"resourceType":132,"resourceTypeDesc":133,"sizeBytes":138,"sourceHtmlUrl":139},"references\u002Feu-mdr-submission-guide.md",3272,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fregulatory-affairs-head\u002Freferences\u002Feu-mdr-submission-guide.md",{"path":141,"resourceType":132,"resourceTypeDesc":133,"sizeBytes":142,"sourceHtmlUrl":143},"references\u002Ffda-submission-guide.md",3931,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fregulatory-affairs-head\u002Freferences\u002Ffda-submission-guide.md",{"path":145,"resourceType":132,"resourceTypeDesc":133,"sizeBytes":146,"sourceHtmlUrl":147},"references\u002Fstandards.md",1333,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-phishing-reporting-button-workflow\u002Freferences\u002Fstandards.md",{"path":149,"resourceType":132,"resourceTypeDesc":133,"sizeBytes":150,"sourceHtmlUrl":151},"references\u002Fworkflows.md",1878,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-phishing-reporting-button-workflow\u002Freferences\u002Fworkflows.md",{"path":153,"resourceType":154,"resourceTypeDesc":155,"sizeBytes":156,"sourceHtmlUrl":157},"scripts\u002Fagent.py","SCRIPT","脚本",7320,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-phishing-reporting-button-workflow\u002Fscripts\u002Fagent.py",{"path":159,"resourceType":154,"resourceTypeDesc":155,"sizeBytes":160,"sourceHtmlUrl":161},"scripts\u002Fprocess.py",10765,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-phishing-reporting-button-workflow\u002Fscripts\u002Fprocess.py",{"path":163,"resourceType":154,"resourceTypeDesc":155,"sizeBytes":164,"sourceHtmlUrl":165},"scripts\u002Fregulatory_tracker.py",8223,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fregulatory-affairs-head\u002Fscripts\u002Fregulatory_tracker.py",[167,192,216,243,269,296],{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":174,"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",[173],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[175,176,177,178,38,46,179,180,43,181,182,183,184,185,186,187,188,189,190,191],"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":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":199,"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",[198],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[200,188,201,202,38,203,46,43,204,205,206,207,208,209,210,211,212,213,214,215],"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":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":220,"categories":221,"keywords":226,"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",[222,225],{"categoryNo":223,"categoryName":224,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[210,227,228,229,230,46,231,232,204,233,234,53,235,236,237,238,239,240,241,242],"backup","recovery","validating backup integrity for recovery","testing","infrastructure","validation","compliance","hash-verification","ransomware","cryptocurrency","detection","t1078","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":244,"name":245,"nameZh":6,"description":246,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":247,"categories":248,"keywords":250,"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",[249],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[251,252,253,46,254,255,256,257,258,259,260,261,262,263,264,265,207,266,267,268],"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":270,"name":271,"nameZh":6,"description":272,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":273,"categories":274,"keywords":276,"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",[275],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[277,278,279,46,280,281,282,283,284,285,286,287,288,289,290,291,292,293,294,295],"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":297,"name":298,"nameZh":6,"description":299,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":300,"categories":301,"keywords":303,"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",[302],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[38,304,46,305,306,307,308,309,310,311,312,238,313,239,314,315,316,317,318,319],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]