Cyber attack under way? Contain it first, then restart.
Files that no longer open, emails sent from your mailbox that you never wrote, a supplier asking why you changed your IBAN. We stop what is happening, find how they got in, get people back to work and leave you a written account of what happened.
The first hours are when the costliest mistakes are made.
Everything gets switched off and the traces are lost, a password is changed from the infected computer, a backup is restored without knowing how long the intruder had been inside. Meanwhile whoever got in may still have access to the email, read what you write to each other and wait for the right moment. And if personal data is involved, the deadlines for notifying the authorities start when you become aware, not when you've finished fixing things.
Contain, understand, restart.
- 01
Contain
We disconnect the affected computers and servers from the network without switching them off, close open sessions and block compromised accounts. Passwords are changed from a device known to be clean.
- 02
Secure the evidence
Before touching anything we save the sign-in logs, the mailbox rules and a copy of the affected systems. They are needed to understand what happened and, if required, by your lawyer and your insurer.
- 03
Find how they got in
A reused password, an opened attachment, an exposed remote access, software left unpatched. We look at Microsoft 365 or Google Workspace sign-ins, forwarding rules hidden in mailboxes, connected devices.
- 04
Restart from clean
We restore data and servers from backups after checking they predate the intrusion. Affected computers are reinstalled, not cleaned. People go back to work in an order of priority agreed with you.
- 05
Close the door
Two-factor authentication on email and remote access, new passwords everywhere, updates, backups with a copy an intruder can't delete. And a written account of what happened.
Systems that restart and a written timeline.
We leave you a report that non-technical people can read: what happened and when, what was touched, what we did, what is left to do. It is the document your lawyer, your privacy adviser and your insurer will ask for.
What to do now and who must be told.
If you recognise one of these signs.
Encrypted or renamed files
Documents that won't open, strange extensions, a text file with a ransom demand on a server, NAS or computer.
Hacked mailbox
Emails sent in your name, replies to messages you never wrote, forwarding rules you didn't create, sign-ins from countries you aren't in.
Payment to a fake IBAN
A real invoice with changed bank details, or a supplier saying they never received a payment your records show as made.
Computers acting strangely
Antivirus switched off, software you didn't install, the cursor moving on its own, accounts locked for no reason.
We know the systems that have to be put back on their feet.
Every day we look after more than 110 servers and 320 domains, email on Microsoft 365, Google Workspace and Kerio, and the NAS units and backups of professional firms, companies and healthcare facilities. So once an attack is stopped, we also know how to get work going again. After a serious security incident, for a group of laboratories we removed the on-site mail gateway and moved everything to Exchange Online.
Where we've done it before.
From an antispam gateway straight to Microsoft 365.
MX on Exchange Online Protection, Microsoft DKIM, DMARC from p=none to p=reject across 8 domains. Then the internal systems that send email: instruments, servers, phone system.
Email that leaves only from those entitled to send it.
Per-site SES policies with allowed IPs, a DMARC path from p=none to p=reject, SendGrid authentication and SPF under 10 lookups. One mistake stopped before going live.
Security remediation for a laboratory group.
External rating and penetration test findings closed one by one, then three inherited servers replaced by two, managed directly.
Four vulnerabilities closed on a platform that runs real heating systems.
CVE-2022-37454, CVE-2022-31629, CVE-2017-8923 and CVE-2020-11022 closed on a CakePHP 2.9.5 application: PHP 7.4.33 with the right FPM handler, jQuery 3.7.1 in seven views and a report on why PHP 8 is not possible.
If it's happening now.
Should we pay the ransom?
Paying doesn't guarantee you get the data back or that it won't be published, and the decision isn't a technical one: it is taken with your lawyer and your insurer. We work to get you running again from backups, and tell you plainly what can be recovered and what can't.
We have backups: can't we just restore?
Only once it's clear how long the intruder had been inside and how they got in. Otherwise you also restore the open door, or a backup that is already compromised.
Who do we have to notify?
It depends on what was touched: the data protection authority if personal data is at risk, CSIRT Italia if you fall under NIS2, the police for the report, the bank and the insurer. We help you gather the facts; assessments and notifications stay with you and your advisers.
We aren't your customers: can you still step in?
Yes. We need someone who can take decisions and administrator access to email, servers and network, or a contact for whoever manages them today.
What if it's the website that was hacked?
Websites have a dedicated service, described on the Hacked site page: clean-up, rebuild from official sources and a move to an isolated environment.