Business Email Compromise: Recognizing and Stopping the Threat Before Money or Data Is Lost
This article is general information and not legal advice.
Business email compromise is one of the most damaging cyber threats because it targets people, trust and everyday business processes—not just technology. In this article, you will learn how business email compromise works, what warning signs to watch for, and how to reduce risk with practical controls such as phishing-resistant MFA, payment verification procedures and employee reporting habits.
What Is Business Email Compromise?
Business email compromise, often called BEC, is a type of cyberattack where a criminal uses email, social engineering or account takeover to trick an organization into sending money, disclosing sensitive information or changing business processes.
Unlike traditional malware attacks, BEC often does not require a malicious attachment or obvious link. The attacker may impersonate a trusted executive, vendor, employee, customer, attorney, auditor or healthcare partner. The message may look ordinary and businesslike.
Common BEC goals include:
- Convincing finance staff to wire funds to a fraudulent bank account
- Redirecting vendor payments to an attacker-controlled account
- Persuading payroll to change an employee’s direct deposit details
- Requesting W-2, employee, patient or customer data
- Gaining access to email accounts for further fraud
- Using a compromised mailbox to launch additional phishing attacks
- Pressuring staff to buy gift cards or transfer funds quickly
BEC is especially dangerous because it exploits normal business activity. An invoice change, urgent executive request or vendor payment update may not appear suspicious unless employees know what to look for and the organization has strong verification controls.
Why Business Email Compromise Is Hard to Stop
Many organizations invest heavily in antivirus, firewalls and endpoint security, but BEC often bypasses traditional defenses. The attacker may not send malware. The email may come from a legitimate but compromised account. The request may be carefully written based on real business relationships.
BEC is difficult to stop for several reasons:
It Exploits Trust
People are more likely to act when a message appears to come from someone they know. If the email seems to come from the CEO, CFO, a major customer or a long-standing vendor, employees may not challenge the request.
It Uses Business Context
Attackers often research organizations before sending messages. They may review public websites, job titles, press releases, social media profiles, procurement portals or prior email threads. This helps them craft messages that sound credible.
It Creates Urgency
BEC messages frequently include pressure such as:
- “This must be handled today.”
- “I’m in a meeting and can’t talk.”
- “Do not delay this payment.”
- “This is confidential.”
- “We are changing banks effective immediately.”
Urgency is designed to make employees bypass normal controls.
It May Involve Real Email Accounts
If an attacker compromises a real mailbox, the email may pass many technical checks. Messages from a vendor’s actual account or an executive’s real mailbox are more convincing than spoofed messages.
It Blends With Phishing and Ransomware Risk
BEC is not the same as ransomware, but the risks often overlap. A compromised email account can be used to steal credentials, distribute malicious links, access shared files or support later ransomware activity. For organizations seeking ransomware prevention for small business environments, stopping credential theft and email compromise is a critical part of the strategy.
Common Types of Business Email Compromise
BEC is not a single technique. It is a family of fraud patterns. Understanding the most common types helps employees and leaders recognize suspicious situations.
Executive Impersonation
An attacker pretends to be a senior leader and asks an employee to take action. The request may involve a wire transfer, payment approval, purchase of gift cards or release of sensitive information.
Example warning signs:
- The request is unusually urgent
- The executive says they are unavailable by phone
- The message asks the employee to keep the request confidential
- The wording or tone is slightly unusual
- The sender address is similar but not identical to the real address
Vendor Invoice Fraud
The attacker impersonates a vendor and requests a change to payment instructions. This may include a new bank account, routing number or payment portal.
Sometimes the attacker compromises a vendor mailbox and inserts themselves into a legitimate invoice thread. This can make the fraud very difficult to detect without an independent verification process.
Payroll Diversion
The attacker pretends to be an employee and asks payroll or HR to update direct deposit information. In some cases, the attacker has taken over the employee’s mailbox. In others, they use a lookalike email address.
Controls should require strong verification before changing payroll information, especially when the request originates by email.
Data Theft Requests
The attacker requests employee records, tax documents, patient information, customer data or other sensitive files. In healthcare environments, this may create privacy and compliance concerns if protected health information is involved.
Organizations subject to the HIPAA Rules should evaluate how email security, access controls, workforce training and incident response align with the HIPAA Security Rule, including administrative, physical and technical safeguards. Specific obligations can vary based on facts, contracts and applicable state law, so legal interpretation should be handled by qualified counsel.
Account Takeover
In an account takeover, the attacker gains access to a legitimate mailbox. They may monitor conversations, create forwarding rules, search for invoices, reset passwords or send phishing emails to contacts.
Account takeover is often the bridge between phishing and BEC. It can also expose sensitive information stored in email.
Attorney, Auditor or Regulator Impersonation
The attacker pretends to be an outside attorney, auditor, regulator or compliance contact. These messages may request payment, records or urgent cooperation.
The key defense is independent verification through trusted contact information—not information provided in the suspicious email.
Red Flags Employees Should Know
Employees do not need to become forensic investigators, but they do need to recognize common red flags.
Email Red Flags
Watch for messages that:
- Ask for payment, banking or payroll changes
- Use unusual urgency or secrecy
- Come from a slightly misspelled domain
- Use a personal email address for business activity
- Ask the recipient to bypass normal procedures
- Include unexpected attachments or links
- Refer to a prior conversation that did not happen
- Contain unusual grammar, phrasing or tone for that sender
- Arrive at an unusual time
- Request sensitive data that would not normally be shared by email
Process Red Flags
Also watch for business-process warning signs:
- A vendor changes bank details shortly before payment is due
- An executive requests a transfer outside normal approval channels
- A request avoids purchase order, invoice or approval systems
- A payment is split to avoid review thresholds
- The sender discourages phone verification
- The request comes during a holiday, travel period or end-of-quarter rush
- A new contact suddenly appears in an existing thread
Technical Red Flags
IT and security teams should watch for:
- New inbox forwarding rules
- Unexpected mailbox delegation
- Logins from unusual locations or devices
- Multiple failed login attempts
- Suspicious multi-factor authentication prompts
- OAuth application consent to unknown third-party apps
- Changes to email display names
- Creation of new mailbox rules that delete or hide messages
- Unusual email volume from one account
Practical Controls to Prevent Business Email Compromise
Stopping BEC requires layered controls. No single tool or policy is enough. The strongest programs combine secure identity, email defenses, financial controls, user training and rapid response.
1. Require Phishing-Resistant MFA
Multi-factor authentication, or MFA, requires users to provide more than one factor to sign in, such as a password plus a hardware key or authenticator prompt. MFA is essential, but not all MFA is equally strong.
Phishing-resistant MFA is designed to prevent attackers from stealing or replaying authentication factors through fake login pages or social engineering. Examples include FIDO2 security keys, platform passkeys and certificate-based authentication when properly implemented.
Less resistant methods, such as SMS codes or basic push notifications, are better than passwords alone but can still be vulnerable to phishing, SIM swapping, MFA fatigue attacks or real-time credential theft.
Action Steps
- Require MFA for all email, remote access, cloud and administrative accounts
- Prioritize phishing-resistant MFA for executives, finance, HR, IT administrators and anyone with access to sensitive data
- Disable legacy authentication methods that do not support MFA where feasible
- Monitor and alert on repeated MFA prompts or denied sign-in attempts
- Review conditional access policies for high-risk logins
- Have a documented process for lost or replaced MFA devices
- Train users to report unexpected MFA prompts immediately
Practical Example
If an employee receives a login approval prompt they did not initiate, they should not approve it. They should report it to IT or the security team immediately. Repeated unexpected prompts may indicate that an attacker has the user’s password and is trying to push their way into the account.
2. Strengthen Email Authentication
Email authentication helps receiving mail systems determine whether a message is authorized to come from a domain. The main controls are:
- SPF, or Sender Policy Framework
- DKIM, or DomainKeys Identified Mail
- DMARC, or Domain-based Message Authentication, Reporting and Conformance
These controls do not stop every BEC attempt, especially if a real account is compromised, but they help reduce domain spoofing and improve visibility.
Action Steps
- Inventory all systems that send email on behalf of your domain
- Configure SPF for approved senders
- Enable DKIM signing for legitimate mail sources
- Implement DMARC reporting to monitor domain abuse
- Move toward a stronger DMARC enforcement policy after testing
- Monitor lookalike domains that mimic your organization
- Ensure marketing, billing and third-party platforms are included in the configuration review
Important Note
DMARC configuration can affect legitimate email delivery if implemented incorrectly. Test carefully, review reports and coordinate with business owners before enforcing strict policies.
3. Use Secure Payment Verification Procedures
Finance controls are one of the most effective BEC defenses. The goal is to make it difficult for a single email to trigger a payment or bank account change.
Payment Verification Checklist
For new vendors or bank account changes:
- Require verification through a known, trusted phone number already on file
- Do not use phone numbers or links provided in the change request
- Require approval from more than one authorized person
- Confirm vendor changes through a supplier portal if one exists
- Document who verified the change, when and how
- Require additional review for high-value or urgent payments
- Use positive pay or similar bank fraud prevention services where appropriate
- Review payment batches before release
- Separate duties between request, approval and payment release
What to Avoid
Avoid relying only on email approvals for:
- Wire transfers
- ACH changes
- Vendor banking updates
- Payroll direct deposit changes
- Refund redirection
- Emergency payments
A simple callback procedure can prevent major losses, but only if employees are trained and empowered to use it.
4. Protect Executive, Finance and HR Accounts
Some accounts are more attractive to attackers. Executives, finance staff, HR employees and IT administrators should receive higher protection because their accounts can authorize payments, access employee data or control systems.
Recommended Controls
- Phishing-resistant MFA for high-risk roles
- Strong conditional access policies
- Reduced mailbox auto-forwarding privileges
- Alerts for unusual sign-ins
- Alerts for inbox rule creation
- Separate administrative accounts for IT staff
- Regular review of mailbox delegation and shared access
- Executive-specific security awareness briefings
- Strong password managers for business credentials
- Prohibition on password reuse across personal and business accounts
Executive Security Matters
Executives are frequent impersonation targets because their authority can pressure employees into bypassing normal controls. Leadership must model secure behavior by following verification procedures and supporting employees who question unusual requests.
5. Train Employees With Realistic Scenarios
Security awareness training should be practical, role-based and repeated. Annual training alone is rarely enough. Employees need to practice recognizing the kinds of BEC messages they may actually receive.
Training Topics
Include examples of:
- Fake executive requests
- Vendor bank change fraud
- Payroll diversion attempts
- Gift card scams
- Fake document-sharing links
- QR code phishing
- MFA fatigue attacks
- Lookalike domains
- Compromised vendor email threads
Role-Based Training
Different teams need different examples:
- Finance: wire transfers, invoice changes, urgent payments
- HR: direct deposit changes, employee records, tax documents
- Executives: impersonation, account protection, travel-related risks
- IT: account takeover indicators, mailbox rules, OAuth abuse
- Clinical and healthcare operations: patient data requests, vendor access, downtime procedures
- Front desk and administrative staff: invoice routing, document requests, caller verification
Reporting Culture
Employees should know how to report suspicious messages quickly. Reporting should be easy, encouraged and blame-free.
Consider:
- A dedicated phishing report button
- A monitored security inbox
- Clear escalation instructions
- Feedback to employees who report real threats
- Short reminders after major phishing trends are observed
If employees fear punishment for reporting a mistake, they may delay. Rapid reporting is often the difference between a contained incident and a major loss.
6. Monitor for Account Takeover
Because BEC often involves compromised mailboxes, detection is essential.
Account Takeover Indicators
Security teams should monitor for:
- New inbox rules that forward, delete or hide messages
- Login attempts from impossible travel patterns
- Access from anonymizing services or unusual geographies
- Suspicious OAuth application grants
- Unexpected mailbox forwarding to external addresses
- Sudden spikes in sent messages
- Password reset activity
- Changes to recovery email or phone number
- Messages sent to finance, HR or vendors shortly after login anomalies
Response Steps for Suspected Account Takeover
If an account may be compromised:
- Disable or block sign-in temporarily if appropriate.
- Reset the password.
- Revoke active sessions and refresh tokens.
- Review MFA methods and remove unauthorized devices.
- Check mailbox rules, forwarding and delegation.
- Review recent sent items, deleted items and audit logs.
- Identify any messages sent to internal or external recipients.
- Notify affected parties where appropriate.
- Preserve logs and evidence for investigation.
- Determine whether sensitive data was accessed or disclosed.
For regulated organizations, including healthcare entities and business associates, incident evaluation may require privacy, legal and compliance review. Breach notification obligations depend on the facts, applicable laws and contractual requirements.
7. Reduce Email Exposure of Sensitive Data
Email often contains more sensitive information than organizations realize. If an attacker compromises a mailbox, stored messages and attachments may become exposed.
Data Reduction Practices
- Limit sending sensitive data by email when secure portals are available
- Use encryption or secure messaging when appropriate
- Apply retention policies based on business and legal requirements
- Train users not to store passwords or access tokens in email
- Avoid emailing full bank details unless necessary and protected
- Use secure file-sharing platforms with access controls
- Restrict auto-forwarding to personal email accounts
- Review shared mailboxes and distribution lists regularly
In healthcare settings, protected health information should be handled according to applicable HIPAA Rules, state privacy laws, payer requirements and business associate agreements. Requirements vary, so organizations should confirm obligations with compliance leadership and qualified counsel.
8. Build BEC Into Your Incident Response Plan
An incident response plan should not focus only on malware or ransomware. BEC requires specific procedures because speed matters.
BEC Response Checklist
If a suspicious payment or email compromise is discovered:
- Preserve the suspicious email with full headers if possible
- Notify IT, security, finance and leadership
- Disable or secure compromised accounts
- Contact the bank immediately if funds were transferred
- Request recall or hold of fraudulent transactions if available
- Contact the receiving bank through appropriate channels
- Review related payments and vendor changes
- Search for similar messages across the email environment
- Identify affected internal and external recipients
- Document the timeline of events
- Preserve logs for investigation
- Determine whether sensitive data was accessed or disclosed
- Evaluate notification obligations with legal and compliance teams
- Update controls based on lessons learned
Who Should Be Involved?
A BEC response may require coordination among:
- IT and security
- Finance and accounting
- Legal counsel
- Compliance and privacy officers
- Executive leadership
- Human resources
- Banking partners
- Cyber insurance contacts, if applicable
- External incident response providers
- Law enforcement, where appropriate
Do not wait until an incident to decide who has authority to contact banks, approve containment actions or communicate with affected vendors.
9. Connect BEC Defense to Ransomware Prevention for Small Business
Small businesses often ask about ransomware prevention for small business operations, and rightly so. Ransomware can disrupt operations, expose sensitive data and create serious financial harm. But ransomware prevention is not only about backups and antivirus. It is also about preventing credential theft, phishing and account compromise.
BEC and ransomware commonly share risk factors:
- Weak passwords
- Lack of MFA
- Poor email filtering
- Untrained users
- Excessive privileges
- Unpatched systems
- Limited logging
- No tested response plan
- Inadequate vendor security review
Small Business Priority Controls
For small and mid-sized organizations, start with these high-impact actions:
- Require MFA for email and remote access.
- Use phishing-resistant MFA for privileged and financial roles where feasible.
- Back up critical data and test restoration.
- Patch operating systems, browsers and business applications.
- Use endpoint protection on all workstations and servers.
- Train employees on phishing and BEC scenarios.
- Require callback verification for payment changes.
- Disable legacy email authentication methods.
- Use least privilege for administrative access.
- Maintain an incident response contact list.
These steps reduce both BEC and ransomware exposure.
Hypothetical Example: A Vendor Payment Change Attempt
The following is a hypothetical example for illustration only.
A mid-sized healthcare services company receives an email that appears to come from a long-time medical supply vendor. The message is part of an existing invoice thread and says the vendor has changed banks. It includes new ACH instructions and asks that the next payment be sent to the updated account.
The accounts payable specialist notices that the wording is slightly different from the vendor’s usual style, but the email appears to come from the correct address. The payment is due the next day.
Instead of processing the change, the specialist follows company procedure:
- They do not reply to the email.
- They call the vendor using the phone number already stored in the company’s vendor master file.
- The vendor confirms that no banking change was requested.
- IT reviews the email headers and finds that the vendor’s account may have been compromised.
- Finance places a temporary hold on pending payments to that vendor until the correct instructions are reconfirmed.
- Security searches for similar messages and alerts employees to the attempted fraud.
- The vendor is advised to investigate its mailbox security.
The organization avoids sending funds to the attacker because the employee followed a simple independent verification process. The key control was not a complex tool—it was a clear procedure supported by training and management.
Technical Controls IT Teams Should Review
While business-process controls are essential, IT teams should also tune technical defenses.
Email Security Gateway or Cloud Email Protection
Review whether your email security tools can:
- Detect impersonation attempts
- Flag external senders
- Identify lookalike domains
- Analyze suspicious links and attachments
- Detect abnormal sending behavior
- Quarantine likely phishing messages
- Support user reporting and automated investigation
- Integrate with identity and endpoint tools
Identity and Access Management
Identity controls should include:
- MFA enforcement
- Conditional access policies
- Risk-based sign-in detection where available
- Privileged access management
- Separate admin accounts
- Regular access reviews
- Disablement of inactive accounts
- Strong joiner, mover and leaver processes
Logging and Alerting
At minimum, collect and review logs for:
- Email sign-ins
- Administrative changes
- Mailbox forwarding and rules
- MFA changes
- OAuth application grants
- Suspicious outbound email volume
- File access and sharing events
- Endpoint alerts
Logs are only useful if retained long enough and reviewed when alerts occur. Retention needs may vary by regulation, contract, cyber insurance requirements and business risk.
Endpoint and Browser Protection
BEC may begin through phishing pages, malicious attachments or credential-stealing malware. Endpoint protection should be deployed and monitored across laptops, desktops and servers.
Consider:
- Endpoint detection and response where appropriate
- Browser protection against known malicious sites
- Application control for high-risk environments
- Local administrator restrictions
- Patch management
- Disk encryption for portable devices
Governance: Make BEC Prevention a Business Control
BEC prevention is not just an IT project. It is a business risk management issue involving finance, HR, legal, compliance, operations and leadership.
Policies to Review
Review and update policies for:
- Wire transfers
- ACH payments
- Vendor onboarding
- Vendor bank changes
- Payroll direct deposit changes
- Email use
- Access control
- Incident response
- Data classification
- Remote work
- Use of personal email
- Third-party risk management
Approval Thresholds
Define when additional approval is required. For example:
- New vendor setup
- Any vendor bank change
- Payments above a defined threshold
- International transfers
- Emergency payments
- Payments requested outside normal systems
- Refunds to a new account
- Payroll changes requested by email
The exact thresholds should reflect the organization’s size, risk tolerance and operational needs.
Separation of Duties
No single person should be able to create a vendor, change bank details and release payment without review. Smaller organizations may have limited staffing, but compensating controls can help, such as owner review, bank alerts or third-party bookkeeping oversight.
Healthcare Considerations
Healthcare organizations face the same BEC risks as other businesses, but the impact can extend beyond financial loss. Email compromise may expose patient information, disrupt operations or create obligations under privacy and security requirements.
Relevant healthcare security considerations include:
- Access controls for email and systems containing protected health information
- Workforce security training
- Audit logging and review
- Incident response and contingency planning
- Business associate management
- Secure transmission and storage of sensitive data
- Vendor payment controls for clinical and operational suppliers
Organizations regulated by HIPAA should evaluate applicable requirements under the HIPAA Security Rule, including 45 CFR 164.308, 45 CFR 164.310 and 45 CFR 164.312, as well as breach assessment and notification obligations under the HIPAA Breach Notification Rule. State privacy and breach notification laws may also apply and vary by jurisdiction. Consult qualified counsel for legal interpretation.
Business Email Compromise Readiness Checklist
Use this checklist to assess your current posture.
People
- Employees receive practical BEC and phishing training
- Finance staff know how to verify payment changes
- HR staff verify payroll changes outside email
- Executives support verification procedures
- Employees know how to report suspicious messages
- Reporting is encouraged and blame-free
Process
- Vendor bank changes require independent verification
- Wire transfers require dual approval
- Payroll direct deposit changes require identity verification
- Emergency payment exceptions are documented and reviewed
- Incident response procedures include BEC scenarios
- Bank contact information is documented
- Vendor master data is reviewed periodically
Technology
- MFA is enabled for all email accounts
- Phishing-resistant MFA is used for high-risk users where feasible
- Legacy authentication is disabled where possible
- Email authentication is configured for organizational domains
- Inbox forwarding and suspicious rules are monitored
- Logs are retained and reviewed
- Endpoint protection is deployed
- Security alerts are routed to responsible staff
Compliance and Risk
- Sensitive data handling procedures are documented
- Email retention aligns with business and legal requirements
- Third-party risks are reviewed
- Incident notification obligations are understood
- Cyber insurance requirements are tracked where applicable
- Security assessments are performed periodically
What to Do If You Receive a Suspicious Email
Employees should have simple instructions. A practical message might say:
- Do not click links or open attachments.
- Do not reply to the suspicious email.
- Use the phishing report button or forward the message to the security team as instructed.
- If the message involves payment, payroll or sensitive data, call the appropriate internal contact.
- If you already clicked or responded, report it immediately.
The last point is important. Employees should understand that early reporting helps the organization contain risk. Delayed reporting can allow attackers to move money, access data or compromise more accounts.
Metrics to Track
Organizations should measure whether controls are working. Useful metrics may include:
- Number of reported phishing messages
- Time from report to security review
- Number of confirmed BEC attempts
- Number of blocked impersonation attempts
- Percentage of users covered by MFA
- Percentage of high-risk users using phishing-resistant MFA
- Number of unauthorized forwarding rules detected
- Time to disable compromised accounts
- Completion rate for role-based training
- Exceptions to payment verification procedures
- Results of phishing simulations, if used appropriately
Metrics should support improvement, not blame. The goal is to identify weak points and strengthen controls.
Conclusion and Next Steps
Business email compromise succeeds when attackers exploit trust, urgency and weak business processes. The best defense combines people, process and technology: train employees to recognize suspicious requests, require independent verification for financial changes, protect accounts with phishing-resistant MFA, monitor for account takeover and prepare a response plan before an incident occurs.
Start with the controls that reduce the most risk quickly: MFA for email, callback verification for payment changes, executive and finance account protection, and clear reporting procedures. Then mature your program with email authentication, logging, incident response exercises and periodic security assessments.
How ThornShield Can Help
ThornShield Technologies helps organizations evaluate email security, identity controls, incident response readiness and business-process safeguards against threats such as business email compromise. If you want an independent review of your current defenses, explore our Full Security Assessments.
This article is general information and not legal advice.