Security testing for websites and apps
Most break-ins use ordinary mistakes: a page that forgets to check who is asking, a reset link that never expires, an API that returns more than the screen shows. We look for those in your product before someone else does.
Pay as you go: you pay for each finding, at a rate agreed before we start.
What we check for security
Access control
One user cannot read or change another user's data, and normal users cannot reach admin pages or actions.
Sign-in and sessions
Limits on password guesses, reset links that expire, and sessions that end when the user signs out.
Input handling
Fields, search boxes and uploads tested for SQL injection, cross-site scripting and unsafe file types.
Exposed data
What API responses, error pages, page source and logs reveal beyond what the screen shows.
Configuration
HTTPS everywhere, security headers, default passwords, test pages and admin tools left on the live site.
Mobile apps
What the app stores on the phone, secret keys built into the app, and how it checks the server it talks to.
How the work runs
We agree the scope in writing
Which sites, apps and accounts are in scope, when testing may run, and what is off limits. We only test systems you own or have written permission to test.
We test
By hand and with tools, as a signed-out visitor, a normal user and an admin, looking for ways to reach what each should not.
You get the report
Each finding with its severity, the exact steps to repeat it, what an attacker could do with it, and how to fix it.
We re-test your fixes
Once your developers have fixed an issue, we check that it is closed and has not opened another.
Questions about this service
How is security testing priced?
It is pay as you go. You pay for each bug or improvement we find, at a rate set by its severity. We agree the rates with you before any testing starts.
Is this the same as a penetration test?
It covers the same common weaknesses, tested by hand and with tools against your application. If you need a formal penetration test report for a regulator, a certification or a customer contract, tell us first so we can agree whether this scope meets that requirement.
Could testing harm our live site or data?
We prefer a test environment. On a live site we avoid anything that could damage data or slow the service, and we agree the timing and limits with you in writing before we start.
Tell us what to test
Send a link and what worries you most. We reply with what we would look at first.
Start a project