A website security checklist for business owners
By the Vertex Stacks team · 6 min read · Updated
You do not need to be a security expert to avoid most website attacks. Attackers mostly look for easy targets: default passwords, forgotten admin pages, outdated software and keys left where anyone can read them.
This checklist focuses on the basics that prevent the majority of real-world incidents. It is written for owners and managers, so you can ask the right questions of whoever builds and hosts your site.
Protect the front door: admin access
- Use a long, unique password (12 characters or more) stored in a password manager.
- Turn on a second factor (an authenticator app) for every admin login.
- Limit login attempts per visitor and per account so guessing passwords is impractical.
- Keep admin pages out of search results and give them a short session lifetime.
- When a team member leaves, remove their access the same day.
Keep secrets secret
API keys, database passwords and signing secrets should live in environment variables on the server. Never put them in front-end code, public repositories, screenshots or chat messages.
If a secret is ever exposed, treat it as stolen: generate a new one, update the server, and revoke the old one. Do not just hope nobody saw it.
Use HTTPS and security headers
- HTTPS everywhere, with HTTP redirecting to HTTPS and Strict-Transport-Security enabled.
- A Content-Security-Policy that limits where scripts, images and connections can come from.
- X-Content-Type-Options: nosniff and a sensible Referrer-Policy.
- Framing protection (frame-ancestors or X-Frame-Options) so your pages cannot be embedded on look-alike sites.
Validate everything people send you
Every form field is untrusted input. Check type, length and format on the server, not only in the browser, and limit the size of each request.
Use parameterised database queries (never build queries by gluing text together) and let your framework escape output so a visitor cannot inject scripts into your pages.
Stop abuse before it costs you money
Forms that send email, call paid APIs or write to a database can be abused by bots. Abuse is a security problem and a billing problem.
- Per-visitor rate limits on every form and login.
- A hidden field that bots fill in and people never see.
- A global daily cap on emails sent and records saved, so a flood of traffic from thousands of addresses still has a ceiling.
- Spending alerts and, where offered, hard budget limits on hosting, database, email and any AI or API service.
Keep software up to date
- Review dependency updates and security advisories at least monthly (npm audit or your platform's equivalent).
- Remove packages and plugins you no longer use.
- Apply operating-system and platform security patches promptly if you manage your own servers.
Back up and rehearse recovery
Follow the 3-2-1 idea: three copies of your data, on two kinds of storage, with one copy somewhere else. A backup you have never restored is only a hope, so test a restore at least once.
Lock down your database
- Turn on row-level security for every table, so a leaked public key cannot read your data.
- Use the powerful service key only on the server, never in the browser.
- Keep file storage for private documents private, and share them only through short-lived links.
Security is a habit, not a one-off project. The goal is not a site that can never be attacked; it is one where an attack is hard, noisy, and cheap to recover from.
