It's 7.40 on a Monday morning. Your office manager calls: nobody can open the shared drive, every file has a strange new extension, and there's a text file on the server telling you to pay in bitcoin within 72 hours.
What you do in the next hour decides a lot. Well-meant reactions, like switching everything off, wiping a laptop or answering the criminals, can destroy evidence, spread the damage or start a clock you didn't know about. This checklist covers what to do first, who to tell in Belgium, and why paying is rarely the shortcut it seems.
Minute 0 to 15: contain it, don't destroy it
Disconnect, don't switch off
The first job is to stop the encryption spreading. The US cybersecurity agency CISA's ransomware response checklist says to identify the affected systems and isolate them immediately: unplug the network cable, turn off Wi-Fi, or take a whole network segment offline at the switch if several machines are hit.
Its advice on powering down is specific: only switch devices off if you can't disconnect them from the network. A running machine still holds evidence in its memory that disappears when it shuts down, and investigators may need it.
What to do:
- Pull the network cable or disable Wi-Fi on every device that shows encrypted files or the ransom note.
- If the server itself is affected, disconnect it from the network but leave it running.
- Disconnect backup drives and NAS devices that are still connected, so they don't get encrypted too.
- Don't wipe, reinstall or "clean up" anything yet.
Assume accounts are compromised too
The encryption is usually the last step, not the first. Attackers often get in through a stolen or weak account, and that account may still be active in your Microsoft 365 tenant or on your network.
What to do:
- Reset the passwords of administrator accounts first, from a device you know is clean.
- Sign affected users out of all sessions in Microsoft 365, so a stolen session can't be reused.
- Check for new admin accounts, new inbox forwarding rules or new devices you don't recognise.
Minute 15 to 30: preserve evidence and start a log
Keep what investigators will need
CISA recommends preserving evidence that is volatile or kept only for a short time, such as system memory and security logs, and taking a system image and memory capture of a sample of affected devices. That's a job for a specialist, but you can make it possible by not destroying anything.
In Microsoft 365, the audit log shows who signed in from where and what they did. It only helps if it was switched on beforehand, which on Business plans isn't always the default.
What to do:
- Photograph the ransom note and the screens showing encrypted files. Don't delete the note.
- Write down the ransom amount, any payment address and any contact details the criminals give.
- Start a timeline: when the problem was noticed, by whom, what was done and when. You will need it for insurers, the police and regulators.
Call for help
Decide now who leads the response. If you have an IT provider, an incident response partner or cyber insurance, call them now. If you're insured, check whether your policy asks you to use the insurer's incident line or approved responders before you bring in anyone else.
Minute 30 to 60: work out what you're dealing with
Before anyone talks about recovery, get answers to three questions:
- What is encrypted? Which servers, laptops, shared drives and cloud storage are affected, and which aren't.
- Are the backups intact? Check them without reconnecting them to an infected network. CISA stresses that offline backups matter because many ransomware strains try to find and delete any backup they can reach.
- Was data stolen? Many groups now copy data before encrypting it and threaten to publish it. Unusual outbound traffic, large uploads or a note that mentions "downloaded files" are warning signs.
The answer to the third question drives your GDPR obligations, so don't guess. Record what you know and what you don't yet know.
The clocks that may already be running
NIS2: 24 hours to the CCB
If your organisation falls under NIS2 (our NIS2 guide explains who does) and the ransomware causes a significant incident, the CCB's NIS2 notification guidance sets a staged timeline:
- an early warning within 24 hours of becoming aware of the incident,
- an incident notification within 72 hours,
- a final report no later than one month after the incident notification.
Notifications go through the CCB's online platform at notif.safeonweb.be. The CCB's notification guide explains what counts as significant. Information in the early warning can be preliminary: the point is to warn early, not to have every answer.
Not in scope of NIS2? You can still report an incident to the CCB voluntarily, and a voluntary report doesn't create obligations you didn't already have.
GDPR: 72 hours to the Data Protection Authority
Ransomware almost always touches personal data: customer files, employee records, email. Under Article 33 of the GDPR, a personal data breach must be notified to the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of it, unless it's unlikely to result in a risk to people.
Two details surprise many businesses:
- Encryption alone can be a breach. The European Data Protection Board's guidelines on breach notification examples include ransomware cases, and data being unavailable, not only stolen, can trigger the duty to notify.
- Belgium has a new portal. Since June 2025 the Data Protection Authority uses a two-part online notification: the first part within the 72 hours, the second within 21 days. Belgian companies sign in with eID or itsme, so check now who in your organisation can log in.
Rule of thumb: the 72 hours start when you become aware, not when the investigation is finished. Notify with what you know, and add details later.
Police
Ransomware is a crime. File a complaint with your local police, who work with the specialised Computer Crime Units. Belgian police and the CCB are partners in the No More Ransom project, and a complaint also helps investigators link your case to others.
Should you pay?
The honest answer: don't decide in the first hour, and don't decide alone.
The FBI's position is that it does not support paying a ransom: payment doesn't guarantee you get your data back, some victims never receive a working key, and every payment funds the next attack. Paying also doesn't remove your NIS2 or GDPR obligations, and it doesn't stop stolen data from being published.
Before anyone replies to the criminals, check the No More Ransom portal, which offers free decryption tools for some ransomware families, and talk to your insurer and a lawyer.
Your first-hour checklist
- Isolate affected devices from the network. Keep them running unless you can't disconnect them.
- Protect the backups by disconnecting anything still attached, and reset admin passwords from a clean device.
- Preserve evidence: photos of the ransom note, a timeline, no wiping or reinstalling.
- Call your help: IT provider, incident response partner and insurer.
- Assess the clocks: NIS2 early warning within 24 hours if you're in scope, GDPR notification within 72 hours if personal data is affected, and a police complaint.
- Don't negotiate or pay before you have expert and legal advice.
The takeaway
The first hour of a ransomware attack is about containment and calm, not heroics: disconnect, preserve, call for help and start the clock. Most of this is easier if you've written it down in advance, with names and phone numbers. Print this checklist, put your own contacts on it, and you're already better prepared than most.
This article is general information, not legal advice. Check the CCB's NIS2 notification guidance and the Data Protection Authority for the latest official guidance.