Proof of security awareness training for audits
Proof of security awareness training for audits
Proof of security awareness training for audits is attendance plus documented content plus a plausible note on effectiveness, not a gold seal. Swiss SMEs with 20 to 250 staff often satisfy insurers and ISO A 6.3 interviews with dated lists, topic bullets, and follow-up after incidents. The FADP does not literally require training; it requires appropriate technical and organisational measures for data security (Art. 8 FADP). Training is one of the most common organisational measures. This is not legal advice.
This how-to is for finance, HR, or the person who coordinates IT on the side when a questionnaire arrives from an insurer, customer, or ISO audit. After personal data leaves on a lost device, privacy steps are separate; see lost laptop with personal data.
Collect attendance
Sign-in sheet, calendar export, or LMS completion with names and dates. New hires listed separately, not only the annual session.
Document topics
One-page outline: phishing, payments, reporting, passwords and MFA, as delivered.
Store facilitator and language
External trainer or internal owner, German or English, matching the team.
Add effectiveness notes
Report counts, short pulse questions, or a follow-up call summary. Do not invent metrics.
Attach mapping if asked
ISO/IEC 27001:2022 A 6.3 or NIST SP 800-50 on request; training does not certify the firm.
What auditors and insurers actually look for
Forms differ. Answer with what you actually did. Do not invent a universal insurer checklist. What a given insurer requires is set out in its application or questionnaire.
If the question says “annual training”, cite your last live date and the next planned date. If it says “awareness programme”, show more than one slide: last year, this year, onboarding, and what changed after an incident. A supplier audit or a corporate customer often wants the same folder as cyber insurance, with a different cover sheet.
ISO/IEC 27001:2022 A 6.3 expects a formal, ongoing programme for all relevant staff and third parties with access, not a one-off talk. Auditors often learn faster in interviews than from PDFs alone. Finance and HR should tell the same story as the attendance list. Mapping to A 6.3, NIST SP 800-50, or NIST CSF PR.AT can be documented on request; it does not replace a firm certificate.
Deloitte Cyber study 2026, firms under 250 staff: regular cyber training in medium-sized companies. Small firms 65%. Not our survey. Source
The figure does not mean you must match the average. It explains why questionnaires ask about training even when the law does not use the word.
E-learning exports and live sessions
A CSV with completion timestamps is often enough if content and language match your risks (Swiss payment fraud, reporting paths, MFA). Pair it with a live Q and A if finance approves payments or the form asks for “interactive” delivery. Store the export and outline in the same year folder as the live list.
What is not proof: a forwarded marketing brochure, a blank certificate with no names, click-rate posters in the kitchen. “Everyone saw the deck” without a date does not count either.
Onboarding and part-time staff
New hires need their own entry: short session, checklist, or LMS module with a date in the first month. Part-time and home office staff count if they see mail and payments. Someone who only works in the warehouse with no firm account may get different modules; note the exception in the folder instead of forcing one list for everyone.
Filing that survives a leadership change
Store PDFs or scans in one folder per year: invitation, attendee list, topic summary, follow-up notes, and copies of insurer form answers. When leadership changes, the folder survives turnover better than chat threads. Keep copies for as long as customers or insurers ask, usually several years.
Tie training to real processes: the same IBAN checks finance uses in ERP, the same report mailbox IT monitors. When processes change after the session, send a one-page update rather than waiting a year.
Labour and privacy limits
Inform staff before phishing simulations. Do not use awareness metrics for hidden performance scoring of individuals. Art. 26 ArGV 3 and Art. 328b OR frame workplace monitoring; this is orientation, not legal advice. More on simulations: phishing simulations allowed in Switzerland.
A made-up example: supplier audit
A made-up example: a 35-person supplier ships to Germany. The audit asks for awareness evidence. The office sends: June live session attendee list, outline covering payment fraud and reporting, facilitator name, August follow-up note, and onboarding checklist for three hires in September. No firm ISO certificate exists; the auditor accepts the pack and asks finance one question about IBAN verification.
Coordination inside the firm
Name one owner for training records and one for the report mailbox. HR schedules dates, IT checks that examples match your mail system, finance confirms payment stories are accurate. Within a week after the session, send a one-page reminder with the report address and IBAN rule. Schedule follow-up questions before people forget.
Typical team questions to settle in the session: do not forward suspicious mail to private addresses, client files only on allowed channels, MFA exceptions only documented and rare.
If an EU customer passes NIS2 duties by contract, they may expect regular training. The evidence folder helps there as with ISO; whether your contract uses the word “training” belongs in the contract review.
Next step
Prepare the folder before the questionnaire arrives. Security awareness training includes a prep review, live session, and follow-up conversation that you can document for records. Mapping to ISO/IEC 27001:2022 A 6.3 or NIST CSF PR.AT is available on request; the session does not certify the company. Content is aligned with training under the FADP and GDPR without promising a firm-wide certificate.
Does one session satisfy ISO A 6.3 forever?
No. Auditors expect an ongoing programme with refresh and onboarding. Keep dates and topics across years.
Can finance train separately from everyone else?
Yes, if everyone still receives core reporting and MFA content. Payment modules should reach anyone who can approve money movement.
What if the board asks whether we have done “enough”?
Show dates, topics, and an honest metric, such as whether reports rose after the session. Do not promise results you do not measure.
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.
Related Articles
You might also be interested in these articles
Are phishing simulations allowed in Switzerland?
Phishing simulations are allowed in Switzerland if staff are told first and clicks are not used to judge a person. Swiss labour law, not German rules.
Security awareness training topics for Swiss SMEs
Which security awareness training topics belong in a session for Swiss SMEs: phishing, payments, passwords, reporting and role-specific risks.
E-learning vs live security awareness training
E-learning vs live security awareness: when Swiss SMEs need a room, when online modules are enough, and how to combine both without checkbox training.