Colour theme
Book a consultation

Practising security decisions with your team

Build role-specific security exercises around real work, a usable reporting route and feedback that improves the process.

Three colleagues discussing work around a meeting table with laptops and notebooks

Security training should help staff make a decision in the tools they use. They need to know how to verify a request, where to report a problem and what to do when the usual support channel is unavailable.

A short exercise can expose a missing instruction more clearly than another presentation. Keep it relevant to the employee’s role and use fictional information so the practice doesn’t expose client records.

Choose a decision from ordinary work

Ask staff where they encounter uncertain requests. Accounts payable may need to verify new banking details; reception may receive an unexpected file; a manager may need to approve access for a contractor.

Choose one decision and define the expected action. Include the point at which the employee should pause and ask for help.

The Cyber Centre’s tailored training guidance supports practical exercises and training for different roles. General awareness doesn’t substitute for specialist training where someone administers systems or develops software.

Prepare the reporting and verification route

Before the exercise, test the contact method staff will use. Check that it reaches the responsible person and that an alternative exists if work email fails.

For a payment or access request, give staff a known phone number or contact they can use to check it independently. Staff shouldn’t have to invent a procedure while a caller pressures them to act.

State what management will do when someone pauses a transaction. The procedure won’t work if employees are penalized for following it during a busy period.

Run the exercise safely

Use a controlled example with the people who own the business process. Ask the participant to explain their next action using the normal tools or a safe demonstration environment.

Include a convincing request without spelling mistakes and a request made by a familiar name. Test a lost-device report or an unexpected sign-in prompt as well as suspicious email.

Don’t collect real passwords, send live malicious attachments or ask staff to disable a control. Any unannounced simulation needs an agreed purpose, privacy boundaries and a review by management before it runs.

Debrief the whole process

Ask whether the instruction was clear, the verification contact was available and the report reached the right place. Record where the workflow made the safe action difficult.

Discuss what someone should do if they’ve already opened a link or shared information. Prompt reporting remains useful after an error; staff shouldn’t wait until they can prove an incident occurred.

Avoid public rankings or blame. Use the results to correct procedures, tools and training. A low click rate won’t tell you whether you could contain an incident or restore your data, so test those separately.

Keep role and management responsibilities clear

Ordinary employees need practical actions within their authority. They aren’t expected to investigate malware, change firewall rules or decide legal notification duties.

Include managers and contractors in the relevant exercises. Give administrators and response staff separate practice for their technical responsibilities.

Revisit the decisions when work changes

Repeat a relevant exercise after changing a payment process, reporting route or business application. Confirm the improvement through another attempt.

Our everyday security habits guide covers the supporting work environment. Keep both the procedures and the training aligned with what staff are asked to do.


Featured Image Credit