data protection

Data protection vs information security in Swiss SMEs

AA
Aurum Avis Labs Author
7 min read

Data protection vs information security

Data protection vs information security is the split between lawful, transparent handling of personal data and the controls that keep systems confidential, intact and available. In a Swiss SME both matter under the revised FADP, but they answer different questions. Data protection asks whether you may process data, for how long, and what you tell people when something goes wrong. Information security asks whether passwords, backups and phishing defences work when someone targets finance on a Tuesday morning.

This comparison is for management, HR and the IT partner in a firm with about 20 to 250 staff. It is orientation, not legal advice.

Data protection

Purpose, rights, privacy notices, contracts with processors, breach notification to the FDPIC when high risk is likely.

Information security

Access control, MFA, patching, backups, incident response to cyber events, awareness on phishing and fraud.

Where the FADP joins both

Art. 8 FADP requires appropriate technical and organisational measures for data security. “Organisational” covers training, policies and who may export a payroll file. “Technical” covers encryption, firewalls and logging. You cannot satisfy Art. 8 with a privacy notice alone, and you cannot satisfy it with a firewall alone if staff paste customer lists into unapproved tools.

Typical data protection work

Publish and maintain a privacy notice. Answer access requests. Keep processor agreements for cloud and payroll vendors, as in our guide on data processing agreements under the FADP. Decide whether a wrong email needs FDPIC notification. Run retention and deletion for HR and CRM. Train people on minimum necessary sharing and internal reporting.

Typical information security work

Roll out MFA, patch servers, test backups, review admin accounts, run phishing awareness, define who may approve payment changes, and report cyber incidents on the internal path. Most SMEs are not subject to the BACS cyber reporting duty for critical infrastructure; they still need a response plan when ransomware locks the file server.

Overlap that confuses teams

Ransomware is information security first and may become a data protection breach if personal data were exfiltrated. A phishing click sits in security training until credentials leak customer data. CEO fraud is process and culture; if customer IBANs were exposed, privacy documentation joins the folder.

  • Wrong email with a payroll attachment

    Data protection leads on notification and rights; IT leads on access logs and mailbox rules.

  • Shared password on a CRM export

    Security fixes access; HR or sales documents who received the file and for how long.

  • Invoice fraud with no data leak

    Mostly security awareness and payment controls; privacy stays in the background unless customer records were visible.

Who owns what in a small company

The owner or delegate sets risk appetite. HR owns applicant and employee files. Finance owns payment fraud process. IT or the external partner owns technical controls. Without labels, everything lands on “the person who does IT on the side”. Splitting a privacy contact from a security contact helps, even if one person wears both hats part-time.

Two trainings, one culture

Data protection training explains lawful bases, rights, safe email habits, and when to escalate to management about a breach. Security awareness training explains phishing, smishing, passwords, MFA fatigue, invoice fraud and internal reporting of cyber events. Auditors and insurers increasingly ask for both records.

65% / 82%

Deloitte 2026, firms under 250 staff: regular cyber training in small and medium companies. Not our survey. Deloitte study PDF.

Privacy training is often the gap after the 2023 FADP revision, even when MFA is already in place.

Aurum delivers both as live sessions of one to two hours after a short needs conversation, remotely or on site in Switzerland, in German or English. A combined day covering security awareness and data protection is the usual format when leadership wants one calendar block rather than two half-days months apart.

When you need only one first

A firm with strong IT hygiene but no privacy notice or breach process should prioritise data protection. A firm with polished GDPR PDFs but shared passwords and no phishing reporting should prioritise security awareness. Most readers of this site need both within the same quarter.

What neither training replaces

Penetration tests, ISO certification, 24/7 SOC, or a full-time CISO. Training does not write your processor contracts or restore backups. It aligns people with decisions technology already supports.

ISO and NIST mapping

Customers may ask how awareness maps to ISO/IEC 27001:2022 control A 6.3 or NIST SP 800-50. Aurum can describe mapping on request; sessions do not certify the company.

A made-up example: two gaps, one audit

A made-up example: a 45-person fiduciary passes an IT health check with MFA and backups. The auditor then asks for privacy training records and breach documentation. None exist beyond a 2018 slide deck. The next month they run data protection training for all client-facing staff. The quarter after, security awareness for everyone with mailbox access. Incident forms split “cyber” and “personal data” sections. The audit file shows two attendance lists and one combined management review. Neither session alone would have answered every question.

Practical sequencing

Month one: privacy notice and processor contracts. Month two: data protection training. Month three: security awareness. Same year: test restore from backup and tabletop on wrong email plus phishing. Link everyday mistakes to email sent to the wrong recipient and reporting a breach to the FDPIC.

Questionnaires from insurers and customers

Cyber insurers ask about MFA and backups. Corporate customers ask about training dates and breach history. One generic “we take security seriously” paragraph fails both. Split attachments: one page on technical controls from IT, one on data protection training attendance from HR.

Supplier and EU customer questionnaires

EU customers pass security questionnaires down the chain even when NIS2 does not apply directly to your firm. Security awareness answers phishing and access; data protection answers processor contracts and retention. Treat them as two curricula, not one boilerplate PDF. A combined training day does not replace a written annual plan with measurement; that is a separate topic in the blog.

Choosing external help

IT partners excel at tools; they rarely want to facilitate live behaviour training in German for finance and reception. A specialist session frees them to patch while staff ask about real processes.

Phishing simulations vs data protection drills

Phishing simulations measure click rates; they do not replace instruction on access requests or breach escalation. Data protection training does not explain why MFA matters when a supplier changes bank details. If a customer asks for an “awareness programme”, plan both and keep attendance lists separate so audits can see which curriculum ran when.

After an incident

Teams often schedule only a data protection refresher after a breach, or only IT drills after ransomware. If the event touched both personal data and systems, run both follow-ups in the same quarter so staff do not assume one department owns the whole story.

Board reporting in one slide

Two bullets are enough: last data protection training date and last security awareness date, plus open actions (encryption gap, pending DPA). Directors want dates and owners, not statute articles.

  • Make the privacy and security contact visible on the intranet or wiki
  • Keep two incident templates: cyber and personal data, with one shared timeline
  • Hold attendance lists for recent sessions ready for questionnaires

Remote work and mixed language teams

Home Wi-Fi and personal printers touch security. A customer call on speaker while family listens touches privacy. Combined training gives staff language for both where possible. English product names on tools are fine; briefings in the language of the warehouse or reception reduce mistakes on the same incident timeline.

Overview of both trainings, including a combined day: Security and privacy training for Swiss SMEs. For data protection topics see data protection awareness. For security awareness see Security awareness training.

data protection information security awareness switzerland training
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.