The most useful security question for a business owner is often simple: who is responsible for this website after launch? If nobody owns updates, account access and backups, even a carefully built site can drift into trouble.
Know what you have and who can access it
Keep an inventory of the domain registrar, hosting account, content management system, plugins, payment integrations and email services. Record the account owner and renewal contact for each. Store credentials in a password manager rather than a shared document or message thread.
Give each person an individual account and only the access they need. Remove access when a supplier or employee leaves. Enable multi-factor authentication where available, especially for hosting, email and administration. OWASP’s authentication guidance is a useful technical reference for the team implementing these controls.
Make updates a routine
Assign someone to review updates for the framework or CMS, extensions and server software. Remove components you no longer use. Check whether each active component is still maintained; an old plugin with no responsible maintainer needs a replacement plan.
Test changes in a separate environment when possible. Before a significant update, confirm that you have a usable backup and a way to roll back. Afterward, check the forms, checkout and administration screens, not just the homepage.
Prove that a backup can be restored
A “backup successful” message is not the same as a working recovery. Agree what is included, how often it runs, where a separate copy is kept and who can restore it. Then perform a restore test away from the live website.
Think about what the business could lose between backups. A brochure site and a shop taking orders all day have different recovery needs. Write down those needs before selecting the backup schedule.
Check the less visible parts
- Production error pages should not expose credentials, internal paths or detailed debug information.
- Uploaded files need server-side validation and restrictions on how they can be served.
- Forms need server-side validation, appropriate abuse controls and safe handling of user input.
- Private configuration files and database exports should never be downloadable from the public site.
- Use HTTPS and check that certificates renew successfully.
Have a response plan
Keep a short contact list for the host, developer and business owner. Decide who can take the site offline, revoke access or restore a backup. Preserve relevant logs when investigating an incident rather than wiping away the evidence.
This checklist helps organise maintenance; it is not proof that a site is secure. If you handle customer accounts or transactions, ask for a technical review suited to those features. Our website audit guide explains how to turn findings into an actionable work list.
Have a project in mind?
Let’s talk it through