Ransomware Recovery for a 10-Person Singapore Company: The Plan to Write Before December
Ransomware recovery for a small Singapore company is not a technology project. It is a decision sequence: who declares the incident, who is allowed to disconnect things, which systems come back first, how the business keeps quoting and invoicing while they are down, and what you must tell customers and the regulator. A ten-person firm with that sequence written down is usually trading again in two to three days. The same firm without it loses two to three weeks, most of it spent deciding rather than restoring. Writing the plan takes one afternoon and no new software.
What does ransomware recovery actually mean for a company with no IT team?
Forget the picture of a server room. In a ten-person Singapore business the hostage is usually a mix of a shared cloud drive, one accounting file, a WhatsApp-driven sales process and a laptop belonging to whoever does the books. Recovery means three separate things, and confusing them is where the lost weeks come from.
First, containment: stopping the spread, which is mostly unplugging and signing out. Second, restoration: getting working copies of the files and systems back. Third, re-entry: finding out what was created in the gap and re-keying it, because the invoices raised on Monday will not exist in a Friday backup. Most owners plan only for the second one. The third is the part that eats the fortnight.
Why is December the worst month to be hit?
Attacks are timed for when nobody is watching, and a Singapore SME in late December is close to unwatched. The owner is away, the one person who knows the admin passwords is on leave, the accounts staff are halfway through a year-end close, and the bank is clearing a larger-than-usual payment run. A compromise that would be spotted in an hour in March can sit unnoticed for three days over the holidays.
The cost is also higher in December. Being down for four days in June delays some work. Being down for four days before 31 December means the stocktake is unverifiable, the receivables chase stops dead at the exact moment collections matter most, and the accounts for the financial year close on numbers you cannot prove. The same incident carries a bigger bill purely because of the date.
What should the first four hours look like?
Write these as instructions a junior staff member can follow alone at 9pm, because that is who will be holding the phone.
- Disconnect, do not shut down. Pull network cables and switch off Wi-Fi on affected machines. Leaving them powered preserves evidence and sometimes keys in memory.
- Call the named person. One name, one mobile number, with a second name as backup. Not a group chat.
- Protect the backups before anything else. If a backup drive or sync folder is still connected, disconnect it. Ransomware encrypts attached backups as happily as live files.
- Force a password reset on email and cloud accounts from a clean device, and sign out all sessions.
- Write a timeline as you go. Times, screenshots, what was done. Your insurer and the regulator will both ask, and memory three weeks later will not hold.
- Make a police report and notify SingCERT. Both are quick, both create the record you will want later.
Nothing on that list requires technical skill, which is the point. The technical work can start an hour later when the right person is awake.
Does a ransomware attack trigger a PDPA notification?
Often, yes, and this is the duty small firms are most likely to miss. Under the PDPA, a data breach must be reported to the Personal Data Protection Commission within three calendar days of assessing that it is notifiable, which generally means it is likely to cause significant harm to the individuals affected, or it involves the personal data of 500 or more people. Affected individuals must be told as well where significant harm is likely.
Two points matter for a ransomware case. Encryption alone can be notifiable if personal data was accessed or taken, and most modern attacks copy data before locking it. And the clock runs on your assessment, so a slow assessment is not a defence. Decide in advance who makes that call and where the PDPC notification form lives, because December is not the month to be reading the guidelines for the first time.
Should a small company ever pay the ransom?
Plan on not paying, and build the plan that makes that choice affordable. Paying funds the next attack, buys a decryption tool that frequently works only in part, and does nothing about data already copied out. Firms that pay still spend most of the same recovery effort afterwards.
The honest exception is a company with no usable backup and no other copy of its records. That is a decision to make with the police, your insurer and your lawyer, not at 11pm on a laptop. If reading this makes paying sound like your only realistic option, the useful conclusion is not about ransoms. It is that your backups need attention this month.
How do you keep trading while the systems are down?
Decide now what the business does for 72 hours without its main systems. For most Singapore SMEs the fallback is modest and entirely workable: a printed or offline copy of the customer and supplier contact list with amounts outstanding, a numbered manual invoice or delivery order book, one staff member authorised to confirm pricing from memory and judgement, and a short message you can send customers that says you are operating with reduced systems.
Agree in advance that nothing gets paid out during an incident without voice confirmation on a known number. Attackers read the mailbox they have just compromised, and a company in the middle of a crisis is the easiest target there is for a fake payment instruction from a familiar address.
What goes on the one page before the office closes?
Keep it to a single sheet, printed, with a copy outside the office and one with the owner.
- Who declares an incident, and who decides if they are uncontactable.
- Three phone numbers: your IT support, your insurer, and whoever handles PDPA questions.
- The three systems that must come back first, in order, with a plain reason for each.
- Where the backups are, how old they are, and who has tested a restore, with the date.
- The holiday roster: who is physically in Singapore each week and reachable.
- The 72-hour manual trading method, in two lines.
A single page of decisions made calmly in October is worth more than any product you can buy in a panic in January. If you do only one thing after reading this, pick up the phone and confirm that someone has actually restored a file from your backups this year.
Frequently asked questions
How much does a ransomware incident typically cost a 10-person Singapore company?
The ransom is rarely the largest line. Expect the real cost to sit in lost trading days, staff time re-entering records created after the last good backup, and specialist help charged at emergency rates. Plan on several days of disruption and a five-figure Singapore dollar bill even in a well-handled case, which is why the planning afternoon pays for itself.
Does cyber insurance cover this, and is it worth it for a small firm?
Policies commonly cover incident response, data recovery, business interruption and sometimes legal costs, but they also carry conditions, such as multi-factor authentication being in place. Read the conditions before you buy, because an unmet condition is how a claim gets reduced. For a ten-person firm holding customer data, a modest policy plus tested backups is a sensible pairing.
We use Google Workspace or Microsoft 365, so are we already safe?
No. Those platforms protect themselves well, but they faithfully sync whatever your laptop does, including encrypting your files. They also retain deleted items only for a limited period, after which the copy is gone. Treat cloud storage as convenient, not as a backup, and keep at least one copy that an attacker on a staff laptop cannot reach.
Ready to Transform Your Business?
Let Digital Perpetual help you automate, streamline, and grow.
Get Started with Digital Perpetual →