Skip to content
Back to the blog

Website care

Website and web app security: what to ask your developer

Updated

Website and web app security: what to ask your developer

You do not need to read code to ask good questions about security. Many of the risks are ordinary ones: a shared password, software nobody updates, a backup nobody has tested. This guide lists the questions to ask before a website or web application goes live, and the answers that should be written down.

Who can log in, and how

Start with the accounts: the domain, the hosting, the website’s admin area and any connected services such as payments or email. For each one, ask who has access and whether each person has their own login. With a shared login, you cannot remove one person without changing the password for everyone.

The government’s guidance on protecting business accounts recommends turning on multi-factor authentication whenever it is available, so that passwords are only one part of account security. Ask for it on every account that offers it, and agree how access is removed when a member of staff or a supplier leaves.

Who keeps the software up to date

A website is built on other people’s software: a content system, plugins, code libraries and the server itself. Fixes for security problems arrive as updates, and they only help once someone applies them. Ask who does that, how often, and how the important pages are checked afterwards. If nobody is named, assume nobody is doing it.

This is usually part of a care agreement, separate from the build. Our guide to ownership, hosting and maintenance covers what such an agreement can include.

What is backed up, and has a restore been tried

Backups let a business recover when files are lost or damaged. Ask what is backed up (the site’s files, its database, uploaded documents), how often, and where the copies are kept. Then ask when a restore was last tested. Until one has been tried, nobody knows whether the backup works.

What personal data the site collects

An enquiry form collects names and email addresses. A customer portal or booking system may hold much more. Ask for a plain list of the personal data the site stores, where it is kept, who can see it and when it is deleted. Collecting less is the simplest protection, because a field you never ask for cannot leak.

Agree in advance what happens if something goes wrong. The Information Commissioner’s Office guidance on personal data breaches says you must assess the likely risk to people and, if a risk is likely, notify the ICO as soon as possible and, where feasible, within 72 hours. The ICO notes that this guidance is under review, so check the page for its current wording. Either way the time is short, so decide now who the developer tells, and how quickly.

What the build itself should include

You can ask for these by name without knowing how they are done:

  • The whole site served over HTTPS, including forms and admin pages.
  • Every form checked on the server, with limits on how often it can be submitted.
  • Uploaded files restricted by type and size, and stored away from the public site.
  • Permissions enforced for each user role in an application, and tested with accounts that should be refused.
  • Passwords and keys for other services kept out of the code, so they can be replaced without a rebuild.

For an application that holds sensitive or regulated information, ask whether an independent security test is appropriate and who would commission it. A developer’s own checklist is not an audit.

A recognised baseline

If a customer or insurer asks what standard you work to, the National Cyber Security Centre describes Cyber Essentials as the minimum standard of cyber security recommended by the Government for organisations of all sizes. It applies to the organisation’s IT as a whole, so the website is only one part. The NCSC also publishes a guide for small organisations, which says you do not need to be a technical expert to use it.

Digital Marvels agrees access, data handling, backups and support responsibilities in the scope of a custom web application, and does not hold or imply a security certification. To talk through the requirements for your project, request a quote.

SecurityPersonal dataWebsite care

Want a price for your project?

Every project is quoted individually. Tell us what you need and you’ll get a written quote.

Request a quote