
Ransomware attack: the first 60 minutes decide the damage
A ransomware attack rarely announces itself. It usually starts with an inconspicuous report: files no longer open, a server stops responding, a ransom note appears on the screen. What happens in the hour that follows largely decides how big the damage becomes – and whether the attack can later be fully reconstructed.
This article explains which immediate steps make sense, which common mistakes destroy evidence for good, and which deadlines organisations in Austria need to keep in mind.
Stay calm – and don’t rush
The first impulse is understandable: restart systems, delete encrypted data, restore backups. Yet these are exactly the reactions that often cause additional damage. A reboot wipes the memory – and with it, often the only traces that show how the attackers operated. A backup restored in haste may already be compromised and trigger the attack all over again.
In the first minutes, the goal is not to fix everything, but to stop the spread without destroying evidence.
The first 15 minutes: contain the spread
The aim is to contain the attack without altering the affected systems.
- Disconnect, don’t power off: take affected machines off the network (pull the cable, disable Wi-Fi), but leave them switched on.
- Block remote access: temporarily disable VPN, remote desktop and any external access.
- Review privileged accounts: lock suspicious administrator accounts, but do not reset passwords across the board yet – that can alert the attackers.
- Isolate backups: disconnect backups from the network immediately so they are not encrypted as well.
Emergency card · PDF
The first hour after a ransomware attack
Seven decisions on one A4 page, with our emergency number and space for your own contacts. Print it, put it in your crisis manual, pin it up next to the server room.
Minutes 15 to 60: assess the situation and secure evidence
Once the spread has been slowed down, structured documentation begins. Every observation should be recorded with the time and the person who made it – these notes will be valuable later for the insurer, the authorities and the forensic analysis.
What should be documented
- When the first anomaly was noticed and by whom
- Affected systems, locations and services
- The text and screenshots of the ransom note (do not click any links)
- All measures taken so far
What you should not do
- Do not communicate with the attackers without expert support.
- Do not delete encrypted files or ransom notes.
- Do not reinstall systems before they have been forensically secured.
By now at the latest, external specialists should be brought in. A professional forensic acquisition of memory and storage media ensures that the attack path can be reconstructed and the evidence documented in a way that holds up in court. This is the core of our incident response work.
Reporting obligations in Austria
A ransomware attack is not just a technical problem. Depending on the organisation and the data involved, statutory deadlines start running from the moment the incident becomes known:
- GDPR: if personal data is affected, the breach generally has to be reported to the Austrian Data Protection Authority within 72 hours.
- NIS2 / NISG 2026: entities covered by Austria’s Network and Information Systems Security Act must submit an early warning for significant incidents within 24 hours.
- Cyber insurance: many policies require the claim to be reported without delay – often before you take any measures of your own.
Clean documentation from the first hour makes all three reports considerably easier.
Conclusion: preparation decides
The first 60 minutes cannot be improvised. Organisations with an incident response plan, isolated backups and a reachable point of contact for emergencies limit the damage significantly – and keep the possibility of fully investigating the attack. How we support companies in this situation is described under ransomware response.
In an emergency, our incident response team is available around the clock on +43 1 226 40 33 or via our contact form.



