Vulnerability Assessment · Service
Web application security assessment.
We test your web application the way a determined outsider or a curious logged-in user would, within a scope you sign, and tell you plainly what we found and how to fix it.
Overview
What this covers
Most serious incidents involving a business start in a web application: a customer portal, an admin panel, a booking system or a SaaS product. These applications hold data, accept input from anyone on the internet and make decisions about who is allowed to do what. Each of those is a place where a small mistake in code or configuration can expose far more than intended.
Our web application assessment combines automated scanning, which is good at finding known patterns quickly, with manual testing, which is needed for the issues scanners cannot reason about. A scanner will not notice that one customer can view another customer's invoice by changing a number, or that a discount can be applied twice. A person working through the application will.
We use the OWASP Web Security Testing Guide as our reference method and the OWASP Top 10 as a checklist of the most common risk categories. The result is a report your developers can act on directly: each finding explained, rated, evidenced and paired with specific guidance for fixing it.
Deliverables
What you get
Written scope and authorisation
A signed document naming the application, environments, user roles, testing windows and anything that is off limits.
Findings report
An executive summary for leadership and a technical section listing every finding with its severity, evidence and steps to reproduce.
Fix guidance per finding
Specific remediation advice for each issue, written for the developers who will make the change, with references to the relevant OWASP guidance.
Walkthrough call
A session with your team to go through the findings, answer questions and agree an order for fixing them.
Retest and confirmation
Once you have fixed the agreed issues, we retest them and confirm in writing which are closed.
Approach
How we run it
- 01
Agree the scope
We confirm which application, which environment, which user roles we test as, and when testing can take place.
- 02
Map the application
We work through the application to understand its pages, functions, user roles and the data it handles.
- 03
Test
Automated scanning runs alongside manual testing of access control, input handling, sessions and business logic.
- 04
Report and walk through
Findings are written up, rated and explained to your team on a call.
- 05
Retest
We check the fixes you make and confirm the result in writing.
Questions
Before you ask.
Do you test our live site or a staging copy?
A staging environment that mirrors production is usually the better choice, because it lets us test more thoroughly without affecting customers. If testing must happen on production, we agree limits and windows in the scope and avoid destructive techniques.
Do you need our source code?
No. Most assessments are carried out from the outside, as a user would see the application. If you want us to look at specific code alongside the testing, we can agree that in the scope.
What user accounts do you need?
Usually one test account for each role you want tested, for example a standard customer and an administrator. Having two accounts in the same role lets us check whether one user can see another user's data.
How long does it take and what does it cost?
Both depend on the size of the application and the number of roles involved. We agree the timeline and price in the scope and quote before any work starts.
Related
Often paired with
Talk to us about web applications
Tell us what you want tested. We will reply with a proposed scope, the authorisation we need, and a quote.
