Most small and mid-sized businesses do not lose their websites to clever, targeted attacks. They lose them to an outdated plugin, a former employee's admin account that nobody removed, or a backup that turned out to be empty on the day it was needed. This website security checklist pulls together the controls we see making the biggest difference on real business sites, grouped so you can work through them with your team or your web provider. By the end you will know what to check, how often, and who should own each item.
Why a website security checklist beats a one-off audit
Security is mostly about consistency. A single audit gives you a snapshot; a checklist gives you a routine. Sites change constantly: new plugins are added, staff come and go, hosting gets upgraded, a marketing tool asks for a script tag. Each change can quietly open a gap.
A checklist also makes responsibility visible. When every item has an owner and a frequency, it becomes obvious when something has been forgotten, which is exactly the situation attackers rely on.
The list below is ordered roughly by impact for a typical business site. If you only have time for the first two sections this month, start there.
1. Accounts and access control
Compromised logins remain one of the most common ways into a website. Before anything technical, tidy up who can get in.
- Inventory every account with access to the site admin, hosting panel, domain registrar, DNS provider, CDN, email server and code repository.
- Remove or disable accounts for former staff, contractors and agencies that no longer work with you.
- Apply least privilege. Content editors do not need administrator rights. Developers do not need billing access to the registrar.
- Enforce strong, unique passwords stored in a password manager, not a shared spreadsheet.
- Turn on two-factor authentication for every admin, hosting and registrar account. We cover the options in our guide to adding two-factor authentication to your web platform.
- Limit login attempts and alert on repeated failures.
- Use named accounts, not a shared "admin" login, so actions can be traced to a person.
Key takeaway: The domain registrar and DNS accounts are often the least protected and the most damaging to lose. Whoever controls them controls your website and your email.
2. Software updates and dependencies
Unpatched software is the other big entry point. Automated scanners look for specific vulnerable versions within days of a public disclosure.
- Keep the CMS or framework core on a supported version.
- Update plugins, themes, packages and libraries on a regular schedule, ideally after testing on a staging copy.
- Remove plugins and themes you are not using; deactivated code can still be exploited if it is reachable.
- Keep the server's PHP, Node or other runtime on a version that still receives security fixes.
- For custom applications, run dependency checks (for example
composer auditornpm audit) as part of each release. - Subscribe to security advisories for the main components you rely on.
If your site runs on WordPress, our WordPress security hardening guide goes deeper into plugin hygiene and configuration.
3. Server and hosting configuration
Your application can be well written and still be exposed by a weak server. Whether you manage the server yourself or use a managed host, confirm these points.
| Area | What good looks like |
|---|---|
| TLS/HTTPS | Valid certificate, automatic renewal, HTTP redirected to HTTPS, HSTS enabled once stable |
| Operating system | Supported release, security updates applied regularly |
| Remote access | SSH keys rather than passwords, root login restricted, non-standard exposure minimized |
| Firewall | Only required ports open; admin panels restricted by IP where practical |
| File permissions | Web server cannot write to application code; uploads directory cannot execute scripts |
| Isolation | Each site or client in its own account or container, not sharing one user |
| Error display | Detailed errors logged, never shown to visitors in production |
For a deeper server-level list, see our Linux server hardening checklist. If you would rather not manage this yourself, our managed hosting and email service covers patching, monitoring and isolation as standard.
4. Application-level protections
These items apply to the website or platform itself and are usually handled by your developers.
Input, output and forms
- Validate all input on the server, not only in the browser.
- Use parameterized queries or an ORM to prevent SQL injection.
- Escape output by default to prevent cross-site scripting.
- Protect forms with CSRF tokens.
- Add bot protection to contact, signup and login forms without punishing real users.
Security headers
Check that your responses include sensible headers:
Content-Security-Policyto restrict where scripts and styles can load from.X-Content-Type-Options: nosniff.Referrer-Policyset to a privacy-respecting value.Strict-Transport-Securityonce HTTPS is reliable.- Frame protection through CSP
frame-ancestors(orX-Frame-Optionsfor older browsers).
Files and third-party scripts
- Restrict file uploads by type and size, store them outside the public code directory and never execute them.
- Review every third-party script (chat widgets, tag managers, analytics). Each one can read and modify your pages.
- Remove old test pages, phpinfo files, database dumps and backup archives from public folders.
5. Backups and recovery
A backup you have never restored is a hope, not a plan.
- Back up both files and databases automatically, at a frequency that matches how often content changes.
- Keep at least one copy off the hosting server, in a separate account the website itself cannot delete.
- Retain several restore points so you can roll back to before an infection that went unnoticed for weeks.
- Encrypt backups that contain personal data.
- Test a full restore to a staging environment at least a few times a year and record how long it took.
Our article on the 3-2-1 backup strategy for websites explains how to structure this.
6. Monitoring and logging
You cannot respond to what you cannot see.
- Monitor uptime and certificate expiry from outside your own network.
- Keep web server, application and authentication logs, and store them somewhere an intruder cannot easily erase.
- Alert on unusual events: new admin users, mass file changes, spikes in failed logins, sudden outbound email volume.
- Use file integrity monitoring on production code where possible.
- Review alerts on a schedule; alerts nobody reads provide no protection.
7. Privacy and data handling
Security and privacy overlap heavily, and privacy laws in Canada, the UAE and the EU all expect reasonable safeguards for personal information.
- Collect only the personal data you actually need through forms.
- Know where submissions are stored: in the database, in email inboxes, in a CRM, or all three.
- Set retention periods and delete old submissions.
- Restrict who can export customer or patient data.
- Keep your privacy policy aligned with what the site actually does.
For Canadian specifics, read PIPEDA for websites. Legal obligations vary by sector and province, so confirm the details with a privacy lawyer.
8. Incident response
Decide what happens before something goes wrong, while everyone is calm.
- Write down contacts: developer, host, registrar, internal decision-maker and, if applicable, legal counsel.
- Define severity levels and who must be told at each level.
- Document containment steps: maintenance mode, credential rotation, isolating the server.
- Preserve evidence: logs, a copy of affected files and a timeline.
- Restore and verify from a clean backup, then close the entry point.
- Assess notification duties if personal information may have been accessed.
- Review afterwards and update this checklist.
Suggested frequency and ownership
| Task | Frequency | Typical owner |
|---|---|---|
| Review user accounts and access | Quarterly and at every staff change | Business owner or IT lead |
| Apply core, plugin and package updates | Monthly or as advisories require | Developer or support provider |
| Server OS and runtime patching | Monthly, urgent fixes immediately | Hosting provider |
| Backup restore test | Quarterly to twice yearly | Developer or host |
| Log and alert review | Weekly | Support provider |
| Third-party script review | Twice yearly | Marketing plus developer |
| Full checklist review | Twice yearly and after major changes | Shared |
Next steps
Print this checklist, assign an owner to each section and note today's status honestly. Most businesses find two or three items that need attention straight away, usually stale accounts, untested backups or overdue updates.
If you would like a second pair of eyes, DigiVort can review your site against this list and fix what we find through our security and compliance service, or keep it maintained month to month with ongoing maintenance and support. When you are ready, tell us about your project and we will suggest a sensible starting point.