Ransomware Protection: Keep Your Computer Safe

Ransomware used to be thought of as a home-computer problem: a pop-up demanding payment to unlock your family photos. That picture is long out of date. Today's ransomware is run by organized groups that target businesses deliberately. They break into networks, look for the systems and backups that matter most, steal data, and then encrypt everything they can reach. The ransom note arrives only once the damage is done.

Small businesses are squarely in the target range. They hold valuable data, depend on a handful of critical systems, and rarely have dedicated security staff. The good news is that most successful attacks exploit a short list of weaknesses, and most of those can be fixed without a large budget.

Ransomware is malicious software that encrypts an organization's files and systems so they can't be used, then demands payment for a decryption key. Most modern attacks also steal data first and threaten to publish it, so effective ransomware protection combines prevention, backups that attackers can't reach, and a tested plan for responding and recovering.

This guide to ransomware protection explains how ransomware works today, how attackers get in, the controls that prevent most attacks, how to build backups that survive one, how to protect websites and servers, what to do if you're hit, and the reporting obligations Canadian organizations need to know.

What Is Ransomware?

Ransomware is a type of malware designed to extort money. Once it runs on a system, it encrypts files with a key the attacker controls. Documents, databases, images and sometimes entire servers become unreadable. A ransom note explains how to pay, usually in cryptocurrency, in exchange for a tool that promises to reverse the encryption.

How ransomware has changed

Early ransomware strains, such as those that spread widely around 2013 and 2014, were mostly opportunistic. They arrived in email attachments, encrypted whatever a single computer and its mapped network drives could reach, and demanded a modest payment. Modern ransomware operations work very differently.

Then Now
Opportunistic, mass-emailed infections Targeted intrusions, often by groups that buy access to a victim's network
Encrypted files on one PC and its mapped drives Spreads across servers, virtual machines, cloud storage and backups
Encryption only "Double extortion": data is stolen first, then encrypted, with a threat to publish it
Run by the malware's authors Often "ransomware as a service": developers rent their tools to affiliates who carry out attacks
Modest, fixed ransom Demands sized to what the attackers think the victim can pay
Hit within minutes of infection Attackers may spend days inside a network before encrypting

That last change matters most for defence. Because attackers often spend time exploring a network before they launch the encryption, there's a window in which good monitoring and access controls can stop an attack before it becomes a crisis.

Some groups now skip encryption altogether and simply steal data and demand payment not to publish it. Backups can't solve that problem on their own, which is why prevention and data protection matter as much as recovery.

How Ransomware Gets In

Most ransomware attacks begin through one of a handful of entry points. Knowing them tells you where to concentrate your effort.

  • Phishing emails. A convincing message persuades someone to open an attachment, click a link to a fake login page or approve a request. Phishing remains one of the most common starting points.
  • Stolen or reused passwords. Credentials leaked in other breaches, guessed or bought from criminal markets let attackers log in as a real user, often to email, remote access or cloud services.
  • Exposed remote access. Remote desktop services, VPNs and remote management tools reachable from the internet are a favourite target, especially when protected only by a password or left unpatched.
  • Unpatched software. Known vulnerabilities in firewalls, VPN appliances, servers, content management systems and their plugins are routinely exploited, often within days of a fix being published.
  • Trusted suppliers. Attackers sometimes compromise an IT provider, software vendor or managed service provider and use that access to reach its customers.
  • Malicious downloads. Fake software updates, cracked software and poisoned search results trick people into installing malware themselves.

Once inside, attackers typically try to gain administrator rights, find and disable or delete backups, copy valuable data out, and then trigger encryption across as many systems as possible at once.

Why Small Businesses Are Targets

It's tempting to assume attackers only go after large corporations. In practice, many ransomware groups favour small and mid-sized organizations for practical reasons:

  • Defences are often thinner. Fewer businesses this size have round-the-clock monitoring, a security team or a tested response plan.
  • Downtime hurts quickly. A clinic that can't access patient records, a manufacturer whose production system is locked, or an online store that can't take orders feels pressure to restore operations fast, which attackers hope will lead to payment.
  • They hold sensitive data. Client records, financial information and employee files are valuable for extortion even when the business itself is small.
  • They're connected to bigger targets. Suppliers and service providers can be a route into larger clients.

The Canadian Centre for Cyber Security has repeatedly identified ransomware as one of the most disruptive cybercrime threats facing Canadian organizations. Size doesn't make a business invisible.

Ransomware Prevention: The Controls That Matter Most

No single product delivers ransomware protection on its own. What works is a small set of controls that close the most common entry points and limit how far an attacker can get. If you do nothing else, do these.

  1. Turn on multi-factor authentication (MFA) everywhere it matters. Email, remote access, cloud services, banking, hosting control panels and administrator accounts should all require a second factor. MFA blocks most attacks that rely on stolen passwords. Where possible, use authenticator apps or hardware security keys rather than text messages.
  2. Patch quickly, especially internet-facing systems. Firewalls, VPNs, remote access tools, servers, and website software and plugins should be updated as soon as practical after fixes are released. Put them on a regular patching routine [URL pending: patch management article] with someone responsible for it.
  3. Lock down remote access. Don't expose remote desktop services directly to the internet. Put remote access behind a VPN or secure gateway with MFA, and close anything that isn't needed.
  4. Limit administrator rights. Day-to-day accounts shouldn't have admin privileges. Keep admin accounts separate, few in number and protected with strong MFA. The fewer accounts that can disable security tools or delete backups, the harder an attacker's job.
  5. Filter email and train people. Email filtering catches much of the malicious mail before it arrives. Short, regular awareness training helps staff recognize what gets through, and a simple way to report suspicious messages without embarrassment helps everyone.
  6. Use endpoint protection that looks at behaviour. Modern endpoint detection tools watch for ransomware-like activity, such as mass file encryption or attempts to delete backups, rather than relying only on known signatures.
  7. Segment the network. Separate critical systems from general office devices, and guest Wi-Fi from both. Segmentation slows an attacker down and limits how much can be encrypted at once.
  8. Know what you have. Keep an inventory of devices, servers, cloud services and accounts. You can't protect systems you don't know exist.

Our earlier look at how attacks now bypass the network edge instead of breaking through it explains why identity and configuration controls such as MFA and least privilege now carry so much of the load.

Remote and hybrid work

Staff working from home extend the business network into places you don't control. Home routers with default passwords, shared family computers and personal phones used for work email all widen the attack surface. A few rules help: company work happens on company-managed devices where possible, remote access goes through a VPN or secure gateway with MFA, home routers get their default passwords changed and firmware updated, and business files live in managed storage rather than on personal laptops.

Ransomware protection on a small budget

Not every business can afford a security team, but the most effective controls are also among the cheapest. If budget is tight, work through them in this order:

Priority Control Typical cost
1 Turn on MFA for email, remote access, banking, hosting and admin accounts Usually included in services you already pay for
2 Turn on automatic updates; close exposed remote desktop Staff time only
3 Remove admin rights from everyday accounts Staff time only
4 Start an offline backup rotation, even with external drives kept off-site Low
5 Short phishing awareness sessions and a reporting habit Low
6 Behaviour-based endpoint protection on every computer and server Moderate, per device
7 Managed backups with immutable copies Moderate
8 Network segmentation and professional monitoring Higher; often through an IT provider

The first five items address the majority of common attack paths and cost little beyond time. Items six to eight add depth as the business grows or the data it holds becomes more sensitive.

Recognizing the warning signs

Because many attackers spend days inside a network before encrypting anything, spotting the early signs can stop an attack. Treat these as urgent:

  • Security software disabled or uninstalled without explanation
  • New administrator accounts, or existing accounts gaining admin rights
  • Logins at unusual hours or from unfamiliar locations
  • Backup jobs failing, or backups disappearing
  • Large volumes of data leaving the network
  • Files suddenly renamed with unfamiliar extensions, or unreadable documents appearing on shared drives

Make sure someone receives these alerts and knows to act on them, even outside office hours.

Backups That Survive a Ransomware Attack

Backups are the part of ransomware protection that decides whether an attack is a bad week or a business-ending event. But ordinary backups often fail in a ransomware attack, because attackers know to look for them. Backups stored on the same network, reachable with the same administrator password, or synced automatically from infected systems are frequently encrypted or deleted along with everything else.

The 3-2-1 rule, updated for ransomware

The long-standing 3-2-1 rule is a good starting point: keep at least three copies of important data, on two different types of storage, with one copy off-site. Ransomware adds two requirements:

  • At least one copy must be offline or immutable. An offline copy is disconnected from your network. An immutable copy can't be changed or deleted for a set period, even by an administrator. Either way, an attacker who takes over your network can't destroy it.
  • Backups need separate credentials. The accounts that manage backups shouldn't be the same as your everyday administrator accounts, and they should be protected with their own MFA.

What to back up

Small businesses often back up their file server and forget everything else. A complete backup plan covers:

  • File shares and documents
  • Business applications and their databases
  • Email, if you host it yourself or your provider doesn't retain it adequately
  • Data held in cloud and software-as-a-service tools, which often have limited built-in retention
  • Your website: its files, database and configuration
  • Configuration of firewalls, servers and key systems, so you can rebuild them

Test restores, not just backups

A backup you've never restored is an assumption, not a plan. Test restores regularly, including at least one full restore of a critical system, and time how long it takes. Decide in advance how much data you can afford to lose (your recovery point objective) and how long you can be offline (your recovery time objective). Then check that your backups actually meet those targets.

Protecting Cloud Storage and Online Office Tools

Many small businesses assume that files stored in online office suites or cloud storage are safe from ransomware. They are safer in some ways, but not immune.

Sync spreads encryption. If ransomware encrypts files in a folder that syncs to cloud storage, the encrypted versions sync too, replacing the good copies. Version history and recycle bins usually allow recovery, but only within their retention periods, and an attacker with account access can sometimes delete those as well.

Accounts are the real target. An attacker who takes over a cloud administrator account can delete data, change sharing settings, read email and turn off protections. MFA on every account, and especially on administrator accounts, matters as much in the cloud as anywhere else.

Built-in retention isn't a backup. Online services are designed to stay available, not to keep your data for as long as you might need it. Check how long deleted items and previous versions are kept. For important data, consider a separate backup service that copies cloud data to storage outside the account.

Review connected apps. Third-party apps granted access to cloud accounts can read and change data. Remove ones you no longer use, and limit new ones to the access they need.

Protecting Websites and Servers

Websites and hosted servers are part of the ransomware picture too. Attackers compromise websites through outdated content management systems, vulnerable plugins and themes, weak administrator passwords and stolen hosting credentials. Once inside, they may encrypt or delete the site's files and database, leave a ransom note on the home page, or use the site as a foothold to steal customer data. Servers running Linux and virtualization platforms are also targeted by ransomware built specifically for them.

Who protects what

Security on hosted infrastructure is shared between the host and the customer. The split depends on the type of hosting.

Responsibility Shared hosting Managed WordPress hosting VPS Dedicated server
Physical security, hardware and network Host Host Host Host
Server operating system and patching Host Host Customer, unless managed Customer, unless managed
Website software, plugins and themes Customer Usually shared; check the plan Customer Customer
Account passwords and MFA Customer Customer Customer Customer
Backups Varies by plan; check retention and location Varies by plan; check retention and location Customer, unless included Customer, unless included
Independent off-site backup copy Customer Customer Customer Customer

The last row is the one most often missed. Even when a hosting plan includes backups, keeping your own independent copy of your website, stored somewhere else, protects you if the hosting account itself is compromised or the plan's retention period is too short.

Hardening a website against ransomware

  • Keep the CMS, plugins and themes updated, and remove any you no longer use.
  • Use MFA on the hosting control panel and the site's admin accounts, and give each person their own login.
  • Use strong, unique passwords for the database, file access and admin accounts.
  • Install only well-maintained plugins and themes from reputable sources.
  • Restrict file permissions so the web server can write only where it needs to.
  • Use HTTPS throughout and keep certificates valid.
  • Monitor for unexpected changes to files and admin accounts.
  • Keep independent backups of files and database, with at least one copy off the hosting account.

Managed hosting can take some of this work off your hands. A managed WordPress environment typically handles core updates and server maintenance, and our breakdown of the routine work behind a reliable WordPress site explains what that involves. For businesses running their own VPS and applications, the extra control over hardening also means full responsibility for it.

Questions to ask your hosting provider

  • How often are backups taken, how long are they kept, and where are they stored?
  • Are backups stored separately from the server they protect, and could someone with my account password delete them?
  • Can I download my own copies of backups?
  • Is MFA available on the control panel?
  • What does the provider monitor, and how will it alert me to a compromise?
  • Which security tasks are mine, and which are yours, in writing?

If you host with 4GoodHosting, ask the team to confirm what your plan includes for backups and monitoring, so the split between your responsibilities and the host's is clear before anything goes wrong.

Your Ransomware Response Plan

Every business should have a short, written plan for a ransomware attack, prepared before it's needed and stored somewhere an attacker can't encrypt it, such as on paper or with a trusted adviser.

Before an attack: prepare

  • List who to call: your IT provider, hosting provider, insurer, legal adviser and key internal decision-makers, with phone numbers that don't depend on your email.
  • Decide who makes decisions, including whether to shut systems down, communicate with customers or engage outside help.
  • Check your cyber insurance, if you have it. Many policies require you to notify the insurer quickly and to use approved responders.
  • Keep the plan offline and review it at least once a year.

During an attack: contain and assess

  1. Isolate affected systems. Disconnect infected devices from the network, wired and wireless, to stop the spread. Don't wipe them, because they hold evidence investigators and insurers may need.
  2. Protect your backups. Disconnect backup systems if they're still intact, and change backup credentials from a clean device.
  3. Call for help early. Contact your IT or security provider, your insurer and, if relevant, your hosting provider.
  4. Preserve evidence. Keep the ransom note, logs and affected devices. Record what happened and when.
  5. Assess the scope. Work out which systems and data are affected and whether data was stolen as well as encrypted.
  6. Reset credentials for affected accounts from clean devices, starting with administrator and email accounts.

After containment: recover and learn

Restore systems from known-clean backups, after making sure the attacker's access has been removed. Restoring onto a still-compromised network invites a second attack. Once operations are back, review how the attackers got in, fix the weakness, and update the plan.

Test the plan with a tabletop exercise

A plan nobody has rehearsed tends to fall apart under pressure. Once a year, gather the people who would be involved and walk through a realistic scenario: it's Monday morning, files on the shared drive won't open, and a ransom note is on the screen. Who notices, who do they call, who decides to disconnect systems, and how do you contact staff if email is down? Where's the insurer's number? How long would restoring the accounting system actually take?

An hour spent talking through these questions usually turns up gaps, such as outdated phone numbers, backups nobody knows how to restore, or decisions with no clear owner, that are far cheaper to fix now than during an incident.

Should you pay the ransom?

Every organization hit by ransomware faces this question, and there's no simple answer. Some points to weigh:

  • Payment doesn't guarantee recovery. Decryption tools can be slow, partial or faulty, and some victims never receive a working key.
  • Payment doesn't undo data theft. Attackers who stole data may still publish or sell it, or demand a second payment.
  • Payers can be targeted again. Paying signals that the organization is willing to pay.
  • There may be legal issues. Payments can raise questions under sanctions laws and other rules, depending on who the attackers are.
  • Payment funds further attacks.

The Government of Canada's guidance recommends against paying ransoms. Any decision should be made with legal advice and, if you're insured, in consultation with your insurer. The strongest position is not to need to decide at all, which is what tested, offline backups provide.

Cyber Insurance and Ransomware

Cyber insurance can help cover the costs of an attack, such as incident response, recovery, legal advice, breach notification and business interruption. It is not a substitute for prevention, and insurers increasingly expect the basics to be in place before they will offer cover.

Application forms commonly ask whether a business uses MFA, keeps offline or immutable backups, patches regularly, uses endpoint protection and trains staff. Answer these accurately. A claim can be complicated if the controls described on the application weren't actually in place.

If you have a policy, read it before you need it. Check what's covered, what's excluded, how quickly you must notify the insurer, whether you must use approved incident responders, and how the policy treats ransom payments. Keep the insurer's emergency contact in your offline response plan.

A ransomware attack is a security incident, and often a privacy breach as well. Canadian organizations should understand their obligations before an attack happens.

Privacy breach reporting. Under the Personal Information Protection and Electronic Documents Act (PIPEDA), a breach of security safeguards includes the loss of, unauthorized access to, or disclosure of personal information. Ransomware can involve all three: encryption causes loss of access, and data theft causes unauthorized access and possible disclosure. If a breach creates a real risk of significant harm to individuals, organizations must report it to the Office of the Privacy Commissioner of Canada, notify affected individuals and notify certain other organizations. Every breach of security safeguards must be recorded and the record kept for 24 months, whether or not it's reportable. Alberta, British Columbia and Quebec have their own private-sector privacy laws, and health information is often covered by provincial health privacy legislation, each with its own requirements.

Reporting the crime. Ransomware is a crime. Report it to your local police, and to the federal reporting channels for cybercrime and fraud, which help law enforcement track and disrupt ransomware groups.

Reporting to the Cyber Centre. The Canadian Centre for Cyber Security accepts reports of cyber incidents and publishes guidance, including a ransomware playbook, that is a good starting point for preparing a response plan.

Contracts and insurance. Client contracts, industry rules and insurance policies may require notification within specific timeframes. Check them as part of your preparation, not during an incident.

Three Scenarios

A small accounting firm in Winnipeg receives an email that appears to come from a client, with a link to a shared document. An employee enters their email password on a fake login page. Because the firm uses MFA on email, the attacker can't log in, and the firm resets the password and reports the phishing attempt. Without MFA, the attacker would have had access to client correspondence and a starting point for a wider attack.

An online retailer in British Columbia runs its store on WordPress with several plugins that haven't been updated in months. An attacker exploits a known plugin vulnerability, encrypts the site's files and leaves a ransom note on the home page. The retailer's hosting plan includes backups, but it also kept its own weekly off-site copy of the site and database. It restores the site from a clean backup, updates every plugin, removes those it no longer uses, and resets all admin passwords. The store is offline for a day rather than weeks, and the retailer reviews whether any customer data was accessed before deciding on breach notification.

A family-owned manufacturer in Ontario left remote desktop access open to the internet so staff could work from home. Attackers guess a weak password, spend several days exploring the network, delete the backups on the connected backup server, and encrypt the production and accounting systems. The company's only surviving copy is an older offline backup. After recovery, it moves remote access behind a VPN with MFA, separates backup credentials from admin accounts, and adds an immutable off-site copy.

A Ransomware Readiness Checklist

  1. MFA is on for email, remote access, cloud services, hosting control panels and all admin accounts.
  2. Internet-facing systems, servers and website software are patched on a schedule, with an owner.
  3. No remote desktop service is exposed directly to the internet.
  4. Everyday accounts don't have administrator rights.
  5. Email filtering is in place, and staff know how to report suspicious messages.
  6. Endpoint protection watches for ransomware behaviour on every computer and server.
  7. Critical systems are separated from general office devices and guest Wi-Fi.
  8. Backups follow 3-2-1, with at least one offline or immutable copy and separate credentials.
  9. Website files and database are backed up independently of the hosting account.
  10. Restores have been tested in the last six months, against recovery time and recovery point targets.
  11. A written response plan, with contacts, is stored offline.
  12. You know your privacy breach reporting obligations and who will handle them.

Where Ransomware Is Heading

Ransomware groups adapt quickly, and a few trends are already clear. More attacks focus on stealing data, with or without encryption, because backups have made encryption-only attacks less reliable. Attackers increasingly target backups, virtualization platforms and cloud accounts directly. And more convincing phishing, including messages generated with AI tools, makes social engineering harder to spot.

The defences, however, are stable. MFA, prompt patching, limited admin rights, segmented networks, offline or immutable backups and a tested response plan block or blunt the large majority of attacks. None of them requires a large security team. They require someone in the business to own them, and the discipline to keep them in place.

Get in Touch

message
Your form has been submitted successfully.
We'll be in touch with you shortly.
Your email address will not be published. Fields marked with an asterisk (*) are mandatory.
+1 S
You may also like: