Skip to content

Reconnu au Royaume-Uni, aux États-Unis, dans l'UE et en Inde - réponse aux incidents 24/7.

VAPT vs vulnerability scan: what is the difference?

Organisations often receive quotes for a 'vulnerability assessment' or a 'VAPT' and assume they are the same thing. They are not. Understanding the difference determines whether the output you receive satisfies your board, your developers and your regulator.

Manual-led testing
Proof-of-concept evidence
Regulator-accepted reports
No scan dumps
Security testing and assessment

What a vulnerability scanner does

A vulnerability scanner is an automated tool that compares your systems against a database of known vulnerabilities, common misconfigurations and software version fingerprints. It produces a list quickly — often thousands of potential findings — without a human analyst deciding whether each is genuinely exploitable in your environment.

Scanners are fast and cheap, and they are a useful first step in any security programme. They are not a substitute for manual testing. A scanner that finds a vulnerable library version cannot determine whether that version is actually reachable, whether the vulnerable function is called in a way that enables exploitation, or what an attacker could do after exploitation.

What VAPT adds

Penetration testing layers human analyst work on top of the scanner output. The analyst validates each potential finding — attempting to exploit it in your specific environment — removes false positives, and chains lower-severity issues together to demonstrate real attack paths. The result is a prioritised, evidence-backed report that tells you what an attacker could actually achieve.

  • False positive removal: a manual tester confirms whether a finding is exploitable, not just present
  • Chained attack paths: a medium-severity misconfiguration and a low-severity information leak can combine into a critical compromise
  • Business logic testing: scanners cannot test whether your application enforces its own rules correctly
  • Proof of concept: each finding comes with a screenshot, request/response pair or reproduction steps that prove it
  • MITRE ATT&CK mapping: findings are labelled with the attacker technique, so your blue team can tune detection

When a vulnerability scan is enough — and when it is not

A standalone vulnerability scan is appropriate for a quick hygiene check on a low-risk internal system, or as a first step before a full VAPT engagement to get a rough inventory of the attack surface. It is not appropriate as evidence of security testing for most Indian regulators or enterprise procurement requirements.

RBI, SEBI, IRDAI and CERT-In all expect penetration testing by trained, independent testers — not a scan printout. ISO 27001 (A.8.8), SOC 2 (security criteria), and most enterprise supplier questionnaires distinguish between scan-only and manual testing. A scan alone does not satisfy the 'reasonable security safeguards' standard under India's DPDP Act 2023.

What to ask when you receive a quote

Before accepting a quote that uses the words 'vulnerability assessment', 'VAPT' or 'pen test' interchangeably, ask these questions.

  • Does the engagement include manual exploitation and proof-of-concept evidence for each finding?
  • Will false positives be removed before the report is delivered?
  • Does the report map findings to CVSS v3.1 and MITRE ATT&CK?
  • Is a free retest included for critical and high findings?
  • Is the report format accepted by the regulator or standard applicable to our organisation?

Frequently asked questions

No. A vulnerability scan is automated and identifies potential weaknesses from a database of known issues. A penetration test adds manual exploitation, false-positive removal, chained attack-path analysis and proof-of-concept evidence. Most Indian regulators and enterprise procurement processes require penetration testing, not scan-only output.

No. RBI's cyber resilience framework and SEBI's CSCRF require vulnerability assessment and penetration testing by trained, independent testers. A scan printout is not the same as a VAPT report and does not satisfy the testing evidence requirement.

A vulnerability scan of a web application may cost USD 500-1,500 from a reputable tool or managed scanner. A manual-led VAPT of the same application from a qualified provider typically starts at USD 3,000. The difference buys false-positive removal, exploited proof-of-concept evidence, chained attack-path analysis, MITRE ATT&CK mapping, and a report that regulators and auditors accept.

It is not required, but it can be useful. Running a scan first gives a broad inventory that helps both sides scope the VAPT more precisely. Some VAPT providers include a scan phase as the first step of their engagement — ask whether this is included or priced separately.

Parlez à un expert en sécurité dès aujourd'hui

Un test d'intrusion, un audit ou une surveillance 24/7 : notre équipe est prête au Royaume-Uni, aux États-Unis, dans l'UE et en Inde.