Frequently Asked Questions
The questions buyers actually ask before an audit or VAPT: scoping, regulators, pricing, re-testing and confidentiality, answered plainly.
Getting an engagement started
Scope is set by what we test and how deep: the number of applications, APIs, IP addresses, and cloud accounts in scope, whether testing is black-, gray-, or white-box, and any compliance driver behind it. A single web application typically means days of testing plus reporting; a multi-asset enterprise scope runs several weeks. We confirm the asset inventory and timeline in a scoping call before any proposal, so the schedule you sign is the schedule we test to. Methodology is mapped to OWASP Top 10, SANS 25, and MITRE ATT&CK.
It depends on scope and our current audit calendar. Smaller, well-defined scopes generally start sooner than multi-entity audits. If you are working against a regulatory deadline such as an RBI submission or a SEBI CSCRF timeline, tell us the date and we plan backwards from it. The fastest route to a start date is a scoping call with your asset list ready.
Both. Most application, API, network, and cloud testing is delivered remotely; that is how we serve clients in 45 countries from Ahmedabad. Onsite work is scheduled where it genuinely matters: data-center and infrastructure reviews, OT environments, and engagements where client or regulator policy requires physical presence. The split is agreed during scoping.
We work alongside your team. Your team gets the methodology up front, a findings walkthrough after fieldwork rather than just a PDF, and re-tests of their fixes. We can log findings in your tracker, and we hand over enough detail that your engineers can reproduce every issue. Many of our 564+ audits run alongside capable internal teams. An independent, empanelled view is what they come to us for.
Meeting your obligations
CERT-In is India's national agency for cyber incident response, and it maintains a panel of security auditing organisations vetted to audit against its standards. Virtual Caim is on that panel. Empanelled audits are commonly required for government and public-sector systems and expected across regulated sectors: banks under RBI directions, SEBI-regulated entities, and organisations covered by the CERT-In Directions 2022. If your regulator asks for a "CERT-In empanelled auditor," this is what it means, and we qualify.
Cadence comes from your regulator's framework. RBI Master Directions for banks and NBFCs and SEBI's CSCRF for market participants both mandate recurring audits, with frequency depending on entity classification and system criticality. In practice most regulated clients run at least an annual cycle, with more frequent VAPT of critical systems. We map your exact obligations during scoping, as we do for 125+ banks and financial institutions and 50+ SEBI-regulated entities.
The DPDP Act makes any organisation that decides how and why the digital personal data of individuals in India is processed a "Data Fiduciary," with duties around lawful consent, purpose limitation, security safeguards, and breach notification. Significant Data Fiduciaries carry additional obligations, including independent audits and impact assessments. We run DPDP gap assessments that map your current controls to the Act (and to ISO 27701 where you want a certifiable privacy framework), then produce a remediation roadmap your team can execute.
Yes. A sanitised sample report is available on request, typically under NDA. It shows the structure you will receive: an executive summary for leadership, risk-rated findings with evidence and reproduction steps, remediation guidance, and the re-test annex. Reading it first is the quickest way to see whether our reporting will satisfy your auditors, board, or regulator.
Pricing, NDAs, and what happens next
Per engagement, against scope: asset count, testing depth, compliance framework, and timeline. We do not work off a rate card. After a scoping call you receive a fixed-fee proposal with deliverables and schedule spelled out, so there are no day-rate surprises mid-engagement. We would rather quote precisely than publish a range that fits nobody.
Every VAPT and audit proposal defines a re-test window: you remediate, we verify each fix, and the report is updated to show closed status. That closure evidence is what regulators and enterprise customers usually want to see. The number of re-test cycles and the window length are agreed in the proposal, so both sides know exactly what "done" looks like.
An NDA is standard before scoping. Most engagements begin under one, and we are comfortable signing yours. During the engagement we operate under an ISO/IEC 27001 Certified ISMS: least-privilege access to your systems, controlled handling of evidence, and agreed disposal of engagement data at close-out. Client names are never referenced publicly without written permission.
The report is not the end of the engagement. We walk your technical team through every finding, agree severity and priorities, and stay available while fixes land. Once you remediate, we re-test and issue updated closure documentation you can hand to auditors, customers, or your regulator. If the findings point to a structural gap, such as missing ISMS controls or an unowned attack surface, we say so plainly and scope that separately rather than burying it.
Please do; our motto is “do your own due diligence.” Our listing is on page 38 of CERT-In’s official register of empanelled auditors, linked from our Awards page so you can open the Government document yourself. Our ISO/IEC 27001 certificate is viewable on the ISO 27001 page after a short request form, and the certificate number can be validated with the issuing registrar.
Question not on the list?
Scoping calls answer most of them in thirty minutes: what to test, what your regulator expects, what it costs, and when we can start. Bring your asset list; we'll bring the audit calendar.