Vulnerability Assessment and Penetration Testing (VAPT) has no list price, in India or anywhere else. Cost follows scope and depth: how much there is to test, how deeply it is tested by people rather than tools, and what the report has to satisfy. Once you can see those levers, comparing quotes becomes straightforward.
Why VAPT quotes vary so much
One vendor prices per application, another per API endpoint, a third per IP address or per testing day. A low quote may cover an automated scan of the login page; a higher one may include authenticated, role-by-role manual testing of every workflow plus a retest. Neither number means anything until you know the scope behind it.
The six drivers of VAPT cost
- Attack surface: number of web applications, user roles, API endpoints, mobile apps (Android, iOS), external and internal IPs, and cloud accounts.
- Testing depth: automated scanning versus manual exploitation; black-, grey- or white-box access; authenticated testing for each role; business-logic testing.
- Methodology and reporting format: OWASP-based testing, CERT-In-aligned reporting, or a report format a specific regulator or customer expects.
- Environment and access: staging versus production, restricted testing windows, VPN or whitelisting set-up, and test data availability.
- Retesting: whether verification of fixes is included, and how many retest rounds.
- Who must sign: some regulators and government buyers require the audit to be performed by a CERT-In empanelled organisation, which affects who can deliver it.
The practical test: a quote is comparable only if it names the assets in scope, the roles tested, the share of manual testing, the reporting format and the number of retests.
Indicative VAPT pricing
As a starting point, VVnT SeQuor’s VAPT for a small application starts from INR 1,50,000 — for example, a single web application with a limited number of user roles and API endpoints. Larger scopes (multiple applications, mobile apps, extensive APIs, infrastructure or cloud) are quoted after a scoping call, against the six drivers above.
Indicative, not a fixed quote: the starting price helps you budget; the final quote depends on the assets, roles, depth and reporting format in your written scope.
How long a VAPT typically takes
A focused engagement on a single web application with a few user roles typically needs one to two weeks of testing, plus reporting. Multi-application scopes with APIs, mobile apps and infrastructure commonly run three to six weeks. Add time before testing for scoping and access set-up, and after it for remediation by your team and a retest — that remediation window is usually the longest part of the calendar.
Red flags in a low VAPT quote
- A scanner report re-branded as a penetration test, with no evidence of manual exploitation.
- No retest included, so you cannot show that findings were actually fixed.
- Findings without proof-of-concept evidence, severity rationale or remediation guidance.
- Vague scope (“your website”) instead of named assets and roles.
CERT-In empanelment: when it matters
If your regulator, a government buyer or a contract requires a CERT-In empanelled auditor, confirm that before you scope. VVnT SeQuor’s assessments follow CERT-In guidelines and processes. Where a regulator or buyer requires the audit to be performed by a CERT-In empanelled organisation, we deliver it together with CERT-In empanelled partners from our partner ecosystem.
How to get quotes you can compare
Write one scope sheet — assets, roles, environments, reporting format, retest expectations — and send the same sheet to every vendor. Our free Pre-VAPT Readiness / Scoping Checklist gives you that structure.