Swiss SME cybersecurity in 2026: what hosting your CRM changes (and what it does not)

Swiss SME cybersecurity: 49% of employees report a serious incident within 3 months. What Swiss CRM hosting solves, and the 6 settings you should insist on.

DT
Dardan Tushi
Fondateur
14 min read
The manager of a small business confirming a login on her phone, sitting at her desk in front of a laptop in a bright office
CRM security also comes down to how people log in · AI-generated image

In short: hosting your CRM in Switzerland with a Swiss provider settles the question of which law applies and where your data sits. It does not stop a password stolen through phishing, an account left active after someone leaves, or a fake IBAN change. In 2026, cybersecurity for a Swiss SME depends first on six settings and on your people.

Cybersecurity is no longer a big-company topic for Swiss SMEs. According to the Deloitte survey published on 20 August 2026, 49% of the SME employees surveyed report a serious cyber incident at their employer in the past three months. Yet only 22% consider the risk to their company to be high. At the same time, the "data hosted in Switzerland" argument has become standard in CRM offers, including ours. It is real, but it answers a specific question: which law applies to your data and who can demand access to it. It says nothing about how an attacker gets into your customer file. This article separates the two. On one side, what location actually protects. On the other, the settings, habits and reporting obligations that remain your responsibility, whether your CRM runs in Geneva, Frankfurt or Virginia.

Are Swiss SMEs really targeted by cyberattacks?

Yes, and more than they think. Almost one SME employee in two reports a serious incident within three months. In micro-businesses with 1 to 9 people, the figure is 38%, while only 15% there consider the risk to be high. Phishing remains the most frequently cited threat.

These figures come from Deloitte's SME cybersecurity index, based on 924 employees of Swiss companies with 249 people or fewer. A quarter of respondents name phishing as the most common threat. The gap between exposure and perception is the real problem: an SME that believes it is too small to interest an attacker configures nothing.

Data from the Federal Office for Cybersecurity (NCSC) points the same way. In the second half of 2025, the office received 29,006 voluntary reports and 145 mandatory reports. Ransomware rose from 47 to 79 cases from one second half-year to the next, and the Akira group alone claimed 26 known attacks on Swiss companies during the half-year. CEO fraud and fake payment orders (Business Email Compromise) climbed from 49 to 73 cases, one of which cost CHF 1.5 million. Phishing reports reached 6,299, 17% more than a year earlier.

For an SME, the CRM holds exactly what these attacks are after: customer contact details, the history of exchanges, quote amounts, sometimes bank details. An exfiltrated customer file can be used to stage a convincing phishing campaign against your own customers, in your company's name.

What does Swiss hosting protect, and what does it not?

Swiss hosting with a Swiss provider protects you on the legal front: applicable law, jurisdiction, access by foreign authorities, a simple privacy notice. It does not protect you against attacks that go through your users: stolen credentials, overly broad permissions, an infected computer, a fake payment order. Those risks depend on your settings.

The first benefit is legal. The 2018 CLOUD Act allows US authorities to compel a US provider to hand over data, whether it is stored in the United States or abroad. According to several lawyers, data hosted in Zurich by a US group could therefore, under certain conditions, be requested from across the Atlantic; how far this law really reaches against Swiss law remains a matter of debate. A Swiss provider hosting in Switzerland falls outside this scenario. We have covered these differences between Swiss and European hosting in a dedicated guide.

The second benefit is organisational: one law, one country to name in your privacy notice, and a contact who can be reached in your language if an incident occurs. Beyond that, location changes nothing about how an attack succeeds. The table below sorts things out.

RiskDoes Swiss hosting solve it?What actually solves it
Access by a foreign authority through the provider's parent companyYes, if the provider is also SwissJurisdiction of the provider and its subprocessors
Country to disclose to your customersYesAn up-to-date privacy notice
Password stolen through phishingNoMandatory multi-factor authentication
Employee who can see the entire customer fileNoRole-based access rights
Former employee's account still activeNoOffboarding procedure, deactivation on the same day
Ransomware on a workstationNo, for local filesUpdates, tested backups
Fake IBAN change sent to a customerNoSystematic call-back, training
Quiet mass export of contactsNoAccess and export log

An honest reading: of eight risks, hosting solves two. These are two questions your customers and clients ask more and more often, and it would be wrong to play them down. But an SME that stops there has dealt with the legal side and left the front door open.

Which security settings should you demand from your CRM?

Six settings cover the essentials: enforced multi-factor authentication, role-based access rights, immediate account deactivation, an access and export log, backups with full export, and encryption plus a data processing agreement. If your CRM does not support one of them, that is a selection criterion, not a detail.

The revised Federal Act on Data Protection (FADP) does not draw up this list, but it lays down the principle. Art. 8 FADP requires the controller and the processor to ensure adequate security of personal data through technical and organisational measures proportionate to the risk. These six settings are its practical translation for an SME CRM. They complement the criteria for choosing a CRM for a Swiss SME.

1. Multi-factor authentication enforced for everyone

According to Deloitte, 66% of companies use MFA, which means one in three does not. The NCSC also recommends it, alongside keeping systems up to date. A password obtained through phishing is then no longer enough to get in. Insist that an administrator can enforce it for all accounts, rather than leaving it optional for each user.

2. Role-based access rights

The intern entering contacts does not need to export the whole file or see your margins. A serious CRM distinguishes at least between read, edit, export and administration. The fewer accounts with full rights, the less damage a compromised account can do.

3. Deactivating accounts on the day someone leaves

A salesperson who leaves for a competitor with an account still active is a leak risk and a data security breach. Write deactivation into your offboarding procedure, just like returning the laptop, and check that the CRM keeps the history of the deactivated account.

4. Access and export log

Without a log, you do not know who exported what, or when. Yet that is exactly the information you will be asked for when assessing a leak. The minimum: logins, exports and mass deletions, timestamped and linked to a user.

5. Backups and full export

Deloitte recommends tested backups, not just backups that exist on paper. Ask the provider how often backups are made, where they are stored and how long a restore takes. Also check that you can export all your data in an open format: it is your safeguard in case of a dispute or if the provider fails.

6. Encryption and data processing agreement

Encryption in transit and at rest, a list of subprocessors with their countries, and a commitment to notify you of any incident. That last point follows from Art. 24 para. 3 FADP: the processor must notify the controller as soon as possible of any data security breach. Your contract should specify the channel and the time frame.

Do you have to report a cyberattack to the NCSC?

Only if you operate critical infrastructure: since 1 April 2025, these organisations must report a cyberattack to the NCSC within 24 hours, with fines applying since 1 October 2025. For an ordinary SME, reporting to the NCSC is voluntary. Notifying the Federal Data Protection and Information Commissioner (FDPIC), however, may be mandatory if personal data is affected.

The Federal Council set the entry into force of the reporting obligation at 1 April 2025, with a 24-hour deadline after detection. According to the NCSC's six-month review, penalties have applied since 1 October 2025 and the fine can reach CHF 100,000 for an operator who fails to report. The half-yearly report published on 30 March 2026 counts 325 mandatory reports since entry into force. An SME active in energy, healthcare, telecoms or transport should check whether it falls within the scope.

For everyone else, the NCSC reporting platform remains useful: a few guided questions, an initial automatic assessment with suggested measures, then the option of passing the case on to the office. It does not replace a criminal complaint, which is normally filed at a police station.

The obligation that really concerns SMEs lies elsewhere. Under Art. 24 para. 1 FADP, the controller must notify the FDPIC as soon as possible of any data security breach that is likely to result in a high risk for the data subjects. The notification must state at least the nature of the breach, its consequences and the measures taken or planned. The FDPIC provides an online form, described by Weka, and the controller documents every breach: that documentation must be kept for at least two years from the notification (Art. 15 para. 4 DPO). The concepts of controller and processor are explained in our FADP glossary for SMEs.

How can you secure your CRM in half a day?

In six steps: take stock of accounts, enforce MFA, review roles, check the log, test a restore and formalise your incident response. Allow about four hours for an SME with ten users, with no external provider or extra budget if your CRM already offers these features.

Estimated time: 240 minutes
  1. 1

    Take stock of accounts

    30 min

    Export the list of CRM users and compare it with your staff list. Deactivate any account belonging to a former employee, a finished intern or a contractor with no current assignment.

  2. 2

    Enforce multi-factor authentication

    45 min

    Make MFA mandatory at administration level, not just optional. Warn the team the day before and plan a fallback procedure in case someone loses their phone.

  3. 3

    Review roles

    45 min

    Limit export rights and the administrator role to two people at most. Remove access to financial data for anyone who does not need it.

  4. 4

    Check the log

    30 min

    Make sure logins and exports are logged. Go through the last thirty days looking for mass exports or unusual logins.

  5. 5

    Test a restore and an export

    45 min

    Ask the provider how often and where backups are made. Run a full export in an open format and check that it opens and is complete.

  6. 6

    Formalise your incident response

    45 min

    Write one page: what to shut down, whom to call at the provider, how to assess the risk for the data subjects, when to notify the FDPIC and where to report to the NCSC. Add the rule of calling back before any change to bank details.

Where should you start, depending on your situation?

Your customers are still in a shared spreadsheet. This is the most exposed situation: no MFA specific to the file, no roles, no log, and copies circulating by email. The priority is to move to a tool that manages access. We have covered the limits of an Excel-based CRM and the point at which they become a risk.

Your CRM is with a foreign vendor. Start with the six settings: they matter more for your day-to-day exposure than a migration. Then assess the legal question (parent company, subprocessors, countries to disclose) in light of your customers and your sector. For a fiduciary firm or a medical practice bound by professional secrecy, this second question carries more weight.

Your CRM is already hosted in Switzerland. The legal side is settled. Your risk now lies in accounts and people: work through the checklist above, then invest in training on phishing and fake IBAN changes, two threats the NCSC sees on the rise.

How much does CRM security cost an SME?

Mostly time rather than money. MFA, roles and account deactivation are settings, not purchases. The item you really pay for is cover for the residual risk: only 11.5% of companies domiciled in Switzerland are insured against cyber risks.

This rate comes from Deloitte, drawing on figures from the Swiss Insurance Association: around 72,000 business cyber policies taken out in 2025. In other words, almost nine companies in ten bear the cost of an incident alone. A single fake payment order case recorded by the NCSC in the second half of 2025 cost CHF 1.5 million.

There is also a direct legal cost. Art. 61 FADP punishes, on complaint, with a fine of up to CHF 250,000 anyone who wilfully fails to comply with the minimum data security requirements set by the Federal Council. The fine is in principle aimed at the responsible individual, often the managing director: see what the FADP requires of business owners personally. Against these amounts, the real calculation concerns the CRM's full subscription, with MFA, roles and log included, not an entry-level price to which security options must be added. Our FADP compliance audit of a CRM details the points to check in the contract.

FAQ: SME cybersecurity and CRM hosting

Is a CRM hosted in Switzerland safer than one hosted abroad?

It is simpler from a legal standpoint, especially if the provider is also Swiss: a single law applies and the scenario of access via the CLOUD Act disappears. On the technical side, security depends on the settings (MFA, roles, log) and on your team's practices, whatever country the servers are in.

Does my SME have to report a cyberattack to the NCSC?

No, unless it operates critical infrastructure. Since 1 April 2025, only these organisations must report a cyberattack within 24 hours, with fines of up to CHF 100,000 applying since 1 October 2025. Other companies can report voluntarily on the NCSC platform.

When must a data breach be notified to the FDPIC?

When the data security breach is likely to result in a high risk for the data subjects, for example sensitive data, a large volume or a risk of identity theft. Notification must be made as soon as possible and state at least the nature of the breach, its consequences and the measures taken or planned.

Is MFA enough to protect my CRM?

It prevents a stolen password from being enough to get in, but it does not deal with an account left active after someone leaves, overly broad permissions, or a fake payment order sent by email. Combine it with roles, an export log and an offboarding procedure.

Is cyber insurance useful for a small SME?

It covers part of the risk that remains once the settings are in place, depending on the policy terms. Only 11.5% of companies domiciled in Switzerland have one, which means most bear the cost of an incident alone. Put the basic settings in place first, then compare offers on what they actually cover.

Who is responsible for which layer of security?

Cybersecurity for a Swiss SME rests on two layers. Location and jurisdiction depend on your choice of provider: a Swiss CRM hosted in Switzerland settles them once and for all. Access, roles, backups and reflexes against phishing are down to you, and no hosting arrangement takes care of them for you. Remember three points: enforce MFA on every account this week, deactivate accounts on the very day someone leaves, and know in advance when a breach must be notified to the FDPIC.

Done well, this double layer becomes a sales argument. When a customer or client asks you where their data is and who can access it, a precise answer covering both layers is more reassuring than a label. Helvee is a CRM hosted in Switzerland and designed for the FADP. To check how it handles the six settings in this article, contact us.

Topicscybersecuritysmescrmswiss-hostingfadpncscmulti-factor-authentication
DT
Written by

Dardan Tushi

Entrepreneur suisse, passionné de SaaS et de souveraineté numérique. Fondateur de Pixelab Sàrl.

Try Helvee for free

The 100% Swiss CRM for SMEs. 30-day trial, no card required, nFADP-compliant by design.