Platform and technology

Securing your webshop and making backups

You prevent a hacked webshop by keeping your software up to date, using strong passwords with two-step verification and limiting the number of access points. You should also make automated backups in a separate location and test that you can actually restore them.

A hacked webshop costs you revenue, customer trust and often days of work. Fortunately, most attacks are not about clever tricks, but about outdated software, weak passwords and forgotten accounts. With a few fixed habits you can reduce the risk considerably. In this article you will read why attacks usually succeed, which measures deliver the most, how to set up backups properly and what to do if things go wrong anyway.

Why webshops get hacked so often

Most attackers do not target your shop personally. They let automated programs scan the internet for known weak spots, such as an old plug-in or a login page without protection. This makes a small shop just as interesting as a large one: it is about the vulnerability, not the revenue.

A webshop is also attractive because it holds data and payments pass through it. Attackers can steal customer data, inject a fake payment page or use your shop to send spam. You often only notice weeks later, for example because customers complain or your hosting provider warns you.

An example from practice: an entrepreneur with a WooCommerce shop installs an extra plug-in for a discount bar and then forgets about it. Six months later it turns out to contain a vulnerability for which an update has existed for a long time. Because nobody ran the update, the attacker was able to add files unnoticed.

Keep your software and extensions up to date

Updates often contain fixes for security vulnerabilities. As soon as such a fix is released, the vulnerability is publicly known and attackers can search for it specifically. Delaying updates therefore means deliberately leaving a known door open. This applies to your platform, your theme and every plug-in or app.

With a hosted platform such as Shopify, the provider takes care of the core for you, but third-party apps remain your responsibility. With WooCommerce or another self-hosted solution you have to keep track of everything yourself, including the server software if you manage it. So schedule a fixed time each week to check for updates.

A common mistake is updating on a busy sales day without testing. An update can break something in your shop. So make a backup first and preferably test major updates in a test environment. If you do not use one, choose a quiet moment and check your ordering process straight afterwards.

  • Remove plug-ins and apps you do not use, even if they are switched off
  • Choose extensions that have been updated recently and are actively supported
  • Turn on automatic updates for minor security releases if your platform allows it

Ensure strong access and limited permissions

Many break-ins start with a stolen or guessed password. People reuse passwords on multiple sites, and leaks at other services then end up at your shop. So use a unique, long password for every account and store them in a password manager rather than in your head or on a note.

Turn on two-step verification for your admin area, your hosting, your domain name and your email. The last one is often forgotten, even though someone with access to your mailbox can reset passwords for almost everything. An extra code on your phone makes a stolen password largely worthless.

Give employees and freelancers only the permissions they need. Someone who updates product texts does not need an administrator account. Delete accounts as soon as someone stops working for you. An old account of a departed web developer is a classic back door that can stay open for years.

Strengthen the technical foundation

Make sure your shop is only accessible via a secure connection, recognisable by the padlock in the browser. This protects data sent between customer and shop. With most hosting packages and platforms this is included as standard, but do check that all pages, including old links, automatically redirect to the secure version.

Choose a hosting provider that pays attention to security itself, such as updating the server, filtering attacks and offering backups. Ask beforehand what exactly they do and what you have to arrange yourself. A cheap package without that foundation can cost you a lot of time later.

Also limit what you store yourself. Preferably let your payment provider handle payments via iDEAL or credit card entirely, so that you do not store any card details yourself. What you do not have cannot be stolen. Also do not keep customer data longer than necessary and delete old test orders and exports.

Backups: how to make them properly

A backup is your safety net. If your shop gets hacked or an update goes wrong, you can go back to a working version. A good backup contains both the files and the database, because your products, customers and orders are in the database. Storing only files is therefore not enough.

Determine how often you need a backup based on how many orders you receive. If you get orders every day, a daily backup is the minimum. A calculation example: if you make a backup once a week and you roll back on day six, you lose six days of orders and customer accounts.

Store backups in a different place from your shop. If the backup is on the same server, an attacker or a failure will take both away at once. Keep multiple versions, so that you can go back further if an infection is only discovered late. A backup from yesterday does not help if the malware has been there for two weeks.

Test whether your backup works

Many entrepreneurs only discover during a crisis that their backup is incomplete or damaged. So restore a backup in a test environment at least a few times a year. Check that products, images, orders and the checkout process work as you expect.

Also note how long restoring takes and who can carry it out. That way you know beforehand whether you will be offline for an hour or half a day, and you do not have to search for login details or instructions during a stressful situation.

Spotting problems and acting when things go wrong

Watch for signs such as unknown administrators, sudden changes to your theme, strange redirects, unusual orders or a warning from your browser or hosting provider. The sooner you see it, the smaller the damage. If possible, turn on notifications for new administrator accounts and login attempts from unknown locations.

If you notice a hack, act step by step. First take the shop offline or put up a maintenance page, so that customers no longer enter data on an infected page. Contact your hosting provider and payment provider, because they can often look into it and help with tracing the cause.

Then restore a clean backup from before the infection and change all passwords, including those for hosting and email. Update everything to the latest version, otherwise the attacker will come back through the same vulnerability. If customer data has leaked, a duty to report may apply; ask for advice from the Autoriteit Persoonsgegevens (the Dutch Data Protection Authority) or an expert.

  1. Take the shop offline or put up a maintenance page
  2. Inform your hosting and payment provider
  3. Restore a clean backup
  4. Renew all passwords and access
  5. Update software and trace the cause

What you can start with today

Start with a short inventory. Make a list of all accounts around your shop: admin, hosting, domain, email, payment provider and any integrations. For each account, note whether two-step verification is on and who has access to it. Remove what is no longer needed.

Then check your updates and your backups. Look at when the last backup was made, where it is stored and whether you have tested it. That takes an afternoon, but it covers the most common causes of damage. Then schedule a fixed monthly check in your diary, so that security becomes a habit rather than a one-off action.

Common mistakes are: thinking your shop is too small to be interesting, making a backup but never testing it, and postponing security until something happens. If you have the basics in order, you keep the biggest risks out and recover faster if something does go wrong.

More on Webshoptiger

Frequently asked questions

Am I responsible myself if my shop runs on Shopify?

Partly. The provider secures the platform itself, but you manage passwords, staff accounts and the apps you install. That is where things often go wrong.

How often should I make a backup?

That depends on how much you change and sell. If you have orders every day, make a backup at least daily, and keep multiple versions in a separate location.

Is a security plug-in enough?

No, it is a supplement. Without updates, strong passwords and limited permissions your shop remains vulnerable, even with an extra security layer.

What should I do if customer data has leaked?

Remove the cause and inform your hosting provider. Then check whether you need to report a data breach to the Autoriteit Persoonsgegevens (the Dutch Data Protection Authority) and whether you need to notify your customers.

← All articles