Colour theme
Book a consultation

Updating phishing exercises for the work people do

Choose phishing practice scenarios around texts, account changes, supplier messages and payment requests, with a clear verification and reporting path.

Three colleagues discussing work around a table with laptops and notebooks

A training example about an obviously misspelled email may not prepare someone for a plausible supplier message or an urgent text. Build practice around the requests people handle and the decisions that are theirs to make.

The aim is to rehearse checking a request and reporting it. Staff don’t need to know which attack type is newest.

Include messages outside email

Choose a text, chat message or social-platform request relevant to the role. Examples include a delivery exception, a meeting invitation or a request to sign into a shared file.

Show how to open the service through a bookmark or a known address and how to check the request another way. A familiar sender name on a text or message can be faked.

Use a safe training environment without real credentials or malicious files.

Rehearse a payment or account change

Practise an invoice with changed bank details, an urgent purchase or a request to alter payroll information. Have the participant follow the real approval process.

Business email compromise can involve a compromised account or impersonation. It doesn’t always require an attacker to log into your own mailbox.

Make the independent contact step practical: a known number and a named approver should be available when the request arrives.

Use role-specific details carefully

A targeted message can mention a real project or customer. Teach people to assess the requested action even when the background information is accurate.

Keep exercise data fictional and avoid unnecessary personal details. Discuss how publicly available information can make a request plausible without suggesting that every familiar fact indicates surveillance.

The Cyber Centre’s phishing guidance describes several phishing approaches and organizational verification measures. Use the current guidance to support examples.

Cover the handoff after a mistake

A phishing message may seek a password, a session, a file download or a financial action. The response depends on what happened.

Ask the participant to report the time and action through the usual reporting route. Don’t require them to identify the attack’s technical category before getting help.

Explain that a security team may need to investigate both the device and the account. Training isn’t a replacement for filtering, endpoint protection or account controls.

Assess the procedure as well as the participant

Record whether the correct verification contact was available, whether reporting worked and whether the sign-off steps were clear. A delayed response may expose a process gap.

Share lessons without shaming individuals or ranking staff publicly. Improve the procedure and repeat a relevant exercise when the workflow changes.

Use the security training schedule guide to decide when to revisit the practice. Pick the next scenarios from the requests your staff are receiving.


Featured Image Credit