Cyber Security | VAPT Reporting

VAPT Report: What a Credible One Actually Contains

Professional reviewing a printed vulnerability findings report at a desk

The report is the only part of a VAPT engagement most people ever see. Testers come and go, tooling is invisible, and what remains on the shared drive is a PDF that will be read by an auditor next quarter and a customer's security team the quarter after. Which makes it odd how rarely buyers specify what the report must contain before signing the purchase order.

The gap between a good report and a poor one is wider than the gap between a good tester and a poor one, because a weak report can hide strong work and a polished template can disguise an automated scan. Whichever of the VAPT types you commissioned, the structure below is what a credible cybersecurity provider delivers, and what you should be contracting for in advance.

Who actually reads it

Four audiences, with incompatible needs, which is why a single undifferentiated list of findings serves nobody.

Engineers need reproduction steps precise enough to confirm the issue on their own machine, and remediation guidance specific to their stack. Management needs a two-page summary that explains business exposure without requiring a security background. Auditors need scope, methodology, dates, tester identity and evidence that findings were remediated. An ISO 27001 assessor will check that testing was proportionate to your risk assessment, a SOC 2 auditor will sample remediation against your stated SLA, and a PCI DSS assessor will check prescribed scope and frequency. Where personal data is involved, the testing and remediation record becomes part of how your security safeguards under DPDP would be judged after an incident.

Customers, finally, usually receive a summary letter rather than the full document, since the full report is a detailed guide to attacking you.

The sections a credible report contains

Executive summary. Two to three pages, written in business language, stating what was tested, the overall security posture, the most serious exposures and what they would mean commercially. If this section is a chart of severity counts and nothing else, it was not written for the people who read it.

Scope statement. Exactly what was tested, by hostname, IP range, application and user role, and exactly what was excluded. It should name the environment, because a finding in a staging clone carries different weight from the same finding in production. For a cloud security review, scope should name the accounts, subscriptions or projects examined.

Methodology and timeline. The standards followed, whether OWASP WSTG, ASVS, MASVS, the API Security Top 10, PTES or NIST SP 800-115, together with the testing dates, the approach taken and the names and credentials of the testers. A described methodology that matches the work is a quiet but reliable quality signal.

Limitations. Honest reports say what the engagement could not establish. Time constraints, inaccessible components, rate limiting that blocked certain techniques, or a source code review that was out of scope. A report with no limitations section is usually incomplete rather than exhaustive.

Findings. The substance, covered below.

Remediation roadmap. Findings grouped and sequenced by effort and impact, rather than left as a flat list for the client to prioritise alone.

Appendices. Tooling used, raw output where relevant, and references.

Engineering team discussing vulnerability severity triage around a laptop

What a single finding should contain

Each finding stands or falls on seven elements. A title describing the issue rather than the tool that found it. A severity rating with the reasoning behind it. The affected component, named precisely by endpoint, parameter or host. A description explaining the underlying cause rather than restating a CVE summary. Reproduction steps a competent engineer can follow without contacting the tester. Evidence, meaning annotated screenshots, request and response pairs or proof-of-concept output. And remediation guidance specific to your technology, not a paragraph copied from a vendor knowledge base.

Severity deserves particular attention. CVSS version 3.1 or 4.0 gives a defensible baseline, but a raw CVSS score is a generic measure that knows nothing about your environment. A critical-scored vulnerability on an isolated internal system with no sensitive data may warrant lower priority than a medium-scored authorisation flaw on the endpoint serving your customer records. Good reports state both the base score and the contextual rating, and explain any divergence.

Credible report against template report

ElementCredible reportTemplate report
Executive summaryBusiness impact in plain languageSeverity pie chart only
FindingsManual discovery, business logic issues presentScanner output reformatted
ReproductionStep-by-step, independently verifiable"Run the scanner" or absent
EvidenceAnnotated screenshots, request and response pairsGeneric tool screenshots
SeverityCVSS plus contextual rating with reasoningTool-assigned severity unchanged
RemediationSpecific to your stack and versionGeneric vendor advisory text
False positivesValidated and removedPassed through unchecked
LimitationsStated honestlyAbsent
RetestIncluded, with an updated reportCharged separately or unavailable

The most reliable single tell is business logic. Automated tooling cannot find a flaw that lets a user in one organisation read another organisation's records by changing an identifier, or a discount workflow that can be replayed. If a report covering a complex application contains no business logic findings and no authorisation testing between roles, very little manual work happened.

Red flags worth checking before you pay

  • Findings that are clearly scanner output, identifiable from the phrasing and generic remediation text.
  • No named testers, or credentials stated at company level only.
  • Every finding rated by the tool with no contextual adjustment.
  • Reproduction steps that do not reproduce when your team tries them.
  • Informational findings padded into the count to inflate apparent value.
  • A missing or vague scope statement, which makes the report useless to an auditor.
  • No retest offered, or a retest priced as a second full engagement.
  • A certificate issued before remediation was verified.
Developer verifying remediation and retest results on dual monitors

The first week after delivery

Reports lose most of their value in the fortnight after arrival, while everyone agrees the findings are serious and nobody has been assigned anything.

Start with a walkthrough. A good provider will spend an hour with your engineering team taking them through the findings live, and that session resolves more ambiguity than a week of email. Insist on it, and have the people who will write the fixes in the room rather than only their managers.

Then triage against your own environment rather than against the severity column. For each finding, decide whether it is exploitable in your real configuration, what it would cost an attacker, and what it would cost you. Some critical-rated findings will be mitigated by controls the tester could not see. Some medium-rated ones will turn out to be the most urgent item in the report.

Put every accepted finding into the system your engineers already use, with an owner and a date. Findings that live only in a PDF do not get fixed, and a tracker entry is also the evidence an auditor will later ask for. Where you decide not to remediate, record the risk acceptance with a named approver and a review date. An auditor can live with a documented decision. An auditor cannot live with silence.

How the report becomes compliance evidence

Treat the report as the beginning of an evidence chain rather than a standalone artefact, because that is how assessors read it.

The chain has four links. The report itself establishes that testing happened, with scope and dates. The tracker shows each finding was triaged and assigned. The remediation record shows what was changed and when, ideally tied to a change ticket or commit. The retest report closes the loop by independently confirming the fix.

Companies that keep all four survive audit questions easily. Companies that keep only the first spend their audit explaining what happened next, usually from memory. The difference costs nothing at the time and a great deal later.

One practical habit helps more than any tool. File each engagement in a single folder containing the rules of engagement, the original report, the tracker export, the retest report and the closure letter. When an auditor or an enterprise customer asks about your testing programme, you send the folder rather than reconstructing a year of work.

Retest and the closure certificate

The retest is where the engagement produces value. After your team remediates, the provider verifies each finding and issues an updated report marking items as closed, partially remediated or open, with evidence for each determination. This updated document, not the original, is what you give an auditor.

Many Indian providers then issue a closure letter or certificate. Customers and auditors commonly accept it, and it is useful in sales conversations. Understand what it is, though. It is a commercial artefact confirming that identified findings were verified as fixed on a given date against a defined scope. It is not an accredited certification, it says nothing about issues outside scope, and it expires in practical terms the moment you ship a significant change.

Final Thoughts

If you have a report in hand and are unsure whether it reflects real testing, our consulting team will review it against the structure above and tell you plainly what you received. Get in touch for a review.

Frequently Asked Questions

How long should a VAPT report be?

Length follows scope rather than value. A focused external network test might produce fifteen to twenty-five pages, while a full web application assessment commonly runs sixty or more. A hundred-page report padded with informational findings is not better than a thirty-page report with six real ones.

How soon after testing should we receive it?

Usually five to ten working days after testing concludes. Critical findings should be communicated immediately during the engagement rather than held for the report.

Is a VAPT certificate officially recognised?

No accredited body issues VAPT certificates. The closure letter most Indian providers supply confirms that findings were verified as remediated, and it is widely accepted commercially, but the report behind it is what carries weight with an auditor.

Can we share the report with customers?

Share the summary letter freely under NDA. The full report contains reproduction steps for weaknesses in your systems and should be distributed narrowly, if at all.

How long does a VAPT report stay valid?

Most auditors and customers expect one no older than twelve months, and many regulated sectors require annual testing. Any significant change to architecture or authentication makes the prior report stale regardless of its date.

What if we disagree with a finding's severity?

Raise it during the draft review, which a good provider will offer. Severity should reflect your environment, and a tester who refuses to discuss context is applying tool output rather than judgment.