Turning every "report phishing" click into a lesson
PRDPDF · 2 pages
Problem, users, principles, success metrics, scope, known failures, risks and rollout.
Employees who report suspicious emails rarely learn anything from it, and simple filters either miss look-alike threats or falsely reassure. A tool that says "looks fine" without evidence trains people to trust the wrong messages.
Employees
Unsure whether an email is safe and don't know which signs to look for
Security Awareness Teams
Reports pile up without becoming teaching moments
SOC Analysts
Triage time spent on reports a clear explanation could resolve
An explainable triage engine that checks look-alike domains, display-name and reply-to mismatches, deceptive links, risky attachments, urgency and credential requests — returning a three-level verdict with reasons and a plain-language lesson for each sign.
Missed-threat rate dropped from 43.5% to 8.7% versus a keyword baseline, with 0% false alarms on legitimate mail and every ambiguous message sent to review. Two residual misses (a compromised internal account, pure social engineering) are kept visible to show the limits of content-only rules.
Want to discuss this project?
I'd love to walk you through the decisions, trade-offs, and what I'd do differently.