What gets practised here first.
The order comes from the playbook catalogue: first the cases recorded for this industry, then the ones that can hit any business.
CEO fraud and payment fraud
A payment supposedly instructed by management or a supplier turns out to be fraud. Covers the payment stop, bank contact, criminal complaint and checking for further manipulated payment runs.
Fake invoice or changed bank details
A supplier supposedly reports new bank details. Covers calling back on known numbers, checking payments already released and hardening the accounts payable process.
Disruption in production or building systems
Control or building systems behave abnormally. Covers separating office and plant networks, consulting the plant manufacturer and safe continued operation.
Ransomware encryption
Systems are encrypted and a ransom demand has been received. Covers immediate isolation, the crisis team, evidence preservation, recovery from backups and how to handle the demand.
Reported phishing email
An employee reports a suspicious email. Covers assessment, searching for further recipients, blocking sender and link, and feedback to the workforce.
Taken-over user account
An account is demonstrably or presumably being used by third parties. Covers lockout, session and token revocation, password and MFA reset, and reviewing what happened with the account.
Data breach with notification duty
Personal data has been exfiltrated or disclosed. Covers initial assessment, evidence preservation, notification to the FDPIC under the FADP and to affected individuals, and documentation.
Malware on a workstation
An endpoint shows signs of infection. Covers network isolation, capturing volatile evidence, cleanup or rebuild, and searching for further affected devices.
Security incident at an IT service provider
A provider, hoster or software vendor is compromised or down. Covers impact analysis, blocking access to and from the provider, emergency operations and contractual steps.
What the law requires.
Swiss law does not impose a separate cyber reporting duty on construction. The general duties in the FADP and the CO apply — plus the reporting duty under the ISA as soon as a business counts as critical infrastructure.
Swiss FADP art. 8 — Data security
The controller and the processor ensure data security appropriate to the risk through suitable technical and organisational measures. The measures must make it possible to avoid data security breaches.
Swiss FADP art. 9 — Processing by a processor
Where the processing of personal data is delegated to a processor, the controller must ensure that the processor is able to guarantee data security. The processor may only subcontract processing with prior authorisation.
Swiss FADP art. 12 — Register of processing activities
Controllers and processors each keep a register of their processing activities including purpose, categories of persons and data, recipients, retention period, data security measures and any disclosures abroad.
Swiss FADP art. 24 — Notification of data security breaches
The controller notifies the Federal Data Protection and Information Commissioner as soon as possible of any data security breach that is likely to result in a high risk to the personality or fundamental rights of the data subject. The notification states at least the nature, the consequences and the measures taken. The processor notifies the controller.
Swiss Data Protection Ordinance art. 1–3 — Minimum data security requirements
Determine the protection needs of the personal data and define measures appropriate to the risk. The measures must ensure confidentiality, availability, integrity and traceability — among others through access control, physical access control and user control.
Swiss ISA art. 74a–74f — Duty to report cyber attacks on critical infrastructure
Organisations subject to the reporting duty report a cyber attack to the National Cyber Security Centre (BACS) within 24 hours of its discovery. An attack must be reported if it jeopardises the functioning of the critical infrastructure, has led to manipulation or leakage of information, remained undetected for a longer period or is linked to extortion, threat or coercion. The report states the organisation, the nature and execution of the attack, its effects, the measures taken and the planned next steps.
GDPR art. 32 — Security of processing
Implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk — as applicable pseudonymisation and encryption, confidentiality, integrity, availability and resilience of systems, the ability to restore availability quickly after an incident, and a process for regularly testing the effectiveness of the measures.
GDPR art. 33 — Notification of a breach to the supervisory authority
Notify a personal data breach to the competent supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of it, unless the breach is unlikely to result in a risk to the rights and freedoms of data subjects. Every breach must be documented; the processor notifies the controller without undue delay.
The catalogue is a selection with official sources, not a complete legal register, and it does not replace legal advice.
Where businesses start here.
Derived from the scenarios above and from the proposal for this company size.
Ready in three steps.
Find your position
The quick check asks 14 questions on the federal ICT minimum standard and shows where the business stands.
Let the staff practise
Phishing simulations with Swiss templates and interactive courses in four languages.
Prepare for the real thing
Response instructions for the scenarios above, so nobody has to improvise during an incident.
Background and practice
Stop the payment before it is executed.
Quick check, simulations and response instructions in one platform. Try it for 30 days.