Awareness

Business Email Compromise: Why Every Suspicious Email Report Is an Intelligence Opportunity

· Regonance Cybersecurity · 10 min read

Business email compromise is the costliest form of cybercrime reported to law enforcement worldwide, and it bypasses nearly every technical control an organisation can deploy. BEC emails carry no malware, no malicious links, and no detectable payload — they rely on trust, timing, and impersonation. The only reliable detection mechanism is the employee who senses something is wrong and reports it. When that report is captured, preserved, and analysed alongside other reports, it stops being a single alert and starts being intelligence — revealing the attacker's campaign, targets, and infrastructure before financial loss occurs.

This article explains how BEC works, why technical controls fail against it, and how a structured reporting process turns every suspicious email report into an opportunity to disrupt an attack.

What Makes BEC Different from Phishing

Phishing casts a wide net — thousands of generic emails with malicious links or attachments. Technical controls catch phishing at scale by scanning for known indicators: malicious URLs, suspicious attachments, domain reputation.

BEC is targeted. The attacker researches the organisation, identifies who authorises payments, who processes invoices, who trusts which vendors. The resulting email is crafted to look like a legitimate business communication from a known party. It asks for a specific action — approve this invoice, update these bank details, wire this payment — using language and context that fits the recipient's daily workflow.

What a typical BEC email contains:

  • A spoofed or compromised sender address matching a known contact
  • Correct names, project references, or transaction details
  • An urgent but plausible request for a financial action
  • No malicious links, no attachments, no technical payload

What a typical BEC email does not contain:

  • Spelling errors or grammatical mistakes (especially in AI-generated variants)
  • Suspicious URLs or domains
  • Executable attachments
  • Anything that triggers a malware scanner or email security gateway

This is why BEC is fundamentally a human-detection problem. The email passes every automated check because, technically, there is nothing wrong with it. The only thing wrong is the intent — and only a human familiar with the business context can detect that.

The Human Sensor Network

Every employee who handles email — which is every employee — is a potential BEC sensor. When those sensors are connected to a structured reporting process, the organisation gains a detection capability that no tool can replicate.

The sensor network works in three ways:

1. Individual detection. A single employee notices that a payment request from a vendor uses a slightly different email domain, or that the CEO's tone in a wire transfer request does not match their usual communication style. The employee reports it. The security team investigates, confirms BEC, and blocks the attack before any money moves.

2. Pattern detection across reports. Multiple employees report emails from what appear to be different senders, but investigation reveals they share infrastructure — the same sending IP, similar domain registration patterns, or coordinating timing. These individual reports, analysed together, reveal a coordinated campaign targeting the organisation.

3. Intelligence extraction. The preserved emails from a BEC campaign — complete with headers, sender details, and content — provide indicators of compromise that can be shared with industry peers, reported to law enforcement, and used to proactively block future attempts.

Without a structured reporting process, none of this happens. The employee who senses something wrong deletes the email or processes the request. The campaign continues unseen.

From Report to Intelligence: The Three Dimensions

The Every Report Matters methodology frames the value of suspicious email reports across three dimensions. BEC illustrates all three at their sharpest:

Knowledge

Each BEC report teaches the organisation something about how it is being targeted. Which departments are receiving BEC attempts? Which vendor relationships are being exploited? What level of research has the attacker conducted? Over time, the accumulation of this knowledge informs strategic decisions about which business processes need additional verification controls.

Response

Each BEC report that reaches the security team triggers a response: verify the request through an alternative channel, alert the targeted department, block the sender, check whether similar emails reached other employees. The speed and quality of this response improves with every iteration. Organisations that handle one BEC report well handle the next one faster.

Intelligence

The aggregate of BEC reports — analysed for common infrastructure, timing patterns, targeting preferences, and evolution of social engineering techniques — produces actionable threat intelligence. This intelligence can predict where the next attack will come from, which vendor relationships are most likely to be exploited, and how the attacker adapts when initial attempts fail.

AI-Generated BEC: The 2026 Challenge

The emergence of AI-generated content has fundamentally changed the BEC threat landscape. Historically, BEC emails from non-native speakers contained subtle language anomalies that attentive employees could detect. AI eliminates this signal entirely.

What AI adds to BEC:

  • Fluent, natural language in any language and any business register
  • Personalisation drawn from publicly available information (LinkedIn, company websites, press releases)
  • Contextual awareness — references to real projects, real transactions, real deadlines
  • The ability to generate variations rapidly, allowing attackers to adjust their approach based on what works

What AI does not change: BEC still requires the attacker to impersonate a trusted party and request a specific action. The social engineering model is the same — the execution is now more convincing.

This shift has a direct implication for reporting culture: the traditional training model of "look for spelling mistakes and generic greetings" no longer works. Employees must be trained to report emails that feel uncertain, not just emails that look wrong. The threshold for reporting must be: "I'm not 100% sure this is legitimate" — not "I can see a red flag."

How Reporting Fits Regulatory Compliance

A successful BEC attack often triggers regulatory reporting obligations:

  • DORA (4 hours): A fraudulent wire transfer resulting from BEC is a major ICT incident for financial entities — the 4-hour notification clock starts at classification
  • NIS2 (24 hours): BEC causing significant financial loss or operational disruption triggers the 24-hour early warning for essential and important entities
  • GDPR (72 hours): BEC that leads to exposure of personal data (from compromised email accounts or shared documents) triggers the 72-hour breach notification
  • CRA (24 hours): If BEC exploits a vulnerability in a digital product (e.g., weak email authentication), the manufacturer may have reporting obligations under Article 14

A structured reporting process that captures BEC attempts — including those that are caught before they succeed — creates the documentation and evidence base needed for all four regulatory notification streams.

Building a BEC-Resilient Reporting Process

1. Lower the reporting threshold. BEC emails do not look malicious — they look like normal business communications with something slightly off. Train employees to report any payment request, account change, or financial instruction that triggers even mild uncertainty.

2. Implement out-of-band verification. For financial transactions above a defined threshold, establish a mandatory verification step: call the requester on a known phone number (not one provided in the email) to confirm the instruction. Make this a policy, not a suggestion.

3. Preserve every BEC report. Even unsuccessful BEC attempts have intelligence value. The attacker's infrastructure, targeting choices, and social engineering techniques are captured in the email — but only if the email is preserved with its full headers rather than deleted.

4. Analyse patterns across reports. Individual BEC attempts may appear unrelated. Correlation analysis across multiple reports — looking for shared sending infrastructure, similar timing, common targeting — reveals the campaign behind the individual emails.

5. Feed intelligence back to employees. When analysis of reported emails reveals a BEC campaign, share the findings (sanitised of sensitive details) with the workforce: "We've identified a campaign impersonating [vendor]. If you receive [type of request], report it immediately." This closes the intelligence loop and makes reporting tangibly valuable.

Frequently Asked Questions


This article is part of the Every Report Matters knowledge series by Regonance Cybersecurity. For the complete methodology and implementation guidance, explore the Reporting Readiness Kit, the Complete Reporting Playbook, or the Organisational Implementation Package.

Related articles:

Download the free Every Report Matters Methodology Brief → Download (email required)

Download the free Every Report Matters Methodology Brief

The reporting gap, the 9-stage lifecycle, and why EU regulation now makes this urgent. 11 pages.

We publish practical cybersecurity reporting articles. No spam. Unsubscribe with one click.