building-phishing-reporting-button-workflow
Implement a phishing report button in email clients with automated triage workflow that analyzes user-reported suspicious emails and provides feedback to reporters.
Best use case
building-phishing-reporting-button-workflow is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Implement a phishing report button in email clients with automated triage workflow that analyzes user-reported suspicious emails and provides feedback to reporters.
Teams using building-phishing-reporting-button-workflow should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/building-phishing-reporting-button-workflow/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How building-phishing-reporting-button-workflow Compares
| Feature / Agent | building-phishing-reporting-button-workflow | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Implement a phishing report button in email clients with automated triage workflow that analyzes user-reported suspicious emails and provides feedback to reporters.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Building Phishing Reporting Button Workflow ## Overview A 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. ## When to Use - When deploying or configuring building phishing reporting button workflow capabilities in your environment - When establishing security controls aligned to compliance requirements - When building or improving security architecture for this domain - When conducting security assessments that require this implementation ## Prerequisites - Microsoft 365 or Google Workspace with administrative access - SOAR platform or automation capability (Microsoft Sentinel, Splunk SOAR, Cortex XSOAR) - Dedicated reporting mailbox for phishing submissions - Email security gateway with message retraction capability - Security awareness training platform for feedback loop ## Workflow ### Step 1: Deploy Phishing Report Button - Enable Microsoft built-in Report button via Security & Compliance Center - Configure user reported settings: route to reporting mailbox and Microsoft - For third-party: deploy KnowBe4 Phish Alert Button or Cofense Reporter - Verify button appears in Outlook desktop, web, and mobile clients - Configure report options: Report Phishing, Report Junk, Report Not Junk ### Step 2: Build Automated Triage Pipeline - Configure reporting mailbox monitored by SOAR platform - Auto-extract IOCs from reported emails: URLs, attachments, sender info, headers - Submit URLs to VirusTotal, URLScan.io for reputation check - Submit attachments to sandbox for dynamic analysis - Check sender against known threat intelligence feeds - Auto-classify: confirmed phishing, spam, simulation, legitimate ### Step 3: Implement Response Actions - Confirmed phishing: auto-retract from all inboxes, block sender domain - Confirmed spam: move to junk for all recipients - Simulation email: mark as correctly reported, credit user - Legitimate email: return to inbox, notify reporter - Generate IOC report for threat intelligence team ### Step 4: Create Feedback Loop - Send automated thank-you response to reporter within 5 minutes - Include classification result when analysis completes - Track reporter accuracy and engagement metrics - Recognize top reporters in monthly security newsletter - Feed reporting metrics into security awareness training program ### Step 5: Measure and Optimize - Track mean time to triage (target: under 10 minutes automated) - Monitor report volume trends and false positive rates - Measure user reporting rate in phishing simulations - Report on confirmed threats caught by user reports vs. gateway - Optimize automation rules based on classification accuracy ## Tools & Resources - **Microsoft Report Button**: Built-in Outlook phishing reporting - **Cofense Reporter + Triage**: Enterprise phishing reporting and automated analysis - **KnowBe4 Phish Alert Button**: Integrated reporting with simulation platform - **Microsoft Sentinel**: SOAR automation for triage workflow - **Proofpoint CLEAR**: Closed-loop email analysis and response ## Validation - Report button visible and functional across all Outlook platforms - Reported email arrives in dedicated mailbox within 60 seconds - Automated triage classifies test phishing email correctly - Auto-retraction removes confirmed phishing from all inboxes - Reporter receives feedback notification with classification - Metrics dashboard shows report volume and accuracy trends
Related Skills
securing-github-actions-workflows
This skill covers hardening GitHub Actions workflows against supply chain attacks, credential theft, and privilege escalation. It addresses pinning actions to SHA digests, minimizing GITHUB_TOKEN permissions, protecting secrets from exfiltration, preventing script injection in workflow expressions, and implementing required reviewers for workflow changes.
secure-workflow-guide
Guide you through Trail of Bits' 5-step secure development workflow. Runs Slither scans, checks special features (upgradeability/ERC conformance/token integration), generates visual security diagrams, helps document security properties for fuzzing/verification, and reviews manual security areas. (project, gitignored)
performing-red-team-phishing-with-gophish
Automate GoPhish phishing simulation campaigns using the Python gophish library. Creates email templates with tracking pixels, configures SMTP sending profiles, builds target groups from CSV, launches campaigns, and analyzes results including open rates, click rates, and credential submission statistics for security awareness assessment.
performing-phishing-simulation-with-gophish
GoPhish is an open-source phishing simulation framework used by security teams to conduct authorized phishing awareness campaigns. It provides campaign management, email template creation, landing pag
performing-adversary-in-the-middle-phishing-detection
Detect and respond to Adversary-in-the-Middle (AiTM) phishing attacks that use reverse proxy kits like EvilProxy, Evilginx, and Tycoon 2FA to bypass MFA and steal session tokens.
investigating-phishing-email-incident
Investigates phishing email incidents from initial user report through header analysis, URL/attachment detonation, impacted user identification, and containment actions using SOC tools like Splunk, Microsoft Defender, and sandbox analysis platforms. Use when a reported phishing email requires full incident investigation to determine scope and impact.
implementing-soar-playbook-for-phishing
Automate phishing incident response using Splunk SOAR REST API to create containers, add artifacts, and trigger playbooks
implementing-patch-management-workflow
Patch management is the systematic process of identifying, testing, deploying, and verifying software updates to remediate vulnerabilities across an organization's IT infrastructure. An effective patc
implementing-google-workspace-phishing-protection
Configure Google Workspace advanced phishing and malware protection settings including pre-delivery scanning, attachment protection, spoofing detection, and Enhanced Safe Browsing.
implementing-anti-phishing-training-program
Security awareness training is the human layer of phishing defense. An effective anti-phishing training program combines regular simulations, interactive learning modules, metric tracking, and positiv
hunting-for-spearphishing-indicators
Hunt for spearphishing campaign indicators across email logs, endpoint telemetry, and network data to detect targeted email attacks.
executing-phishing-simulation-campaign
Executes authorized phishing simulation campaigns to assess an organization's susceptibility to email-based social engineering attacks. The tester designs realistic phishing scenarios, builds credential harvesting infrastructure, sends targeted phishing emails, and tracks open rates, click-through rates, and credential submission rates to measure human security awareness. Activates for requests involving phishing simulation, social engineering assessment, email security testing, or security awareness measurement.