Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Research & Resources 6 min read

Website security checklist for business owners

A plain-English checklist covering ownership, access, patching, configuration, backups, monitoring and incident readiness.

E
EncryptTechBD · 0 comments
Office team reviewing charts
Photo: Matt Moloney / StockSnap

Most small business websites are not hacked by a determined attacker. They are compromised through an abandoned plugin, a shared password, an administrator account nobody owns, or a backup stored on the same server. The fixes are unglamorous and mostly administrative.

This checklist is written for the owner or manager, not for the developer. Each group has items you can verify, an owner to name and evidence to keep. Work through it once, then put the recurring items on a calendar.

Group 1: Ownership and inventory

  1. Name the owner of the domain and hosting accounts. The business should hold the registrar and hosting logins, not an agency that may change suppliers. Evidence: account ownership register. Owner: business owner.
  2. List every component. CMS version, theme, plugins, forms, payment integration, chat widget, analytics and CDN. Evidence: inventory with version numbers. Owner: technical lead.
  3. Record who has access. Names, roles and last login for every administrator. Remove anyone who has left or changed role. Evidence: access list with review date.

Group 2: Accounts and access

  1. Turn on multi-factor authentication for the registrar, hosting panel, CMS administrator accounts and any database console. Evidence: screenshot or policy showing MFA enforced. Owner: technical lead.
  2. Remove shared logins. Every administrator should have a named account. Shared accounts make an incident investigation almost impossible.
  3. Apply least privilege. Editors do not need administrator rights, and no one needs file editing in the dashboard if changes go through deployment. Evidence: role matrix.

Group 3: Patching and versions

  1. Patch the CMS, theme and plugins monthly, and within days for critical security releases. Evidence: patch log with dates and versions.
  2. Delete what you do not use. Deactivated plugins still contain code. Remove them rather than leaving them disabled.
  3. Keep the server runtime current. An unsupported PHP version is a security decision made by neglect. Evidence: runtime version and support end date.
  4. Watch for abandoned components. A plugin with no update in two years is a liability. Replace it before it becomes urgent.

Group 4: Configuration and transport

  1. Serve everything over HTTPS and redirect HTTP. Add HSTS once you are confident every subdomain supports it. Evidence: response headers.
  2. Turn off debug output and directory listing in production. Error pages should not reveal file paths or database details.
  3. Restrict the admin area by IP, VPN or an extra authentication layer where practical. It will not stop everything, but it removes background noise.
  4. Set sensible security headers and remove version banners that advertise your stack.

Group 5: Backups and recovery

  1. Back up files and database on a schedule that matches how much data you can afford to lose. Evidence: schedule and last successful run.
  2. Store a copy off the hosting account, with credentials the website cannot delete. This is the single most valuable item on this list.
  3. Test a restore quarterly. A backup that has never been restored is an assumption. Evidence: dated restore test with duration.

Group 6: Monitoring and logging

  1. Monitor uptime and certificate expiry. An expired certificate looks like a security failure to every customer.
  2. Use file-integrity monitoring or a reputable security plugin that alerts on changed core files. Route alerts to a person, not to an inbox nobody reads.
  3. Keep logs long enough to investigate. Web server, authentication and administrative action logs should survive at least the detection window you agreed on.

Group 7: Forms, data and payments

  1. Collect only the fields you need. Every extra field is data you must protect, retain and delete.
  2. Protect forms with rate limiting, spam controls and file-type restrictions on uploads.
  3. Never store card numbers on your server. Use a hosted checkout or tokenisation so the card data stays with the payment provider. Evidence: data-flow diagram showing card data never touching your application.
  4. Publish a privacy notice that matches what you actually collect, and give people a route to ask for correction or deletion.

Group 8: Incident readiness

  1. Write a one-page incident sheet: who to call, how to take the site offline, how to rotate credentials and how to reach the hosting provider. Evidence: offline copy with a review date.
  2. Know how to preserve evidence. Take a snapshot and export logs before cleaning up, or you lose the ability to understand what happened.
  3. Agree who speaks to customers. One named person, with a holding statement prepared in advance.
  4. Review after every incident, including near misses. A short written note beats a long meeting.

Verification calendar

  • Weekly: uptime and backup status, security alerts triaged.
  • Monthly: patches applied, access list reviewed, logs checked for unusual admin activity.
  • Quarterly: restore test, plugin and dependency review, certificate and domain renewal check.
  • Annually: full checklist review with the business owner, plus an external review if you handle payments or personal data at scale.

Common mistakes

  • Believing the hosting provider handles website security. They secure the platform, not your plugins or your passwords.
  • Letting the agency hold every credential with no handover document.
  • Installing a security plugin and assuming it replaces patching, backups and access control.
  • Keeping backups on the same account as the site.
  • Ignoring staging environments and old copies of the site that are still publicly reachable.

Metrics

  • Percentage of administrator accounts with MFA.
  • Days since the last patch, and number of components past end of support.
  • Backup success rate and last verified restore date.
  • Mean time to apply a critical security update.
  • Number of publicly reachable staging or old copies of the site.

Who holds the keys

Many small businesses in Bangladesh hand the domain, hosting and administrator accounts to a web agency and never keep a copy. That is fine while the relationship is healthy. Keep a sealed record of account ownership, recovery email addresses and the person authorised to request changes, and review it when the contract renews.

Where this fits in our work

If you want the checklist turned into a maintained routine, start with Operations & Managed Services; the pricing page explains how ongoing maintenance is scoped. If the site has already been compromised, read the malware cleanup and prevention checklist.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes