Cybersecurity & Data Security

VAPT Services and CERT-In Empanelled Security Audits in India

Last reviewed: 2026-11-07

Has a customer, regulator, bank partner or tender asked for a VAPT report or a security audit by a CERT-In empanelled auditor? Tell us what needs testing, why, and by when.

ConformArc reviews your requirement and, where a suitable provider is available, introduces you to a security testing firm, including a CERT-In empanelled auditing organisation if your requirement specifies one.

Discuss Your VAPT Requirement

Security specialist reviewing application vulnerability test results

At a glance

What to send with your enquiry

  • Number and type of applications (web, mobile, API), with approximate size
  • Number of external IPs and internal network segments
  • Cloud providers and number of accounts or subscriptions
  • Who requires the test (customer, regulator, auditor, tender) and the exact wording
  • Whether a CERT-In empanelled auditor is required
  • Preferred dates and any blackout periods

What a specialist can help with

  • Scoping document and rules of engagement
  • Vulnerability assessment and penetration test report
  • Executive summary for management and customers
  • Retest and closure report
  • Where applicable, an audit report or compliance statement signed by a CERT-In empanelled organisation
  • Optional: secure development training and remediation support
Scope and report acceptance. ConformArc does not perform security testing or audits. Testing, reports and audit opinions are provided by the selected security firm. Do not send passwords, VPN details, source code, vulnerabilities or network diagrams through the public form; the provider arranges secure sharing after scope and contract are agreed.
Role clarity. Enquiry support and specialist introductions. Testing, audit opinions and regulatory interpretation remain with the selected security firm, your advisers and the relevant authorities.

Return to Cybersecurity and Data Security.

What VAPT means

Vulnerability Assessment and Penetration Testing (VAPT) combines two activities:

  • Vulnerability assessment: systematic scanning and review to identify known weaknesses, misconfigurations and missing patches across applications, networks, cloud and devices.
  • Penetration testing: authorised, controlled attempts by skilled testers to exploit weaknesses and show their real impact, within an agreed scope and rules of engagement.

The output is a report describing findings, severity, evidence and recommended fixes, usually followed by a retest to confirm remediation. A VAPT report is evidence of testing at a point in time. It is not a certification that systems are secure.

Types of testing you can request

Test type What is tested Typical trigger
Web application testing Customer-facing and internal web apps, admin panels Customer security review, SOC 2 or ISO 27001 evidence, launch
Mobile application testing Android and iOS apps and their back-end APIs App store launch, fintech partner requirement
API testing REST and GraphQL APIs, authentication and authorisation Partner integrations, open banking, B2B SaaS
External network testing Internet-facing IPs, firewalls, VPNs, mail servers Annual audit, PCI DSS requirement, tender
Internal network testing Internal infrastructure, Active Directory, segmentation Ransomware resilience, PCI DSS segmentation testing
Cloud security assessment AWS, Azure, GCP configuration against security benchmarks Cloud migration, SOC 2 or ISO 27001, CERT-In audit scope
Source code review Secure code review of critical components High-risk applications, regulator or customer request
IoT / OT / product security testing Connected devices and firmware, industrial control systems Product launch, EU cybersecurity readiness for connected products (see CE certification in India)
Red team assessment Objective-based simulation across people, process and technology Mature organisations testing detection and response

When a CERT-In empanelled auditor is required

CERT-In (the Indian Computer Emergency Response Team) maintains a published list of empanelled information security auditing organisations. Empanelment applies to the auditing organisation, not to the organisation being audited. There is no such thing as a “CERT-In certified” company.

An empanelled auditor is typically required when:

  • A government department, PSU or government project requires a security audit or “safe-to-host” clearance before an application goes live
  • A sectoral regulator, or a regulated entity you supply, requires audits by CERT-In empanelled organisations
  • A tender or contract specifies a CERT-In empanelled auditor

CERT-In has issued Comprehensive Cyber Security Audit Policy Guidelines (July 2025) that set expectations for auditee organisations and empanelled auditors, including audit scope, standards, management responsibility and at least annual comprehensive audits. Sectoral regulators can require more frequent audits. Organisations covered by CERT-In’s April 2022 directions must also report specified cyber incidents to CERT-In within six hours of noticing them and maintain logs as required. An audit can check readiness for these obligations.

Whether and how these guidelines and directions apply to your organisation depends on your sector, regulator and contracts. Confirm the current requirements with your compliance or legal adviser and with the party asking for the audit, and check the originals on the CERT-In website.

How to verify an empanelled auditor: check the organisation’s exact legal name on the current list on cert-in.org.in on the date you sign the contract and again on the date the report is issued.

Who commonly needs VAPT in India

  • Fintech, payment and lending platforms (bank and partner requirements; PCI DSS)
  • SaaS companies (SOC 2 and ISO 27001 evidence; customer security questionnaires)
  • E-commerce and consumer apps handling personal and payment data
  • Healthcare and health-tech platforms
  • Government suppliers and system integrators
  • Manufacturers of connected products exporting to the EU
  • Any organisation preparing for security safeguards under the DPDP Act

How a VAPT engagement works

  1. Define scope and objectives. List applications, URLs, IP ranges, cloud accounts, APIs and environments (production or staging), plus the reason for testing.
  2. Agree rules of engagement. Testing windows, contact points, out-of-scope systems, data handling, and written authorisation from the system owner. Third-party hosting providers’ testing policies may also apply.
  3. Testing. The provider performs automated and manual testing using recognised methods, for example OWASP guidance for applications.
  4. Reporting. An executive summary, findings with severity ratings, evidence and remediation advice.
  5. Remediation. Your team fixes the findings.
  6. Retest and closure report. The provider retests and confirms which findings are closed.
  7. Repeat at least annually and after significant changes, or as your customer, auditor or regulator requires.

Have a deadline or a specific auditor requirement? Tell us who requires the test and whether a CERT-In empanelled auditor is specified. We will discuss a suitable introduction. Share Your Testing Requirement

Timeline and cost factors

  • Number and complexity of applications, APIs, IPs and cloud accounts
  • Depth of testing (automated scanning only versus manual penetration testing)
  • Authenticated testing with multiple user roles
  • Whether CERT-In empanelment, on-site testing or specific methodologies are required
  • Retesting rounds
  • Reporting format required by your customer or regulator

ConformArc does not set provider fees. Ask for a quotation that lists scope items, testing days, retest inclusion and the report format.

How to choose a VAPT provider

  • Ask for a sample (redacted) report and the testing methodology
  • Check team qualifications and experience with your technology stack
  • Confirm CERT-In empanelment on the official list if required
  • Confirm data handling, confidentiality and insurance
  • Agree retest terms in advance
  • Avoid “VAPT certificates” issued after automated scans only, if your requirement calls for manual penetration testing

How to verify your provider

Provider type How to verify
CERT-In empanelled auditor Check the organisation’s exact legal name on the current list published on cert-in.org.in on the date you sign the contract.

How ConformArc helps

  1. Share your requirement, the systems in scope and who requires the test.
  2. We clarify scope and auditor requirements.
  3. We agree the introduction with you before sharing your details.
  4. The provider confirms scope, fees, dates and rules of engagement directly with you.

Tell us what needs testing

Share the systems in scope, who requires the test and your deadline. We will review the details and reply about the next step. Testing is often evidence for SOC 2, ISO 27001, PCI DSS and DPDP work.

Discuss Your VAPT Requirement

Frequently asked questions

Is a VAPT report the same as a VAPT certificate?

Most customers and regulators need the test report and a closure report after retesting. Some providers issue a 'certificate' summarising the test, but it is not a formal certification. Ask the party requiring the test what they need.

How often should we do VAPT?

At least annually and after significant changes is a common expectation. Your customers, auditors, PCI DSS (where applicable) or sector rules may require specific frequencies.

Do we need a CERT-In empanelled auditor?

Only if your regulator, customer, contract or government project requires one. Many private customers accept testing by any competent firm. Check the exact requirement.

Can you test our production systems?

Testing scope, including production, is agreed between you and the provider in writing, with safeguards and testing windows. Some tests are better done in staging.

Does VAPT make us compliant with ISO 27001 or SOC 2?

No. VAPT provides evidence that supports controls in those frameworks, but certification or attestation requires the full audit process.

Will ConformArc perform the testing?

No. ConformArc introduces suitable providers. The provider performs the testing and issues the report.

Sources / further reading

Requirements can change. Confirm the current route and applicable edition for the specific product before starting the project.

Discuss your VAPT or security audit requirement

What needs testing, who requires it and by when? Do not include passwords or confidential details.

We use your details to respond to this enquiry. If a suitable external specialist could help, we will tell you who we propose to contact and ask before sharing your name, contact details or project information. The specialist may then contact you about this request. Read the Privacy Notice. See also how we choose providers.

Related options for VAPT & CERT-In audits.

Add more details (optional)

We use your details to respond to this enquiry. If a suitable external specialist could help, we will tell you who we propose to contact and ask before sharing your name, contact details or project information. Please do not include passwords, confidential documents or sensitive personal information.