"Audit report from a CERT-In empanelled auditor" is a phrase that appears in many Indian tender documents, regulator circulars and enterprise vendor forms. Companies often discover it late, just before a bid deadline, and rush to hire whoever is available. That rush is where money and time are wasted.
This guide explains what CERT-In empanelment means, when an empanelled auditor is genuinely required, how to verify one, and how to prepare so the audit is smooth.
What is a CERT-In empanelled auditor?
CERT-In, the Indian Computer Emergency Response Team under MeitY, maintains a list of information security auditing organisations it has empanelled. The list is published on CERT-In's website, which describes it as the up-to-date valid list and says it is updated whenever there is a change (CERT-In empanelled auditing organisations). The list gives each organisation's address, website and contact person.
Empanelment tells you the organisation has passed CERT-In's selection process. It does not, by itself, tell you which specialist skills a given firm has, how deep its testing is, or how quickly it delivers. You still need to evaluate the firm.
When must the audit come from a CERT-In empanelled auditor?
There is no single law that says every company must use an empanelled auditor for every audit. The requirement comes from specific sources. The common ones are:
| Source of the requirement | What it typically looks like | What to do |
|---|---|---|
| Securities market regulation | SEBI's Cybersecurity and Cyber Resilience Framework requires cyber audits by CERT-In empanelled auditing organisations for regulated entities | Follow the exchange or SEBI circular that applies to your category |
| Government and PSU tenders | A clause asking for a security audit certificate or VAPT from a CERT-In empanelled agency before go-live or payment | Read the exact clause: scope, validity period, format of certificate |
| Government website and application hosting | Departments often require a security audit clearance before an application is hosted | Confirm with the department's IT team which format they accept |
| Other sector regulators and large clients | Banks, insurers and some enterprises name empanelment in vendor security requirements | Ask for the requirement in writing; it may be a preference, not a rule |
The securities market is a clear, documented example. An NSE circular dated 22 April 2026 on cyber audits of trading members lists, as the first auditor selection norm, that the auditing organisation "must mandatorily be CERT-In empaneled". It also limits one auditing organisation to a maximum of three consecutive years of audits for the same entity, followed by a two-year cooling-off period, and asks entities to follow CERT-In's Comprehensive Cyber Security Audit Policy Guidelines (NSE circular 19/2026). Rotation rules like this mean you should plan auditor changes in advance, not discover them at renewal time.
When you probably do not need empanelment
If a private client simply asks for "a penetration test" or "a VAPT report", or you want testing for your own assurance, ISO 27001 or SOC 2 readiness, any competent tester can do the work. Empanelment matters when it is written into the requirement. Do not pay for a label nobody asked for, and do not skip it when the document clearly demands it.
How to check whether an auditor is really empanelled
- Download the current list directly from cert-in.org.in. Do not rely on a logo on the vendor's website or a PDF the vendor sends you.
- Match the exact legal entity name. A firm with a similar name, or a partner of an empanelled firm, is not the same thing.
- Check that the report or certificate will be issued and signed by the empanelled organisation itself, not subcontracted with the empanelled firm only "co-branding".
- Recheck close to the audit date, since the list changes.
How to prepare so the audit passes first time
Failed or delayed audits are rarely caused by sophisticated vulnerabilities. They are caused by unclear scope, missing evidence and findings that could have been fixed beforehand.
Six weeks before
- Fix the scope in writing: URLs, IP ranges, mobile app versions, APIs, environments, user roles.
- Build an asset inventory: servers, cloud accounts, domains, third-party services.
- Run your own pre-audit test and fix the obvious issues: missing patches, weak TLS, default credentials, exposed admin panels, broken access control.
Two to four weeks before
- Collect policy evidence the auditor will ask for: access control, backup, incident response, change management, logging.
- Confirm logging and time sync. The CERT-In Directions require logs of ICT systems to be maintained securely for a rolling 180 days within India and clocks synchronised to NIC or NPL NTP servers or sources traceable to them (CERT-In Directions, 2022). Expect auditors to ask for evidence of both.
- Prepare test accounts for each role and a staging environment if production testing is restricted.
During and after the audit
- Name one technical contact who can answer questions the same day.
- Fix findings quickly and request the retest promptly; most certificates are issued only after closure.
- Keep a closure tracker with evidence for each fix. You will need it again next year.
Questions to ask an empanelled auditor before you sign
- Have you audited organisations in our sector, under the same regulator or tender format?
- Which named people will do the testing, and how much of it is manual?
- Will the final report or certificate be in the exact format our regulator or department expects?
- How many retest rounds are included, and how long does certificate issue take after closure?
- How will our test credentials, data and findings be stored and destroyed after the engagement?
Common mistakes that delay the certificate
The same problems recur. Scope changes midway because a new module went live during the audit. The staging environment does not match production, so findings cannot be reproduced. Developers fix one instance of a vulnerability but not the same pattern elsewhere, and the retest fails. Evidence for policies exists only as a draft nobody approved. Each of these adds weeks, and in a tender that can mean missing the deadline. Freeze releases in the audited scope during testing, and fix patterns, not just individual pages.
A note on cost and timelines
Empanelled firms set their own fees, and scope drives price. The fastest way to reduce both is to arrive with a clean application. Paying an empanelled auditor to find missing patches and default passwords is the most expensive way to discover them.
How Cehpoint can help
Cehpoint does not ask you to treat our testing as a substitute where empanelment is mandatory. What we do is help you get there prepared: a pre-audit VAPT and remediation engagement that finds and fixes issues before the formal audit, evidence and policy preparation, and support during the auditor's retest. For ongoing compliance work, our virtual CISO service keeps the evidence current year round. If you are unsure whether your requirement needs empanelment at all, a short consultation with a senior engineer can review the clause with you.