Skip to content

Home Topics Email Security Management Business email compromise

Email Security Management · Business email compromise

Business email compromise (BEC) and GDPR and ePrivacy compliance in the European Union

Short answer

GDPR requires a lawful basis (usually consent) for marketing email and documented consent records. Business email compromise (BEC) supports compliance by making sender identity verifiable and recipient choices enforceable.

What GDPR and ePrivacy requires#

GDPR requires a lawful basis (usually consent) for marketing email and documented consent records.

What business email compromise (BEC) is#

BEC is a targeted attack where an attacker impersonates an executive or vendor to redirect payments or extract data, often from a legitimate compromised mailbox rather than a spoofed one.

Why it matters#

BEC causes more financial loss than any other cybercrime category, and it frequently passes authentication because the mailbox is real.

How business email compromise (BEC) supports GDPR and ePrivacy compliance#

Regulators and recipients need to identify who sent a message and trust that opt-out mechanisms work. Business email compromise (BEC) contributes by bEC causes more financial loss than any other cybercrime category, and it frequently passes authentication because the mailbox is real.

Implementation steps#

  1. Require MFA on all mailboxes and disable legacy authentication protocols.
  2. Alert on new inbox rules that forward or delete mail, a common attacker persistence step.
  3. Verify payment changes by phone using a known number, never the one in the email.
  4. Flag external mail with display names matching internal staff.

Frequently asked questions#

How is BEC different from phishing?

Phishing casts wide for credentials; BEC is targeted social engineering for money, often using a real hijacked account.

Keep reading on Business email compromise