A website security audit for small businesses, in plain English
What the audit looks at
Every audit starts from the outside, the same view an attacker or a curious visitor has, and moves inwards only as far as you allow.
- The outside view: your SSL certificate and TLS set-up, the HTTPS redirect, security headers, cookie settings, version disclosure and mixed content. This is the same ground as our free website security check, reviewed by a person.
- Your email domain: SPF, DMARC and DKIM, because email spoofing in your name is one of the most common problems small businesses actually feel.
- An authorised scan: with proof that you own the site and a signed authorisation to test, a non-destructive vulnerability scan that looks for known, published flaws in what your site runs.
- The admin side, if you give access: WordPress or CMS version, plugins and themes, user accounts, two-factor authentication and backups.
What you get at the end
- 01
A plain-English report
Each finding explained twice: the technical detail for your developer, and what it means for your business. See a sample website security report.
- 02
A priority order
What to fix this week, what can wait, and what is fine to leave. Not every finding is worth money.
- 03
A fixed price per fix
If you want us to do the work, each item has a quoted price. Nothing starts until you say yes. See website security fixes.
- 04
A record of what was checked
Dates, scope and results, which is useful when a customer, insurer or partner asks how you look after your website.
Audit, vulnerability scan or penetration test?
These words get mixed up, so here is how we use them. A vulnerability scan is automated and looks for known weaknesses. An audit combines scans and manual review of settings and practices, and ends in a prioritised list. A penetration test goes further: a specialist actively tries to break in, within agreed rules.
For most small business websites, an audit is the sensible first step. If your site handles payments directly, stores sensitive records, or a contract requires it, a penetration test by a specialist firm may be the right next step, and we'll tell you honestly if we think you need one.
What an audit can't promise
We never scan a site without proof of ownership and written permission, we never try to exploit what we find, and we don't use findings for anything other than your report.
Common questions
How much does a website security audit cost?
It depends on the size of the site and how deep you want to go, so we quote a fixed price before starting. The outside check is free; you can run it yourself right now.
Do you need my passwords?
Not for the outside check or the authorised scan. For the admin review we'll ask for a separate, temporary account that you can delete afterwards, never your own login.
Will the audit slow down or break my site?
The scans we use are non-destructive and run at a gentle pace. We agree a time window with you first, and we don't attempt to exploit anything.
How long does an audit take?
For a typical small business site, a few working days from signed authorisation to report. We'll give you a date when we quote.
Can you audit a site we built for a client?
Yes, with the site owner's written authorisation. Agencies can also have the report carry their brand. See white-label website security.
// related
// terms on this page
Want an audit of your site?
Tell us your website and what worries you. We'll reply within one business day with what an audit would cover and a fixed price.