A suspicious email rarely arrives at a convenient time. It may appear during a payment run, a staff handoff, or the final hours before a deadline. A company can have filtering software and written procedures, yet still lose time deciding who should act first. A short tabletop exercise can reveal those delays before a real incident puts them under pressure.
Instead of rehearsing a dramatic, company-wide breach, test one ordinary scenario: a familiar vendor emails a changed bank account, and a second message appears to come from a senior manager asking for a quick payment. Teams assessing their broader exposure to email and collaboration threats can review resources from safeguardcyber.net/, then use a focused exercise to see how their own people respond in practice.
Make the scenario feel routine
The most useful exercise begins with details employees recognize. Choose a supplier the finance team works with, a payment amount that fits normal operations, and a believable reason for urgency. Do not make the message so obviously suspicious that the group can solve it by spotting a spelling error. The point is to test the decisions people make when a request looks plausible.
Give participants only the information they would have at that moment. The finance employee might see the account-change email first. A manager could receive a separate request to approve the payment. An IT responder might not hear about either message until someone reports a concern. These different views help the group uncover where a clear signal gets lost between teams.
Follow the decision, not the software
Security tools matter, but a tabletop exercise should focus on the human and operational steps around them. Ask who verifies a bank-account change, which contact method the employee uses, and whether the team can find the correct vendor number without relying on details in the suspicious email. Then ask what happens if the usual approver is away.
Keep the discussion grounded in actual working conditions. If staff rely on a shared inbox, include it. If employees use chat to approve exceptions, include that too. The exercise should reflect how work gets done, including the shortcuts people take when deadlines crowd the calendar.
- Who can pause a payment while the request is checked?
- How does an employee reach the vendor using a trusted phone number?
- Where should staff report a suspicious message, and who monitors that channel?
- Can the response team preserve the email and related records for review?
- Who tells finance, leadership, and the vendor what is happening?
Notice where time disappears
Record the moments when participants hesitate or search for information. A long pause may point to a missing procedure, an unclear approval boundary, or a contact list that no one trusts. Write down the question that caused the delay. “Who is allowed to stop this?” is more useful than a broad note such as “communication needs improvement.”
It also helps to distinguish a policy gap from a findability problem. A company may already require a second verification for account changes, but if employees cannot locate the rule during a busy shift, the safeguard may not shape their choices. The right fix could be a shorter procedure, a better link on the finance team’s internal page, or a reminder in the payment workflow.
Turn observations into small changes
End the exercise by assigning each improvement to a person and setting a date to check it. One owner might update the supplier-verification script. Another could confirm that the reporting inbox reaches a monitored team. Keep the first round manageable. A few changes that staff can test in daily work are easier to evaluate than a long list of policy revisions.
Run the scenario again after the changes have been in place. Participants should know the updated process, but the facilitator can alter one detail, such as making the regular approver unavailable. That small variation tests whether the team understands the reason behind the check or has memorized a single sequence.
A tabletop exercise does not predict every attack or replace technical controls. It gives a company a low-pressure way to inspect how a believable email request moves through real roles and routines. When the group can verify a change, pause a payment, and report a concern without guessing who owns the next step, the procedure has become easier to use when the inbox gets busy.