Colour theme
Book a consultation

Five cyber scenarios to review with your team

Practise staff responses to deceptive requests, ransomware, suspicious downloads, impersonation and unfamiliar connected devices using safe scenarios.

An illustration of a person using a laptop beneath a world map linked by shield symbols.

A short team discussion can expose a missing verification step or an incident contact that staff can’t reach. Use examples drawn from your team’s work and ask what each person would do next.

These five scenarios aren’t a ranking of the most frequent threats. They overlap: a deceptive message can deliver malware, and ransomware is itself malware. The purpose is to practise decisions and reporting without introducing live threats.

1. A message asks for an unusual action

A supposed supplier requests new banking details, or an apparent colleague asks for a sign-in code. The message can look familiar and arrive within a real conversation.

Ask the team how they’d verify the request using a known contact route. Don’t use a phone number supplied in the suspicious message. Identify who approves payment-detail changes and where staff report a request they haven’t acted on.

Use the email-request guide for specific checks. A request can have perfect spelling and a familiar sender name and still be fake.

2. Shared files stop opening

A staff member sees renamed files and a payment demand. Ask how they’d stop work, reach the response lead and follow the device-isolation instructions.

Check that someone can coordinate when normal email is unavailable. Staff shouldn’t reconnect backup drives or attempt their own restore. The ransomware damage guide covers the business decisions during containment and recovery.

The exercise is about the handoff. Don’t suggest that backups or antivirus will prevent every interruption or undo stolen-data exposure.

3. A website asks someone to install a fix

A browser page claims a document viewer needs an update, or instructs someone to paste commands into a terminal. Ask where staff normally obtain software and how they’d check the request.

Use a written example. Don’t visit a malicious site or download a real sample for training. Your IT contact should be able to assess the request without asking staff to recreate it.

The malware-reporting guide covers observations and escalation. A device that appears to work normally can still need investigation.

4. A familiar voice demands an urgent exception

An apparent manager calls for a payment or confidential file and says the usual approval process is too slow. The voice may be imitated, but staff don’t need to determine which technology produced it before verifying the request.

Practise the known callback and sign-off steps. Give staff permission to pause an unusual request, including one apparently made by a senior person. Cover what happens if the person who normally signs off is away.

The voice-impersonation guide covers this process. Don’t assume every fraudulent message uses AI, and don’t take a convincing voice as confirmation of who’s calling.

5. An unfamiliar device appears on the network

Someone brings in a camera, meeting-room device or smart appliance. Ask who decides whether it can be used, records its owner and chooses where it may connect.

Have IT check support, updates, administrative access and the information it handles. Getting it online and changing the default password are only part of that check.

The office IoT guide covers the technical review. Staff should have an easy way to request equipment without connecting an unreviewed device first.

Turn unanswered questions into fixes

Record the missing contact, unclear authority or blocked process from each discussion. Assign an owner and verify the corrected route with the relevant staff. Include new starters and people working away from the office.

Use the Cyber Centre’s baseline controls for the wider technical program. Staff practice works alongside account protection, updates and alert handling. It doesn’t replace them.

If someone has already acted on a suspicious request, have them report it promptly without fear of blame. Use a trusted device for account recovery, and let IT assess sessions and other access as well as passwords.

Contact us to review staff reporting and verification processes alongside your technical safeguards.


Featured Image Credit