Cybersecurity

The Website Security Essentials Checklist

A practical website security checklist for business owners: 25 essentials across logins, updates, HTTPS, hosting, backups and monitoring, with what to do first.

F

Force Media Team

7 min read
Gold combination padlock and bank cards resting on a white keyboard

Photo: Towfiqu barbhuiya on Unsplash

Most website break-ins aren't clever. They come through a password that was reused, a plugin that wasn't updated, or an admin account nobody remembered still existed. The attacker doesn't need to be brilliant. They just need you to have skipped something boring.

That's why we like checklists. Over the last three weeks we've written about ransomware, WordPress plugins, React2Shell and poisoned npm packages. This post pulls the lessons together into one website security checklist: 25 essentials, grouped so you can hand each section to whoever owns it.

Where attacks actually start

Verizon's 2025 Data Breach Investigations Report analysed more than 22,000 security incidents, including 12,195 confirmed breaches. Two ways in stood out: stolen or abused credentials, and exploited software vulnerabilities.

22%

of breaches began with credential abuse

Verizon DBIR 2025

20%

began by exploiting a vulnerability, up 34% on the year before

Verizon DBIR 2025

30%

involved a third party, double the previous year

Verizon DBIR 2025

Logins, updates and the suppliers you trust. Keep those three in mind, because most of the checklist below is about closing exactly those doors.

Website security checklist: logins and access

This is where we'd start, because it's cheap and it blocks the most common way in. Microsoft researchers studied real attacks on Azure AD accounts and found that multi-factor authentication reduced the risk of compromise by 99.22%, and by 98.56% even when the password had already leaked.

Logins and access

  • Turn on multi-factor authentication for every admin login: the website, hosting, domain registrar, DNS and email.
  • Give everyone their own account. No shared 'admin' logins passed around by email or chat.
  • Remove accounts for people who have left, and agencies or freelancers who no longer work on the site.
  • Use a password manager, so every password is long, unique and never reused.
  • Give people the least access they need: an editor who writes blog posts doesn't need to install plugins.

Software and updates

Software and updates

  • Keep the CMS or framework, plugins, themes and packages up to date, and apply security patches within days, not months.
  • Delete plugins, themes and test pages you no longer use. Deactivated code can still be attacked.
  • Know what your site depends on: keep a list of plugins, or a committed lock file for custom builds.
  • Turn on vulnerability alerts (for example Dependabot, or your security plugin's alerts) so you hear about problems the day they're announced.

The OWASP Top 10, the standard list of the most serious web application risks, added Software Supply Chain Failures at number three in its 2025 edition. Updates aren't housekeeping any more. They're the front line.

Developer wearing headphones working at screens of code in a dark room
Most of website security is unglamorous: regular updates, tidy accounts and someone who actually reads the alerts. Photo: Jefferson Santos on Unsplash

HTTPS and security headers

HTTPS is now close to universal: the HTTP Archive's 2025 Web Almanac found 97.3% of mobile homepages were served securely. Security headers are a different story. These are short instructions your server sends with every page, telling browsers to block common tricks such as loading your site inside someone else's page or running injected scripts. They cost almost nothing to add, yet most sites still don't send them.

Share of websites using each security feature (mobile, 2025)

Figures marked ~ are approximate readings from the report's charts. Source: HTTP Archive, Web Almanac 2025, Security chapter

HTTPS and headers

  • Serve every page over HTTPS, redirect HTTP to HTTPS, and make sure certificates renew automatically.
  • Add Strict-Transport-Security (HSTS), so browsers never fall back to an insecure connection.
  • Add X-Content-Type-Options, X-Frame-Options (or a frame-ancestors rule) and a Referrer-Policy.
  • Work towards a Content-Security-Policy that only allows scripts from sources you trust. Test it in report-only mode first.

Hosting, forms and data

Hosting, forms and data

  • Use reputable hosting with up-to-date server software, and a web application firewall (many hosts and CDNs include one).
  • Protect every form from spam and abuse with rate limiting or a CAPTCHA, and validate what users send on the server, not just in the browser.
  • Keep secret keys and passwords out of your code and out of public folders; store them in environment variables or a secrets manager.
  • Collect only the personal data you need, and know where it's stored and who can see it.

The cheapest security work is deleting things: old accounts, old plugins, old data you never needed.

Backups and recovery

Backups are what turn a disaster into a bad afternoon. Verizon found ransomware in 44% of the breaches it studied, and a working backup is the difference between paying and restoring.

Backups and recovery

  • Back up files and the database automatically, at least daily for sites that change often.
  • Keep at least one copy somewhere separate from your hosting account, so one compromised login can't delete both.
  • Keep several days or weeks of history, not just last night's copy, in case a problem went unnoticed.
  • Test a restore at least twice a year. A backup you've never restored is a hope, not a plan.

Monitoring and response

Monitoring and response

  • Use uptime monitoring that alerts you when the site goes down or its content changes unexpectedly.
  • Keep login and error logs, and get alerted to repeated failed logins or new admin accounts.
  • Know who you'd call if the site were hacked tonight, and write their number down somewhere that isn't the website.
  • Keep a short incident plan: take the site offline, change every password, restore from a clean backup, then find how they got in.

Keeping it up: a simple routine

Security isn't a one-off project. It's a few small habits on a schedule.

  1. Weekly

    Updates and alerts

    Apply updates, read any security alerts, and check that last night's backup actually ran.

  2. Monthly

    Accounts and plugins

    Remove accounts nobody needs, delete unused plugins, and look over the login logs.

  3. Quarterly

    Test and review

    Run a header and SSL check, restore a backup to a test site, and review who has access to hosting and DNS.

  4. Yearly

    Bigger picture

    Get a professional review or penetration test, and revisit this whole checklist against how the site has changed.

Security work and search performance overlap more than people expect: HTTPS, speed and a site that stays online all matter to Google too. Our technical SEO checklist is a good companion to this one.


Force Media builds, secures and maintains websites for businesses in Sri Lanka, Australia and beyond, with updates, backups, security headers and monitoring included. Ask us for a website security check, and we'll tell you which items on this list your site is missing.

Speak to our experts

From AI agents to secure, fast websites, we build technology that does real work for your business.

Get in touch
FAQ

Common Questions

Everything you need to know about working with Force Media.

Ask Us Anything
We primarily serve businesses in Sri Lanka and Australia, but our remote-first approach means we can work with clients globally.
Project timelines vary by scope. A standard website takes 2–4 weeks. Custom software projects range from 6–16 weeks depending on complexity.
Yes. All our projects include a support period, and we offer ongoing retainer packages for maintenance, SEO, and feature development.
Absolutely. We specialize in integrating with existing platforms, APIs, and legacy systems to extend their capabilities.