Allow admins to configure the Report Message add-in to prevent phishing tests from being processed.
We send phishing tests to staff using a third-party vendor. If staff use the Microsoft Report Message add-on instead of the reporting add-on provided by our phish testing vendor, staff end up getting tagged as clicking the link (and assigned additional training) because Microsoft is automatically following links and opening attachments. This is the worst feedback loop; "punishing" staff for reporting a phishing email.
There are multiple ways the add-on could be improved to fix this.
1. Allow admins to remove the report phishing option so staff can still use the add-on to report spam/junk but not phishing (they would use our phish testing vendor's add-on for phishing).
2. Allow us to add information in the admin portal related to our phishing testing service to exclude messages sent from them. (X-header, IP's, etc.)
3. Allow Admins to configure the add-on send phishing emails ONLY to us and give us the option to report as phishing after Admins review the submission.
Please don't ask us to use your phishing test service. While it has some nice features, it isn't as good as the service we have. At this point we will probably disable the add-on all together which is a shame as we like it for spam reporting and are happy to give staff options when they work with our processes.
Craig Chambers
shared this idea
1 comment
-
Anonymous
commented
We completely agree this is a total disaster for us. Employees still click the Mark as Phishing button all the time and then it counts as a click for them when Microsoft looks into the email, and then we think the employee actually clicked on a phishing email. It was the same with Gmail. We might as well stop even trying to teach users about Phishing because we have no way to test and manage this since we can't get rid of the phishing button.