Join our Newsletter — 33% off our NHI Course
Home› Guides› Switzerland Cyberattack Reporting: ISG duties for critical infrastructure
Guide Regulations & Frameworks

Switzerland Cyberattack Reporting: ISG duties for critical infrastructure

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 14 November 2026 16 min read
On this page

Since 1 April 2025, operators of critical infrastructure in Switzerland must report cyberattacks to the federal cyber security authority within 24 hours of discovery, and since 1 October 2025 failing to do so can end in a fine of up to CHF 100,000. The duty comes from an amendment to the Federal Act on Information Security (Informationssicherheitsgesetz, ISG, SR 128) adopted by Parliament on 29 September 2023, with the detail in the Cybersecurity Ordinance (Cybersicherheitsverordnung, CSV). This guide explains who is in scope, which attacks are reportable, what goes into the 24 hour and 14 day reports, how the duty sits beside FINMA and data protection notifications, and how to build the internal process so the clock is never missed. It is written for CISOs, incident managers and compliance leads in Swiss organisations and in foreign groups with Swiss operations. Personal data breach notification under the revised FADP is covered in the Switzerland nFADP Guide and is not repeated here.

Status checked 13 November 2026: the ISG reporting provisions (Art. 74a to 74h) and the CSV have applied since 1 April 2025; the penalty provision (Art. 74h ISG) has applied since 1 October 2025. Sources are the amending act published in the Federal Gazette (BBl 2023 2296), the CSV explanatory notes of the Federal Office for Cyber Security (BACS) dated 1 April 2025, and BACS reporting pages. Confirm the consolidated text on Fedlex before relying on article wording.

Key takeaways

  • Twenty-one categories of operator are in scope. Art. 74b ISG lists them in letters a to u, from universities and public authorities to cloud and data centre providers and makers of software used by critical infrastructure; the CSV then exempts some by size or sector threshold.
  • Four triggers make an attack reportable. Art. 74d ISG covers attacks that endanger the functioning of the infrastructure, lead to manipulation or outflow of information, stay undetected for a long period, or involve extortion, threats or coercion.
  • Two deadlines, neither extendable. The initial report is due within 24 hours of discovery (Art. 74e ISG) and the supplementary report within 14 calendar days (Art. 16 CSV), whatever the time of day or week.
  • Fines follow a ruling, not the miss itself. BACS first sets a deadline, then issues a ruling with a penalty warning; only intentionally ignoring that final ruling attracts a fine of up to CHF 100,000 (Art. 74g and 74h ISG).
  • One report does not cover every regulator. BACS forwards a report to FINMA, the FDPIC and certain other authorities only if you explicitly ask, and FINMA still expects its own detailed report.

Scope: who must report

Art. 74a ISG places the duty on the authorities and organisations listed in Art. 74b and requires them to ensure that cyberattacks on their IT resources are reported. The duty has a stated purpose: it serves only to let the authority recognise attack patterns early and warn others who may be affected. Reporting also entitles the operator to the authority's support (Art. 74a para. 3 with Art. 74 para. 3). The authority confirms on request, by formal decision, whether an organisation is subject to the duty (Art. 74a para. 2), and the BACS FAQ says the Cyber Security Hub shows the status for registered organisations.

Art. 74b para. 1Category (summary of the act)CSV threshold or note (Art. 12 CSV, per the explanatory notes)
aUniversitiesExempt below 2,000 students
bFederal, cantonal and municipal authorities and inter-cantonal bodies (armed forces excluded when deployed in assistance or active service)Size exemption does not apply
cPublic-law bodies for security and rescue, drinking water, wastewater and waste disposalSee the CSV for any sector detail
dEnergy supply, trading, metering or control (nuclear licence holders excluded for attacks on a nuclear facility)Electricity: only protection levels A and B; gas: exempt below 400 GWh a year to end consumers
eBanks, insurers and financial market infrastructuresNo exemption
fHospitals on a cantonal hospital listNo exemption
gMedical laboratories licensed under the Epidemics ActExempt under 50 staff and CHF 10 million turnover or balance sheet
hFirms licensed to manufacture, market or import medicinesExempt under 50 staff and CHF 10 million
iProviders of sickness, accident, disability and old-age insurance benefitsNo exemption
j, kThe Swiss Broadcasting Corporation (SRG) and news agencies of national importanceNo exemption
lPostal service providers registered with the Postal CommissionExempt under 50 staff and CHF 10 million
mRailway, cableway, trolleybus, bus and boat operators with concessionsRail: only companies supervised by the Federal Office of Transport with public system tasks
nCivil aviation firms with FOCA authorisation, and national airportsExempt if not required to implement the cited aviation security rules
oRhine cargo carriers and Port of Basel operatorsSee the CSV
pSuppliers of essential everyday goods whose failure would cause major shortagesExempt under 50 staff and CHF 10 million
qRegistered telecommunications providersSee the CSV
rInternet domain registries and registrarsSee the CSV
sProviders of services that support the exercise of political rightsSee the CSV
tCloud, search engine, digital security and trust services, and data centre providers with a Swiss seatOnly if serving third parties for payment; security and trust services regardless of size
uMakers of hardware or software used by critical infrastructure, where the product has remote access or serves control, monitoring or public security functionsSee the CSV

Three scope rules catch organisations out:

  • Covered activities only: Art. 74b para. 2 excludes attacks that affect only activities outside the listed category, so a diversified group must know which business lines and systems carry the duty.
  • Effect in Switzerland: under Art. 74b para. 3 the duty applies to attacks with effects in Switzerland even where the IT resources sit abroad. A foreign parent running a shared cloud tenant for its Swiss subsidiary cannot assume the attack is out of scope.
  • Who files: the BACS FAQ says the affected organisation always has to report. A managed service provider may file on its behalf where this is agreed and documented, and Art. 17 CSV allows a third party to submit. Where a municipality runs on cantonal IT and network services, the FAQ says the canton as network operator reports.

Which attacks are reportable

Art. 74d ISG sets four triggers. The CSV (Art. 14) and its explanatory notes give the practical reading, summarised below. Organisations outside critical infrastructure have no legal duty, but BACS recommends voluntary reports.

Trigger (Art. 74d ISG)Practical reading (Art. 14 CSV and BACS FAQ)Typical example
a. Endangers the functioning of the affected critical infrastructureSystems are disrupted or emergency plans are needed to keep operating; the test is impact on the infrastructure as a wholeRansomware (ATT&CK T1486 Data Encrypted for Impact) forcing manual operation of a control room
b. Leads to manipulation or outflow of informationIncludes personal data; manipulation of data or configuration counts as well as theftExfiltration of customer records through a stolen API token
c. Remains undetected for a long period, especially with signs of preparing further attacksReportable where the attack began more than 90 days before discovery (Art. 14 para. 3 CSV)A web shell found during a compromise assessment, installed five months earlier
d. Involves extortion, threats or coercionExtortion or threats against the operator or its staffA ransom demand or a threat to leak stolen data

The FAQ gives a useful boundary case: a DDoS attack on a non-critical application does not automatically trigger the duty, because the test is the effect on the operability of the critical infrastructure. Document that reasoning when you decide not to report, since BACS can later ask why.

Deadlines and report content

Art. 74e para. 1 ISG requires the report within 24 hours of discovering the cyberattack. Art. 16 CSV adds the follow-up: missing information, or confirmation that it does not exist, must reach BACS within 14 days of the initial report. The explanatory notes state that neither deadline can be extended and that the 24 hours run regardless of the time of day. The FAQ confirms the 14 days are calendar days and gives the example of a system that fails on Friday evening but is only recognised as an attack on Monday: the 24 hours run from that discovery, so the report is due on Monday. Known information must be sent even when incomplete.

ElementLegal basisWhat to have ready
Reporting entity and contactArt. 74e para. 2 ISG; Art. 15 para. 4 CSVName, address, contact person, phone and email (only if not already registered)
TimingArt. 15 para. 1 CSVDate and time of discovery and of the attack, or the best estimate
Nature and execution of the attackArt. 74e para. 2 ISG; Art. 15 para. 1 CSVAny information about the attacker, such as IP addresses, DNS records and malware hashes
Extortion and criminal complaintArt. 15 para. 2 CSVWhether extortion or threats were involved and whether a criminal complaint was filed
EffectsArt. 74e para. 2 ISG; Art. 15 para. 3 CSVSeverity (low, medium, high or severe) for availability, integrity and confidentiality, effect on operations, expected duration
Measures and next stepsArt. 74e para. 2 ISGMeasures taken and, if known, planned next steps
  • No self-incrimination: Art. 74e para. 4 ISG means the reporting person need not make statements that would incriminate them under criminal law; the explanatory notes add that business secrets need not be disclosed.
  • Channel: registered organisations report through the form on the BACS Cyber Security Hub, where accounts are personal and group mailboxes are not allowed. Organisations without an account use the email form on the BACS website, and BACS confirms receipt (Art. 17 CSV). Registration is optional, but BACS recommends it because it saves time during an incident.
  • Completion: BACS tells the organisation when it has all the required information (Art. 74e para. 5 ISG). If the 14 day deadline is missed, BACS issues a demand to complete the report.

How it fits with FINMA, data protection and other regulators

Art. 74f ISG requires BACS to provide a secure electronic system that lets operators forward reports to other authorities. The FAQ says BACS passes a report to the FDPIC, FINMA, the Federal Social Insurance Office or the Swiss Space Office only if the reporter explicitly asks; any other recipient must be informed by the organisation itself.

RegimeTriggerRecipient and clockWhere to read more
ISG Art. 74a to 74hReportable cyberattack on an in-scope operatorBACS, 24 hours, then 14 daysThis guide
FINMA supervisory reportingCyber attack on a supervised institution (Art. 29 para. 2 FINMASA)FINMA: the FAQ says the 24 hour report can go through the BACS form and be forwarded to FINMA if timely transmission is ensured; the detailed report follows within 72 hours through FINMA's survey and application portalFINMA Circular 2023/1
Revised FADP Art. 24Data security breach likely to result in a high risk to the data subjectsFDPIC, as soon as possibleSwitzerland nFADP Guide
EU NIS2, for groups with EU entitiesSignificant incident at an EU essential or important entityNational CSIRT or authority, 24 hour early warningNIS2 Directive Guide

A single ransomware incident at a Swiss bank with EU branches can therefore start four clocks. Build one incident record that feeds all of them, and decide in advance which regulator gets which wording. The Cyber Incident Reporting Requirements Map compares the clocks across jurisdictions.

Enforcement and penalties

Enforcement is staged. The BACS FAQ says there is no active compliance supervision; BACS acts when it learns of an unreported, reportable attack.

  1. Notice and deadline: where there are indications of a breach of the duty, BACS sets a reasonable deadline to report (Art. 74g ISG).
  2. Ruling with penalty warning: if the operator still does not report, BACS issues a formal ruling with a new deadline and a warning of the penalty under Art. 74h.
  3. Fine: anyone who intentionally fails to comply with a final ruling faces a fine of up to CHF 100,000 (Art. 74h para. 1). For offences within a business, Art. 6 of the Federal Act on Administrative Criminal Law applies. Where the fine would not exceed CHF 20,000 and identifying the responsible individuals would need disproportionate investigation, the business itself can be fined instead (Art. 74h para. 3).
  4. Prosecution: the cantons prosecute and judge these offences (Art. 74h para. 4); the FAQ says BACS can file a complaint with the prosecution authorities.

Penalties have applied since 1 October 2025, six months after the duty began. Because the fine attaches to the ruling, the larger practical risk is usually reputational and supervisory: a sector regulator that learns of an unreported attack will ask why your process failed.

What it means for non-human identities

Many reportable attacks run through machine credentials: a leaked API key or OAuth token gives silent access to data (trigger b), and a persistent service account or token stays unnoticed for months (trigger c, the 90 day line). Two consequences follow. First, the "date and time of the attack" in Art. 15 CSV often depends on when a token was first misused, which you can only establish if token issuance and use are logged and retained beyond 90 days. Second, revocation of compromised credentials belongs in the "measures taken" field, so the incident team needs an inventory that says which keys and service accounts touch in-scope systems. See the Service Account Security Guide and the API Key Management Guide.

Compliance steps

  1. Confirm status: map each legal entity and business line to the Art. 74b letters and CSV thresholds. Where it is unclear, ask BACS for a decision under Art. 74a para. 2 and keep it on file.
  2. Register: create personal Cyber Security Hub accounts for at least two named reporters and a deputy per shift pattern, and keep the email form as a fallback.
  3. Write the triage rule: add the four Art. 74d triggers, with the CSV readings, to your incident classification so that the decision "reportable or not" is taken by the incident manager within hours, not by legal after a week. The Incident Severity Classification Matrix Template can carry the extra column.
  4. Define discovery: agree internally what "discovery" means (for example, the moment a responder confirms malicious activity, not the first unreviewed alert) and record that timestamp in every case.
  5. Pre-fill the form: keep entity details, contacts and asset descriptions ready so the 24 hour report needs only incident facts.
  6. Coordinate regulators: decide per incident type whether to ask BACS to forward to FINMA or the FDPIC, and who sends the FINMA 72 hour report and any FADP notification.
  7. Contract your providers: require MSPs, cloud and software suppliers to notify you fast enough for your 24 hour clock, and document any MSP filing on your behalf. In-scope suppliers under letters t and u may also have their own duty.
  8. Exercise it: run a weekend scenario at least once a year, timing discovery to submission. See the Incident Response Plan Template.

Detection, measurement and framework mapping

Track these measures (our recommendations): time from discovery to initial report, against 24 hours; share of reports completed within 14 days; share of incidents with a recorded "reportable or not" decision and reason; time for suppliers to notify you; and the oldest dwell time found in the year, which shows whether the 90 day trigger is a live risk.

ObligationNIST CSF 2.0NIST SP 800-53 Rev. 5ISO/IEC 27001:2022 Annex A
Know you are in scopeGV.OC-03IR-1 Policy and Procedures5.31 Legal, statutory, regulatory and contractual requirements
Decide and report within 24 hoursRS.CO-02IR-6 Incident Reporting5.24, 5.26, 6.8
Supplement within 14 daysRS.CO-02IR-4 Incident Handling, IR-65.26 Response to information security incidents
Establish attack timing and dwell timeDE.AE-03AU-6, AU-118.15 Logging, 8.16 Monitoring activities
Coordinate with regulatorsRS.CO-02IR-65.5 Contact with authorities

Common failure patterns

  • Waiting for certainty: teams hold the report until forensics confirms scope. The law expects the known facts within 24 hours and the rest within 14 days.
  • No weekend cover: the only registered Hub account belongs to someone on leave, and group mailboxes are not allowed. Register several named people.
  • Assuming the bank or hospital exemption logic applies to everyone: the size exemption covers only some letters; banks, insurers, hospitals, social insurers and public authorities have no size exemption.
  • Treating one report as all reports: BACS does not pass reports to FINMA or the FDPIC unless asked, and FINMA's detailed report has its own channel.
  • Losing the start date: without retained identity and access logs, the operator cannot say whether an attack began more than 90 days earlier, which itself decides reportability. See the Log Retention Requirements Map.
  • Supplier silence: a provider discovers the attack first and tells you days later, after your clock has effectively run.

Practitioner checklist

  • Map every Swiss entity and business line to Art. 74b letters a to u and the Art. 12 CSV thresholds, and record the result.
  • Request a BACS decision where scope is uncertain and file it with the compliance register.
  • Register at least two named reporters on the Cyber Security Hub and test the email fallback.
  • Add the four Art. 74d triggers and the 90 day rule to incident classification.
  • Define "discovery" and log its timestamp in every incident record.
  • Keep a pre-filled report pack with entity, contact and asset details.
  • Agree forwarding choices and owners for FINMA, FDPIC and EU NIS2 reports.
  • Put supplier notification clauses in contracts with MSPs and cloud providers.
  • Retain identity, token and access logs long enough to date an intrusion beyond 90 days.
  • Run a timed out-of-hours reporting exercise each year.

Standards and references

This guide summarises the Swiss reporting obligation for cyberattacks on critical infrastructure under the Information Security Act and the Cybersecurity Ordinance and is not legal advice. Related NHI Mgmt Group resources: Switzerland nFADP Guide · FINMA Circular 2023/1 · Cyber Incident Reporting Requirements Map · Incident Response Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 14 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.