Website security for a growing UK business: a practical plan

Website security for a growing business is mostly about control and routine. Know who can log in to the website, the hosting and the domain, and protect every login with 2-step verification. Keep the software updated, take backups you have actually restored, use HTTPS everywhere and handle forms and file uploads with care. Agree in writing what your web developer and your host do. Then plan what you’ll do if something goes wrong, before it does.

This guide is general information, not legal advice. If you’re unsure what applies to your business, check with an adviser.

Key takeaways

  • You stay responsible for the personal data your website collects. UK GDPR puts security duties on you and on suppliers who handle it for you.
  • Give every person and supplier their own login, turn on 2-step verification or passkeys, and remove leavers promptly.
  • A backup only proves itself when you restore it. Test a restore, and keep one copy away from the live site.
  • Write down who does what if something goes wrong. A notifiable personal data breach must be reported to the regulator within 72 hours of becoming aware of it, where feasible.
  • Answer security questionnaires with what is true today, including what your suppliers do. Claim Cyber Essentials only if you hold a current certificate.

Why does website security matter more as your firm grows?

For an established firm, the website is no longer just a brochure. It collects enquiries with names and phone numbers, drawings and specifications sent with tender requests, CVs from job applicants and, on some sites, logins for clients or staff. It is often one of the first things a new buyer checks, so a defaced page or a browser warning costs you trust as well as time.

The government’s Cyber Security Breaches Survey 2025/2026, published on 30 April 2026, found that “Just over four in ten businesses (43%)” reported a cyber security breach or attack in the last 12 months. The figures were higher for medium (65%) and large (69%) businesses, and phishing was reported by 38% of businesses. The survey notes that it “only includes the breaches or attacks that organisations were able to identify and willing to report”, so the true numbers may be higher.

The website is one part of a bigger picture. The National Cyber Security Centre (NCSC) covers email, devices and backups in its Small organisations guide to cyber security. This guide concentrates on the website and the accounts around it.

Who is responsible for what: you, your developer or your host?

Security gets missed when everyone assumes someone else is doing it, so write down who does what.

Under UK GDPR, your business is usually the controller of the personal data your website collects: you decide why it is collected and what happens to it. A host or developer who handles that data on your behalf is usually a processor. Article 32 of UK GDPR says “the controller and the processor shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk”. So both have duties, and using a supplier doesn’t take yours away. Guidance from the ICO (the UK’s data protection regulator; since 30 September 2026 its legal name is the Information Commission) says “as a data controller you are responsible for ensuring compliance with the UK GDPR and this includes what the processor does with the data”, and that “you must choose a data processor that provides sufficient guarantees about its security measures”. The ICO notes that this guidance is under review after the Data (Use and Access) Act.

The ICO also says “You should identify a person with day-to-day responsibility for information security within your organisation”. Often that is a director or office manager, with suppliers doing the technical work. A typical split:

Job Usually done by Agree in writing
Domain and DNS You, through your registrar account Who holds the login and pays the renewal
Server and server software Your host What they update, and how they report incidents
Website software and add-ons Your developer, or you Who updates, how often, and who checks afterwards
Backups Host, developer or both Where copies are kept, for how long, and who tests a restore
Logins You Who approves new logins and removes old ones
Forms and uploads You decide; your developer builds What is collected, where it goes and when it is deleted

Accounts and access

Much of the practical protection for a website sits in its logins. List every account that can change your site or where it points: the domain registrar, any separate DNS provider, the hosting control panel, the website’s admin area, the email accounts that receive password resets, Google Search Console and any form or booking service. The NCSC lists “your company website (and domain hosting if that is a separate account)” among the accounts a business should protect.

  • One named login per person. No shared admin logins. Each person and supplier gets their own, with the lowest access that does the job.
  • 2-step verification or passkeys on every account. The NCSC says “Turning on 2SV is one of the most effective ways to protect online accounts when passwords are still in use”, and advises enabling passkeys for business-critical accounts where they are available.
  • Strong, unique passwords. A password manager makes this practical. Never send passwords by email.
  • Remove leavers and old suppliers. The NCSC warns that when people leave, “those accounts often stay active without anyone noticing”, and says “you should remove or disable the accounts you no longer use”. That includes the agency or freelancer who built your last site.
  • Review access regularly. The NCSC’s advice: “Make it a habit to review who has access to important accounts every few months, and remove anyone who no longer needs it.”
  • Keep the key accounts in your company’s name. The domain, hosting and admin accounts should belong to your business, with recovery details you control. Our guide to checking whether you own your website takes five minutes.

Updates, and backups you have tested

Updates

The NCSC describes security update management as a way to “Prevent cyber criminals using vulnerabilities they find in software as an access point to your systems”. Keep the website’s software, theme and add-ons up to date, remove add-ons you no longer use, and ask your host how the server software is kept current. The NCSC’s advice for apps applies to websites too: “If you use apps or software that no longer receive updates, you should find an alternative that is supported”. If your site runs on WordPress, our guide to updating WordPress safely sets out a routine.

Backups

A backup is only useful if you can put the site back from it. The NCSC says that once you’ve made a backup, “it’s important you know how to restore it, and to check that it contains all your important data”. UK GDPR asks for the same thing where personal data is involved: Article 32 lists “the ability to restore the availability and access to personal data in a timely manner in the event of a physical or technical incident”.

  • Back up both parts: the files and the database.
  • Keep a copy away from the live site. The ICO gives the example of a business that follows a 3-2-1 approach of “three copies, with two stored on different devices and one stored off-site”, and recovers from ransomware using the off-site copy.
  • Test a restore. Our suggestion, which is not a legal test, is to restore a backup to a test location at least twice a year and after any major change, and to note the date and how long it took.
  • Protect the backups. The NCSC says “You should protect your online backups by turning on 2-step verification (2SV)”. In our view, your retention schedule should also say how long backups are kept.

HTTPS, forms and file uploads

HTTPS

Every page should load over https, with a certificate that renews automatically and the http address redirecting to the secure one. The ICO says “if you are storing personal data, or transmitting it over the internet, we recommend that you use encryption”. HTTPS protects information in transit, not the site itself. Our guide to SSL certificates and browser security warnings explains how to fix a warning.

Forms

  • Ask only for what you need to reply.
  • Know where every submission goes. An inbox, a copy on the website, a form service: each copy is another place to protect and, later, to delete.
  • Set how long you keep submissions, and delete them on that schedule.
  • Stop spam without blocking people. Hidden checks and a sending limit can keep out much of the spam without asking visitors to solve puzzles.

Our guide to enquiry forms and UK GDPR covers the privacy side.

File uploads

Drawings, specifications and CVs often arrive through upload fields. In our view, these deserve extra care, because they can carry both personal data and commercially sensitive information:

  • Accept only the file types you expect, such as PDF or DWG, and set a sensible size limit.
  • Make sure uploaded files can’t be opened by anyone who guesses their web address. Ask your developer where they are stored.
  • Limit who can open them, and delete them when the tender or recruitment round is over.

Hosting basics and monitoring

Questions to ask your host

  • Where are the servers and the backups located?
  • Who keeps the server software updated, and how quickly are security fixes applied?
  • How often are backups taken, how long are they kept, and how do we restore one?
  • How and how quickly will you tell us about a security incident? Under Article 33 of UK GDPR, “The processor shall notify the controller without undue delay after becoming aware of a personal data breach.”
  • What logs do you keep, and for how long?

Changing host? See our guide to moving your website to a new host.

For example, we designed and built the website for V&H Construction Group, a cladding company based in Dartford. Its case study lists, under “Looked after”, “HTTPS, UK hosting and a daily backup”.

Monitoring

In our view, a light routine covers the basics:

  • Google Search Console. Google says “If a Google evaluation determines that your site was hacked, or that it exhibits behavior that could potentially harm a visitor or their computer, the Security issues report will show Google’s findings.”
  • Uptime alerts that tell you when the site stops responding.
  • Login and update emails from your website, host and registrar, read and acted on.
  • A monthly look at the user list in the website’s admin area and the hosting account.
  • Unexpected renewal notices. Check emails about your domain or hosting through your own account, not the links in them. Our guide to spotting domain renewal and SEO scam emails shows what to look for.

What should you do if something goes wrong?

Before it happens

The NCSC says “your business should have a cyber attack plan in place that will define who does what (and when) if something goes wrong”. The ICO’s breach checklist includes “We have prepared a response plan for addressing any personal data breaches that occur.” Many firms don’t have one: in the Cyber Security Breaches Survey 2025/2026, 25% of businesses had a formal incident response plan, rising to 57% of medium businesses and 76% of large businesses.

A one-page plan for the website can cover:

  1. Who decides, and who calls the host and developer, with out-of-hours numbers.
  2. Where logins and recovery codes are kept, securely.
  3. Where the latest tested backup is, and who can restore it.
  4. Who decides whether personal data was involved, and who reports it.
  5. Who tells clients and staff, and what you’ll say.
  6. Your insurer’s notification terms, if you have cyber cover.

When it happens

Our guide to what to do first if your website is hacked covers the first hours. The legal side runs alongside it.

The ICO says “A personal data breach means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data.” If that happens, Article 33 of UK GDPR says the controller must notify the regulator “without undue delay and, where feasible, not later than 72 hours after having become aware of it”, “unless the personal data breach is unlikely to result in a risk to the rights and freedoms of natural persons”. You must record every personal data breach, reported or not. The ICO’s guide to personal data breaches adds that if a breach “is likely to result in a high risk of adversely affecting individuals’ rights and freedoms, you must also inform those individuals without undue delay.”

Reporting a crime

GOV.UK says “Contact Report Fraud if you think you’ve lost money or been hacked because of an online scam or fraud and you’re in England or Wales.” The NCSC gives Report Fraud for England, Wales and Northern Ireland, on 0300 123 2040, and says “If you live in Scotland, you should report to Police Scotland by calling 101”. For other incidents, the NCSC points businesses to a government signposting service on GOV.UK, Where to Report a Cyber Incident.

How should you answer a buyer’s security questionnaire?

Main contractors, public bodies and larger clients may send supplier questionnaires about cyber security. Your website, hosting and email are part of the answer.

Cyber Essentials

The NCSC describes Cyber Essentials as “the minimum standard of cyber security recommended by the Government for organisations of all sizes”. It covers five technical controls: firewalls, secure configuration, security update management, user access control and malware protection. The current requirements document, according to the NCSC, is “Cyber Essentials Requirements for IT infrastructure v3.3”, effective from 27 April 2026. Cyber Essentials Plus adds independent technical testing. The NCSC’s page says basic certification is priced by the size of your organisation, “starting at £320 +VAT” (checked 18 November 2026), and that “A growing number of organisations require suppliers to be certified to bid for work”.

For central government, the Cabinet Office’s Procurement Policy Note 014 says “This PPN applies to all central government departments, their executive agencies and non-departmental public bodies, and NHS bodies.” It tells those bodies to make sure suppliers meet certain technical requirements on contracts with particular characteristics, such as “where personal information of citizens, such as home addresses, bank details, or payment information is handled by a supplier”. It also says “The Cyber Essentials Scheme should not be applied to all contracts as a matter of course”, that a supplier without the certificate “must be able to demonstrate equivalent controls are in place through other means”, and that “Other public sector bodies may wish to apply the approach set out in this PPN.”

PPN 014 also notes that a certificate covers the legal entity by default, and that “Cyber Essentials does not ensure that the security of the third party is in scope of certification.” In our reading, your certificate doesn’t vouch for your host or web developer, so expect questions about them too.

Answering honestly

  • Answer for the company that is bidding, as things stand today.
  • Say partly, with a date for the fix, rather than a hopeful yes.
  • Name your website suppliers and what they do, and ask them for their answers in writing.
  • Keep evidence: your account list, backup test notes, update routine and supplier contracts.
  • Claim only certificates you hold, by their exact name and while current. The NCSC links to a public search of current Cyber Essentials certificates, so buyers can check.
  • Keep one master set of answers and review it every six months, which is our suggestion. The NCSC notes that suppliers can use Cyber Essentials “as evidence across their customer base, reducing the time spent filling out duplicative questionnaires.”

Our B2B website checklist covers the documents buyers look for, and our guide to websites for construction tenders covers pre-qualification.

The plan on one page

Area Done when
Responsibilities A named owner, and a written split with your host and developer
Accounts Listed, held by the company, one login per person, leavers removed
2-step verification On for every account that can change the site or the domain
Updates A routine with a named person; unused add-ons removed
Backups Files and database, one copy off-site, a restore tested and noted
HTTPS Every page on https, certificate renewing automatically
Forms and uploads Minimal fields, known storage, file limits, deletion dates
Hosting Answers on location, updates, backups and incidents
Monitoring Search Console, uptime alerts and a monthly user check
Incidents A one-page plan, contacts and the 72-hour rule understood
Questionnaires One honest master set of answers, with evidence

Common questions

Do we need Cyber Essentials?
It depends on who you sell to. PPN 014 asks in-scope public bodies to require it, or equivalent controls, on certain contracts, and the NCSC says a growing number of organisations require it from suppliers. Even if no buyer asks, the ICO says “A good starting point is to make sure that you’re in line with the requirements of Cyber Essentials”.

If our website is hacked, is it our developer’s fault?
It depends on what happened and what your contract says. Article 32 puts security duties on both the controller and the processor, so write the split down.

How often should we test a backup?
The law doesn’t set a frequency. On testing security measures generally, the ICO says UK GDPR “does not specify the type of testing, nor how regularly you should undertake it.” Our suggestion is at least twice a year and after any major change.

Do we have to report every breach to the ICO?
No. You report a personal data breach unless it is unlikely to result in a risk to people’s rights and freedoms, but you must record every one, with your reasons for not reporting.

Free help

If you’d like help with your website

We’re Hintling Studio, an independent web design studio registered in London. We build websites for established businesses across the UK. Every package includes a contact form, a booking-request or quote-request form and 30 days of aftercare, and hosting can be added as an extra. We don’t sell a security monitoring service.

See our work and what’s in each package, or tell us about your business.

Sources checked on 18 November 2026: legislation.gov.uk, GOV.UK, the NCSC, the ICO and Google. Hintling Studio is not connected with the NCSC, the ICO (Information Commission), the Cabinet Office, GOV.UK, the Cyber Essentials scheme, Report Fraud, Police Scotland, Google or WordPress.

Is your website working for you?

A one-page checklist to score your website in about ten minutes. No sign-up and no email needed: just download it.

Preview of the one-page Is your website working for you? checklist

Let’s build yours.

Send us a short brief and we’ll reply with a fixed quote and a timeline. No calls needed unless you want one.