security awareness

How often to run security awareness training

AA
Aurum Avis Labs Author
6 min read

How often to run security awareness training

How often security awareness training should run in a Swiss SME rarely comes down to a single sentence in law. Practical anchors are three: within the first working weeks at hire, at least once a year for everyone, and again after a serious near-miss or fraud attempt. The FADP requires appropriate technical and organisational measures, not a fixed training calendar. Insurers, ISO/IEC 27001:2022 control A 6.3 and customer audits still expect a continuing programme, not one forgotten afternoon years ago.

This checklist is for HR and owners with about 20 to 250 staff and no CISO. Whether training counts as mandatory in your situation is covered in is security awareness training mandatory. Dates and topics for the year belong in the annual awareness training plan.

  • Within two weeks of hire: report path, passwords, payments if relevant
  • At least yearly: live session or equivalent refresh for all staff
  • After fraud or major near-miss: targeted repeat within a few months
  • When tools change: MFA rollout, new payment portal, new CRM with client mail

Onboarding

New people should know the internal report path before they process their first invoice or paste client data into a new tool. A short briefing with IT or HR plus the next firm-wide session is enough in many firms. If you only train once a year, January hires work without shared rules until the next date.

Use the same core topics at hire as in the annual slot: where suspicious mail goes, how IBAN changes are checked, that reporting is welcome. Topic lists are in security awareness training topics.

Annual rhythm

Pick a fixed month, for example after the summer break or before the year-end audit. A one- to two-hour live session with Swiss payment examples reaches more people at once than scattered reminder mails. Training only in December means people forget the report path by summer.

E-learning alone is often a weak sole annual channel but can cover hires between dates. Compare formats in e-learning vs live security awareness. Part-time and home office staff do not change the rhythm: the same duty to attend, only the slot has to work for everyone.

After incidents and near-misses

971

BACS: CEO fraud reports in Switzerland in 2025. External statistic. Source: BACS weekly review week 4/2026 (German). After a false payment request to finance, a repeat within weeks belongs in the plan, not only on next year’s calendar.

If finance almost paid a changed IBAN, rerun payment content for everyone who can approve money. Then a short reminder for everyone else. The same applies after a phishing click with account loss or ransomware on a workstation. Log date, attendees and topic in the same folder as the annual session.

When once a year is enough

Often enough

  • Stable headcount, little change in finance and IT roles
  • Rising internal reports, no major near-misses
  • Onboarding briefing plus one fixed annual date

Too sparse

  • Many hires without anything between annual dates
  • New payment process without follow-up training
  • EU customer asks for proof more often than your calendar

When to run more often than yearly

Doubling headcount, opening a second site, or a CRM that sends client mail from the system are common triggers. The same applies when you roll out MFA and half the firm still skips the app. Plan phishing simulations separately: announce them, do not use them to score individuals. Rhythm and labour limits are in phishing simulations allowed in Switzerland. Surprise tests without notice are neither a rhythm nor a substitute for a clear annual session.

What is not a rhythm

Monthly mandatory videos nobody watches produce click proof without behaviour change. Training as punishment after a mistake discourages reporting. A one-off session without onboarding and refresh satisfies neither A 6.3 nor a typical insurer questionnaire. Mapping to ISO/IEC 27001:2022 A 6.3 can be supplied on request. The session does not certify the company.

A made-up example:

A fiduciary firm with 45 staff has trained live every October for years. In March someone in finance clicks a link; IT contains the access in time. Leadership schedules within three weeks a second session for finance and assistants only, using the same IBAN steps as in the ERP, plus a one-page reminder for everyone else. Spring hires had only the ten-minute briefing, no e-learning. HR logs both dates in the same folder as the October invite.

Documentation auditors ask for

Keep it simple: calendar invite or sign-in sheet, slide titles or one-page summary, facilitator name, language used. Store A 6.3 mapping separately from attendance. When leadership changes, one folder per year survives turnover better than chat threads.

Coordination inside the firm

Most SMEs use an external facilitator while IT owns mail rules and MFA. Agree in writing who sends reminders, who collects attendance and who answers report mail after the session. HR schedules dates, IT checks examples match your mail system, finance confirms payment stories. Without named owners the programme stops when someone is on holiday.

Swiss context

Fraud dominates public BACS reports (German page). Payment and CEO-style requests belong in every annual slot even if last year looked like “only” phishing links. The cyberattack reporting duty from April 2025 applies to critical infrastructure, not most SMEs. Do not confuse staff with 24-hour rules unless you know you are in scope.

After the session

Send a one-page reminder with the report address and IBAN rule within a week. Schedule time for follow-up questions. Store e-learning completions in the same folder as live attendance.

Does one session satisfy ISO A 6.3 forever?

No. Auditors expect an ongoing programme with refresh and onboarding coverage. Keep dates and topics across years.

Can we train finance separately?

Yes, if everyone still receives core reporting and MFA content. Payment modules should include anyone who can approve money movement.

Is e-learning enough as the only annual channel?

Often not for the whole firm. E-learning suits hires between dates. Live reaches everyone at once.

Must every simulation trigger an extra session?

No. After an announced simulation a short debrief is often enough. After a real incident, plan targeted training.

Draft dates on the annual plan. When the next session needs Swiss payment examples in the room, format and booking are on Security Awareness Training.

security awareness frequency switzerland hr
AA

Written by

Aurum Avis Labs

Builds and ships at Aurum Avis Labs. Writes here about what we learn working with founders and SMEs in the DACH region.

Customize your cookie preferences. Essential cookies cannot be disabled as they are required for the website to function properly.

Essential Cookies

Required for basic website functionality, security, user authentication, and error tracking.

Always active

Analytics Cookies

Help us understand how visitors interact with our website to improve user experience. Includes Google Analytics and Microsoft Clarity session recordings.

Marketing Cookies

Used to track visitors across websites to display relevant and engaging advertisements.