
Key takeaway
A VAPT report is an audit artefact. Its value depends on whether a board member can understand the risk, a developer can fix the finding, and a regulator can accept the evidence — all from the same document.
What a VAPT report is (and is not)
A VAPT report is not a vulnerability scanner printout. Automated tools produce raw lists of potential weaknesses at a specific point in time. A VAPT report adds the work a human analyst does: validating each finding by attempting to exploit it, removing false positives, chaining lower-severity issues into real attack paths, scoring each finding against business impact, and writing actionable remediation guidance a developer can implement.
The difference matters for two reasons. Practically, a report with unexploited scan output leaves developers guessing which findings to fix first. For compliance, regulators and auditors in India — including the RBI, SEBI and IRDAI — are increasingly specific about what constitutes evidence of adequate testing. A scan dump rarely satisfies that standard.
Section 1: Executive summary
The executive summary is written for a board member or senior decision-maker with no security background. A good one answers four questions without technical jargon.
- What was tested and over what period
- What is the overall risk posture — critical, high, medium or low — with a one-sentence plain-English rationale
- How many findings were discovered, and how many are remediated
- What the single highest-priority action is
Section 2: Methodology and scope
This section establishes what was tested and how. Without it, the report is not reproducible and an auditor cannot assess its adequacy.
- Testing framework (OWASP WSTG for web, MASVS for mobile, PTES or NIST 800-115 for infrastructure)
- Scope: applications, IP ranges, environments (production, staging, cloud accounts)
- Testing type: black-box, grey-box or white-box, with rationale
- Testing window: start and end dates
- Tester credentials and access provided
Section 3: Technical findings
Each finding is a self-contained evidence unit. A finding that cannot stand alone — that relies on verbal explanation or a follow-up email — is incomplete. These are the required elements for each.
- Finding title and unique reference number
- Severity (Critical / High / Medium / Low / Informational) with CVSS v3.1 base score and vector string
- Description: what the vulnerability is and where it was found
- Proof of concept: screenshot, request/response pair or reproduction steps that prove exploitability — this is the difference between VAPT and a scan
- Business impact: what an attacker could achieve
- Remediation: a specific, developer-actionable fix mapped to the relevant framework (OWASP, CIS, MITRE ATT&CK)
Section 4: Remediation summary and risk register
After the individual findings, a summary table lets the development and security teams track remediation progress. It is also the section most auditors turn to first.
- One row per finding with reference, severity, affected component and current status (open / in-progress / remediated / accepted)
- Prioritised remediation order: Critical first, then High, Medium, Low
- Retest status column, updated after the free retest
- Risk acceptance section for findings the organisation has formally decided to accept rather than fix
Section 5: Attestation and sign-off
The final page is the attestation. It confirms that testing was conducted within the agreed scope, by the named testing provider, and that the report reflects the findings accurately. For regulatory submissions in India — to RBI, SEBI, IRDAI or CERT-In — the attestation is the document the regulator may ask to see first.
- Provider name, testing team, testing dates
- Scope reference (links back to the signed rules of engagement)
- Statement that testing was conducted in accordance with the named methodology
- Provider signature or authorised representative sign-off
- Any caveats or scope exclusions agreed before testing
Frequently Asked Questions
A report for a mid-size web application and API scope typically runs 30–60 pages. The length is not what makes it good: a 150-page report stuffed with scanner output is less useful than a 40-page report with ten manually verified, clearly evidenced findings and actionable remediation for each. Quality of evidence per finding matters more than volume.
CVSS (Common Vulnerability Scoring System) is a standardised 0–10 numerical score for vulnerability severity. Version 3.1 is the current standard. The score is calculated from a vector that captures attack complexity, privileges required, user interaction, scope, confidentiality and integrity impact. It matters because it allows your development team to prioritise fixes consistently, and because regulators and auditors recognise it as a standard severity scale.
Yes. A VAPT report is standard supporting evidence for the technical vulnerability management controls in both frameworks. For ISO 27001 it supports control A.8.8 (management of technical vulnerabilities). For SOC 2 it supports the Availability and Security criteria. Ensure the report covers the systems in scope for the certification.