If ransomware hits your business, the first 48 hours decide whether you recover in days or limp along for weeks. Disconnect infected machines from the network immediately, don't power them off, call your IT partner and your insurer, notify the Information Regulator as soon as reasonably possible, and do not pay the ransom until every clean recovery option has been exhausted.
It usually starts on a Tuesday morning. An accountant opens what looks like a supplier invoice, clicks it, and by 10am the shared drive is a wall of encrypted files with a cheerful note demanding Bitcoin. The receptionist can't print. The practice manager can't open client files. The owner is standing in the passage asking the question nobody wants to answer: how bad is this?
That sinking feeling — the one where you realise your month-end, your client trust and possibly your reputation are all on the line at once — is why this article exists. You don't need a lecture on cyber hygiene right now. You need a clear order of operations.
What should you do in the first hour?
Speed matters, but panic makes it worse. In the first sixty minutes, your job is containment, not investigation.
- Disconnect, don't shut down. Pull the network cable or disable Wi-Fi on any machine showing signs of encryption. Powering off can destroy forensic evidence and sometimes interrupts recovery keys stored in memory.
- Isolate the shared storage. Your file server, NAS or cloud sync folders are the blast radius. If OneDrive or SharePoint is syncing encrypted files up to the cloud, pause sync on every machine before the damage spreads to backups.
- Stop staff from "just checking". Every curious click on an infected machine makes the forensic picture murkier. Send everyone home from their laptops or to a meeting room.
- Call your IT partner. Not a WhatsApp to the one-man IT guy who might reply tomorrow — a proper incident call. This is exactly why businesses move to managed IT support with a logged-ticket process instead of hoping someone picks up.
If you're in a regulated profession — law, accounting, healthcare, financial advisory — also pull out your incident response plan and your cyber insurance policy. Both have clauses about who you must call and when.
Who do you need to notify, and when?
This is where South African owners get caught out. POPIA is not GDPR — the rules are different.
Under POPIA (section 22), once you have reasonable grounds to believe personal information has been compromised, the responsible party must notify the Information Regulator and affected data subjects as soon as reasonably possible. You do not need to have finished investigating first, and there is no fixed hour-count deadline in POPIA — the obligation is to act promptly. The Information Regulator's guidance is at inforegulator.org.za.
Other calls to make early:
- Your cyber insurer. Most policies require notification within a set window and may dictate which forensic responders you can use. Call them before you engage anyone else, or you risk voiding the claim.
- Your bank. If finance data or banking credentials may have been exposed, flag accounts for monitoring.
- Key clients. Especially in professional services. A short, honest call to a top client before they read about it on a leak site protects the relationship far better than silence.
- Your legal advisor. Particularly for law firms, where client confidentiality obligations layer on top of POPIA.
Should you pay the ransom?
Short answer: treat payment as a last resort, and only after your IT and legal advisors have exhausted recovery options.
Paying funds criminal operations, marks your business as a soft target, and provides no assurance you'll actually get working decryption keys. Many businesses that pay still can't restore everything. The real question is not "should we pay?" — it's "do we have clean, tested backups we can actually restore from?"
That's where most SA SMBs discover the ugly truth: backups existed, but nobody tested a restore. Or backups ran to a drive that was also encrypted. Proper backup and recovery isn't just "do we have a copy" — it's "can we restore it, how fast, and to what point in time?"
How do you actually recover?
Once containment is done and notifications are underway, recovery runs on three parallel tracks.
| Track | What it involves | Typical timeline |
|---|---|---|
| Forensics | Identify the ransomware strain, entry point, and what data was accessed or exfiltrated | 2–7 days |
| Rebuild | Wipe affected endpoints, rebuild servers, reset all credentials, restore from clean backups | 1–5 days |
| Comms & compliance | Notify Regulator, clients, staff, insurer; document decisions | Ongoing for weeks |
Do not simply decrypt and carry on. If you don't find and close the entry point — a phished credential, an unpatched VPN, an exposed remote desktop — the attackers often come back within weeks using the same door.
This is also the moment to be honest about your prevention stack. Proper cyber security services, proactive monitoring and endpoint protection aren't optional extras for regulated SA businesses — they're the difference between "we caught it at one laptop" and "the whole practice is down".
How do you stop it happening again?
After the dust settles, the owners who recover well all do similar things:
- Patch management on every endpoint and server — not just "when we remember".
- Multi-factor authentication everywhere, especially on email and remote access.
- Backups with tested restores, kept off the main network, with a known recovery time.
- Phishing awareness training that staff actually complete, not a once-off slide deck.
- A written incident response plan — one page is better than none.
- An IT partner you can reach, with logged tickets and a real response commitment.
MiBOT's monthly service includes unlimited remote support, patch management, network monitoring, antivirus and anti-ransomware, and a sub-1-hour response on logged incidents Monday to Friday, 08:00–17:00. Our information security management system is certified to ISO/IEC 27001:2022 — proof that the processes behind the service are audited, not improvised.
Frequently asked questions
Will my cyber insurance cover the ransom?
Sometimes, but policies vary enormously. Many now exclude ransom payments entirely or require pre-approval of forensic providers. Read your policy before an incident, not during one, and call your broker the moment you suspect ransomware.
How long will my business be down?
For a prepared business with tested backups and a managed IT partner on standby, core systems can often be back within 1–3 working days. For businesses relying on a part-time IT person and untested backups, two weeks is not unusual — and some never fully recover.
Do I have to tell my clients?
If their personal information was or may have been compromised, POPIA requires you to notify affected data subjects as soon as reasonably possible. Beyond the legal obligation, a direct and honest call usually preserves trust better than discovery after the fact.
Can a small business really prevent ransomware?
You can't reduce the risk to zero, but you can reduce it dramatically. Most attacks that succeed on SA SMBs exploit basic gaps: missing patches, no MFA, weak backups, untrained staff. Close those and you move from "easy target" to "not worth the effort" for most attackers.
If you've been through a ransomware scare — or you're reading this hoping you never will — it's worth having a calm conversation with a team that handles these incidents regularly. Book a free consultation and we'll walk through where your real exposure sits.
Last reviewed: November 2026