Colour theme
Book a consultation

Setting a useful security training schedule

Plan security training around staff roles, tool changes and observed gaps, then test reporting and verification without relying on one universal interval.

A blue shield over a background of digital patterns

Security training needs a schedule people can follow and content they can apply to their work. An annual presentation alone may leave gaps when staff, tools or responsibilities change between sessions.

No single interval suits every business. Choose a starting schedule, provide refreshers at relevant changes and check whether people can use the process.

Understand the four-month claim

The SOUPS 2020 study cited in older training advice tested phishing and legitimate-email identification over time after an awareness program.

It found significant improvement immediately and after four months, but not after six months, and recommended a reminder after half a year in that setting.

That finding doesn’t make four months the right interval for every security topic, and it doesn’t show that any schedule prevents ransomware. Use it as a reason to evaluate reinforcement, alongside your own evidence.

Provide training at the point of need

Include the reporting route and essential safeguards in onboarding before a person takes on the relevant work. Provide additional guidance when someone begins approving payments or administering systems.

Explain a new tool or policy before people must use it. A change to sharing permissions, authentication or device ownership can make last year’s instructions incomplete.

The Cyber Centre’s tailored-training guidance supports matching training to personnel and organizational needs, including contractors, managers and executives.

Choose a manageable refresher plan

Schedule short practice sessions and a broader review that fit the business’s work. Increase attention to a topic when incidents, support requests or task changes reveal a gap.

Combine a demonstration with a simple exercise: verify changed payment details, report an unexpected sign-in prompt or find the business’s file-sharing instructions.

Keep instructions accessible to remote staff and people who miss the live session. Give them an equivalent way to ask questions and practise.

Cover more than suspicious email

Include text and social-message requests, secure sign-in, lost devices and handling customer records. Teach the tools and contact routes the business uses.

Keep the reporting process usable when email or the normal laptop is unavailable. Staff should know whom to contact after entering information as well as before taking an action.

Use the reply-chain guide for an example where a familiar conversation can still contain an unsafe request.

Measure whether the process works

Check whether staff can find the instructions, verify a request and report a problem. Record recurring obstacles and improve the workflow or controls that create them.

Completion records show who attended. They won’t tell you whether people can use what they learned, and they don’t stop incidents. If using simulations, review their scope and privacy, avoid public shaming and provide practical follow-up.

Keep only the training records the business needs, and limit who can see them and how long they’re kept.

Review the schedule and ownership

Assign someone to update content, arrange refreshers and handle questions. Revisit the plan after a significant incident or system change and during the regular security review.

Training complements technical controls and responsive support. Our cybersecurity service can help connect those responsibilities with the risks and tasks staff encounter.


Featured Image Credit