ISC · Security and Confidentiality and Privacy · 6 practice questions
BEC Wire Fraud: Red Flags and Out-of-Band Verification
Hold suspicious payment changes until authorization is verified through a known, independent contact method and required approvals are complete. Below: judge possible responses to an urgent wire request that appears to come from the CFO.
Try one first
Hint
Compare the sender's display name to the actual sender domain, check for requests that bypass standard approval steps, and remember the company's verbal-confirmation rule for large transfers.
Answer C. The facts show classic BEC indicators: the display name is spoofed while the sender domain differs, the message requests an urgent wire to a new account, and it attempts to bypass the company's verbal-confirmation policy for large payments. The clerk should refuse to transfer funds until independently verifying authorization by calling the CFO on the verified number and should escalate the incident to information security for investigation and evidence preservation.
Why not A: Plausible if one suspects a technical compromise, but this misclassifies the primary threat: the message is a social-engineering BEC designed to trick staff into moving funds. Isolating the workstation and scanning won't stop a transfer; the immediate priority is independent verification and stopping the payment.
Why not B: Tempting because the display name looks legitimate and urgency pressures action, but attackers commonly spoof display names while using a different sender domain; initiating the wire without independent verification risks fraud and violates the company's confirmation policy.
Why not D: Well-intentioned but ineffective: attackers often use multiple or changing addresses, and broadly forwarding the message can spread sensitive details and interfere with proper incident response. The proper immediate actions are to verify the request and notify security so they can investigate.
What should you do?
The situation
At Ridgewell, a clerk receives an urgent request to redirect a $150,000 vendor payment. The display name is the CFO's, but cfo@ridgewell-pay.com differs from ridgewell.com. The email has no links or attachments and says, "Don't call my office; use this number." Policy requires independent telephone verification and two-person approval. The clerk has the CFO's verified directory number. No wire has been sent.
Hold the wire, call the CFO's verified directory number, follow vendor-change procedures, obtain the second approval, and notify information security.
Best This breaks the attacker's communication path and satisfies the required controls before any money moves.
Keep the wire on hold and notify information security before taking further action.
Acceptable This prevents immediate loss and starts escalation. Independent verification and the required approvals still must occur before payment.
Reply to the email and release the wire after receiving written confirmation.
Wrong The attacker can reply. Confirmation within the same suspicious thread does not independently establish authorization.
Call the number in the email and release the wire if the person confirms.
Wrong The attacker supplied that number. A different communication method is not enough when its contact details come from the suspicious message.
Send the wire now because the CFO requested it and the email contains no malicious attachment.
Wrong BEC can work through payment instructions alone. Apparent executive authority and urgency do not replace verification or required approval.
Key points
- Remember: Switching from email to phone is not independent verification if the suspicious email supplies the number.
- A correct display name does not authenticate the sender. Check the actual domain.
- BEC can redirect money without links, attachments, or malware.
- Verification and required approvals are separate controls. Complete both before releasing the wire.
How the exam traps you
- Replying to the suspicious email for confirmation. Use the CFO's previously verified directory number, not the attacker's email thread.
- Calling the number supplied in the suspicious message. Obtain the number independently. An attacker can answer a phone call too.
- Treating urgency, executive authority, or missing attachments as permission to pay. Keep the wire on hold until independent verification and required approvals are complete.
Question 2
Hint
Consider whether the attack's goal is an immediate, targeted fund transfer using executive impersonation rather than delivering malware or sending generic messages to many recipients.
Answer A. This scenario is classic Business Email Compromise (CEO fraud): an attacker impersonates a trusted executive, uses internal details and an email-similar address, and requests an urgent, confidential wire transfer. BEC attacks rely on social engineering to cause immediate fraudulent transfers rather than delivering malware or harvesting credentials.
Why not B: Spear phishing is targeted and may use internal details, but its primary goal is typically credential capture or malware delivery via links/attachments. Here the immediate objective is to trick an employee into wiring money, which aligns with BEC.
Why not C: Whaling targets senior executives as the victims. In this case the CEO is being impersonated to deceive a subordinate (the controller) into transferring funds, so the executive is the impersonated source rather than the direct victim, pointing to BEC instead.
Why not D: Mass phishing is non‑targeted and uses generic language and malicious links sent widely. This email is clearly targeted, personalized, and requests a specific fund transfer, which is inconsistent with mass phishing.
Question 3
Hint
Focus on whether the attacker is directly requesting payment redirection via a targeted, spoofed vendor email (social-engineering of funds) versus trying to harvest credentials or intercept network traffic; note the absence of links/attachments and the accurate invoice details.
Answer B. This scenario describes a targeted vendor impersonation with accurate invoice details and a request to change payment instructions to a new bank account, with no links or attachments, hallmarks of BEC aimed at redirecting funds. The slightly different sending domain and timing outside normal billing cycles further support spoofing or account takeover rather than credential-harvesting or network interception.
Why not A: Generic phishing is typically broad and not tailored with correct vendor invoice numbers or a specifically timed payment request; the targeted, invoice-specific nature of this message makes mass phishing unlikely.
Why not C: Spear-phishing is targeted, but when the primary goal is credential theft or malware delivery it usually includes malicious links or attachments; this message lacks those indicators and instead requests a direct funds transfer to a new account, pointing to BEC.
Why not D: MITM implies interception of an existing communication channel and altering messages in transit; the scenario describes a fraudulent email from a spoofed/altered sender rather than evidence of intercepted network traffic, so MITM is less likely.
Question 4
Hint
Focus on the attacker's primary method in the facts: Was the harm caused by deception, by malware, by service disruption, or by password guessing?
Answer B. This is best classified as business email compromise (BEC), a social engineering attack in which the attacker impersonates a trusted vendor to trick staff into redirecting payments. The key facts are the lookalike email domain and the fraudulent payment instruction; there was no malware infection or service disruption.
Why not A: Ransomware involves encrypting or locking systems or data to extort payment. Although this incident caused a financial loss, there was no system encryption or extortion, only fraudulent payment instructions.
Why not C: A DDoS attack floods systems or networks to disrupt availability. The scenario describes deception to redirect funds, with no network overload or service outage, so DDoS is not the correct classification.
Why not D: A brute-force attack involves repeated attempts to guess credentials. While account compromise can be part of some BEC cases, the facts here point to impersonation via a spoofed/lookalike email domain and fraudulent instructions rather than credential guessing.
Question 5
Hint
Focus on the log evidence (foreign login and added forwarding rule) and the organization's current authorization method for wires, what immediate containment and control changes address an account takeover and stop fraudulent transfer requests?
Answer A. The log evidence (foreign login and added forwarding rule) shows an account takeover and classic business-email-compromise. Immediate containment is required: suspend the compromised account, remove persistence (forwarding rules), and notify the bank and law enforcement to attempt recovery. Short-term preventive changes should block the attack vector: require out-of-band verification for wire requests and implement MFA to reduce the risk of credential-based re‑takeovers.
Why not B: Password resets and training are useful long-term measures but do not by themselves contain an active compromise or remove persistence like unauthorized forwarding rules; without suspending the account and adding MFA the attacker may regain access.
Why not C: Email authentication helps block spoofed external senders, but this incident involves a legitimate internal mailbox that was hijacked; SPF/DKIM/DMARC will not stop messages sent from the compromised account and therefore will not prevent this type of fraud on its own.
Why not D: Contacting the bank and insurance and limiting authority are reasonable recovery and mitigation steps, but they are reactive and do not contain the active compromise or put in place the specific authentication and verification controls (suspending the account, MFA, out-of-band verification) needed to prevent recurrence.
Question 6
Hint
Decide whether this incident was primarily a technical account compromise or a social‑engineering/payment‑process failure, and pick the control that addresses that root cause.
Answer A. This incident is a business email compromise (BEC) using a look‑alike external domain and social engineering to request a payment change. Technical defenses and malware scanning are unlikely to stop a targeted, non‑malicious spoofed message. Process controls, out‑of‑band verification using a previously verified phone number and requiring dual authorization for vendor bank‑account changes or large wire transfers, directly address the human/procedural gap and would most likely have prevented the fraud.
Why not B: Gateway sandboxing and link/attachment analysis are effective against malware and credential‑harvesting pages, but this message contained no attachments or malicious links, only a fraudulent request, so those tools would likely not have flagged it.
Why not C: SPF/DKIM/DMARC reduce some spoofing but may not block attackers using look‑alike domains or carefully crafted external domains that pass or avoid triggering checks; they do not address the procedural approval failure that allowed the wire.
Why not D: MFA helps prevent account takeover, which is valuable, but the attack involved an external impersonation that tricked an employee rather than a compromised internal account; MFA would not have stopped the employee from following fraudulent payment‑change instructions.
Common questions
What should I do first with a suspected BEC wire request?
Hold the wire. Verify the request using a previously known contact method, follow the required approval process, and notify information security.
Does calling the phone number in an email count as out-of-band verification?
Not when the suspicious email supplies the number. Use an independently trusted number, such as the CFO's previously verified directory number.
Can an email be BEC without links or attachments?
Yes. Here, the attacker impersonates the CFO to redirect a payment. The fraud relies on persuasion rather than a malicious attachment or link.
Watch it solved
A full CPA ISC task-based simulation on Threats and attacks, worked step by step.
SIEM Attack Identification | CPA ISC Simulation (TBS) on YouTube
Practice ISC like the real exam
The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.
Open the free simulator →More on Threats and attacks
Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.