AuditXYZ

VAPT: Vulnerability Assessment and Penetration Testing Explained

VAPT is the combination of two distinct security testing activities. Vulnerability Assessment (VA) systematically identifies and prioritises known weaknesses in a system — typically using automated scanners augmented with manual review. Penetration Testing (PT) then takes those (and newly discovered) findings and attempts to exploit them under controlled conditions, demonstrating real-world business impact.

Treating VA and PT as a single service is a common commercial packaging in India in particular, but under the hood they answer different questions:

Vulnerability AssessmentPenetration Testing
Primary questionWhat weaknesses exist?Can those weaknesses actually be used to compromise us?
ApproachBroad, scan-drivenDepth-focused, attacker-simulated
Typical outputPrioritised list of findings with CVSS scoresChain-of-exploits narrative, business impact, remediation
AutomationHeavy (Nessus, Qualys, Nuclei, Burp active)Light — a tester drives it

Where VAPT Is Required

  • PCI DSS: Requirement 11 mandates internal/external vulnerability scans quarterly and penetration tests at least annually.
  • ISO 27001 (Annex A.12.6.1): Technical vulnerability management is a required control; VAPT is the usual evidence.
  • RBI Cyber Security Framework: Banks must perform VAPT regularly; critical systems demand it before go-live and after major changes.
  • SEBI CSCRF: Market intermediaries must have VAPT performed by a CERT-In empanelled auditor.
  • UIDAI AUA/KUA, GIGW, MeitY empanelment: Various Indian government and regulated-entity requirements point to CERT-In empanelled VAPT.

CERT-In Empanelled VAPT

When an Indian regulator says "VAPT by a CERT-In empanelled auditor," it means the audit must be performed by one of the organisations on the official CERT-In empanelment list. Only reports from empanelled firms are accepted for the regulatory filings.

Typical VAPT Engagement

  1. Scoping: Define targets (web apps, APIs, mobile apps, network ranges, cloud accounts). Clarify grey-box vs. black-box, credentialed vs. non-credentialed.
  2. Reconnaissance and VA scan: Automated scanning plus manual enumeration.
  3. Exploitation (PT): Attempt to chain findings into meaningful compromise paths.
  4. Reporting: Executive summary, technical findings with CVSS, exploit chains, remediation guidance, and compliance mapping.
  5. Re-testing: Validate that fixes close the findings.

Related terms

Related frameworks

Request a consultation

Step 1 of 520%

Which framework do you need?