Application Security

Web Application Penetration Testing

Assess authentication, authorisation and transaction integrity using controlled validation of the deployed application. Findings establish exposure to account compromise, unauthorised disclosure and manipulation of business transactions.

APP 015 min read9 sections

01 / Overview

Assessment objectives and control obligations

The assessment reconstructs the application’s authorisation model across principals, resources and security-sensitive state transitions. Differential testing compares permitted operations with prohibited cross-role and cross-tenant requests, including exports, asynchronous jobs and endpoints absent from the user interface. Authentication, session invalidation and server-side enforcement are examined as distinct control obligations.

System owners define transaction invariants, approval hierarchies and ownership rules before active validation. Synthetic records support bounded replay and concurrency experiments involving refunds, entitlement changes and approval bypass. Findings establish the causal relationship between a defective enforcement point and demonstrated disclosure, transaction manipulation or operational exposure, with regression criteria attached to the proposed remediation.

02 / Technical analysis

Failure mechanisms and security implications

A restriction may be enforced in one controller but omitted from an export or queued task. OWASP verification requirements help define expected protection; the investigation establishes whether all relevant execution paths apply it. Transaction findings retain the final stored state, since an unusual response alone does not demonstrate financial or data impact.

03 / Scope

Technical coverage and authorisation boundaries

Coverage is agreed in writing before testing begins. The rows below describe what this service normally examines. Exclusions, testing windows and escalation contacts are recorded in the rules of engagement.

Authentication and sessions
Registration, login, MFA, recovery, token renewal and termination, including alternate access routes.
Access control
Object ownership, role permissions, tenant separation and administrative operations using representative accounts.
Input and transaction integrity
Injection, file handling, outbound requests and agreed business rules, with bounded replay and concurrency checks.
Supporting tools
Environment-appropriate instrumentation may include Burp Suite Professional, Caido, ffuf, Nuclei, sqlmap, Playwright. Selection follows the investigative objective, compatibility requirements and approved operating constraints. Automated output requires corroboration against implementation evidence or observed execution before classification as a substantiated finding.

04 / Methodology

Investigation and validation methodology

Threat-informed test design aligns architectural trust boundaries, attacker prerequisites and consequential business outcomes. Automated discovery supports attack-surface coverage; manual validation establishes reachability, effective authority and the causal mechanism of each substantiated control failure.

  1. 01

    Scope and safeguards

    Before active work

    We agree assets, test identities, techniques, windows, exclusions and stop conditions, and confirm required third party permissions.

  2. 02

    Map permissions and workflows

    Establish test identities, record ownership and the expected result of sensitive operations.

  3. 03

    Challenge the enforcement points

    Apply controlled variation to identity, object references, input and request sequence; corroborate the outcome against persisted application state.

  4. 04

    Review and verification

    Agreed delivery

    Findings pass technical review. We explain remediation and, where agreed, verify the correction during the retest window, including relevant bypass cases.

05 / Assessment options

Access models and evidential confidence

Supplied access determines investigative reach, validation depth and evidential confidence. The proposal records the access model, supporting material and unresolved coverage limitations; no model implies unrestricted authority or exhaustive verification.

Black box
Testing starts without supplied credentials or internal design material. External exposure is examined, while authenticated workflows may remain inaccessible.
Grey box
Representative accounts and selected design information support direct comparison of roles, tenants and sensitive workflows.
White box
Source, configuration and design evidence support root cause analysis. Runtime and access limitations are still recorded.

06 / Deliverables

Decision-support and verification deliverables

Deliverables distinguish what was observed, what was concluded and where the evidence stops. The agreed scope states which evidence, review sessions and retesting are included.

Executive summary

The summary explains the demonstrated exposure, the business functions affected and the treatment decisions required, including material uncertainty.

Technical findings

Each confirmed issue records the affected assets, prerequisites, reproduction evidence and a specific remediation. Technical severity is presented separately from business priority.

Coverage and limitations

The record identifies the systems, identities and conditions tested, together with exclusions and assumptions that affect interpretation.

Treatment and retest status

Recommendations are sequenced by risk, dependency and ownership. Any agreed retest records resolved, partly resolved and unresolved issues without implying a new assessment.

Service specific evidence

Role coverage, sanitised requests, tested release and state changes support reproduction and regression checks.

07 / References

Applicable technical references

References are selected for the technology and objective in scope, and the edition applied is recorded. A framework mapping supports review; it is not certification or proof of complete compliance.

OWASP Web Security Testing Guide
The stable testing guide structures application test cases. The engagement records the selected release and applicable cases; the development edition is not silently substituted.
OWASP Application Security Verification Standard
ASVS supplies verifiable application requirements. Requirements are selected for the architecture and assurance objective, with implementation evidence rather than a blanket compliance claim.

08 / Safeguards

Operational safeguards and evidence governance

Active work is conditional on written authority from the appropriate asset owner and approved rules of engagement. The operating plan specifies permitted procedures, testing windows, prohibited actions, third-party restrictions and nominated stop authority. Unexpected instability or suspected genuine compromise triggers suspension of affected activity pending the client’s operational decision.

Evidence governance applies purpose limitation, data minimisation and access proportionality to collection, transfer, processing, retention and disposal. The signed terms define authorised recipients and any external processing arrangement. Publication, secondary use and disclosure of client material require the applicable written permission.

Conclusions distinguish substantiated exposure, untested consequence and residual uncertainty. Each material finding identifies the control obligation, causal mechanism, observed outcome and verification criteria for the proposed treatment. Technical severity informs analysis; prioritisation and acceptance of residual risk remain decisions for the client’s authorised risk owner.

Traffic ceilings and excluded workflows are recorded. Tests do not enumerate customer records to estimate maximum loss.

09 / Suitability

Commissioning criteria

Use before a sensitive release or after changes to authentication, tenancy or transaction handling.

Next step

Define the assessment you need

Tell us the business decision, the systems involved and any operational constraint. We will explain the coverage proposed, the access required and the evidence the engagement can provide.

  • Confidentiality first

    A mutual confidentiality agreement is signed before any technical detail is exchanged, so scope discussions can happen safely.

  • Scope and cost in writing

    Deliverables, access expectations, timeline and fee are confirmed before the engagement begins, and a scope change needs agreement.

  • Answered by the delivery team

    The consultants who scope an engagement are the consultants who perform it and explain the result to your team.

We value your privacy

We use essential cookies to keep the site working and analytics cookies to understand how you use it, so we can improve. We do not sell your data. See our Privacy Policy for details.