Cyber security · 01
Web application testing that finds what scanners miss.
Customer portals, SaaS platforms, admin panels and e-commerce sites, tested by hand against the OWASP Top 10 and the business logic only your application has.
Overview
The worst bugs are rarely in the scanner report. They are in how your app trusts its users.
We log in as each of your user roles and try to do what that role should not: read another customer's data, approve our own refund, skip a payment step, promote ourselves to admin.
Alongside that we work through the OWASP Top 10: injection, broken authentication, misconfiguration, vulnerable components. Every finding comes with the request that proves it.
Standards & frameworks
- OWASP Top 10
- OWASP WSTG
- OWASP ASVS
- CREST-aligned
- CVSS 3.1
- PCI DSS 11.4
What we test
What's in scope.
And what we look for.
01 · Access
Who can do what. Most serious findings come down to access control.
Authentication
Login, password reset, MFA, SSO and session handling, including token reuse and fixation.
Authorisation
Horizontal and vertical privilege escalation, IDOR and missing ownership checks.
Multi-tenancy
Whether one customer can ever see or change another customer's data.
Admin surfaces
Exposed back offices, debug routes and forgotten internal tools.
02 · Input
What the app accepts. Classic vulnerabilities still turn up in modern frameworks.
Injection
SQL, NoSQL, command and template injection, including second-order cases.
Cross-site scripting
Stored, reflected and DOM-based XSS, and how far each one could go.
File handling
Uploads, path traversal, unsafe parsing and server-side request forgery.
Client-side
Content Security Policy, CORS, cookies and third-party scripts.
03 · Logic
How the business works. Flaws a scanner cannot understand.
Payments and pricing
Discount abuse, negative quantities, race conditions and skipped payment steps.
Workflows
Approvals, onboarding and state changes done out of order.
Rate limits
Brute force, enumeration and abuse of expensive operations.
Data exposure
Over-sharing APIs behind the front end, verbose errors and leaked secrets.
Process
How a test runs, start to finish.
- 1
Scope
Applications, environments and user roles agreed, with test accounts for each role.
- 2
Map
We crawl the app and its API to understand every route, role and workflow.
- 3
Attack
Manual testing per role and per workflow, supported by tooling, with impact proven safely.
- 4
Report & retest
Findings with evidence and fixes for your framework, then a retest once remediated.
Deliverables
What ships with
every test.
One report for two audiences: leadership gets the risk, engineers get the evidence and the fix. Here is how that compares with an automated scan.
Read the sample report →“They managed to find a very serious vulnerability in our platform and walked us through fixing it. We will surely use their services!”
Yes, that is where most of the risk is. We ask for test accounts for every user role so we can check what each one can and cannot reach.
Either. Staging with production-like data and configuration is usually best. If we test production, we agree windows and avoid anything destructive.
Yes. Our developers work in Laravel, React, Node.js and other common stacks, so we can raise fixes ourselves or pair with your team, then retest.
Typically 5 to 10 days depending on the number of roles, workflows and integrations. You get a fixed quote and timeline after scoping.
Scope your web application testing.
Get a fixed quote.
A developer or security engineer reads every enquiry and replies, not a salesperson.
- Fixed quote after a short scoping call
- NDA available before you share details
- Remediation and retest on every security engagement