Skip to content
KnockSec Academy

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.

  1. STEP 01

    Map

    Crawl and manually explore the application, its roles, APIs and trust boundaries.

  2. STEP 02

    Model

    Identify where authorisation and business rules are enforced — and where they are assumed.

  3. STEP 03

    Test

    Systematic manual testing against OWASP guidance, supported by tooling such as Burp Suite.

  4. 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.

  1. 01

    Scoping call

    We clarify objectives, targets, environments, constraints and any compliance or customer-review drivers.

  2. 02

    Proposal & authorisation

    You receive a written scope, timeline and rules of engagement. Testing starts only after written authorisation.

  3. 03

    Testing window

    Manual testing within the agreed window, with a named point of contact and immediate escalation of critical issues.

  4. 04

    Reporting

    A structured report with executive and technical layers, delivered through an agreed secure channel.

  5. 05

    Debrief

    A walkthrough of findings with your engineering team, focused on root causes and remediation order.

  6. 06

    Retest

    Where included, fixed findings are verified and the report is updated to reflect remediation status.

FAQ

Questions buyers ask.

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.