businessleadersaward.comWebsites, portals and workflows for corporate teams

Insights · businessleadersaward.com

Website security basics: backups, updates and access control

By the businessleadersaward.com editorial team · · 4 min read

In short: Most website security comes down to three habits: keep tested backups stored separately from the site, apply software updates promptly, and control access with individual accounts, multi-factor authentication, minimum necessary permissions and immediate removal of leavers. Add HTTPS, monitoring and a short incident plan, and review the setup at least once a year.

Website security is the set of measures that keep a company website available, unaltered and free from unauthorised access. For most organisations, the serious risks are not sophisticated attacks but ordinary failures: an outdated plugin with a known vulnerability, a former employee whose login still works, a shared password, or a backup that turns out not to restore. Addressing those covers a large share of the practical risk.

This guide is written for managers who are responsible for the website but are not security specialists. It does not replace a professional assessment where your sector or contracts require one.

1. Backups you can actually restore

A backup is a copy of your site's files and database that can be used to rebuild it after a failure, error or attack. Three questions matter: how often backups are made, where they are stored, and whether anyone has tested a restore.

  • Frequency: daily backups suit most business sites; sites with frequent changes or portal uploads may need more.
  • Separation: store copies away from the live server, so a compromise or server failure does not destroy them too. The widely used 3-2-1 rule suggests three copies, on two types of storage, with one kept off-site.
  • Retention: keep several days or weeks of versions, because some problems, such as injected malicious code, are noticed only later.
  • Testing: restore a backup to a test environment periodically. An untested backup is an assumption, not a safeguard.

2. Updates and patching

Websites run on layers of software: the server operating system, the web server, the content management system, themes, plugins and libraries. Vulnerabilities are discovered in all of them, and fixes arrive as updates. Attackers routinely scan for sites running versions with known weaknesses.

  1. Keep an inventory of the software and plugins your site uses.
  2. Remove plugins and themes that are not in use; they still carry risk.
  3. Apply security updates promptly, ideally after a quick check on a staging copy.
  4. Assign responsibility: on managed hosting, agree in writing what the provider updates and what you update.
  5. Replace components that are no longer maintained by their developers.

3. Access control

Access control decides who can log in to the site, hosting account, domain registrar and email, and what they can do there. It is where many incidents start, and it is entirely within your control.

PracticeWhat it means in practice
Individual accountsEvery person has their own login; no shared admin password
Multi-factor authenticationA second factor, such as an authenticator app, on all admin, hosting, registrar and email accounts
Least privilegeEditors can edit content but not install plugins or manage users
Leaver procedureAccess removed on the person's last day, including registrar and hosting accounts
Periodic reviewList all accounts every quarter and remove those no longer needed
Ownership of key accountsDomain and hosting registered to the company, not an individual or former supplier

The last point is often overlooked. If your domain is registered in the name of an employee or a previous agency, regaining control during an incident can take a long time. Check who the registrant is.

4. HTTPS, forms and monitoring

  • HTTPS encrypts traffic between visitors and your site. Certificates expire, so monitoring their renewal avoids sudden browser warnings.
  • A web application firewall filters common malicious requests before they reach the site.
  • Forms should collect only the data you need, validate input and use spam protection; sensitive documents belong in a secure portal rather than a contact form or email.
  • Uptime and change monitoring alerts you when the site goes down or files change unexpectedly.

5. A short incident plan

Write a one-page plan before you need it: who decides, who contacts the hosting provider, where backups are, how to reset all admin credentials, and who assesses whether personal data was affected. Under data protection laws such as the GDPR, a personal data breach may need to be reported to the supervisory authority, in the GDPR's case within 72 hours of becoming aware of it where it is likely to result in a risk to individuals, so knowing who makes that assessment matters.

Quick annual checklist

  1. Restore a backup to a test environment.
  2. Review all user accounts across site, hosting, registrar and email.
  3. Confirm multi-factor authentication is enabled everywhere it is available.
  4. Remove unused plugins, themes and integrations.
  5. Check domain registrant details and renewal dates.
  6. Review what personal data forms collect and how long it is kept.
  7. Update the incident plan with current names and contacts.

Trade-offs

Stronger controls add friction. Multi-factor authentication slows logins, staging checks delay updates, and restricted permissions mean editors occasionally need to ask for help. These costs are usually small compared with recovering from a compromised site, but they need management support to stick. No setup makes a site immune; the aim is to reduce likelihood and recovery time.

Our hosting and email service includes a firewall, SSL monitoring and daily backups on Professional, while portals in Digital Office Premium use individual accounts for every user.

Questions and answers

Is HTTPS enough to make a website secure?

No. HTTPS protects data in transit between the visitor and the server, but it does nothing about outdated software, weak passwords or missing backups. It is one necessary layer among several.

Who is responsible for website security on managed hosting?

Responsibility is shared. The provider typically secures the server infrastructure and the services it manages, while your organisation controls user accounts, passwords, content and who has access. Agree the split in writing.

How often should we review user access?

Quarterly reviews suit most companies, plus an immediate check whenever someone leaves or changes role. Include hosting, domain registrar and email accounts, not just website logins.

Talk to us about your project

Email support@businessleadersaward.com or send a request. We reply by email within one business day.