Browse the site
Call Get a quote

Can you audit our third-party vendors for security?

Yes. A third-party security audit assesses your vendors' controls, evidence and exposure, not your own network. Scope is a questionnaire and evidence review, a breach and disclosure-history check, privileged-access testing, supply-chain review, and a re-test of vendor-remediated findings. This matters because Indian ransomware operators treat suppliers as entry points.

Key takeaways

  • A third-party security audit typically costs Rs 40,000 to Rs 2,50,000 per vendor depending on depth, and is quoted per vendor rather than per engagement.
  • India recorded 77 ransomware attacks between January and June 2026 (Cyble CRIL, reported by Fortune India, 23 July 2026), with supply chain a growing entry route.
  • Evidence review matters more than questionnaire answers, because a signed questionnaire from a vendor that was breached is worth very little.
  • Privileged access to your environment is the single item to check on every vendor, including whether the vendor still needs it.
  • 83% of Indian organisations have not begun comprehensive DPDP implementation, so vendor contracts rarely contain adequate data processing terms yet.

As of 24 October 2026: the service descriptions, prices and turnaround figures on this page are current.

What does a third-party security audit actually cover?

Five areas. First, a control questionnaire mapped to a named framework, which is only a starting point rather than the assessment. Second, an evidence review, because a vendor's control is only as real as the artefact it produces, and a screenshot is not a log, a policy is not a configuration and a certification is not a current attestation. Third, breach and disclosure history, including any CERT-In or public disclosure, any dark web appearance of the vendor's credentials, and any prior incident the vendor has not disclosed. Fourth, credential and privileged-access testing, focused on what the vendor's accounts can reach in your estate. Fifth, software supply-chain and dependency review, checking for known vulnerable components and unmaintained packages in what the vendor supplies you.

Why are vendors the front door now?

Because the attacker does not need to defeat your controls, only your supplier's. Indian ransomware operations in 2026 have consistently reached large enterprise customers through IT vendors, logistics partners, payroll processors and managed service providers, and the pattern is consistent: compromise a supplier that already has privileged access, then move laterally. The scale of the problem is also a staffing problem, since 57% of Indian security providers struggle to hire AI-security specialists and 73% of organisations cannot fill roles, so many suppliers are operating with the same thin security coverage as their customers. The relevant statistic is that 83% of Indian organisations have not begun comprehensive DPDP implementation, which means most vendor contracts still lack proper data processing terms, audit rights and breach-notification deadlines.

How do I build a vendor risk register that is actually useful?

Start with a tiering that reflects exposure rather than spend. Tier one is every vendor that has privileged access to your production environment, holds your customer or patient data, or is on the payment path, and these get a technical audit annually. Tier two is vendors holding data or with network connectivity, which get a questionnaire and evidence review annually or on a two-year cycle. Tier three is everything else, which gets an annual standard questionnaire and a monitoring check for breach mentions. For each vendor, record the tier, the last audit date, the findings raised, the remediation status, the data shared and the contractual notice period. That register is what makes the next audit cheaper, because you are not starting from zero each year.

How often should vendors be re-audited?

Annually for tier one, at minimum, and immediately on any of four triggers: a vendor announces a breach, a vendor is acquired or changes ownership, a new system or data category is shared, or a failed audit finding is not remediated by its due date. For tier two, on a two-year cycle with annual questionnaire refresh, and for tier three, an annual questionnaire plus monitoring. The retest matters as much as the cadence, because a vendor that failed to remediate a finding last year and is not retested will simply fail again, and the register will show a growing list of findings nobody is tracking.

Third-party vendor security audit tiers, cost and frequency in India
Vendor tierExamplesAudit cost (ex-GST)Re-audit frequency
Tier 1, privileged access or payment pathManaged service provider, payment gateway, payroll vendorRs 1,20,000 - 2,50,000Annually, plus on incident
Tier 2, holds data or has connectivityCRM provider, ticketing SaaS, cloud resellerRs 60,000 - 1,20,000Every 1-2 years
Tier 3, low exposure, no dataFacilities, courier, non-sensitive SaaSRs 40,000 - 60,000Annually, questionnaire only
Continuous monitoring add-onBreach mentions, dark web credential exposure, certification statusRs 20,000 - 40,000 per yearContinuous

What are the frequently asked questions?

Can you audit our third-party vendors for security?
Yes. A third-party security audit assesses your vendors' controls, evidence and exposure, not your own network. Scope is a questionnaire and evidence review, a breach and disclosure-history check, privileged-access testing, supply-chain review, and a re-test of vendor-remediated findings. This matters because Indian ransomware operators treat suppliers as entry points.
How much does a third-party security audit cost in India?
Roughly Rs 40,000 to Rs 2,50,000 per vendor excluding 18% GST, depending on depth. A tier one vendor with privileged access sits at the top of that range, and low-exposure vendors are usually covered by a standard questionnaire at the bottom.
Can you audit a vendor that will not cooperate?
You can assess what is observable from your side, such as exposed infrastructure, leaked credentials and public breach history, and you can make it a contractual condition that the vendor must allow an audit. Where a tier one vendor refuses both, that refusal is itself the finding and should be escalated to the business as a risk acceptance.
What should a vendor contract include for DPDP compliance?
Written data processing terms covering purpose limitation, security obligations, sub-processor disclosure, audit rights, breach notification within a fixed period, retention and deletion at exit, and the data fiduciary's responsibilities under the Digital Personal Data Protection Act 2023.
How do we know if our vendor has been breached?
We check public disclosure records, CERT-In and media reporting, dark web listings for the vendor's credentials and customer data, and any certificate or attestation status that has lapsed. Continuous monitoring of the same sources is available as an annual add-on, which is cheaper than a full audit every year.

Get a straight answer on this

Send us your vendor list with the systems each one touches, and we will return a tiering, a per-vendor audit plan and a fixed price for the first tier.

Send us the details See pricing

Last reviewed: 24 October 2026. Information on this page is general guidance, not legal advice. Prices are indicative bands for a typical scope and are confirmed in a written quote before any work begins.