Written by Alexis Hirschhorn, CEO of Acuna GRC. ISO/IEC 27001 Lead Auditor, ISO/IEC 42001 Lead Auditor, PECB Certified Trainer; leads ISO 27001 and ISO 42001 implementations for Swiss organisations. Resilience review by Henri Haenni, President of Abilene Group, business continuity, operational resilience and DORA (DRI CBCP).
The legal statements in this article rest on primary sources (Fedlex, FINMA, the National Cyber Security Centre, the FDPIC, EUR-Lex), listed under Sources.
This article provides general information about Swiss and EU regulatory frameworks as at 16 November 2026. It is not legal, regulatory, tax or compliance advice, does not create a lawyer-client or advisory relationship, and should not be relied on to determine whether a specific law applies to your organisation. Regulatory scope depends on facts such as legal form, establishment, licensing, products, customers, data flows, contracts and group structure. Obtain advice from a qualified Swiss and, where relevant, EU lawyer before making compliance decisions. Laws, guidance and implementation dates change.
The short answer. A Swiss company must comply with the Federal Act on Data Protection (FADP, SR 235.1). If it falls within the reporting scope of the Information Security Act (ISA, SR 128), it must since 1 April 2025 report qualifying cyberattacks to the NCSC within 24 hours. Financial institutions add FINMA rules. GDPR, NIS2, DORA, the CRA and the AI Act can apply through links to the EU market or an EU establishment.
See how Acuna GRC covers each regulation →
Picture a Swiss bank hit by ransomware on a Friday evening. It may owe three reports, to three authorities, on three different clocks. If the bank is in the ISA's scope and the attack qualifies, the National Cyber Security Centre wants a report within 24 hours. FINMA wants an initial notice within 24 hours and a full report within 72. The data protection commissioner wants to hear "as quickly as possible" if personal data is at high risk. If the same group also sells connected devices in the EU, ENISA gets a report too.
Most guides on Swiss compliance cover one of those laws. This one covers all of them on one page. It separates the home rules that apply because you are in Switzerland from the export rules that follow your products, customers or group structure into the EU. It then sets out what to do first, which skills your team needs, and when outside help is worth paying for.
Think of it as the SBB network map. The FADP is the main line every company rides. FINMA and the ISA are branch lines for finance and critical infrastructure. The EU laws are the international connections at Geneva and Basel: you only take them if your business actually crosses the border.
- FADPEvery firm handling personal data
- ISA: 24-hour cyber reportingOrganisations in its reporting scope
- FINMASupervised financial institutions
- GDPRYou offer goods or services to, or monitor, people in the EU
- NIS2Through an EU subsidiary, EU-facing cloud or DNS, or client contracts
- DORAThrough EU subsidiaries or branches, or ICT services to EU finance
- Cyber Resilience ActYou sell products with digital elements in the EU
- AI ActYour AI system, or its output, is used in the EU
Which rules apply to my company?
These seven questions identify possible compliance triggers. A "yes" does not by itself establish that a law applies; it marks an area that needs a documented scope assessment. This is general information, not legal advice: confirm your scope with a qualified lawyer.
| # | Question | If yes: possible trigger, assess scope |
|---|---|---|
| 1 | Do you process personal data of people in Switzerland? | The FADP may apply. The GDPR may also apply if the processing has an EU link: an EU establishment, offering goods or services to people in the EU, or monitoring them. If you process data for an EU controller, GDPR terms reach you through the contract. |
| 2 | Are you supervised by FINMA? | FINMA requirements may apply. The duties depend on your licence category and business model. Circular 2023/1 is addressed to banks and securities firms; the cyber reporting duty in Guidance 05/2020 covers all supervised institutions. |
| 3 | Are you an authority or organisation listed in Art. 74b ISA? | ISA reporting may apply. Confirm you are not exempt under Art. 12 of the Cybersecurity Ordinance, and assess each attack against the reporting criteria. |
| 4 | Do you have an EU subsidiary or establishment? | NIS2 and the GDPR may apply through the EU entity. Scope depends on its activities, role and size; an establishment alone does not trigger either law. |
| 5 | Do you provide ICT services to EU financial entities? | DORA requirements may reach you through contracts. DORA binds the EU financial entity; its ICT third-party rules flow down through your contracts. |
| 6 | Do you make or sell products with digital elements on the EU market? | The CRA may apply. Confirm the product's classification, your role (manufacturer, importer, distributor), exclusions and transition dates. |
| 7 | Do you develop, supply or use AI systems with a link to the EU? | The AI Act may apply. Determine your role (provider, deployer, importer, distributor), the system's risk class and the applicable dates. |
Size matters differently under each law. NIS2 generally applies from medium-sized organisations upwards, and DORA scales by proportionality. The ISA duty depends first on whether you are on the Art. 74b list and whether the attack meets the reporting criteria; the Cybersecurity Ordinance then exempts some organisations, by size in some sectors and by role in others.
The Swiss regulation map
Eight rulebooks, one table: what each law asks, who enforces it, and where the evidence lives in Acuna GRC.
| Law | Applies to | Key obligation | Deadline or window | Authority | Sanctions | Acuna GRC module |
|---|---|---|---|---|---|---|
| FADP / LPD (SR 235.1) | Anyone processing personal data in Switzerland | Record of processing, DPIA, breach notice (Art. 24) | Breach: "as quickly as possible" | FDPIC | Up to CHF 250,000, on individuals | Data Privacy |
| ISA / LSI (SR 128) | Authorities and organisations listed in Art. 74b ISA, unless exempt | Report qualifying cyberattacks | 24 h, completed within 14 days | NCSC (BACS) | Up to CHF 100,000 | Core GRC: incident issues, risks, BIA |
| FINMA Circ. 2023/1, Guidance 05/2020 | Banks and securities firms (Circ. 2023/1); all supervised institutions for cyber reporting (Guidance 05/2020) | Operational risk, ICT, cyber, BCM; cyber reporting | 24 h initial notice, 72 h full report | FINMA | Supervisory measures | Core GRC, TPRM |
| GDPR | Swiss firms offering to or monitoring people in the EU, or with an EU establishment | Art. 3(2) scope, EU representative, 72 h breach notice | 72 h | EU supervisory authorities | Up to EUR 20m or 4% (higher tier); EUR 10m or 2% otherwise | Data Privacy |
| NIS2 | EU establishments that are essential or important entities; qualifying non-EU providers serving the EU | Art. 21 measures, supply chain, reporting | 24 h / 72 h / 1 month | EU national authorities | Maximum of at least EUR 10m or 2% (essential), EUR 7m or 1.4% (important); states may go higher | Core GRC, TPRM |
| DORA | EU subsidiaries that are DORA financial entities; EU branches of Swiss banks and insurers (Commission's view, Q&A DORA 102); ICT providers to EU finance, through contracts | ICT risk framework, register of information, contract clauses | Applies since 17 Jan 2025 | EU financial supervisors | Set by member states | TPRM, Core GRC |
| CRA | Manufacturers, importers and distributors of products with digital elements on the EU market | Vulnerability handling, incident reporting, conformity | 24 h / 72 h; full 11 Dec 2027 | CSIRTs and ENISA (reports); market surveillance authorities (enforcement) | Up to EUR 15m or 2.5% (essential requirements); lower tiers for other breaches | Vulnerability management, Core GRC |
| AI Act (amended by 2026/1744) | Providers, deployers, importers and distributors with an EU link | AI inventory, risk classification, AI literacy, transparency | Annex III high-risk: 2 Dec 2027 | EU AI authorities | Up to EUR 35m or 7% (prohibited practices); up to EUR 15m or 3% for other obligations | AI Governance, Staff Portal |
"Applies to" describes possible triggers, not conclusions. Whether a law applies depends on your facts.
Home rules: FADP, ISA and FINMA
Three Swiss rulebooks apply because of where you are, not whom you sell to. The FADP applies to nearly everyone; the ISA and FINMA apply to defined sectors.
FADP: the baseline for every company
The revised FADP has applied since 1 September 2023 and is now simply "the FADP" (you will still see "revFADP" or "nLPD"). Four obligations generate most of the work:
- Record of processing activities (Art. 12). A statutory exemption may apply to companies with fewer than 250 employees whose processing poses a negligible risk (Art. 12(5) FADP, implemented in Art. 24 of the Data Protection Ordinance).
- Data protection impact assessment (Art. 22) when processing is likely to bring a high risk.
- Breach notice (Art. 24) to the FDPIC "as quickly as possible" when a breach likely brings a high risk, through databreach.edoeb.admin.ch. There is no fixed 72-hour rule. A processor must inform the controller of any data security breach as quickly as possible (Art. 24(3)); the duty to notify the FDPIC normally sits with the controller.
- Processor contracts and cross-border transfers, documented and kept current.
Fines reach CHF 250,000 and target individuals, for intentional acts only. A company can be fined up to CHF 50,000 when finding the responsible person would be disproportionate. Cantonal prosecutors impose them, not the FDPIC. That personal exposure is why FADP compliance tends to land on a named manager's desk. In 2025/26 the FDPIC received more than 2,000 reports of potential violations and carried out 22 preliminary investigations and 9 investigations.
ISA: 24 hours to report a cyberattack
Since 1 April 2025, authorities and organisations subject to the ISA reporting obligation must report qualifying cyberattacks to the NCSC within 24 hours of discovery, through the Cyber Security Hub. The report can be completed within 14 days where information is not yet available. The duty is not triggered by every cyber incident: it depends on the organisation's designation and on the nature and impact of the attack. Since 1 October 2025, an operator that ignores an NCSC order to report can be fined up to CHF 100,000. The NCSC must first contact the operator and set a deadline, then issue a formal order.
The ISA covers designated authorities and organisations listed in Art. 74b, such as energy and drinking-water suppliers, transport companies and cantonal and communal administrations. It is not a general duty for every Swiss business. Art. 12 of the Cybersecurity Ordinance exempts some of them below sector-specific thresholds, for example universities with fewer than 2,000 students. Reportable attacks include those that threaten the functioning of the infrastructure, lead to information being manipulated or leaked, or involve blackmail, threats or coercion.
Two mistakes recur. The 24-hour duty does not apply to every company, only to authorities and organisations within the ISA's reporting scope, and only to qualifying cyberattacks. And the ISA report is not the FADP breach notice: one incident can require both, to two different authorities.
FINMA: operational resilience for the financial sector
FINMA Circular 2023/1 "Operational risks and resilience - banks" has applied to banks and securities firms since 1 January 2024. It covers ICT risk, cyber risk, critical data, business continuity and operational resilience. Other FINMA-supervised institutions face requirements that depend on their licence and business model. The cyber reporting duty is wider: under Art. 29 para. 2 FINMASA and Guidance 05/2020, clarified by Guidance 03/2024, every supervised institution notifies its FINMA account manager within 24 hours of discovering a cyberattack that meets the criteria of Guidance 05/2020. It then files the full report through the EHP platform within 72 hours. Our FINMA page covers the circular in more depth.
Two details catch teams out. When an outsourcing provider detects the attack, the 24 hours start when the provider learns of it. And FINMA's Risk Monitor 2025 names outsourcing among its principal risks. Your supplier register is part of your incident readiness.
One incident, three clocks
The deadlines start at different moments and run at different speeds. Agree before an incident who files which report.
- NCSC (ISA)Critical infrastructure
- Discovery
- 24 hoursReport
- 14 daysComplete report
- FINMASupervised institutions
- Discovery
- 24 hoursInitial notice
- 72 hoursFull report (EHP)
- FDPIC (FADP)If high risk to people
- Discovery
- "As quickly as possible": no fixed hours
- ENISA (CRA)Makers selling in the EU
- Discovery
- 24 hoursEarly warning
- 72 hoursNotification
- LaterFinal report: 1 month after the notification
One relief for financial institutions: under FINMA Guidance 03/2024, an institution also subject to the ISA may file its 24-hour initial notice through the NCSC form and have it forwarded to FINMA, provided it gets there in time. The 72-hour report still goes through FINMA's EHP. Separately, under FADP Art. 24(5bis), the FDPIC may forward a breach notice to the NCSC for analysis, with the controller's consent.
"In a real incident, the first hour is usually lost to decision-making, not technology. Teams know they must report, but not who decides whether an event is reportable, who contacts FINMA, who drafts the FDPIC notice, or who can reach the right person outside office hours. Set those roles and escalation contacts before an incident, and keep them accessible without relying on a laptop, email or the affected network."
Henri HaenniPresident of Abilene GroupNeutral doesn't mean exempt: EU laws that reach Swiss firms
Switzerland is outside the EU, but EU law follows your customers, subsidiaries and products across the border. In practice it rarely arrives as a regulator's letter. It arrives as a contract clause or a security questionnaire from an EU customer.
GDPR. It can apply to a Swiss company that processes personal data in the context of offering goods or services to people in the EU, or monitoring their behaviour (Art. 3(2)).
- It can also apply through an EU establishment, and EU controllers will impose GDPR terms on you if you process data for them.
- It does not apply merely because your website can be reached from the EU, because a few customers happen to live there without your having sought them, or because you use an EU-based supplier.
- Unlike the FADP, the GDPR sets a 72-hour breach deadline.
NIS2. The directive does not apply in Switzerland directly.
- It may reach a Swiss group through an EU establishment that is an essential or important entity.
- A Swiss cloud, data-centre, DNS, domain, managed-service or online-platform provider that offers its services in the EU and falls within NIS2's scope must appoint an EU representative under Art. 26.
- Most often, NIS2 arrives as contractual requirements derived from customers' own risk-management and supply-chain duties.
- A targeted amendment proposed by the Commission in January 2026, COM(2026) 13, would change the jurisdiction and representative rules; it is still before the European Parliament and the Council and has not been adopted.
DORA. The regulation has applied since 17 January 2025.
- It does not apply to a Swiss bank or insurer merely because it is Swiss.
- It applies to EU subsidiaries that are financial entities within DORA's scope.
- In the Commission's answer in the joint ESAs Q&A DORA 102, it also applies to EU branches of third-country credit institutions and (re)insurers, so treat an EU branch as in scope unless you have advice to the contrary.
- It reaches Swiss ICT providers indirectly, through the contract terms in Art. 28 to 30 that their EU financial clients must impose.
- FINMA Circular 2023/1 overlaps with DORA, but it is not equivalent to it.
Cyber Resilience Act. It can apply to Swiss manufacturers of products with digital elements made available on the EU market, and to the importers and distributors that sell them there, subject to its scope and exclusions.
- Since 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe incidents through ENISA's platform.
- The main obligations apply from 11 December 2027.
- In practice, border checks are moving to the factory gate: expect EU importers and distributors to ask for your conformity documentation.
AI Act. It can apply to Swiss organisations that place an AI system on the EU market or put it into service there, or whose AI system produces output that is used in the EU, as provider or deployer.
- Importers and distributors of AI systems in the EU are covered too.
- Prohibitions and the Art. 4 AI-literacy duty have applied since 2 February 2025; other obligations apply on different dates.
- The AI Omnibus, Regulation (EU) 2026/1744, is adopted law, in force since 27 July 2026. It moved Annex III high-risk duties to 2 December 2027 and Annex I duties to 2 August 2028.
- Switzerland does not yet have a comprehensive, AI-specific federal statute comparable to the EU AI Act. It has taken a sector-specific approach and intends to ratify the Council of Europe AI Convention; a consultation draft is expected in spring 2027.
"For many Swiss service providers, NIS2 and DORA first arrive as customer due diligence, not as a regulator's letter: a security questionnaire, an audit-rights clause, evidence requests and a deadline before contract renewal. The organisations that manage this well maintain a current supplier register, a controlled set of security answers and evidence that can be reused consistently. Rebuilding the same answer from scratch each time creates avoidable inconsistency, and inconsistency is what assessors notice."
Alexis HirschhornCEO, Acuna GRC; ISO/IEC 27001 Lead Auditor and ISO/IEC 42001 Lead AuditorKey deadlines 2023 to 2028
Ten of these milestones are already behind us, so most obligations here are live today, not future.
- Revised FADP in forceIn force:
- FINMA Circular 2023/1 in forceIn force:
- NIS2 transposition deadlineIn force:
- DORA appliesIn force:
- AI Act bans and AI literacyIn force:
- ISA 24-hour reporting dutyIn force:
- AI Act general-purpose AI rulesIn force:
- ISA fines up to CHF 100,000In force:
- AI Omnibus 2026/1744 in forceIn force:
- CRA reporting liveIn force:
- You are here: Nov 2026
- New AI Act prohibitions (Article 5)Still ahead:
- Swiss AI law consultationStill ahead:
- AI Act Annex III high-riskStill ahead:
- CRA applies in fullStill ahead:
- AI Act Annex I high-riskStill ahead:
The next crunch is December 2027, when AI Act Annex III high-risk duties (2 Dec) and the CRA's full application (11 Dec) land nine days apart. Before that, new AI Act prohibitions apply from 2 December 2026. The Swiss AI consultation is expected in spring 2027; the exact date is not yet set.
Where to start: the first 90 days
Start with what every rulebook asks for, not with the most frightening one. Five controls cover most of the map at once.
- Incident procedure and log
- FADP
- ISA
- FINMA
- GDPR
- NIS2
- DORA
- CRA
- AI Act
- Risk register and assessments
- FADP
- FINMA
- GDPR
- NIS2
- DORA
- CRA
- AI Act
- Supplier register
- FADP
- FINMA
- GDPR
- NIS2
- DORA
- Record of processing
- FADP
- GDPR
- AI inventory
- AI Act
- Settle your scope in writing (weeks 1 to 2). Answer the seven questions above and record the reasoning, especially on the ISA and DORA. A dated scoping note is the first thing an auditor or a customer's assessor will ask for.
- Build one record of processing (weeks 2 to 6). It serves the FADP and the GDPR, and it tells you which systems and suppliers hold personal data.
- Write one incident procedure with all the clocks in it (weeks 4 to 8). Name who decides whether an event is reportable, who files with the NCSC, FINMA, the FDPIC or ENISA, and keep a single incident log. One log serves all eight rulebooks.
- Start a supplier register (weeks 6 to 10). NIS2, DORA and FINMA's outsourcing rules all ask what your providers do and how they are secured. FINMA's Risk Monitor 2025 names outsourcing among its principal risks.
- List the AI in use (weeks 8 to 12). Include tools bought off the shelf. Without an inventory you cannot classify anything under the AI Act, and the AI-literacy duty has applied since February 2025.
The principle behind the list: map once, comply many times. Each control above is evidence for several laws.
One passport, many visas: the controls are the passport, and each law is a stamp you add by showing the same document at a different border. The record of processing is your data's land register, like a cantonal cadastre: once it exists, every new question about your data is paperwork, not a survey.
"Start with the shared foundations, not the most intimidating framework. A current inventory of personal data, suppliers, incidents and AI systems supports several obligations at once. The step most often missed is assigning an accountable owner to each control. In a smaller organisation, one person may own several controls, but that should be a deliberate, documented decision, not something discovered during an audit."
Alexis HirschhornCEO, Acuna GRC; ISO/IEC 27001 Lead Auditor and ISO/IEC 42001 Lead AuditorThe skills behind the map: who needs which training
Three of these laws build training into the obligations themselves, each in a different way. Since 2 February 2025, the AI Act (Art. 4) has required providers and deployers to act on the AI literacy of staff who operate or use AI systems. The AI Omnibus reworded the duty in July 2026: companies must take measures to support AI literacy, without having to guarantee a set level for each person. Under NIS2 Art. 20(2), members of management bodies must follow training themselves, and entities are encouraged to offer similar training to their employees regularly. Under DORA Art. 5(4), members of the management body must keep their own knowledge of ICT risk up to date, including through regular training, and under Art. 5(2)(g) they approve the budget for staff security awareness and resilience training. They are three distinct duties, not one.
The right course depends on the role, not on the regulation:
| Role | What they need to be able to do | Why it matters here | Typical training |
|---|---|---|---|
| Board and executive management | Approve risk appetite, understand incident duties, sign off AI use | NIS2 Art. 20, DORA Art. 5, personal FADP fines | Short executive briefing on Swiss and EU duties |
| CISO, ISMS lead | Run a management system that answers ISA, FINMA and NIS2 controls | ISO/IEC 27001 is the shared vocabulary of auditors and supplier questionnaires | ISO/IEC 27001 Lead Implementer or Lead Auditor |
| AI lead, product owner, data scientist | Inventory, classify and assess AI systems; set human oversight | AI Act risk classes and Annex III dates | AI governance and ISO/IEC 42001 |
| DPO, legal | Run DPIAs, transfer assessments and breach decisions | FADP Art. 22 and 24, GDPR Art. 3(2) | Swiss data protection and GDPR |
| All staff | Recognise phishing, report incidents fast, use AI tools safely | The 24-hour clock starts at discovery | Awareness, with attendance recorded |
"Tabletop exercises often expose a process weakness rather than a technical one: someone notices something unusual late on a Friday but waits until Monday to raise it. For operators within the ISA's reporting scope, that delay can consume much of the 24-hour reporting window. Give staff a clear escalation path through a route that works outside normal office hours and train them to report to it early."
Jean MunyarugereroHead of AuditISO certification is voluntary in Switzerland, and no law requires ISO/IEC 27001 or ISO/IEC 42001. They are useful because they give one structure to many laws: ISO/IEC 27001 maps cleanly onto ISA, FINMA and NIS2 controls, and ISO/IEC 42001 gives the AI Act's obligations a management system to live in.
In the ISO/IEC 42001 projects I lead, the first workshop always produces the same surprise. Asked how many AI systems they use, teams answer two or three. The real list, once procurement, HR and marketing tools are counted, is usually several times longer. AI governance starts with that honest inventory, not with a policy.
Abilene Academy runs these courses: AI governance (Certified EU AI Governance Professional), ISO/IEC 42001 (Lead Implementer, Lead Auditor), ISO/IEC 27001 (Lead Implementer, Lead Auditor) and related tracks such as GDPR Certified Data Protection Officer, taught by practitioners who implement and audit the same standards for clients. Whoever trains you, keep the attendance records. "We trained our staff" is only evidence if you can show who attended, when, and on what.
When outside help is worth paying for
Many companies can run most of this map themselves once scope is settled and the tooling is in place. Outside help earns its fee in five situations:
- A scoping call with legal consequences. Whether you fall within the ISA's reporting scope, or whether DORA reaches you through a client contract, changes your obligations. A documented outside opinion is also a defensible record.
- Independence. ISO/IEC 27001 and ISO/IEC 42001 require internal audits to be objective and impartial. A small team cannot easily audit its own work.
- Rehearsal. FINMA's Guidance 03/2024 expects scenario-based cyber exercises. Running a tabletop exercise with all the clocks in play, before a real incident, shows who freezes and which phone numbers are missing.
- A backlog with a deadline. A FINMA audit finding, a DPIA backlog, or an EU customer's DORA clauses to negotiate before renewal.
- A group spread across borders. A Swiss head office with EU subsidiaries needs one model that respects both the FADP and the GDPR, and both FINMA and DORA.
If none of these applies, start with training and a platform, and spend the advisory budget later on an independent review.
Abilene Advisors, based in Morges, works on exactly these situations across GDPR, the Swiss FADP, NIS2, DORA, the AI Act and ISO/IEC 27001, 42001 and 22301, among others. Its consultants hold certifications such as ISO 27001 Lead Implementer (PECB), CISA and CRISC (ISACA), and IAPP data-protection credentials. A first conversation is usually enough to tell whether you need outside help at all.
How Acuna GRC maps this
Acuna GRC keeps one compliance programme for all the rulebooks you selected. A requirement is met by a measure, a measure is verified by a control, and a control is performed through recurring tasks. When two frameworks ask for the same thing, they share one measure, so one piece of evidence answers both.
| Obligation | Where it lives in Acuna GRC | What Acuna GRC does not do |
|---|---|---|
| FADP and GDPR: record of processing, DPIA, transfers, data-subject requests | Data Privacy: processing register with a legal basis per applicable law, DPIA screener and wizard, TIA wizard, DPAs generated as Word documents, data-subject requests on a 30-day clock, public Privacy Portal | Decide your legal basis for you |
| Breach notices (FADP, GDPR) | Data Privacy breach wizard with a live 72-hour clock and a generated authority notice | File with the FDPIC. The clock follows the GDPR's 72 hours; under the FADP, aim for "as quickly as possible". |
| ISA, FINMA, NIS2 incident reporting | Core GRC: incident issues with a dated timeline, risk register, business impact analysis | Submit reports to the NCSC, FINMA or ENISA |
| NIS2, DORA and FINMA supplier duties | TPRM (Supplier Shield): supplier register, questionnaires in English, German, French and Spanish, campaigns, ratings, a daily A to F grade from scans of each supplier's public domain | Produce a DORA register of information in the regulators' format |
| CRA vulnerability handling | Vulnerability management: Tenable, Qualys and Rapid7 connectors, CSV or API import, issues with severity-based due dates | Scan your products, generate SBOMs or run a CRA conformity assessment |
| AI Act and ISO/IEC 42001 | AI Governance: AI system register, classification, impact assessments with a fundamental-rights section, human oversight, a 72-hour clock on serious AI incidents, a public page to contest an AI-assisted decision | Certify conformity with any law or standard |
| AI literacy, policy awareness | Staff Portal: published policies, read-and-acknowledge campaigns, reminders | Deliver the training itself |
| Proof for customers and auditors | Trust Center: questionnaire answers drafted from facts you approved, and a trust page with NDA-gated documents; audits, records and KPIs in Core GRC | Answer on your behalf without your approval |
| Swiss head office with EU subsidiaries | Group management: one view of every subsidiary's compliance, risks, suppliers and KPIs | Replace each entity's own legal assessment |
Hosting: your data is hosted in Switzerland, the EU or the US, as you choose. See the Security and Trust Center.
The right-hand column is deliberate. Filing a report or signing a conformity declaration stays with your team, because the authority expects to hear from you. What we do is make sure that, when a clock starts, the people filing already have the incident timeline, the affected systems and suppliers, and the named owners in one place. That preparation is where most incidents are won or lost, and it is the work we help companies do every day.
A Swiss analogy helps here. A spreadsheet of controls is a poll: a snapshot of opinion, out of date by the time you read it. An evidence register is a votation: dated, counted, attributable, and still defensible years later when someone asks how the result was reached.
Related reading: the Microsoft 365 outage, on concentration risk and reporting duties when a supplier fails, and Freezers at 50 °C, on NIS2 lessons from an attack through contractor access.
See the platform → · See pricing
Sources
Swiss sources are the Fedlex consolidated texts and the authorities' own pages; EU sources are the Official Journal texts on EUR-Lex. All accessed on 16 November 2026. The Information Security Act and the Cybersecurity Ordinance have no English version on Fedlex, so the links point to the German text.
- Federal Act on Data Protection, SR 235.1 (Fedlex)
- Data Protection Ordinance, SR 235.11 (Fedlex)
- FDPIC: data breach reporting portal
- FDPIC: 33rd annual report 2025/26
- Information Security Act, SR 128 (Fedlex, German)
- Cybersecurity Ordinance, SR 128.51 (Fedlex, German)
- Cybersecurity Ordinance (CSO), SR 128.51, as at 1 April 2025 (German PDF)
- NCSC: reporting obligation for cyberattacks on critical infrastructure
- NCSC: information on the reporting obligation
- NCSC: who has to report
- Financial Market Supervision Act (FINMASA), SR 956.1 (Fedlex)
- FINMA circulars, incl. Circular 2023/1
- FINMA Guidance 05/2020, Duty to report cyber attacks pursuant to Article 29 para. 2 FINMASA (PDF)
- FINMA Guidance 03/2024, cyber risk findings and clarification of Guidance 05/2020 (PDF)
- FINMA Risk Monitor 2025, 17 November 2025
- GDPR, Regulation (EU) 2016/679 (EUR-Lex)
- NIS2, Directive (EU) 2022/2555 (EUR-Lex)
- European Commission: proposal for targeted NIS2 amendments, COM(2026) 13, 20 January 2026
- European Parliament Legislative Observatory: procedure 2026/0012(COD), status of the NIS2 amendment proposal
- DORA, Regulation (EU) 2022/2554 (EUR-Lex)
- Joint ESAs Q&A DORA102 - 3097 (answer by the European Commission) on EU branches of third-country institutions
- Cyber Resilience Act, Regulation (EU) 2024/2847 (EUR-Lex)
- ENISA: the CRA Single Reporting Platform is launched
- AI Act, Regulation (EU) 2024/1689 (EUR-Lex)
- AI Omnibus, Regulation (EU) 2026/1744 (EUR-Lex)
- Federal Council, 12 February 2025: AI regulation, Federal Council to ratify Council of Europe Convention
- OFCOM: artificial intelligence, the Swiss approach
| Date | Change |
|---|---|
| 2026-11-16 | First published. Covers ISA fines (since 1 Oct 2025), CRA reporting (since 11 Sep 2026) and the AI Omnibus, Regulation (EU) 2026/1744. |
Regulatory References
.png&w=3840&q=75&dpl=dpl_96PxuEbyzwoWxjweCh9wLaGaDCHP)

