Security review
Authentication, authorisation, input handling, file uploads, dependencies, headers and transport, checked against the OWASP Top 10.
What we do
Patched, monitored and backed up, every month
Security reviews, hardening and an ongoing maintenance retainer, so dependencies stay patched, access stays controlled and problems are found before they are incidents.
The short version
Websites are rarely attacked for interesting reasons. They are attacked by automated scanners looking for an unpatched plugin, a default admin account or a form that never validated its input. The defence is not dramatic either: it is patching, least privilege, input validation and backups you have tested.
We do the review that finds the gaps, close them in priority order, and then keep things current month by month. You get a written report you can show a client or a board, not a vague assurance that everything is fine.
Scope
Every item below is in the written scope before work starts, so nothing on this list is an upsell later.
Authentication, authorisation, input handling, file uploads, dependencies, headers and transport, checked against the OWASP Top 10.
Each issue with its real impact, how to reproduce it and the fix, ordered by risk rather than by how alarming it sounds.
Security headers, rate limiting, session rules, secret rotation and least-privilege access applied without breaking the site.
Monthly updates to framework, library and server packages, tested on staging before they reach production.
Off-site backups with a restore actually performed, and a documented recovery time you can quote.
Uptime, error and certificate alerts, with an agreed response time and a plan for who does what.
How it runs
Five stages, each with something you can see or review at the end of it.
Written agreement on what is in scope and when testing happens, before anything is touched.
Automated scanning plus manual review, delivered as a prioritised report with reproduction steps.
Critical issues first, each change tested on staging so the fix does not break the feature.
Re-test every finding and confirm in writing that it is closed.
A monthly maintenance cycle of patches, backup checks and a short status report.
Questions
If your question is not here, ask it directly. We answer the awkward ones too.
Dependency and server patching, backup verification, uptime and error monitoring, small content or layout fixes, and a short monthly report. Larger feature work is quoted separately so your retainer is not quietly consumed by new development.
We perform application security reviews and authorised testing against systems you own, with written scope and permission first. For a formal third-party penetration test with a certified report, we help you scope it and fix what it finds.
Yes. The sequence is contain, clean, patch, then harden: take the site off the attack surface, remove the injected code, close the hole that let it in, rotate every credential, and only then restore normal service. We also tell you honestly what we cannot determine about what was accessed.
We handle the technical side: what you collect, where it is stored, who can reach it, how long it is kept, and how a deletion request is honoured. For legal interpretation you need a lawyer, and we will say so rather than improvise.
Also relevant
Cloud infrastructure, CI/CD, monitoring and backups set up so deployments are routine, costs are predictable and recovery is tested rather than hoped for.
Read moreSchema design, query optimisation, migrations and reporting pipelines, so your data stays correct, fast and usable past the first ten thousand rows.
Read moreSend us the situation as it is, including the parts that are messy. We will tell you what we would do first and what it would cost.