Security audit
from £249
A close read of your code for the weaknesses attackers look for. We work from the code and its configuration. We never attack your live site.
Choose a tier- 1.1
Known vulnerabilities in what you depend on
Every library, plugin, theme and package your site pulls in, checked against the public vulnerability records (CVEs) and each ecosystem's security advisories. An old plugin with a published flaw is one of the commonest ways into a small business website.
- 1.2
Passwords and keys in the code
Database passwords, API keys, payment keys and tokens written into files or left in the repository's history. Anyone with a copy of the code has them too, and deleting the file does not remove them from the history.
- 1.3
Injection
Places where what a visitor types is built straight into a database query, a file path or a server command. That is how a search box or a login form ends up handing over the database.
- 1.4
Cross-site scripting
Text a visitor sends that is shown back on a page without being made safe. It lets someone run their own script in other visitors' browsers: a fake login box, or a stolen session.
- 1.5
Logins and sessions
How passwords are stored, how sessions start and end, how password reset works, whether repeated login attempts are slowed down, and whether two-factor sign-in is available where it matters.
- 1.6
Who can reach what
Whether every admin page, API route and file actually checks who is asking, rather than relying on nobody finding the link. That includes database rules, such as Supabase or Firebase security rules, wherever the browser talks to the database directly.
- 1.7
Forms and uploads
Uploads that accept any type of file or store them where they could be run, forms that can be submitted from another site (CSRF), and forms with no protection against spam.
- 1.8
HTTPS and security headers
A valid certificate with every address redirected to HTTPS, and the headers that tell browsers how to protect your visitors: HSTS, a content security policy, and protection against framing and content sniffing.
- 1.9
Out-of-date platform software
Your CMS, PHP or Node version and frameworks, checked for releases that have reached end of life and no longer get security fixes.
- 1.10
Leaks and exposed files
Debug modes left on, error pages that print the code's internals, and server configuration that would let the web reach backups, .env files or the .git folder.