[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EFH2QS5RWECKAREGDAQFP0":3,"skill-same:01M7EFH2QS5RWECKAREGDAQFP0":105},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":69,"commitSha":70,"skillDirectory":71,"forksCount":72,"repositoryHtmlUrl":73,"repositoryHomepageUrl":6,"ownerHtmlUrl":74,"ownerBlogUrl":6,"ownerDescription":75,"updatedAt":76,"install":77,"resources":90},"01M7EFH2QS5RWECKAREGDAQFP0","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.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fbuilding-phishing-reporting-button-workflow\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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":24,"author":32,"domain":33,"license":15,"version":34,"mitre_f3":35,"nist_csf":57,"subdomain":62,"description":7,"mitre_attack":63},[25,26,27,28,29,30,31],"phishing-reporting","email-security","incident-response","security-awareness","outlook","microsoft-365","soar","mahipal","cybersecurity","1.0",{"tactics":36,"version":41,"techniques":42},[37,38,39,40],"reconnaissance","resource-development","initial-access","stealth","1.1",[43,47,50,53],{"id":44,"name":45,"source":46,"tactic":37},"T1598","Phishing for Information","attack",{"id":48,"name":49,"source":46,"tactic":39},"T1660","Phishing",{"id":51,"name":52,"source":46,"tactic":40},"T1672","Email Spoofing",{"id":54,"name":55,"source":56,"tactic":38},"F1020.002","Create Fake Materials: Fake Website","f3",[58,59,60,61],"PR.AT-01","DE.CM-09","RS.CO-02","DE.AE-02","phishing-defense",[64,65,66,67,68],"T1566.001","T1566.002","T1598.003","T1204.001","T1534","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fbuilding-phishing-reporting-button-workflow",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":78,"prompt":88,"zipAvailable":89},[79,82,85],{"tool":80,"command":81},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill building-phishing-reporting-button-workflow",{"tool":83,"command":84},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill building-phishing-reporting-button-workflow",{"tool":86,"command":87},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill building-phishing-reporting-button-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fbuilding-phishing-reporting-button-workflow\u002FSKILL.md",true,[91,97,101],{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fapi-reference.md","REFERENCE","参考文档",1835,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fbuilding-phishing-reporting-button-workflow\u002Freferences\u002Fapi-reference.md",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fstandards.md",1333,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fbuilding-phishing-reporting-button-workflow\u002Freferences\u002Fstandards.md",{"path":102,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fworkflows.md",1878,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fbuilding-phishing-reporting-button-workflow\u002Freferences\u002Fworkflows.md",[106,115,120,127,134,141],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":114},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":116,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":114},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":114},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":114},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":114},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":114},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]