Service · Web App · SVC-02

Web Application Security Testing.

OWASP-aligned testing of business logic, authentication flows, authorization boundaries and API surfaces - manual depth where it counts.

1–3 weeks Fixed quote Manual-first methodology
ASVS L2
Default coverage tier
18+
OWASP test categories
10 days
Typical delivery
Methodology

Three approaches. One uncompromising standard.

Choose the depth of engagement that matches your risk profile and reporting needs.

ASVS L1

ASVS Level 1

Opportunistic-attack defence for public-facing apps. Suitable for low-risk applications or as a fast-turnaround pre-launch assurance step.

  • Authentication & session hygiene
  • Input validation & injection coverage
  • Common misconfigurations
  • Transport security & headers
ASVS L2

ASVS Level 2

The default coverage tier for production applications handling sensitive data. Adds business-logic depth and authorisation testing on top of L1.

  • L1 coverage in full
  • Authorisation & RBAC boundary testing
  • Business-logic flaw discovery
  • API security - REST & GraphQL
  • Authenticated & unauthenticated testing
ASVS L3

ASVS Level 3

Designed for systems holding regulated data or operating critical infrastructure. Includes source-aware review and threat-modelling deliverables.

  • L1 + L2 coverage
  • Source-aware code review
  • Threat-modelling workshop
  • Cryptographic implementation review
  • Supply-chain & dependency audit
What we cover

The full surface - tested manually.

01Authentication & session management
02Authorization & access control (IDOR, RBAC)
03Injection & deserialization
04Business-logic flaws
05API security (REST & GraphQL)
06Client-side & CSP review
Engagement variants

Four ways to scope this service.

External

External Web Application Test

Black-box assessment of your public-facing applications - think anonymous attacker on the internet.

  • Unauthenticated attack surface
  • Login & signup flow attacks
  • Public API security review
Authenticated

Authenticated Application Test

In-app testing across the roles your customers, staff and admins use.

  • Role-based access control
  • Multi-tenant isolation
  • Privilege-escalation paths
API

API Security Test (REST / GraphQL)

Deep testing of the API surface - the most common breach vector in modern web apps.

  • REST & GraphQL coverage
  • Rate-limit & quota bypass
  • Schema introspection & abuse
SPA

SPA / Client-side Audit

Frontend-specific review for single-page applications - CSP, XSS, postMessage, storage hygiene.

  • CSP & header audit
  • Client-side storage review
  • Dependency & bundle review
The process

Six clearly-defined phases.

From scoping call to remediated environment - each step has a deliverable, a check-in and a documented owner.

01
Define Scope

Goals, asset inventory, RoE and success criteria.

02
Information Gathering

Recon, fingerprinting and threat modelling.

03
Identification

Vulnerability discovery and validation.

04
Attack & Penetration

Manual exploitation & chain analysis.

05
Reporting

Executive & technical deliverables.

06
Remediation Support

Fix guidance & debrief session.

Why it matters

Outcomes you can measure.

Standards alignment

OWASP ASVS & WSTG with full traceability.

Business-logic depth

Findings tools cannot catch.

Code-level fixes

Developer-ready remediation guidance.

Threat-model led

Tests guided by how attackers actually target apps.

What you receive

Deliverables.

Executive summary

Board-ready overview - risk posture, business impact, recommended priorities.

Technical report

Every finding with reproduction steps, evidence, CVSS & business-impact scores.

Remediation tracker

Jira / Linear-ready issue list with severity, owner and acceptance criteria.

Frequently asked

About web application security.

What about single-page apps and APIs?
Both are first-class. We test the rendered SPA, the backing REST/GraphQL APIs and the integration boundary between them as a single attack surface.
Do you need source code?
No. We default to gray-box (authenticated, no source). White-box with source improves coverage; we will scope it if you prefer.
Will testing affect production data?
We test in staging where possible. When production is in scope, destructive payloads are excluded and a kill-switch protocol applies.
How often should we test?
Annually as a minimum. After any architectural change - a new authentication flow, major refactor, or migration - we recommend a focused re-test.
Do you cover mobile and desktop variants?
Mobile is a separate service (see Mobile App Pen-Test). Desktop / Electron apps can be folded into a web app engagement.
SVC-02

Let's scope your web application security.

A 30-minute call. A fixed quote within two business days.