Clone phishing copies a legitimate-looking message and sends it from an external or spoofed account, usually with a small change such as a link or attachment. Business email compromise uses a real or compromised internal account to send messages directly. Both are dangerous, but BEC often has stronger credibility because the attacker speaks from inside the trusted channel.
How clone phishing differs from BEC in the attack path
Clone phishing is a message-level imitation. The attacker takes a legitimate email, reproduces its look and intent, then swaps in a malicious or altered element such as a link, file, or destination. Business email compromise is an account-level abuse of trust, where the message comes from a real internal mailbox or a mailbox the attacker has already taken over.
That difference matters because the defender is not looking for the same failure mode. Clone phishing mainly abuses familiarity and message cloning, while BEC abuses sender legitimacy, mailbox access, or internal trust. When the sender is genuinely inside the organisation, ordinary “spot the fake email” cues become much less reliable.
For readers who want the broader pattern of phishing variants, the Phishing Guide is useful because it places clone phishing alongside other common phishing techniques and the layered defences that reduce them.
Why BEC is usually harder to detect than clone phishing
Clone phishing is often easier to catch at the message edge because the email may come from an external, spoofed, or newly created source. Defences can focus on reputation, spoofing signals, attachment safety, and link analysis. BEC is harder because the sender can be a legitimate employee account, a compromised supplier mailbox, or a trusted delegated identity already allowed to communicate with the target.
That makes BEC especially effective for invoice fraud, payment diversion, payroll change requests, and other workflows where the content looks routine. The compromise is often not technically noisy until the attacker starts changing bank details, redirecting payments, or creating forwarding and reply rules to preserve access.
If you need a practical view of how trusted email channels are abused, Email Identity and BEC Guide explains the controls that separate sender authenticity from mailbox trust.
For common attacker behaviours that make the distinction operationally important, MITRE ATT&CK T1586 Compromise Accounts Guide shows how hijacked accounts are used to stage follow-on abuse, including email abuse and trusted-sender fraud.
How to respond when the email is cloned versus when the account is real
With clone phishing, the immediate priority is to remove the lure, block the malicious destination, and warn recipients who may have seen the same message. With BEC, the first task is broader: contain the compromised mailbox, revoke active sessions or app permissions where needed, review forwarding rules, and look for signs that the attacker has already used the account to reach finance, HR, or supplier contacts.
The response also differs in scope. Clone phishing can be isolated to the campaign artefact. BEC often requires a mailbox and identity review because the attacker may have left behind persistence, changed account settings, or used the account to impersonate internal approvers. If payment or banking information was touched, fraud containment becomes part of the incident handling.
When the incident is email-driven, a Phishing Incident Response Playbook helps teams decide what to triage first, what to purge, and when to reset credentials or revoke sessions.
For teams that need to understand the mailbox-abuse angle specifically, T1114 Email Collection Defensive Guide is useful because BEC often depends on mailbox access, forwarding rules, or other post-compromise email collection techniques.
Risk and Threat Considerations
Both techniques can lead to credential theft, payment fraud, or secondary compromise, but BEC usually creates greater downstream exposure because the attacker can operate from a trusted account and extend the abuse across internal and external workflows. Clone phishing is often a single-message problem; BEC is often a trust-preservation problem that can persist until the mailbox or related permissions are contained.
Failure mechanism: Clone phishing succeeds by copying a legitimate message closely enough to bypass user suspicion, while BEC succeeds by inheriting trust from a real or compromised account. That makes BEC more likely to bypass simple sender-based checks and more likely to survive long enough for fraud or lateral abuse.
Impact: Clone phishing typically delivers the initial lure, but BEC can directly enable invoice redirection, supplier impersonation, account takeover follow-on activity, and mailbox abuse that affects multiple recipients or business processes.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses the attack and risk surface, while CIS Controls v8 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| MITRE ATT&CK | T1586 — Compromise Accounts | BEC commonly uses hijacked accounts to abuse trusted email channels. |
| T1114 — Email Collection | BEC often relies on mailbox access, forwarding rules, and message collection. | |
| Recommendation — Map trusted-sender abuse to T1586 and hunt for compromised mailbox activity. Check for mailbox collection techniques and remove forwarding or collection rules. | ||
| CIS Controls v8 | CIS-5 — Account Management | The comparison hinges on compromised versus spoofed account use and access control. |
| Recommendation — Audit and disable suspicious accounts, sessions, and delegated access promptly. | ||
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | Compromised email accounts depend on weak credential lifecycle controls. |
| AC-6 — Least Privilege | BEC impact grows when mailbox and payment workflows have excessive privilege. | |
| Recommendation — Rotate exposed credentials and invalidate active authenticators after compromise. Limit mailbox and workflow privileges to the minimum needed for each role. | ||
Practitioner Guidance
What to prioritise: Treat clone phishing as a content and delivery problem, but treat BEC as an identity and workflow problem. If the message is coming from a valid internal mailbox, your verification steps should shift from email inspection to transaction verification, session review, and mailbox-state checks.
What to verify: Confirm whether the sender account is real, compromised, delegated, or recently changed, and check whether the message is trying to alter payment instructions, supplier details, or approval chains. If those elements are present, the incident deserves fraud handling as well as email containment.
Practitioner takeaway: The key distinction is not just where the email came from, it is whether the attacker is impersonating trust from outside or operating inside it. That determines whether the correct response is message cleanup or account-and-process containment.
Related resources from NHI Mgmt Group
- Email compromise
- Why do phishing and business email compromise campaigns remain hard to detect with payload-based controls alone?
- Why do human errors still drive so many successful phishing and business email compromise attacks?
- Why do email gateways remain a critical control for phishing, malware, and business email compromise?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 4, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org