Is there a cyberattack reporting obligation in Switzerland?
Direct answer
Yes, but not for every company. Since 1 April 2025, the Information Security Act (ISA) requires the authorities and organisations listed in its Article 74b to report qualifying cyberattacks to the National Cyber Security Centre (NCSC) within 24 hours of discovery. The report can be completed within 14 days.
Since 1 October 2025, an operator that ignores an NCSC order to report can be fined up to CHF 100,000. Financial institutions also report cyberattacks to FINMA, and a breach of personal data can require a separate notice to the FDPIC.
Who has to report
The duty is not a general one for every Swiss business. It covers the authorities and organisations listed in Article 74b ISA. The list includes energy and drinking-water suppliers, hospitals, transport companies, telecoms providers, banks, insurers and financial market infrastructures, and federal, cantonal and communal authorities. It also covers universities, cloud and data-centre providers based in Switzerland, and makers of hardware or software used by critical infrastructure.
Being on the list is a possible trigger, not a conclusion. Article 12 of the Cybersecurity Ordinance exempts some listed organisations below sector-specific thresholds. See are small organisations exempt from ISA reporting?
What must be reported, and how fast
Only qualifying cyberattacks are reportable: the duty depends on the organisation’s designation and on the nature and impact of the attack. See which cyberattacks must be reported under the ISA.
- 24 hours. The report is due within 24 hours of discovering the attack (Article 74e ISA), through the NCSC’s Cyber Security Hub.
- 14 days. Where information is not yet available, the report can be completed within 14 days (Article 16 of the Cybersecurity Ordinance).
What happens if you do not report
Since 1 October 2025, failing to report can cost up to CHF 100,000. A fine does not follow automatically. The NCSC first contacts the operator and sets a deadline. If that passes, it issues a formal order with a new deadline, and the fine punishes ignoring that order (Articles 74g and 74h ISA).
Other reports the same incident can trigger
- FINMA. An institution supervised by FINMA notifies its account manager within 24 hours of discovering a cyberattack that meets the criteria of FINMA Guidance 05/2020, then files the full report within 72 hours through the EHP platform. Under Guidance 03/2024, an institution also subject to the ISA may send its 24-hour notice through the NCSC form and have it forwarded to FINMA, provided it arrives in time.
- FDPIC. If personal data is at high risk, the FADP asks for a separate notice. See can one cyberattack trigger both an ISA report and an FADP breach notice?
- NIS2. An EU establishment that is an essential or important entity reports under its member state’s NIS2 law. See ISA vs NIS2 incident reporting.
What to do
- Assess scope in writing. Record whether you are listed in Article 74b and whether an exemption applies, with the reasoning.
- Name the roles. Decide who judges whether an attack is reportable and who files with the NCSC, FINMA or the FDPIC, and keep their contacts reachable outside office hours.
- Keep one incident log, so every report draws on the same facts.
This is general information, not legal advice: scope depends on your facts, so confirm it with a qualified lawyer. For the full picture, read what a Swiss company must comply with, and see how NIS2 and FINMA requirements sit next to the ISA.
Keeping the incident record in Acuna GRC
In Acuna GRC, incidents are logged as issues with a timeline of dated steps, next to the risk register and the business impact analysis. Acuna GRC does not submit reports to the NCSC, FINMA or the FDPIC: filing stays with your team. See Assure.
How Acuna GRC handles it
Acuna GRC does not file the report: it keeps the incident timeline, the affected systems and suppliers and the named owners in one place for the people who do.
- Core workspace
Assure
KPIs and measurements, reports, records, audits, issues and corrective actions.
- Solution
FINMA
Map critical processes and recovery objectives, find single points of failure, manage outsourcing and ICT providers, and run FINMA next to DORA.
- Solution
NIS2
Put NIS2 measures in place with owners, reuse your ISO 27001 controls, check suppliers, follow incidents and vulnerabilities, and keep proof in one place.
- Core workspace
Operate
Risks and opportunities, threats, treatment plans, objectives, business impact analysis, tasks, the annual plan and documents.
Sources
- Information Security Act (ISA, SR 128), Articles 74a to 74h (Fedlex, German)
- Cybersecurity Ordinance (CSO, SR 128.51), Articles 12, 14 and 16 (Fedlex, German)
- NCSC, reporting obligation for cyberattacks on critical infrastructure
- NCSC, who has to report?
- FINMA Guidance 05/2020, duty to report cyber attacks
- FINMA Guidance 03/2024, clarification of Guidance 05/2020
This page explains the rules in general terms and is not legal advice.
Frequently asked
Does the 24-hour duty apply to every Swiss company?
No. It applies only to the authorities and organisations within the ISA’s reporting scope (Article 74b, minus the Cybersecurity Ordinance exemptions), and only to qualifying cyberattacks.
Who receives the report?
The National Cyber Security Centre (NCSC), through its Cyber Security Hub. BACS is the German abbreviation for the same office.
Is the ISA report the same as a data breach notice?
No. The ISA report goes to the NCSC; the FADP breach notice goes to the FDPIC when personal data is at high risk. One incident can require both.
See how Acuna GRC runs this.
Tell us your frameworks and your team. We show you how Acuna GRC runs the program.
Hosted in Switzerland, the EU or the US
.png&w=3840&q=75&dpl=dpl_96PxuEbyzwoWxjweCh9wLaGaDCHP)

