How to tell if a BEC attack was caught automatically or by a human
Security controls often fail to flag Business Email Compromise cases because attackers lurk silently in mailboxes for weeks without triggering outbound spam alerts. This leaves security teams unable to determine whether automated defenses or manual human review actually caught the breach.
Core Friction Pattern
Analysis of 3 peer accounts across online developer and community forums reveals that “How to tell if a BEC attack was caught automatically or by a human” repeatedly surfaces due to edge-case mismatches between standard defaults and real-world environments. Standard troubleshooting frequently falls short, compelling practitioners to develop custom workarounds.
+5 alternative community-tested workarounds cataloged below.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
Found another way around this?
Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.
How to tell if a BEC attack was caught automatically or by a human
- 1relying on IAM suspicious sign-in reportsDid this help you?
- 2checking outbound anti-spam rules after bulk sendsDid this help you?
- 3using powershell to audit forwarding rules after user complaintsDid this help you?
- 4Searching audit logs using PowerShell or Purview for MailItemsAccessed eventsDid this help you?
- 5Manually inspecting inbox rules, hidden rules, and forwarding addressesDid this help you?
- 6Checking OAuth app consents under enterprise applicationsDid this help you?
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
“I caught one last year where someone was sitting in a mailbox for like six weeks just reading everything and setting up rules to hide replies from vendors. no outbound spam or anything just silently gathering contract details”source ↗
“We had the dumbest person person get access right after sign in check. Sat there for a week and had access to literal gold mine of stuff.”source ↗
“when you've dealt with BEC case, did email auth flagged it, or did it look totally normal and only a human caught it?”source ↗
Where this came up
People with this problem also raised
Related community dilemmas clustered by discussion consensus
Why are phishing emails bypassing Exchange Online Protection?
Clean phishing emails are being delivered straight to the inbox with no warning from Exchange Online Protection. These spoofs sail through primarily because of per-user whitelists. When a client allowlisted a sender years ago, it causes these malicious emails to bypass current filtering entirely.
Getting weird scam letters or emails from banks I don't use
People are receiving physical letters and emails from unfamiliar financial companies and banks claiming missed payments or unknown inquiries using outdated personal information. This causes immediate panic and forces people to spend hours trying to figure out if their information has been compromised or if it is just a phishing scam.
Why does IT send fake phishing emails that stress us out?
Simulated phishing tests interrupt the workday and trigger unnecessary stress, especially when they use manipulative lures like teacher appreciation emails. Punishing employees with mandatory quizzes just for deleting or marking a test as spam stops people from focusing on their actual work.
Why do users keep clicking phishing links?
End-users frequently ignore explicit security instructions, blindly entering their credentials simply because a message says 'click here'. Attackers exploit this inattention and bypass traditional red flags like poor grammar by using AI, embedding QR codes in Word documents, and spamming Teams messages. This behavior forces administrators to aggressively block even legitimate files containing QR codes just to prevent breaches.
Automated notification emails only show IDs instead of client names
Automated alerts only include cryptic internal IDs rather than recognizable names, forcing consultants to manually dig through every customer organization to figure out which account the message refers to. This turns a simple notification into a frustrating treasure hunt that wastes hours of troubleshooting time reconnecting integrations.
How to stop an email spam bomb attacking a user inbox
An ongoing email spam bomb floods a user's inbox with hundreds of random newsletter and phishing messages a day in multiple languages. This relentless wave buries legitimate communications and overwhelms standard inbox management, leaving administrators searching for effective filtering and mitigation strategies.