Imagine your office manager arrives on a Monday morning and nobody can open the shared drive. Every folder holds a note demanding payment in cryptocurrency, and a warning that client files will be published if you don't pay. Good ransomware protection is what turns that morning into a bad day with a clear recovery path, rather than a business-ending event. This guide covers how attacks get into a small or medium business, the controls that stop them, backups that survive, how to respond, and what Australian law requires.
In short, ransomware protection works in layers. Close the common ways in with the Essential Eight, especially multi-factor authentication, fast patching and limited admin rights. Keep at least one backup that attackers cannot reach, change or delete, and prove it restores. Then add monitoring and a written response plan, so you act in minutes, not days.
How ransomware gets into small businesses
Ransomware locks devices or encrypts files, then demands payment. Many attackers also steal data first and threaten to publish or sell it, which the Australian Signals Directorate (ASD) calls data extortion. A backup restores files, but it cannot recall stolen data.
ASD's Australian Cyber Security Centre (ACSC) says most ransomware attacks are the result of poor cyber hygiene rather than sophisticated techniques. Its ransomware guidance and small business handbook point to a familiar set of entry points:
- Phishing emails and messages with malicious links or attachments, including Office files carrying macros
- Unsafe websites and infected downloads, including pirated software
- Compromised accounts, where a password has been stolen, reused or guessed
- Unpatched devices, including servers and network attached storage (NAS), which the ACSC notes are common targets
- Internet-exposed services such as remote desktop, file shares, webmail and remote administration tools
Most attacks are opportunistic: ASD's Essential Eight maturity model describes entry-level attackers as seeking any victim with common weaknesses. If an account they compromise has special privileges, they use it, and they may destroy data, including backups. Fixing the common gaps makes your business a much harder target.
Ransomware prevention mapped to the Essential Eight
The Essential Eight is a set of eight mitigation strategies from ASD, covering patching, multi-factor authentication (MFA), admin privileges, application control, Office macros, application hardening and backups. Its Essential Eight maturity model, last updated in November 2023, defines Maturity Levels Zero to Three and recommends reaching the same level across all eight before aiming higher. New to it? Start with the Essential Eight framework explained.
As at November 2026, ASD is evolving the Essential Eight into its new ASD Essentials series, published on 15 October 2026, which replaces maturity levels with priority phases. ASD says the series is written mainly for Commonwealth entities, critical infrastructure and large organisations, that every Essential Eight strategy maps to at least one of its principles, and that current Essential Eight uplift should continue while organisations assess alignment. For a small business, the Essential Eight remains a practical baseline.
The table maps common entry points to the ransomware protection controls that close them, drawing on Maturity Level One and ACSC guidance.
| How ransomware gets in | Essential Eight control | What good looks like |
|---|---|---|
| Phishing attachment with a macro | Restrict Microsoft Office macros | Macros off for staff with no business need; macros in files from the internet blocked; users can't change macro settings |
| Malicious download or fake installer | Application control; user application hardening | Only an approved set of programs and scripts can run from user folders; browsers don't process web ads or Java from the internet |
| Stolen or reused password | Multi-factor authentication | MFA on email, Microsoft 365 and every online service holding sensitive data |
| Unpatched internet-facing system | Patch applications; patch operating systems | Critical fixes for internet-facing services and devices applied within 48 hours when the vendor rates them critical or an exploit exists; unsupported systems replaced |
| Exposed remote desktop or admin tool | MFA; patching | Remote access behind MFA and kept patched; services you don't need switched off |
| Attacker using an admin account to spread | Restrict administrative privileges | Separate admin accounts used only for admin work and blocked from email and web browsing |
| Attacker deleting your backups | Regular backups | Restores tested; ordinary user accounts cannot modify or delete backups |
1. Put MFA on email and remote access first
The ACSC's ransomware prevention guide says to prioritise MFA on critical services such as email and remote access. Then extend it to every cloud service that holds business or customer data. At Maturity Level Two, the model expects phishing-resistant MFA, because more capable attackers use social engineering to get around weaker forms.
2. Patch fast, starting at the edge
Anything that faces the internet comes first: firewalls, VPNs, remote access gateways and web-facing servers. At Maturity Level One, critical fixes for these are applied within 48 hours. Office suites, browsers, email clients and PDF software get two weeks, and workstation operating systems one month.
3. Take admin rights off everyday accounts
Staff should work in standard accounts, with admin accounts kept separate and used only for admin tasks. The ACSC notes this limits how much data ransomware can encrypt, steal or delete.
4. Control what can run
Application control stops unapproved programs and scripts from running, which blocks many malicious downloads outright. Pair it with macro restrictions, hardened browsers, and security software with its ransomware protection switched on. Teach staff how malware usually arrives and how to report anything odd.
5. Shrink what you expose to the internet
Audit every internet-facing service, especially remote desktop, file shares, webmail and remote administration tools. Switch off what you don't need and secure the rest.
Backups that survive: the last line of ransomware protection
The ACSC is clear that the best way to recover from ransomware is to restore from an unaffected backup. A backup stored on an infected device, or reachable over the same network, may be encrypted or deleted along with everything else.
Backups that survive an attack share a few traits:
- At least one copy sits out of the attacker's reach. That can be an offline copy, disconnected from your network when not in use, or an immutable copy that cannot be changed or deleted until its retention period ends.
- Backups use separate credentials. The maturity model expects that ordinary users cannot modify or delete backups, and at Maturity Level Two only dedicated backup administrator accounts can. Protect the backup console with MFA and never reuse an everyday admin password.
- Cloud data is included: the ACSC's handbook asks whether email and cloud accounts are in your backup plan.
- Restores are tested as part of disaster recovery exercises. Time them.
The handbook suggests a simple backup plan that answers six questions: what is backed up, when, where it is stored, who manages it, how long copies are kept, and how often restores are tested. Computer Support Professionals (CSPRO) covers scheduled recovery testing, defined recovery objectives and 24/7 backup health monitoring through its IT disaster recovery services.
Detecting an attack and responding fast
Ransomware protection doesn't stop at prevention. The ACSC's handbook notes that no security software is 100% effective, so plan to spot trouble early.
Endpoint detection and response
Endpoint detection and response (EDR) goes beyond scanning files. Microsoft's EDR is a typical example: it continuously collects behavioural data from each device, such as processes, network activity, logins and file changes. It raises alerts for an analyst and lets a responder isolate a device from the network. For a plain-English comparison, see antivirus versus EDR explained.
Logging and monitoring
The ACSC's handbook suggests watching for:
- multiple failed logins or unusual login behaviour
- access from unexpected locations or outside normal hours
- creation or modification of administrator accounts
- large or unusual data transfers
- unexpected system or configuration changes.
For servers and NAS devices, the ACSC also suggests alerts for high disk activity and account logins. Alerts only help if someone acts on them.
A response plan and who to call
A response plan sets out who does what, how to contain an incident, and when to escalate and report. The ACSC recommends testing it with simple drills. Keep a printed copy with phone numbers, because the ACSC points out you may not have access to your devices during an attack. For the detail, see this guide to writing an incident response plan.
The ACSC's first steps are to record what you see (a photo of the screen is fine), turn off infected devices, then turn off or disconnect other devices, starting with servers and NAS. Change important passwords, get professional help, and only restore from backups you know are clean. The step-by-step data breach response walks through the full sequence.
Your call list should include:
- your IT provider or internal IT lead
- the Australian Cyber Security Hotline, 1300 CYBER1 (1300 292 371), available 24 hours a day, 7 days a week
- your cyber insurer, if you hold a policy
- IDCARE's Small Business Cyber Resilience Service, which offers eligible small businesses free support
- your lawyer or privacy adviser, for notification decisions.
What Australian law requires if you are hit
This section is general information as at November 2026, not legal advice. Check your obligations with a qualified adviser or the relevant regulator.
Ransomware payment reporting
Part 3 of the Cyber Security Act 2024 requires certain businesses to report ransomware and cyber extortion payments. The Home Affairs guidance on the Act sets out the essentials:
- Who: businesses carrying on business in Australia with annual turnover of more than $3 million in the previous financial year, plus responsible entities for critical infrastructure assets under Part 2B of the Security of Critical Infrastructure Act 2018. Businesses that traded for only part of the year use a pro-rated threshold.
- Trigger: making a payment, or becoming aware one was made on your behalf. Non-monetary benefits count. If nothing is paid, no payment report is required.
- Deadline: within 72 hours, using the reporting form on cyber.gov.au.
- Timing: Home Affairs states reporting has been mandatory since 30 May 2025, with an education-first approach until 31 December 2025 and a more active compliance focus from 1 January 2026.
- Penalty: failing to report can attract a civil penalty of 60 penalty units.
The Notifiable Data Breaches scheme
Ransomware that steals data is often a data breach too. Under the Notifiable Data Breaches scheme, organisations covered by the Privacy Act 1988 must notify affected individuals and the Office of the Australian Information Commissioner (OAIC) when a breach is likely to cause serious harm. Coverage generally means annual turnover above $3 million, plus some smaller businesses, such as private health service providers. You must take all reasonable steps to assess a suspected breach within 30 days. The two regimes are separate, so a business that pays may owe both reports.
Reporting the attack itself
Whatever your size, the ACSC asks businesses to report cyber security incidents through ReportCyber or by calling 1300 CYBER1. Reporting a demand you didn't pay is voluntary but encouraged.
Should you pay the ransom?
The Australian Government strongly discourages paying. Its reasons:
- Paying does not ensure your data is decrypted, or that stolen data won't be leaked or sold.
- Payments fund criminal activity and encourage further attacks.
- A payment may contravene sanctions laws, which is a serious criminal offence.
- You may be targeted again.
Make ransom decisions part of your ransomware protection planning: decide now who has authority to make decisions, who calls the insurer and lawyer, and who tracks the 72-hour clock if a payment is ever made. The strongest position is backups that restore, so the question never becomes urgent.
Where to start with ransomware protection this month
- List every internet-facing system, and switch off or secure what you don't need.
- Turn on MFA for email, Microsoft 365, remote access and your backup console.
- Check patch status on firewalls, VPNs, servers and NAS devices, and set a 48-hour target for critical fixes.
- Remove admin rights from everyday user accounts.
- Confirm one backup copy is offline or immutable with separate credentials, then run a timed test restore.
- Write a one-page response plan with phone numbers, and print it.
- Check your turnover and Privacy Act coverage, so you know which reporting rules apply.
Conclusion
Ransomware rarely needs a clever attack. It usually needs one unpatched system, one reused password or one admin account used for email. Close those gaps with the Essential Eight, keep a backup attackers can't touch, watch for warning signs, and know who to call and what to report. That is ransomware protection a small business can realistically run. If you would like an outside view of where your gaps are, CSPRO's managed cybersecurity services start with a free initial cybersecurity risk assessment.




