[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HCJBK3TB0W85XQE8MS5XRT":3,"skill-same:01M6HCJBK3TB0W85XQE8MS5XRT":127},{"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":70,"commitSha":71,"skillDirectory":72,"forksCount":73,"repositoryHtmlUrl":74,"repositoryHomepageUrl":6,"ownerHtmlUrl":75,"ownerBlogUrl":6,"ownerDescription":76,"updatedAt":77,"install":78,"resources":91},"01M6HCJBK3TB0W85XQE8MS5XRT","building-phishing-reporting-button-workflow",null,"Implement a phishing report button in email clients with automated triage workflow that analyzes user-reported suspicious emails and provides feedback to reporters.","HenriqueMC17\u002Fagente-core","HenriqueMC17","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206460478?v=4","01M6HB63HBBF18AC4H09XTB549","Henrique Monteiro Cardoso","01M6HB63NGSQXWKWCFWW2B20W0",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\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],"workflow","reporting","phishing","building phishing reporting button workflow","awareness","with","emails","incident","cm","feedback","t1566","phishing-reporting","outlook","suspicious","email-security","email","pr","implement","soar","cybersecurity","2026-11-10 10:12:30",false,"---\nname: building-phishing-reporting-button-workflow\ndescription: Implement a phishing report button in email clients with automated triage workflow that analyzes user-reported suspicious emails and provides feedback to reporters.\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\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\ncategory: building-phishing-reporting-button-workflow\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":56,"domain":46,"license":15,"version":57,"category":5,"nist_csf":58,"subdomain":63,"description":7,"mitre_attack":64},[38,41,53,54,39,55,45],"incident-response","security-awareness","microsoft-365","mahipal","1.0",[59,60,61,62],"PR.AT-01","DE.CM-09","RS.CO-02","DE.AE-02","phishing-defense",[65,66,67,68,69],"T1566.001","T1566.002","T1598.003","T1204.001","T1534","main","5eea5b3296f4673b5f481e8bcc1ba76281149f16","modules\u002Fbuilding-phishing-reporting-button-workflow",0,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core","https:\u002F\u002Fgithub.com\u002FHenriqueMC17","Qualquer tecnologia suficientemente avançada é indistinguível da mágica.","2026-09-28 22:40:38",{"source":8,"skillName":5,"commands":79,"prompt":89,"zipAvailable":90},[80,83,86],{"tool":81,"command":82},"npx","npx skills add HenriqueMC17\u002Fagente-core --skill building-phishing-reporting-button-workflow",{"tool":84,"command":85},"bunx","bunx skills add HenriqueMC17\u002Fagente-core --skill building-phishing-reporting-button-workflow",{"tool":87,"command":88},"pnpm","pnpm dlx skills add HenriqueMC17\u002Fagente-core --skill building-phishing-reporting-button-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-phishing-reporting-button-workflow\u002FSKILL.md",true,[92,98,103,109,113,117,123],{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"assets\u002Ftemplate.md","ASSET","资产文件",945,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-phishing-reporting-button-workflow\u002Fassets\u002Ftemplate.md",{"path":99,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-phishing-reporting-button-workflow\u002FLICENSE",{"path":104,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fapi-reference.md","REFERENCE","参考文档",1835,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-phishing-reporting-button-workflow\u002Freferences\u002Fapi-reference.md",{"path":110,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fstandards.md",1333,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-phishing-reporting-button-workflow\u002Freferences\u002Fstandards.md",{"path":114,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Fworkflows.md",1878,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-phishing-reporting-button-workflow\u002Freferences\u002Fworkflows.md",{"path":118,"resourceType":119,"resourceTypeDesc":120,"sizeBytes":121,"sourceHtmlUrl":122},"scripts\u002Fagent.py","SCRIPT","脚本",7320,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-phishing-reporting-button-workflow\u002Fscripts\u002Fagent.py",{"path":124,"resourceType":119,"resourceTypeDesc":120,"sizeBytes":125,"sourceHtmlUrl":126},"scripts\u002Fprocess.py",10765,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-phishing-reporting-button-workflow\u002Fscripts\u002Fprocess.py",[128,155,180,203,219,238],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":137,"publishedAt":47},"01M6HPFF0RCN0X6WT5EBSV71GY","validating-backup-integrity-for-recovery","Validate backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to ensure backups are reliable for disaster recovery and ransomware response scenarios.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[134],{"categoryNo":135,"categoryName":136,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[138,139,140,141,142,143,46,144,145,146,53,147,148,149,150,151,152,34,153,154],"integrity","backup","recovery","validating backup integrity for recovery","for","testing","validate","verification","hash-verification","ransomware","detection","t1078","t1490","disaster-recovery","restore","disaster recovery","ransomware response",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":47},"01M6HPFAWJVFK25Q33K3T7WQ8G","triaging-vulnerabilities-with-ssvc-framework","Triage and prioritize vulnerabilities using CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree framework to produce actionable remediation priorities.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[],[162,163,164,165,32,46,166,167,168,169,170,171,172,173,174,175,176,177,178,179],"vulnerabilities","framework","ssvc","triaging vulnerabilities with ssvc framework","triage and prioritize","CISA","vulnerability-management","risk-management","cvss","remediation","vulnerability","prioritization","decision-tree","prioritize","decision","priorities","actionable","tree",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":186,"publishedAt":47},"01M6HPF6JS9X72WP59094H3ASQ","triaging-security-incident","Performs initial triage of security incidents to determine severity, scope, and required response actions using the NIST SP 800-61r3 and SANS PICERL frameworks. Classifies incidents by type, assigns priority based on business impact, and routes...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident\u002FSKILL.md",[],[187,188,34,46,189,190,191,149,150,192,193,194,195,196,197,198,199,200,201,202],"security","triaging security incident","actions","soc","NIST","analysis","severity-classification","incident-triage","SANS-PICERL","SOC-operations","picerl","conversion","isolation","scope","impact","consistency",{"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":209,"publishedAt":47},"01M6HPF2EX6ZYNYYHKBRJN7GEF","triaging-security-incident-with-ir-playbook","Classify and prioritize security incidents using structured IR playbooks to determine severity, assign response teams, and initiate appropriate response procedures.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident-with-ir-playbook\u002FSKILL.md",[],[187,210,211,188,34,32,46,212,190,53,213,214,149,150,215,193,175,216,217,218],"playbook","triaging security incident with ir playbook","teams","IR-playbook","severity","classification","classify","incidents","initiate",{"skillNo":220,"name":221,"nameZh":6,"description":222,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":223,"categories":224,"keywords":225,"publishedAt":47},"01M6HPEY9XPGE7X95AG4XJFQAW","triaging-security-alerts-in-splunk","Triages security alerts in Splunk Enterprise Security by classifying severity, investigating notable events, correlating related telemetry, and making escalation or closure decisions using SPL queries and the Incident Review dashboard. Use when...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-alerts-in-splunk\u002FSKILL.md",[],[187,226,227,228,229,230,46,231,232,233,190,234,149,37,235,236,196,35,34,237],"security alerts","splunk","triaging security alerts in splunk","alerts","review","siem","dashboard","search","correlation-search","notable-events","incident-review","de",{"skillNo":239,"name":240,"nameZh":6,"description":241,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":242,"categories":243,"keywords":244,"publishedAt":47},"01M6HPET6XGEPEJPN7V032JGZ0","tracking-threat-actor-infrastructure","Threat actor infrastructure tracking involves monitoring and mapping adversary-controlled assets including command-and-control (C2) servers, phishing domains, exploit kit hosts, bulletproof hosting, a","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftracking-threat-actor-infrastructure\u002FSKILL.md",[],[245,246,247,248,46,249,250,251,252,253,254,37,255,256,35,257,237,258,259,260],"infrastructure","tracking threat actor infrastructure","tracking","threat","monitoring","mitre-attack","threat-actor","threat-intelligence","command-and-control","dns","command","exploit","intelligence","domains","kit","hosts"]