VAPT Reporting

πŸ“ Concept Note β€” EHPT Unit V | Source: MCA Sem III Syllabus


Penetration Test Report Structure

A professional VAPT report is the primary deliverable β€” it’s what the client pays for.

Report Sections

1. Cover Page

  • Tester name and organisation
  • Client name
  • Date of testing
  • Target systems and scope
  • Classification: CONFIDENTIAL

2. Executive Summary (1 page, non-technical)

  • What was tested and why
  • Overall risk posture (Critical/High/Medium/Low)
  • Top 3 most critical findings
  • Key recommendations
  • Written for management β€” no technical jargon

3. Scope & Methodology

  • Systems in scope (IPs, URLs, applications)
  • Testing approach (black-box, grey-box, white-box)
  • Tools used (Nmap, Metasploit, Burp Suite, etc.)
  • Timeframe of testing
  • Limitations and exclusions

4. Technical Findings

Each finding includes:

FieldContent
TitleClear, descriptive name
SeverityCVSS v3.1 score + rating
Affected SystemIP, URL, or component
DescriptionWhat the vulnerability is
Proof of ConceptStep-by-step with screenshots
Business ImpactWhat could happen if exploited
RemediationHow to fix it
ReferenceCVE number or CWE

5. Risk Heat Map

Plot findings by likelihood vs impact:

Impact
  High   β”‚  ●Medium    ●High      ●Critical
         β”‚
  Medium β”‚  ●Low       ●Medium    ●High
         β”‚
  Low    β”‚  ●Info      ●Low       ●Medium
         β”‚
         └────────────────────────────────
              Low       Medium     High
                    Likelihood

6. Remediation Priority Table

PriorityFindingCVSSFix
1vsftpd Backdoor (RCE)9.8Update to latest version
2SQL Injection in login8.6Implement parameterised queries
3Stored XSS in comments6.1Implement output encoding + CSP

7. Conclusion

Summary of findings and next steps.


CVSS v3.1 Calculation Examples

Example 1: vsftpd Backdoor (RCE)

MetricValueJustification
Attack VectorNetworkExploitable remotely
Attack ComplexityLowNo special conditions needed
Privileges RequiredNoneNo authentication needed
User InteractionNoneNo victim action needed
ScopeUnchangedSame component affected
ConfidentialityHighFull file system access
IntegrityHighCan modify any file
AvailabilityHighCan shut down service

Score: 9.8 (Critical)

Example 2: Stored XSS

MetricValueJustification
Attack VectorNetworkVia web browser
Attack ComplexityLowSimple payload
Privileges RequiredLowNeed account to post
User InteractionRequiredVictim must view page
ScopeChangedAffects other users’ browsers
ConfidentialityLowCookie theft possible
IntegrityLowPage content modified
AvailabilityNoneService stays up

Score: 5.4 (Medium)

πŸ”— Calculator: CVSS Scoring Reference ⚑


Remediation Strategies

StrategyApplication
PatchingUpdate software to fix known CVEs
Secure ConfigurationDisable defaults, remove unnecessary services
Least PrivilegeRemove excessive permissions
Input ValidationSanitise all user input
Output EncodingEncode output to prevent XSS
Network SegmentationIsolate critical systems
MFAAdd multi-factor authentication

Professional Ethics

Responsible Disclosure

  1. Discover vulnerability
  2. Report privately to affected organisation
  3. Give reasonable time to fix (typically 90 days)
  4. Disclose publicly only after fix is available (or deadline passes)

Bug Bounty Platforms

  • HackerOne β€” Largest bug bounty platform
  • Bugcrowd β€” Another major platform
  • Companies pay researchers for finding vulnerabilities legally

Absolute Rules

  • Never test without written permission
  • Protect client data discovered during testing
  • Don’t exfiltrate real data β€” demonstrate access, don’t steal
  • Report everything β€” even findings that seem minor

Certification Pathways

CertificationLevelFocus
CompTIA Security+EntryBroad security fundamentals
CEH (EC-Council)IntermediateEthical hacking methodology
eJPT (eLearnSecurity)Beginner-IntermediatePractical pentesting
OSCP (OffSec)AdvancedHands-on exploitation (24hr exam)