Buyer guide

Building a security awareness training program that changes behaviour

Awareness training changes behaviour when it is short, frequent, relevant to each person's job and backed by easy, no-blame reporting. An annual slideshow and a completion certificate rarely do.

The short answer

A security awareness program that changes behaviour has five parts:

Clear goals

Real risks: phishing, accounts, data handling, quick incident reporting.

Short, regular content

Instead of one long annual session.

Role-based depth

Finance, executives, IT administrators, anyone handling sensitive records.

Practice and feedback

Including fair phishing simulations.

No-blame reporting

One-click reporting and a quick, friendly response.

Start with the behaviours you want

NIST's SP 800-50 Rev. 1 (September 2024) frames training as a life cycle aimed at behaviour change, with metrics to improve it (NIST). Write goals as behaviours, not topics; they also tell you what to measure.

Instead ofAim for
"Understand phishing"Suspicious emails reported within minutes; payment changes verified by phone
"Password training"MFA and a password manager for all; no reused work passwords
"Data protection awareness"Sensitive files sent through approved tools, never personal email
"Incident awareness"Lost devices and mistakes reported immediately, without fear of punishment

Make it relevant to Canadian staff

Generic foreign content feels irrelevant. Use lures people recognize:

  • CRA, Canada Post, bank or courier impersonation
  • Fake Interac e-Transfer notifications and requests
  • A known supplier's "new banking details"
  • Executives asking for gift cards or urgent wires
  • Fake Microsoft 365 or Google sign-in pages

The Government of Canada's Get Cyber Safe campaign offers free supplementary material. Offer English and French where needed, with captions, screen reader support and plain language.

Role-based depth

Everyone needs the basics in the Canadian Centre for Cyber Security's baseline controls: password practices, spotting malicious email, approved software, appropriate internet use. Some roles need more:

  • Finance and payroll
  • Executives and assistants
  • IT and administrators
  • HR and client-facing staff
  • New staff
What each role needs
RoleExtra focus
Finance and payrollPayment verification, supplier banking changes, invoice fraud
Executives and assistantsImpersonation, targeted phishing, travel and device security
IT and administratorsPrivileged accounts, help desk social engineering, secure remote access
HR and client-facing staffPersonal information, unknown senders' resumes and attachments
New staffBasics in week one, before habits form

Phishing simulations, done fairly

Safe practice for people, data for you. To build trust:

  • Announce that simulations happen, not when.
  • A click is a learning moment: explain straight away.
  • No naming, shaming or discipline tied to results.
  • No lures exploiting real distress or promising fake benefits such as bonuses.
  • Vary difficulty and themes; mirror real attacks you have seen.
  • Measure reporting, not just clicking.

Make reporting easy

Fast reporting matters most: one suspicious email reported early protects everyone.

A report button

In the email client.

A clear contact

Lost devices, mistaken emails, anything that "feels off"; after hours if covered.

A quick thank-you

Plus feedback on the message, where possible.

People who fear blame hide mistakes: say often that quick reporting is the right thing.

Back training with technical controls

Someone will eventually click. Pair training with MFA, email filtering, endpoint protection, least-privilege access and tested backups (common settings: Microsoft 365 security baseline).

A 12-month plan

WhenActivity
Month 1Baseline simulation, report button, leadership no-blame message
MonthlyOne 5 to 10 minute module on one topic
QuarterlyNew-theme simulation; role sessions for finance, executives and IT
On hireOnboarding module in week one
After incidentsShort, anonymized lessons learned
Month 12Review metrics, update topics, report to leadership

Measure what matters

Track over time:

  • Report rate, simulated and real
  • Time to first report
  • Click rate by theme (to target modules, not rank people)
  • Repeat clicks (to offer support)
  • Real human-error incidents and report speed
  • Completion (hygiene only)

Treat training and simulation data as employee personal information: restrict access, set retention.

Program checklist

Design

  • Program goals written as behaviours
  • Higher-risk roles identified with extra content planned
  • Canadian examples and bilingual needs addressed

Delivery

  • Monthly short modules scheduled
  • Onboarding module for new staff
  • Quarterly phishing simulations with fair rules published

Reporting culture

  • One-click reporting in email
  • Clear contact for mistakes and lost devices
  • Leadership statement on no-blame reporting

Measurement

  • Report rate and time to report tracked
  • Annual review with leadership
  • Training data access and retention defined

Limitations

One control among many: it works best with visible leadership and takes months, not weeks. For help designing or running a program, see our cybersecurity awareness training service.

Sources and further reading

Product capabilities and guidance change. These are the primary sources this article relies on, checked on the review date above.

  1. Building a Cybersecurity and Privacy Learning Program (NIST SP 800-50 Rev. 1), National Institute of Standards and Technology
  2. Baseline cyber security controls for small and medium organizations, Canadian Centre for Cyber Security
  3. Get Cyber Safe, Government of Canada

This article is general information, not legal, accounting or security advice for your specific situation. Examples are hypothetical unless stated otherwise.

Talk to Promatics

Get a straight answer for your situation

General advice only goes so far. Tell us about your environment and we will tell you what we would do, what it would cost and what to watch out for.

  • A named specialist who owns the outcome, not a chat window
  • Advice checked against your actual systems, contracts and risks
  • Written scope and costs in CAD before any work starts