Colour theme
Book a consultation

Testing your ransomware defences

Test sign-in coverage, patch exceptions, alert handoffs and backup recovery through a controlled exercise before ransomware interrupts business operations.

A metal combination padlock resting on a white computer keyboard.

Knowing that backups and endpoint protection are installed leaves several questions unanswered. Would an alert reach someone who can act? Could you recover the application people need first? Would the instructions still be available if work email stopped working?

A ransomware readiness exercise checks those handoffs and records what needs fixing. Use a discussion scenario, harmless test alerts and an isolated restore environment. Don’t introduce live malware or interrupt production to see what happens.

1. Trace access to a critical system

Choose an application that supports important work. List the accounts, remote-access services and administrative tools that can reach it. Include suppliers and integrations outside your main sign-in system.

Ask IT to demonstrate the intended access restrictions using test accounts. Check whether MFA applies, whether former users have lost access and whether routine staff accounts can perform administrative actions. Record each exception and who accepts its risk.

The ransomware prevention guide covers common entry paths. This exercise checks whether your own controls and responsibilities match the plan.

2. Follow one overdue security update

Choose an update failure or unsupported system from the current report. Identify who received the finding, who decides its priority and what prevents completion. Include exposed remote-access equipment, applications and firmware where relevant.

Ask what temporary measures are in place and when the exception will be reviewed. Priorities should reflect exposure, exploitation information and business impact. Don’t assign the same deadline to every vulnerability or let a blocked update disappear from the work list.

3. Walk an alert through the response chain

Use a written scenario such as a suspicious administrator sign-in or a device showing unusual file activity. Ask each participant what they’d receive, what they’d check and whom they’d contact next.

Establish who can isolate a device, restrict an account and involve an incident-response specialist. Repeat the handoff with the primary contact unavailable and outside ordinary office hours. Record unanswered calls, missing permissions and decisions the business owner has to make.

The Cyber Centre’s ransomware playbook includes preparation, response and recovery guidance. Use it to review your plan with technical and business owners. Keep contact details and essential instructions somewhere accessible if normal accounts are unavailable.

4. Restore something the business can use

Agree which application or dataset to restore, how much recent work the business can afford to lose and how long it can operate without the system. Test in a separate environment with the necessary licences, configuration, keys and dependencies available.

Ask a business user to validate the recovered result. One file opening tells you little about whether the application, its integrations and its latest records work. Record the backup’s age, elapsed recovery time and anything missing.

Review who can delete or change recovery copies. If backups use retention locks, check how they’re configured and who can change them; the immutability guide explains that separate review. A good restore won’t deal with information that’s already been stolen.

5. Assign the findings and repeat the failed checks

Give each gap an owner, action and due date. Separate changes IT can make from decisions the business must approve, such as recovery priorities or spending on a replacement system.

Repeat the relevant exercise after the fix. Keep dated evidence for internal reviews and insurance questions, without claiming a test guarantees a future outcome. Update the plan when applications, suppliers or key people change.

If you’re dealing with a suspected attack now, use the cyberattack response guide and your response contacts. For planning and recovery testing, contact us to discuss your current setup.


Featured Image Credit