Skip to content
cccskills
FreePublished on GitHub

building-phishing-reporting-button-workflow

Set up an email reporting button and an automated security response workflow. Classify reported messages, extract attack indicators, remove confirmed phishing emails, and send feedback to the people who reported them.

OriginalShow the original description

Implement a phishing report button (Microsoft 365 built-in Report button or third-party like KnowBe4/Cofense) 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.

Works withOutlook

Run score Not tested

See how to install

Good for

  • Deploying a phishing reporting button in Outlook
  • Automating triage of a dedicated reporting mailbox
  • Retracting confirmed phishing emails across inboxes
  • Sending classification results to reporters

Files included (8)

  • SKILL.md5.1 KB
  • assets/template.md945 B
  • LICENSE11.0 KB
  • references/api-reference.md1.8 KB
  • references/standards.md1.3 KB
  • references/workflows.md1.8 KB
  • scripts/agent.py7.1 KB
  • scripts/process.py10.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Assess exposure of Windows secrets protected by DPAPI, the operating system’s data protection service, during authorized security tests. Guide examination and decryption of saved credentials and browser data using available user sessions, credentials, or backup keys.

  • Assessing saved credential exposure in authorized tests
  • Examining collected DPAPI files offline
  • Reviewing protected browser and RDP credentials
mukul975/Anthropic-Cybersecurity-Skills34.9KUpdated Aug 31, 2026

Assess Shadow Credentials account takeover during authorized Active Directory testing. Examine permissions that allow public key registration, validate authentication without a password reset, and document credential cleanup, detection opportunities, and access control changes needed for remediation.

  • Assessing risky permissions identified in BloodHound
  • Validating account takeover without resetting a password
  • Generating directory change records during security exercises
mukul975/Anthropic-Cybersecurity-Skills34.9KUpdated Aug 31, 2026

Prepare for CMMC Level 2, a cybersecurity certification for defense contractors. Define the systems handling controlled information, review security requirements, calculate the SPRS assessment score, and organize remediation plans and evidence into a readiness report.

  • Define the assessment scope for systems handling controlled information
  • Calculate an SPRS score and prioritize unmet security requirements
  • Prepare security plans, remediation milestones, and assessment evidence
mukul975/Anthropic-Cybersecurity-Skills34.9KUpdated Aug 31, 2026

Create disk images for investigations using dd or dcfldd on Linux. The workflow covers write protection, bit-for-bit copying, hash checks to verify integrity, and documentation of the acquisition process.

  • Preserving a suspect drive before investigation
  • Creating evidence copies of USB devices or memory cards
  • Verifying that a disk image matches its source
mukul975/Anthropic-Cybersecurity-Skills34.9KUpdated Aug 31, 2026

Review Active Directory permissions with ldap3, a Python library for directory queries. Identify excessive access granted to non-administrative accounts, explain potential privilege escalation paths, and produce a JSON report with affected objects and remediation recommendations.

  • Auditing excessive Active Directory permissions
  • Investigating privilege escalation paths from ordinary accounts
  • Reporting affected objects and permission remediation recommendations
mukul975/Anthropic-Cybersecurity-Skills34.9KUpdated Aug 31, 2026

Inspect suspicious Android APK files without running them. Analyze permissions, app components, suspicious code patterns, and network indicators, then produce a JSON risk report to support malware triage and detection rule development.

  • Triage suspicious APK files without running them
  • Inspect dangerous permission combinations and suspicious API calls
  • Extract network indicators for malware detection rules
mukul975/Anthropic-Cybersecurity-Skills34.9KUpdated Aug 31, 2026

See all skills by mukul975

Report a problem with this skill