The short answer: VAPT combines a vulnerability assessment, which finds and ranks known weaknesses with automated scanning, and a penetration test, where a tester actually tries to exploit them the way an attacker would. Most businesses should test internet-facing systems at least once a year and after every major change. Regulated entities, such as those under SEBI or RBI, must follow their regulator’s schedule and often use a CERT-In empanelled auditor.
Key takeaways
- A vulnerability assessment finds known weaknesses; a penetration test proves what an attacker could do with them.
- Test internet-facing systems at least once a year and after every major change.
- SEBI and RBI regulated entities must follow their regulator's schedule, usually with a CERT-In empanelled auditor.
- A good report has proof, severity, specific fixes and a retest, not just scanner output.
“We need a VAPT” is a sentence IT teams in India hear often, usually because a customer, auditor or regulator asked for a report. The risk is buying the cheapest report that ticks the box, and learning nothing. This guide explains what you should actually be paying for.
A complete VAPT cycle
- 1. ScopeAgree systems, method and dates
- 2. Scan (VA)Find and rank known weaknesses
- 3. Exploit (PT)Prove what an attacker can reach
- 4. ReportSeverity, proof and fixes
- 5. FixOwners and deadlines
- 6. RetestConfirm and close
VA vs PT: what is the difference?
| Compared on | Vulnerability assessment (VA) | Penetration test (PT) |
|---|---|---|
| Question it answers | What known weaknesses do we have? | What could an attacker actually do with them? |
| How it is done | Mostly automated scanning, then manual review | Mostly manual, by a skilled tester |
| Depth | Broad, covers many systems | Deep, follows attack paths |
| False positives | Common, need to be filtered | Few, since findings are proven |
| Typical frequency | Monthly or quarterly | Yearly and after major changes |
A scan alone might report that a server runs an outdated version of some software. A penetration tester goes further: uses that weakness to get in, finds a stored password, and shows how it leads to the customer database. That chain is what management needs to see, and it is what a scan cannot show.
What should be in scope?
Scope decides the value of the test. Common areas are:
- External network: public IP addresses, firewalls, VPN gateways and mail servers, tested from the internet.
- Internal network: what an attacker could reach after getting onto one office laptop.
- Web applications: customer portals, websites with logins, and APIs, usually tested against the OWASP Top 10 risks.
- Mobile apps: both the app itself and the APIs behind it.
- Cloud configuration: storage, identity and network settings in Azure, AWS or Google Cloud.
- Wi-Fi: whether the guest network can reach internal systems.
If budget is limited, start with what faces the internet. That is what attackers scan every day.
Black box, grey box or white box?
- Black box: the tester gets no inside information, like a real outside attacker. Realistic, but time is spent on discovery.
- Grey box: the tester gets a normal user login and some documentation. This is the best value for most businesses, because it tests what happens when one account is compromised, which is how many real attacks start.
- White box: full access to code and architecture. Most thorough, used for critical applications.
How often should you run a VAPT?
For businesses that are not regulated, a sensible baseline is:
- A full VAPT of internet-facing systems and key applications at least once a year.
- A targeted test after any major change: a new application, a new firewall, a cloud migration or a merger.
- Automated vulnerability scanning monthly or quarterly in between.
Regulated entities have stricter rules. SEBI’s Cybersecurity and Cyber Resilience Framework (CSCRF) requires VAPT by CERT-In empanelled auditors for the entities it covers, on a schedule that depends on the entity’s category, with some categories testing every six months. RBI-regulated entities have their own requirements. If you supply software or services to banks, brokers or insurers, expect them to ask you for a recent VAPT report as well.
What does “CERT-In empanelled” mean?
CERT-In maintains a list of organisations it has empanelled to carry out information security audits, including VAPT. Government bodies and many regulated entities are required to use an auditor from that list. For other businesses it is not mandatory, but it is a reasonable signal of a minimum standard. You can check any vendor’s name against the current list on the CERT-In website.
How to judge a VAPT report
A good report should contain:
- An executive summary a non-technical director can read in five minutes.
- A clear scope and method: what was tested, when, from where, and what was excluded.
- Each finding with a severity rating, usually based on CVSS, adjusted for your business context.
- Proof: screenshots or steps showing the issue was actually exploited or confirmed.
- Specific fixes, not just “apply patches”.
- A retest after you fix the issues, with a closure report.
Warning signs are a report that is mainly raw scanner output, hundreds of “informational” findings with no prioritisation, or no retest included in the price.
After the report: fixing what was found
The test is the easy part. Assign each finding an owner and a deadline, fix critical and high findings first, and book the retest. Keep the reports, because auditors, customers and, under the DPDP Rules, the Data Protection Board may ask how you checked that your safeguards work. VAPT is also a good input for your ransomware defences, since it shows the same weaknesses attackers look for.
How Enterprise Solutions can help
Enterprise Solutions is a corporate solutions provider based in Noida, working with businesses across Delhi NCR and India. If this article raised questions about your own setup, these are the teams to talk to:
- Cybersecurity: Security services for endpoint protection, data protection, security monitoring, and vulnerability testing.
Send us an enquiry or call +91 97185 59908 and our team will get back to you.
Frequently asked questions
What is the difference between VA and PT?
A vulnerability assessment finds and ranks known weaknesses, mainly with automated scanning. A penetration test goes further: a tester tries to exploit those weaknesses to show what an attacker could actually reach.
How often should a business do VAPT?
A common baseline is a full VAPT of internet-facing systems and key applications at least once a year, plus a test after major changes and regular scanning in between. Regulated entities must follow their regulator's schedule.
Is a CERT-In empanelled auditor mandatory for VAPT?
It is required for government bodies and for many regulated entities, for example under SEBI's CSCRF. For other private businesses it is not mandatory, but it is a useful minimum standard.
What should a VAPT report include?
An executive summary, the scope and method, each finding with a severity rating and proof, specific remediation steps, and a retest after the fixes.
Which is better: black box, grey box or white box testing?
Grey box testing, where the tester gets a normal user login, is good value for most businesses because it shows what happens if one account is compromised. White box suits critical applications.
Keep reading
Sources
- CERT-In: information security auditing organisations and empanelment
- SEBI: Cybersecurity and Cyber Resilience Framework (CSCRF) for SEBI Regulated Entities
- OWASP Top 10
This article is general information, not legal or regulatory advice. Rules and figures are as published on the date shown, and may change. Please confirm your organisation’s obligations with a qualified professional.
