Sample alert How it works Coverage PENTEST METHODOLOGY DOCS PRICING FAQ MCP CONTACT LOG IN SCAN MY APP →

Web Application Security Checklist for Small Businesses

CHECKLIST / SMALL BUSINESS

A small business can cover most web security risk with a short list of checks: know who owns each part of the site, put multi-factor authentication on every admin account, keep tested backups, and own your domain. You do not need to write code. You need to ask the right questions and keep the answers in writing.

This checklist is for owners and managers of a business website, an online shop, or a customer portal. The site may be built by an agency, a freelancer, or a software vendor. Mark each item when you have proof that it is done. “My developer said it is fine” is not proof. A screenshot, a document, or a test result is proof.

Who owns which fix?

Many sites have security gaps because each person thinks that another person owns the fix. Use this table to find the owner of each area. Then write the name next to it. If the owner is “nobody”, that is the first problem to solve.

Area Usually the business owner Usually the developer or agency Usually the vendor
Domain name registration Owns the account Can have access if you grant it Not applicable
Admin accounts and MFA Decides who gets access Creates and removes accounts Provides the MFA feature
Software updates (core, plugins, themes) Pays for and approves Does the update, if the contract says so Updates the hosted product
Backups Asks for proof and test restore Makes the backups, if the contract says so Makes backups of hosted data, with limits
Hosting account Owns the account Manages the server, if agreed Manages the server for hosted products
Payment and customer data Is responsible in law Builds the checkout safely Processes the card data
Incident response Decides and tells customers Finds the cause and fixes it Tells you about problems in their product
Ending the contract Must get all access and files Must hand over all access and files Must allow export of your data

The business owner is the one who answers to customers and regulators. You can give the work to others. You cannot give away the responsibility.

Are your accounts and admin access under control?

Most break-ins start with a stolen or weak password. An attacker who gets one admin account can change the site, steal customer data, or add hidden code.

  • Make a list of every person who can sign in as an admin to the website, the hosting, the domain, and your email.
  • Remove accounts for people who left, and for developers who finished a project.
  • Give each person their own account. Do not share one login.
  • Turn on multi-factor authentication (MFA) for each admin account. Use an authenticator app or a hardware key if the service supports it.
  • Turn on MFA for the email account that receives password reset messages. This account can reset all others.
  • Give most users the lowest role that they need. A person who writes blog posts does not need to install plugins.

For a short guide on MFA, read the CISA multi-factor authentication page.

Do you own your domain and DNS?

Your domain name is your address. If someone else owns it, they can take your site offline or send your visitors elsewhere. This happens when a freelancer registers the domain in their own name.

  • Find your domain registrar account. Make sure the account is in your business name and uses your business email.
  • Make sure you are the registrant and that the contact email is yours.
  • Turn on the registrar lock, so that nobody can move the domain without you.
  • Ask who controls the DNS records, which tell the world where your site and email live. Get an export of these records.
  • Ask your developer to list all subdomains, such as shop.yourbusiness.com. Remove any that you no longer use.

An old subdomain that points to a closed service can be taken over by another person. See how to discover forgotten web apps for the technical background to give your developer.

Are your backups real?

A backup that was never restored is a hope, not a backup. If a hacker or a bad update destroys the site, the backup is your way back.

  • Ask where backups are stored. They must be in a place other than the web server itself.
  • Ask how often they run, and how long the provider keeps them.
  • Ask who can delete them. One compromised admin account must not be able to delete all backups.
  • Ask for a test restore in a safe copy of the site. Ask for the date of the last successful test.
  • Make sure no backup file sits in a public folder of the website. Old .zip and .sql files in the web folder can be downloaded by anyone. See wp-config backup or SQL dump is downloadable.

Is the WordPress site and its plugin set under control?

Skip this section if your site does not use WordPress or a similar content system. If it does, plugins and themes are the main source of risk. Each plugin is code from a third party that runs with the power of your site.

  • Ask for a list of all plugins and themes, with the version of each.
  • Remove plugins and themes that you do not use. A switched-off plugin can still hold a flaw.
  • Ask who updates the core software, the plugins, and the themes, and how often.
  • Make sure each plugin is still maintained. Look at the last update date on the plugin page.
  • Ask whether any plugin or code was written with an AI tool, and who reviewed it. See AI-written WordPress plugin: security holes.
  • Ask your developer to check that the user list is not public. See WordPress users endpoint leaks usernames.
  • If visitors are sent to spam pages, act at once. See WordPress site redirects to spam.
  • If you let an AI agent manage the site through a connector, ask what the agent can change. See WordPress MCP adapter access.

The WordPress project has its own hardening guide for your developer.

Which vendors and SaaS tools hold your data?

Your site probably uses tools that you do not run: a payment provider, a booking tool, an email service, a chat widget, or an online form tool. The vendor secures its own system. You must secure how you use it.

  • Make a list of each outside tool that connects to your site or holds customer data.
  • For each tool, write the name of the person who owns the account.
  • Turn on MFA in each vendor account.
  • Find the vendor’s security or trust page. Check if it states where the data is stored and how you can export it.

What must a contract and a handover include?

Most disputes start because the contract is silent. Add these items to every agreement with an agency or a freelancer. Add them also when you renew.

  • The business, not the developer, owns the domain, the hosting account, and all code.
  • The contract states who does software updates, and how often.
  • The contract states who makes backups, where they are stored, and who tests a restore.
  • The contract names who responds to a security incident, and how fast.
  • The developer must use their own named account, not a shared login, and must use MFA.
  • At the end of the work, the developer must give you a list of all accounts, keys, and services used.
  • At the end of the work, the developer must remove their own access, and you must change the shared passwords.

At handover, ask for a one-page document that lists: the domain registrar, the hosting provider, the DNS provider, the website platform and its version, all plugins, all vendor tools, and the name of each account owner. Keep it in a safe place. Update it each year.

What should you ask your developer?

You do not need to understand the answers in detail. You need to see if the developer can answer at all. A vague or slow answer is a warning.

  1. Who can sign in as an admin today, and do they all use MFA?
  2. When was the last software update, and who did it?
  3. Where are the backups, and when did you last restore one?
  4. Does the site hold customer data? Where is it stored, and who can read it?
  5. Can one customer see the data of another customer? How did you test that?
  6. Did you use AI tools to write any part of the site? Who reviewed that code?
  7. Are there test, staging, or old versions of the site that are still online?
  8. Do keys or passwords appear in the code or in public files?
  9. What is the plan if the site is hacked tonight?

Write the answers down with the date.

How can you do a basic check yourself in 15 minutes?

These steps need no technical skill. They find only the simplest problems, but those problems are common.

  1. Open your site in a private browser window. Make sure the address starts with https:// and that the browser shows no warning.
  2. Type http:// and your domain, without the “s”. Make sure the browser moves you to the secure version.
  3. Open the admin sign-in page of your site. Make sure it asks for a second factor after the password.
  4. Sign out. Press the browser Back button. Make sure you cannot see admin pages again.
  5. Check your domain with a public security headers tool, such as the VibeEval security headers checker. Send the result to your developer.

For a free scan of the site from outside, see the free security self-audit. Only test sites that you own, or that you have written permission to test.

When should you pay for a penetration test?

A penetration test is a paid test by a person who tries to break into your site, as an attacker would. It costs more than an automated scan. It is worth the cost in some cases and not in others.

Your situation Automated scan Human pentest
Brochure site with no accounts or forms Enough, with the checklist above Not needed
Site with a contact form and a mailing list Enough, run each quarter Not needed at first
Online shop with a hosted payment page Run after each large change Consider once a year
Customer portal, booking system, or member area Run on a schedule Do one before launch and after major changes
Site with health, legal, or financial data Run on a schedule Required by most customers and insurers
A customer, an insurer, or a regulator asks for a report Helpful as a first step Do it, and ask what scope they need

Do the basic checks first. A pentest on a site with open admin accounts and no backups finds basic problems at a high price. For the difference between the two kinds of test, read vulnerability scanning vs AI pentest. For a view of the whole process, read the penetration testing guide.

For many sites, see multi-site security monitoring.

What should you do each year?

Do the full checklist once a year. Check the admin list, the plugin list, and the last backup each quarter. Run a scan after each large change. For checks between these dates, see security monitoring. The FTC guide for small businesses and the UK NCSC small business guide cover other parts of business security.

How does VibeEval help a small business?

VibeEval tests a live website from the outside. It reports each finding with the request and the response that proved it, a severity level, and fix steps that you can give to your developer. You can re-run a scan after a fix to confirm the result. Add only sites that you own or have written permission to test. VibeEval does not replace the contract and account checks in this list. It shows if the live site has open problems.

Common questions

What is the most important item on a small business security checklist?
Put multi-factor authentication on every account that can change your website, your domain, or your hosting. A stolen password then cannot open the account alone. Start with the email account, because it can reset all other passwords.
Who is responsible for the security of a website that an agency built?
It depends on the contract. If the contract does not say who updates the software, who keeps backups, and who answers an incident, nobody is clearly responsible. Ask for these three points in writing.
Do I need a penetration test for a small website?
Usually not at first. A brochure site with no customer accounts needs the basic checks in this list. Consider a pentest when the site holds customer data, takes payments, or when a customer or insurer asks for one.
How often must I check my website security?
Do the full checklist once a year. Check backups and admin accounts every three months. Run a test after each large change to the site, such as a new plugin, a new payment tool, or a new developer.
Are WordPress sites unsafe?
No. WordPress is a common target because many sites use it. Most problems come from old plugins, weak admin passwords, and missing updates. A well-kept WordPress site can be safe.

Check your live website

Give VibeEval the address of a site you own. It tests the live site and shows each finding with the evidence and the fix steps.

14-day free trial · Cancel anytime

START FREE SCAN →