WEB — Penetration testing
Web Application Penetration Testing
Automated scanners find the obvious. The findings that matter — broken access control, flawed workflows, chained weaknesses — come from a tester who understands how your application is meant to work and deliberately makes it misbehave.
Who it's for
Built for teams that ship.
01
SaaS & product teams
Shipping features quickly and needing independent assurance before major releases.
02
Customer security reviews
Organisations asked by enterprise customers for a recent third-party penetration test.
03
Regulated and data-heavy platforms
Applications processing personal, financial or health data where access control failures are costly.
What we test
Coverage, defined up front.
OWASP-aligned manual assessments of web applications and their APIs — authentication, authorisation, business logic and injection classes, validated by hand.
Authentication & sessions
- Login, MFA and password-reset flows
- Session lifecycle, fixation and invalidation
- Token handling (JWT, OAuth/OIDC flows)
- Account enumeration and brute-force controls
Authorisation & access control
- Horizontal and vertical privilege escalation
- Insecure direct object references (IDOR)
- Multi-tenant isolation
- Role and permission model enforcement
Input handling & injection
- SQL, NoSQL and command injection
- Cross-site scripting (reflected, stored, DOM)
- Server-side request forgery (SSRF)
- Template injection and deserialisation
APIs & business logic
- REST and GraphQL API testing
- Mass assignment and excessive data exposure
- Workflow and state-machine abuse
- Rate limiting and abuse resistance
Common risks
What typically goes wrong.
Broken access control
Users reaching data or actions that belong to other users, tenants or roles.
Logic flaws
Legitimate features combined in unintended ways — skipped steps, replayed requests, manipulated prices or states.
Injection
Untrusted input interpreted as code or queries, leading to data exposure or server compromise.
Session weaknesses
Tokens that leak, never expire or survive logout, enabling account takeover.
Methodology
How the testing works.
- STEP 01
Map
Crawl and manually explore the application, its roles, APIs and trust boundaries.
- STEP 02
Model
Identify where authorisation and business rules are enforced — and where they are assumed.
- STEP 03
Test
Systematic manual testing against OWASP guidance, supported by tooling such as Burp Suite.
- STEP 04
Validate
Every reported issue is reproduced and its real impact demonstrated safely.
What you receive
Deliverables
Executive summary
Scope, overall risk posture and the priorities leadership needs to act on — in plain language.
Technical findings
Each issue with affected components, description, evidence and severity reasoning.
Risk prioritisation
Severity and likelihood in the context of your business, so fixes are ordered by real risk.
Reproduction evidence
Requests, responses, screenshots and step-by-step reproduction for your engineers.
Impact explanations
What an attacker could realistically achieve with each finding in your environment.
Remediation guidance
Specific fixes that address root causes, not just symptoms.
Retesting
Verification that fixes work, with an updated report — when included in scope.
CONFIDENTIALITY
Reports are delivered through an agreed secure channel. Client findings are never published or reused.
Engagement process
What to expect, step by step.
- 01
Scoping call
We clarify objectives, targets, environments, constraints and any compliance or customer-review drivers.
- 02
Proposal & authorisation
You receive a written scope, timeline and rules of engagement. Testing starts only after written authorisation.
- 03
Testing window
Manual testing within the agreed window, with a named point of contact and immediate escalation of critical issues.
- 04
Reporting
A structured report with executive and technical layers, delivered through an agreed secure channel.
- 05
Debrief
A walkthrough of findings with your engineering team, focused on root causes and remediation order.
- 06
Retest
Where included, fixed findings are verified and the report is updated to reflect remediation status.
FAQ
Questions buyers ask.
Either, as agreed in scope. Staging environments that mirror production are preferred; production testing is performed with agreed safeguards and timing.
No. Tooling supports the work, but findings are discovered and validated manually by an experienced tester.
Yes. Provide documentation (OpenAPI, GraphQL schema or a Postman collection) and test accounts for each role.
It depends on the size and complexity of the application. We propose a duration after the scoping call rather than quoting a generic number.
Next step
Get a penetration testing proposal.
Tell us what you need tested. We'll arrange a scoping call and come back with a written proposal — scope, approach, timeline and rules of engagement.