
Главное
Effective VAPT in India is not just a testing exercise — it is an audit artefact. Use this checklist to ensure your engagement produces a report that satisfies your regulator, your board and your insurance underwriter.
Before you engage a VAPT provider
Choosing the right provider and scoping the engagement correctly determines how useful the results are. These checks happen before any testing begins.
- Confirm whether your regulator (CERT-In, RBI, SEBI, IRDAI) requires an empanelled auditor or accepts any qualified provider
- Obtain proof of the provider's methodology (ask for the testing framework — OWASP WSTG, PTES, NIST 800-115)
- Request a sample redacted report to assess depth, structure and CVSS usage
- Confirm whether a free retest for critical and high findings is included
- Check that rules of engagement and a written scope document will be signed before testing
Scoping: what to include
An incomplete scope produces an incomplete result. These are the asset classes most often missed.
- All internet-facing web applications, including staging environments used in production support
- Mobile applications (Android and iOS), not only the production version
- REST and GraphQL APIs — including internal APIs accessible from the front end
- Cloud environments (AWS, Azure, GCP) — IAM, storage, compute, networking
- Active Directory and VPN infrastructure for hybrid environments
- Third-party components and integrations that have access to production data
- Any mobile apps or APIs introduced since the last VAPT
Regulatory alignment checklist
Different regulators require different testing outcomes. Check the applicable ones before scoping.
RBI: Banks and NBFCs must conduct VA/PT by trained, independent auditors, map findings to CIS or NIST, and provide evidence to RBI on request. SEBI (CSCRF): stock exchanges, brokers and depositories categorised as Market Infrastructure Institutions or Qualified RTAs must conduct annual PT. IRDAI: insurers must test internet-facing and critical applications annually through a CERT-In empanelled auditor. CERT-In (2022 directions): all critical information infrastructure operators must conduct periodic VAPT. DPDP Act 2023: data fiduciaries must demonstrate 'reasonable security safeguards' — a VAPT report is the standard evidence.
During the engagement
- Ensure a named point of contact is available to the testing team for clarifications
- Confirm that test accounts and credentials provided are valid before testing begins
- Agree an emergency pause process if a critical finding needs immediate disclosure
- Ask for preliminary findings within 24 hours for critical and high severity issues
- Keep an internal log of scope changes agreed during the engagement
Reviewing the VAPT report
A good report is actionable by three audiences: the board (risk summary), developers (remediation steps), and auditors (methodology and evidence). Check these before accepting delivery.
- Executive summary includes a risk rating and business-impact statement
- Every finding has a CVSS score, severity, proof-of-concept evidence, and a remediation recommendation
- Findings are mapped to OWASP categories and MITRE ATT&CK where applicable
- False positives have been removed or labelled as such
- The report is signed or attributed to the testing provider
Remediation and retest
Remediation without verification is incomplete. Use these checks after fixes are applied.
- Critical and high findings remediated within 30 days (or as required by your regulator)
- Developer team has acknowledged each finding in writing
- Retest window agreed with provider (typically 30–90 days from report delivery)
- Retest report received confirming remediation status of each finding
- Attestation letter received for submission to auditor or regulator
Keeping evidence for regulators and auditors
Indian regulators increasingly ask for VAPT evidence during inspections. These documents should be retained and readily available.
- Signed rules of engagement and scope document
- Full VAPT report (original, not summary)
- Remediation tracking log
- Retest report confirming closure
- Provider attestation letter
Часто задаваемые вопросы
At minimum annually, and after every significant infrastructure change or major release. RBI-regulated entities should follow the RBI cyber resilience framework timelines. SEBI Market Infrastructure Institutions must test annually under CSCRF. CERT-In directions specify periodic VAPT for critical infrastructure. The DPDP Act requires 'reasonable security safeguards' but does not prescribe frequency — annual testing supported by a written rationale is the defensible baseline.
Not unless it is explicitly in scope. Many VAPT engagements focus on web applications and APIs and exclude mobile apps by default. If your platform has an Android or iOS app, make sure it is listed as an in-scope asset and confirm the provider tests against OWASP MASVS.
A vulnerability scan report is automated output from a tool. A VAPT report includes manual analysis, exploited proof-of-concept findings, chained attack paths, false-positive removal, and developer-ready remediation steps. Indian regulators accept VAPT reports as audit evidence; automated scan outputs alone typically do not satisfy this requirement.
The CISO or head of IT security should own the scope document. The legal or compliance team should review it where the engagement is regulatory-driven. Developer and DevOps leads should confirm that all relevant assets — including staging, shadow IT and third-party integrations — are captured.