R02 — Business Email Compromise (BEC)

Stress-test Business Email Compromise (BEC) in the Standard run scenario Mid-size SaaS company. Balanced challenge.
Start playing →
R02 External Severity 8 · Major

Mostly an awareness + email security problem. Detection helps catch in-progress.

What is Business Email Compromise (BEC)?

Mostly an awareness + email security problem. Detection helps catch in-progress. CISO Game tracks this as R02 in the live risk register, severity 8 (Major), category External.

How does CISO Game model Business Email Compromise (BEC)?

Exposure for R02 runs from 0 to 100, recomputed live as you buy, cancel, or reassign products. How the exposure model works →

Real-world parallel

Business Email Compromise is the highest-dollar attack vector by reported losses (the FBI's IC3 has put the cumulative impact above $50B). It rarely shows up in posture-tooling demos because there's no malware to detect — just a well-researched social-engineering path through finance approval workflows. The CISO Game lever is the awareness + identity stack (DMARC, MFA on every shared mailbox, out-of-band confirmation policies for wire changes), not the next EDR upgrade.

How do security teams mitigate Business Email Compromise (BEC)?

The dominant subscore levers for this risk are:

Which investments mitigate Business Email Compromise (BEC)?

Products in CISO Game that reduce exposure to R02:

Which related risks should you also watch?

Risks with similar dominant subscores or shared category — addressing one often helps the others:

Why does Business Email Compromise (BEC) matter to a CISO?

External adversarial risks like business email compromise (bec) are the risks boards expect their CISO to talk about. They drive the strongest demand for detection + response capability and the strongest emotional response in the boardroom.

How can you test your mitigation strategy?

Click Play CISO Game free to see R02 appear live in your risk register and watch each purchase move the exposure number in real time. No signup required.

Stress-test Business Email Compromise (BEC) in the Standard run scenario →