Illustrative Sample: Fictional Data

Web Application VAPT: Sample Report

An illustrative excerpt showing how Virtual Caim structures and writes its VAPT reports. Every number, finding and system in this document is fictional. Real reports are confidential and client-specific.

1. Executive summary

In this fictional engagement, the assessment identified 9 findings — 1 critical, 3 high, 3 medium and 2 low — plus 3 informational observations across the customer web portal and its APIs. The critical finding (F-01) allows account takeover through a predictable password-reset token; the report recommends holding the release until it is closed and the high findings carry a dated fix plan. Each finding carries a proof of concept, a CVSS v3.1 score, business impact in plain language, and a specific fix.

2. Scoping at a glance

What this sample engagement actually took — published so you can compare like for like when you evaluate quotes.

DimensionThis sample engagement
Team5 people — 1 lead auditor, 3 security testers, 1 independent reviewer
Effort36 person-days across five phases, kick-off to reporting
Window14 September to 21 October 2026, with interim notification of critical and high findings during testing
Output9 findings + 3 informational observations, each with PoC, CVSS v3.1 vector and a specific fix
Re-testIncluded — targeted re-test of each fixed finding, typically within 5 working days of the request

All names, systems and figures in the sample are fictional; the scoping dimensions are how we actually staff and run an engagement of this size.

3. Severity breakdown

SeverityCountCVSS in this sample
Critical19.1
High37.1–7.6
Medium35.3–6.1
Low23.1–3.7
Informational3—

4. Sample finding

F-02: Broken object-level authorisation on the loan statement API (High, CVSS 7.1)
An authenticated customer can read another customer's loan statements by changing the object identifier in an API request (CWE-639). No server-side ownership check is performed.

FieldDetail
ImpactOne customer can read another customer's loan data — the kind of flaw that attracts regulator attention and customer complaints
ReproductionAuthenticate as user A, then request /api/records?id= with a record ID belonging to user B
RemediationEnforce server-side, per-object authorisation checks; deny by default
StatusOpen at report issue; re-test of each fixed finding, typically within 5 working days of the request, is included

5. What a full report contains

  • Scope, methodology (OWASP, NIST, PTES) and testing window
  • Every finding with PoC evidence, CVSS score and remediation guidance
  • Risk-ranked remediation plan for engineering teams
  • Executive summary written for leadership, not just engineers
  • Free revalidation and a closure certificate once fixes are confirmed

This document is an illustrative sample with fictional data. Real reports are confidential and client-specific. Request a walkthrough at audit<at>virtualcaim.com.