How To Deal With Business Email Compromise
How To Deal With Business Email Compromise
WHITE PAPER
Executive Summary
Business email compromise (BEC) attacks have not engendered the same level of
notoriety as ransomware attacks, but rank in combination as one of the most
financially devastating and common types of cybercrimes against organizations.
Many organizations are ill-prepared to address the threat of BEC and lack sufficient
protections across people, process, and technology factors. This white paper
reports on an in-depth survey exploring current readiness and confidence to deal
with the threat of BEC, highlights solutions that have been specifically designed to
counteract BEC threats, and outlines a series of best practices to strengthen
defenses against BEC threats.
KEY TAKEAWAYS
This white paper references data from an in-depth survey conducted in November
and December 2021 of 119 professionals in IT, cybersecurity, risk, and compliance
roles. Respondents work for mid-sized and large organizations (average employees
14,388, median 1,599) across multiple industries. All respondents know how their
organization is addressing or planning to address the threat of BEC.
What is BEC?
In this section, we explore the nature of the BEC threat, profile several successful
BEC attacks, and look at the cost of BEC incidents.
WHAT IS BEC?
BEC attacks are a specific type of phishing attack. They rely on targeting (i.e., going
after a specific person or role type in an organization) and normally seek monetary
payment as a direct outcome. Types of BEC attacks include diverting payment on a
valid invoice to a fraudulent bank account, submitting a fake invoice for payment,
diverting employee payroll to a fraudulent bank account, and using impersonation
of senior executives to lend credibility to plausible but irregular requests (i.e.,
paying a large sum to a new bank account to secure a merger or acquisition target).
BEC also includes gift card fraud and romance scams. BEC types of attack have also
been called man-in-the-email attacks, email account compromise (EAC), and wire
fraud. Employees at all levels of an organization are targeted by BEC attacks.
BEC attacks differ from many other forms of cyberthreats, relying almost entirely on BEC attacks
social engineering to trigger human susceptibility to plausible requests. Social
engineering tricks include establishing rapport (pretexting), promising personal
differ from
benefit, and invoking urgency. BEC attacks do not generally carry malware, include many other
weaponized links, or seek to compromise email account credentials. By definition,
BEC attacks rely on the compromise of business email—a normal and highly used
forms of
channel for business communication—by inserting fraudulent email messages into cyberthreats,
a stream of regular ones. Examples of different types of BEC attacks include:
relying almost
• An impersonated email account entirely on
A threat actor finds out the name of the CFO at your organization from LinkedIn
and registers a personal email account in their name with Google or Microsoft.
social
Email messages can then be sent to your accounts department from engineering to
[email protected], beginning with a plausible explanation, such as
“I’m travelling and don’t have access to my corporate email, but could you trigger human
please wire an urgent payment to XYZ Corp who we are trying to buy.” susceptibility to
• An impersonated domain plausible
A threat actor registers a domain name that looks like the domain name of the
targeted company or one of their trusted vendors. While the text of the requests.
domain is clearly different, many people miss the subtle differences in lookalike
domains—microsoft.com versus microsofl.com or amazon.com vs
amazom.com. Lookalike domain name variants are hard to spot with only a
cursory glance and it is unsurprising that people regularly miss the differences.
• A compromised email account (the EAC variant of BEC attacks)
A senior executive at a vendor company is the victim of a phishing attack that
results in the compromise of his or her email account credentials. Until the
credential compromise is detected, the threat actor can send email messages
impersonating the senior executive—such as new messages requesting
payment to a different bank account or re-submitting invoices already sent
with new payment details. For organizations using Microsoft 365 or Google
Workspace for email, the compromise of account credentials also gives access
to the user’s documents in OneDrive/SharePoint or Google Drive, which can
include invoices or invoice templates that can be altered before sending.
• Almost 20,000 complaints in the United States in 2020 costing $1.8 billion
In the United States, BEC attacks rank at the most expensive type of the 33
categories of internet crime tracked by the FBI.9 For 2020 (the latest year for
which full data is available), the FBI received almost 20,000 complaints of
successful BEC scams, with losses of more than $1.8 billion. This was 43% of the
total cost for all internet crime types reported to the FBI, and over three times
more costly than the second most expensive type of internet crime. The
average direct cost of each BEC attack was $96,372, or around 85% higher than
the direct cost estimated from our survey (see page 6). The 2020 numbers
were up significantly from the $215 million in losses and 2,126 incidents
recorded by the FBI from October 2013 to December 2014.10
• 95% of BEC attacks cost between $250 and $984,855
Drawing on a global data set, Verizon’s Data Breach Investigations Report for
2021 found that 95% of BEC attacks cost between $250 and $984,855 per
incident.11 That means 2.5% of incidents cost less than $250, and 2.5% cost
more than $984,855 per incident.
64%
Two-fifths of organizations reported that no BEC attacks reached any of these three
states (36%) or gave no response to this question (6%). With the prevalence of BEC
attacks across organizations and industries, we are inclined to interpret these
answers as non-disclosure rather than zero incidents.
Organizations
MOST ORGANIZATIONS ARE UNSURE OF THEIR ABILITY TO SAFEGUARD that are at best
FUNDS AFTER A BEC ATTACK
Two-thirds of organizations do not have high confidence that a BEC attack only somewhat
“tomorrow” would result in no funds being paid to a fraudulent bank account. The confident that a
majority of this grouping have a “somewhat” level of confidence, and the
remainder have no confidence. See Figure 2. BEC attack
would not result
Figure 2
Confidence that a BEC Attack Would Not Result in Funds Being Paid to a in funds being
Fraudulent Bank Account paid to a
Percentage of respondents
fraudulent bank
account
Figure 3
Estimated Direct and Indirect Costs of a Successful BEC Incident
Percentage of respondents
Individual BEC
incidents often
cost too little to
trigger help
Source: Osterman Research (2022) from law
enforcement
This distribution of expectations gives a conservative weighted average of $52,115
of direct costs and $62,607 of indirect costs per incident, or a total of $114,762 per agencies and
successful BEC incident. Based on the average distribution of incidents per year, insurance
therefore, the average amount at risk from BEC attacks per organization is $1.6
million per year. This is comprised of: companies.
• Cost at risk from attacks that were almost successful
$849,239 for 7.4 attacks per organization that were caught by organizational
processes.
• Cost at risk from attacks that failed due to a lucky chance
$516,429 for 4.5 attacks per organization that were paid but the money was
returned by a lucky chance. When the lucky chance fails, however, these funds
are more likely to be lost too.
• Cost of attacks that succeeded and the funds were not recovered
$252,476 for 2.2 attacks per organization that were paid, and the funds were
not recovered.
This level of cost is pesky in the sense that individual incidents may cost too little to
trigger help from law enforcement agencies and insurance companies, but multiple
attacks in combination represent a costly incursion on corporate funds.
Figure 4
Confidence in Achieving Discovery and Recovery Outcomes After a BEC Attack
Percentage of respondents indicating “confident” or “highly confident”
73%
Organizations
that are not
confident in
their ability to
recover 100% of
funds paid to a
Source: Osterman Research (2022) fraudulent bank
The ability to recover 100% of funds paid to a fraudulent bank account is the account after a
outcome with the lowest confidence level. Only one in four believe they could
BEC attack
recover 100% of funds. For the others, there is a foreboding sense of “the money is
gone and not coming back.” This is consistent with several of the examples quoted
above, e.g., One Treasure Island, Scoular. Some organizations have been successful
in recovering a portion of the lost funds, e.g., Ubiquiti Networks was able to quickly
recover $8.1 million of the $46.7 million and had another $6.8 million under
protection, but did not know how it would recover the final $31.8 million.
Figure 5
Confidence in the Sufficiency of Current Cybersecurity Protections
Percentage of respondents indicating “confident” or “highly confident”
71%
Organizations
that cannot rely
on current
technology
solutions to stop
BEC attacks
from reaching
Finance and
Accounts
Payable staff
The last three items in Figure 5 indicate that the traditional technical solutions
organizations are currently relying on are insufficient in the fight against BEC
attacks. For instance:
The traditional technical solutions that are currently deployed are insufficient
because organizations are relying on cybersecurity solutions and approaches that
are ineffective against BEC attacks. Two of the top five protections rated highly for
effectiveness offer little to no value in protecting against BEC. Both anti-malware
(rated by respondents as 56% effective, in third place) and a secure email gateway
(54%, fifth place) focus on identifying and blocking malicious content and code in Organizations
messages, attachments, and links rather than identifying malicious intent. Both are relying on
protections are essential components in a wider cybersecurity posture for
addressing other types of email-borne threats, but are ineffective against BEC cybersecurity
attacks specifically. The only approach in the top five that specifically focuses on solutions and
addressing BEC threats is employee training (which 59% of respondents say is
“effective” or “extremely effective”)—which is an essential component of an anti- approaches that
BEC security posture but does not enact any effective technical protections to are ineffective
reduce the number of BEC threats from getting through to employees. See Figure 6.
against BEC
Figure 6 attacks.
Efficacy of Solutions and Approaches in Protecting Against BEC Attacks: Top Five
Percentage of respondents indicating “effective” or “extremely effective”
Figure 7
Confidence in the Ability of Groups and Individuals to Recognize BEC Attacks
Percentage of respondents indicating “confident” or “highly confident”
48%
Organizations
that are not
confident that
Accounts
Payable staff in
the Finance
department can
recognize a BEC
attack
Source: Osterman Research (2022)
While some BEC attacks can be easily identified through poor spelling, bad
grammar, and other visual indications that the message does not come from the
person who claims to have sent it, other BEC attacks include none of these easy
signals. For example, it is more difficult to identify a BEC threat when a threat actor
has compromised a vendor’s email account and replies to a current conversation
about payment of an invoice. Likewise, BEC threats that come from lookalike
domains hosted on highly reputable email infrastructures, such as Microsoft 365
and Google Workspace, are difficult to identify with only a cursory glance, especially
if the message has been written by a native language speaker.
In addition to reliance on ineffective cybersecurity tools, there are two reasons why
organizations appear to be unable to rely on key people and groups to recognize
and prevent BEC attacks:
Figure 9
Effectiveness of Current Employee Training on Cybersecurity in General and BEC
Threats Specifically
Percentage of respondents
The conflation of these factors creates a perfect storm where threat actors are
likely to step up the frequency and cost of BEC attacks. It is unlikely that we have
seen the peak of BEC attacks yet, either in number of incidents or overall losses to
the economy.
Figure 10
Level of Concern About Types of Cyberattacks
Percentage of respondents indicating “concerned” or “extremely concerned”
2/4
Two of the top
four types of
cyberattacks that
organizations
are most
concerned about
involve targeted
attacks by email.
Phishing attacks have been widely implicated as the initial threat vector for a range
of subsequent cyberattacks, including ransomware13 and breaches of customer and
employee data (e.g., through account credential compromise providing access to
email accounts, confidential files, and cloud services). BEC attacks are a subset of
targeted phishing attacks that focus on direct theft of financial resources.
Figure 11
Importance of Protecting Against BEC Attacks: Three Year View
Percentage of respondents indicating “important” or “extremely important”
80%
Organizations
indicating that
protecting
against BEC
Source: Osterman Research (2022)
attacks in 2022
This elevation in importance is to be expected given the growing frequency and cost is of high
of BEC attacks, along with the overall poor state of preparedness to counteract such
attacks.
importance
Figure 12
Relative Importance of People, Process, and Technology in BEC Protections
Percentage of respondents indicating “important” or “extremely important”
When great
technology is
used by well-
trained people
according to
optimal process
designs, the
likelihood of
Source: Osterman Research (2022)
identifying and
While the relative importance weighting varies between the three categories, none
stand alone. Technical solutions that block or identify BEC attacks provide signals to
defeating BEC
employees who need to be trained to look for highlighted and other hidden signals, attacks is high.
and both culminate in how organizational processes are designed to function.
When great technology is used by well-trained people according to optimal process
designs, the likelihood of identifying and defeating BEC attacks is high. When any
category is operating below standard, the other two must work much harder to
achieve the same level of efficacy, if that is even possible.
Figure 13
Efficacy of Solutions and Approaches in Protecting Against BEC Attacks
Percentage of respondents indicating “effective” or “extremely effective”
While both explanations could be true, the wider survey data indicates the second
is more likely to be correct. Throughout the survey, respondents repeatedly said
that their current technical solutions were ineffective against a variety of BEC attack
types, and have rated both anti-malware and a secure email gateway as two of the
most effective protections against BEC. This does not make sense. These
protections by design cannot provide high efficacy against BEC attacks.
Some vendors include more advanced in-line warnings in email messages that
surface insights on communication patterns and message construction that are
better designed to warn employees of BEC threats. Examples include: End-to-end
• Warning when an email message has unusual address characteristics encryption
BEC attacks can include abnormal address characteristics, such as when a implements
cybercriminal alters the reply-to address of an email message so it will be sent
to a different address than the address it purports to come from. An in-line security controls
warning such as “this email will be sent to someone you have never on messages and
communicated with before” alerts the recipient to exercise caution.
attachments
• Warning when an email is received from a new sender
Masquerade attempts that combine a sender’s name that the recipient during both
normally interacts with and an impersonated address can be detected through transmission
in-line warnings, e.g., “this is the first email received from this sender.”
and storage.
• Warning when an email message includes common social engineering tricks
Requests for urgency and secrecy are two frequently used social engineering
tricks. In-line coaching and awareness on the presence of such tricks in an email
message can be signaled through warnings such as “this message contains
words that indicate urgency.”
Vendors that can detect multiple warning signals and abnormalities in an email
message can automatically quarantine suspected BEC messages before they reach a
user’s inbox.
Figure 14
Priority of Protecting Against BEC Attacks Relative to All Security Priorities
Percentage of respondents
62%
Organizations
ranking
Source: Osterman Research (2022)
protections
In other recent surveys by Osterman Research, respondents have assigned high
priority to implementing zero trust,14 discovering sensitive data,15 preventing data
against BEC
exfiltration,16 and assessing the extended cybersecurity threat surface for attacks as one of
organizations with subsidiaries.17 Across multiple separate surveys, therefore,
respondents are indicating heightened focus on initiatives to improve baseline
their top five
cybersecurity protections. priorities.
Given the commonality of BEC attacks and the cumulative number and cost of
incidents seen each year, including protecting against BEC threats as a top-10
priority appears a fair response. In addition, given the general low state of current
preparedness across multiple dimensions, a specific focus on BEC is more than
appropriate. We encourage organizations to act on the heightened priority assigned
to protecting against BEC attacks.
Figure 15
Relative Influence of Various Factors in Safeguarding Funds in a BEC Attack
Percentage of respondents indicating “influential” or “extremely influential”
65%
Organizations
where currently
used anti-BEC
technology
would probably
not stop a BEC
attack from
Source: Osterman Research (2022)
being delivered
Only 35% of respondents indicated that the anti-BEC technology they are currently to an end user
using for stopping BEC attacks from being delivered to end users would be
“influential” or “extremely influential” in preventing the payment of funds to a
fraudulent bank account. This reflects the challenge of accurately identifying
malicious intent in messages that do not include attachments or links with
malicious content, code, or behavioral attributes. For many organizations, the anti-
BEC technology they are currently using for stopping the delivery of BEC attacks is
insufficient, and any BEC threats that are delivered to an inbox must then rely on
people or process for identification and neutralization. We have already explored
the need for organizations to select and deploy much more effective anti-BEC
technology to protect against BEC attacks, and organizations that lack sufficient
protections need to address this shortcoming.
Figure 16 compares the priority of providing training to various people and groups
specifically on BEC threats with their corresponding efficacy at detecting BEC
attempts. Except for the CFO role, efficacy always trails priority by a few percentage
points, indicating that increasing the priority (proxied by frequency and intensity of
effective training) has a flow-on effect to efficacy at detecting BEC. The other
takeaway from Figure 16 is that the efficacy of employees at detecting BEC based
on currently used training approaches is not as high as it needs to be. Organizations
should evaluate alternative training approaches to increase detection efficacy. Targeted
training for
Figure 16
Priority on Providing Cybersecurity Training Specifically on BEC Threats to Various employees and
People and Groups and Efficacy at Detecting BEC Threats managers on
Percentage of respondents indicating “priority” or “essential priority” and
percentage of respondents indicating “confident” or “highly confident” BEC attacks
strengthens the
organization’s
defenses against
the threat of BEC.
Training approaches that increase detection efficacy are likely to have the following
characteristics:
Figure 17
Actions Taken to Harden Processes for Changes to Invoices Due
Percentage of respondents
Three-fifths of
organizations
have taken two
or three actions
to harden
invoicing
processes
Source: Osterman Research (2022)
against BEC
Respondents had the option of noting other actions taken as well. Two respondents threats.
left notes about other actions, and both focused on identity verification.
However, many organizations have not taken enough actions to harden invoicing
processes. Those that lack the more widely adopted safeguards outlined in Figure
17 would be well-advised to step up current protections.
There are also other ways of strengthening internal process controls for financial
transactions, but many organizations have shied away from implementing these.
For example, requiring alignment between a quote issued by a vendor, a purchase
order and number issued by the organization, and the invoice issued by the vendor
decreases the likelihood that fake invoices will be authorized and paid. The trifecta
benefits internal financial planning and protections, and is also a strong practice for
reducing the threat of BEC attacks.
Figure 18
Actions Taken to Harden Processes for Changes to Employee Payroll
Percentage of respondents
Organizations
still relying on
email for
changing
employee
Source: Osterman Research (2022) payroll details
should adopt
Respondents had the option of noting other actions taken as well. Two respondents
left notes about other actions. The first said that any change “must be done in newer anti-BEC
person,” and the second was verification of the request was required but safeguards.
“specifically not [by] phone call or SMS.”
Conclusion
BEC is a costly cyberthreat for organizations around the world, and many are ill-
prepared with their current people, process, and technology posture to fend off
attacks. Many organizations appear to be relying on technology that was not
designed to identify and protect against BEC attacks, have people who lack training
to recognize and counteract BEC threats, and use weak processes that enable BEC
threats to become incidents. Except for BEC incidents at the more costly end of the
spectrum, confidence in securing help from law enforcement is low, and gaining
insurance coverage for losses is equally problematic. Organizations need to take
urgent action to strengthen current processes targeted by BEC, deploy new
technology that specifically identifies and neutralizes BEC attacks, and elevate
preparedness of executives, managers, and employees to stop BEC in its tracks.
Sponsored by SonicWall
SonicWall is well known for its market-changing Boundless Cybersecurity vision.
This approach safeguards organizations with seamless protection that stops the
most evasive cyberattacks across boundless exposure points and increasingly
remote, mobile and cloud-enabled workforces. Boundless Cybersecurity upends www.sonicwall.com
traditional thinking by empowering organizations to know the unknown, unify @SonicWall
visibility and control, and disrupt TCO expectations. SonicWall has nurtured a
reputation of professionalism, innovation and integrity that spans nearly three +1 888 557 6642
decades. SonicWall has helped protect and secure more than 500,000 customers in Contact us
215 countries and territories.
No part of this document may be reproduced in any form by any means, nor may it be distributed without
the permission of Osterman Research, nor may it be resold or distributed by any entity other than
Osterman Research, without prior written authorization of Osterman Research.
Osterman Research does not provide legal advice. Nothing in this document constitutes legal advice, nor
shall this document or any software product or other offering referenced herein serve as a substitute for
the reader’s compliance with any laws (including but not limited to any act, statute, regulation, rule,
directive, administrative order, executive order, etc. (collectively, “Laws”)) referenced in this document. If
necessary, the reader should consult with competent legal counsel regarding any Laws referenced herein.
Osterman Research makes no representation or warranty regarding the completeness or accuracy of the
information contained in this document.
THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND. ALL EXPRESS OR IMPLIED
REPRESENTATIONS, CONDITIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, ARE DISCLAIMED, EXCEPT TO THE EXTENT
THAT SUCH DISCLAIMERS ARE DETERMINED TO BE ILLEGAL.
1 James Rundle, Hackers Stole $650,000 From Nonprofit and Got Away, Showing Limits to Law
https://www.wkyt.com/content/news/Scott-County-Schools-victim-of-37-million-scam-509017341.html
3 Todd Niall, America’s Cup: How Team New Zealand Was Scammed out of $2.8m in Hungarian Fraud,
https://www.csoonline.com/article/2884339/omahas-scoular-co-loses-17-million-after-spearphishing-
attack.html
5 Krebs on Security, Tech Firm Ubiquiti Suffers $46M Cyberheist, August 2015, at
https://krebsonsecurity.com/2015/08/tech-firm-ubiquiti-suffers-46m-cyberheist/
6 Therese Poletti, The strange case of a money-transfer firm's missing millions, January 2015, at
https://www.marketwatch.com/story/the-strange-case-of-a-money-transfer-firms-missing-millions-
2015-01-07
7 FBI, Leader of Fraud Ring Sentenced: Protect Yourself from Business Email Compromise Schemes,
https://www.infosecurity-magazine.com/news/spanish-police-arrest-three-in-10m/
9 FBI, FBI Releases the Internet Crime Complaint Center 2020 Internet Crime Report, Including COVID-19
https://www.ic3.gov/Media/PDF/Y2015/PSA150122.pdf
11 Verizon, 2021 Data Breach Investigations Report, May 2021, at
https://www.verizon.com/business/resources/reports/dbir/
12 Aon, 2021 Cyber Security Risk Report, at https://www.aon.com/2021-cyber-security-risk-report/
13 Osterman Research, How to Reduce the Risk of Phishing and Ransomware, March 2021, at
https://ostermanresearch.com/2021/03/17/orwp_0336/
14 Osterman Research, Why Zero Trust is Important, November 2021, at
https://ostermanresearch.com/2021/11/10/orwp_0348/
15 Osterman Research, Sensitive Data Discovery Rises as a Top Concern for Organizations, September
2021, at https://ostermanresearch.com/2021/09/22/activenav-sensitive-data-discovery/
16 Osterman Research, Preventing Data Exfiltration: Introducing Anti-Data Exfiltration (ADX), October
2021, at https://ostermanresearch.com/2021/10/26/orwp_0347/
17 Osterman Research, Managing Risk from Subsidiaries: Goals, Friction, and Failure, September 2021, at
https://ostermanresearch.com/2021/09/23/cycognito-subsidiary-risk/
18 Ry Crozier, BOQ Tries to Pin BEC Blame on a Branch Manager, February 2021, at
https://www.itnews.com.au/news/boq-tries-to-pin-bec-blame-on-a-branch-manager-560557