Key takeaways
- Decide before an incident who leads, who decides and who calls whom. Keep the contact list on paper or offline.
- Contain first, for example by isolating devices and resetting credentials, but do not wipe anything yet: evidence matters.
- Call your IT provider, your insurer and a lawyer early. Report to the authorities where required or useful.
- Recover from known-good backups in the order of business priority, and only once you know how the attacker got in.
Before it happens: a one-page plan
The worst moment to decide who is in charge is during an attack. A one-page plan costs an afternoon and saves hours when it counts.
- Name an incident lead and a deputy, and who decides on business questions such as shutting systems down.
- List contacts: IT provider, insurer’s incident hotline, lawyer, data protection contact, key customers.
- Print the list and store a copy offline. Email and file shares may be unavailable.
- Know where your backups are and who can restore them.
Hour 0 to 1: contain
The goal is to stop the spread without destroying evidence.
- Disconnect affected devices from the network (unplug the cable, turn off Wi-Fi), but do not power them off or reinstall them yet.
- Reset passwords and sign out sessions for affected accounts, administrators first. Disable accounts you suspect are compromised.
- Block the obvious paths, for example a compromised remote access account.
- Write down what you see and when: times, screens, messages. Photograph ransom notes.
Hour 1 to 6: assess and preserve
- Work out what is affected: which systems, which data, which accounts.
- Preserve logs and keep affected machines as they are, so that a specialist can analyse them.
- Check whether backups are intact and out of reach of the attacker before connecting anything.
- Call your insurer’s incident line early. Many cyber policies require quick notice and may bring their own response team.
Hour 6 to 24: communicate and decide
Tell staff briefly what happened, what they must not do (for example open the ransom note links or use shared passwords) and who to ask. Prepare a short holding statement for customers and partners.
Check your reporting duties. Cyberattacks on critical infrastructure operators must be reported to the Federal Office for Cybersecurity (FOCS, formerly the NCSC) within a short deadline under the Swiss rules in force since 2025, and anyone can report voluntarily. If personal data is likely at high risk, the data protection authority (FDPIC) must be told as soon as possible. Rules change, so confirm the current ones.
On ransom payments: authorities generally advise against paying. It does not guarantee your data back and it funds further attacks. Do not decide this alone, and involve your lawyer and insurer.
Recover in a safe order
Restoring too early can hand the attacker a second chance. First understand how they got in and close that door, then rebuild the most important systems from clean sources, in the order of business priority. Change all credentials that may have been exposed, and monitor closely for a while after.
After the incident
Hold a blameless review within a few weeks. What failed, what worked, and what do you change? Update the plan, fix the root cause and practise again once a year.
A ready plan and a partner who answers the phone make the difference. See our security services and managed services.