CERT-In Empanelled Auditors List: How to Verify and Choose
CERT-In empanelment narrows the candidate list, but it does not pick a winner. Here is what to actually evaluate when shortlisting auditors for a regulated engagement.
- Published
- Last updated
- Reading time
- 3 min
- Filed under
- Compliance services · CERT-In · Procurement · Vendor Selection · Compliance
On this page (13)
Looking for the CERT-In empanelled auditors list? Start with CERT-In's official published register, not a copied list. Verify the auditing firm's legal name and empanelment status before evaluating its technical capability, methodology, reporting and retesting process.
What follows is the rubric we wish more procurement teams used.
What CERT-In empanelment actually verifies
The empanelment process certifies that a firm has documented processes, qualified personnel, technical capability across application and network testing, and reporting standards that meet CERT-In's expectations. Renewals are periodic, and empanelment can be revoked.
What it does not verify: depth of expertise in your specific industry, retention of senior staff, quality of remediation guidance, willingness to push back when scope discovery surfaces something the procurement team didn't anticipate. Those qualities you have to evaluate yourself.
Where to find the official CERT-In empanelled auditors list
CERT-In maintains the authoritative list of empanelled information security auditing organisations on its own website.
Official list: https://cert-in.org.in/PDF/Empanel_org.pdf
To verify an auditor:
- Open the current list from CERT-In's website.
- Search for the firm's registered legal name, not just its brand name.
- Confirm the empanelment status and applicable engagement period.
- Ask which legal entity will perform and sign the audit.
- Then evaluate the firm's technical qualifications, experience and deliverables.
The official list establishes empanelment. It does not, by itself, establish whether a firm is the best choice for a particular engagement.
Eight questions to ask
1. How long have you been empanelled, continuously?
Empanelment lapses happen. A firm empanelled since 2008 (which we are) has been audited multiple times across multiple panel cycles. A firm empanelled in the most recent cycle is still building its cumulative track record.
2. What is your team retention rate?
Penetration testing is delivered by people, and those people accumulate institutional pattern-matching. A firm where senior consultants have worked together for five years will catch things a freshly assembled team won't. Ask for tenure ranges of the actual L2/L3 reviewers.
3. Walk me through your methodology end to end.
Anyone running a real engagement should have a documented methodology that goes beyond "we'll scan and write a report." Ask about scoping, reconnaissance, manual versus automated testing, business-logic coverage, exploitability validation, and quality review layers.
4. Show me a sample report: anonymised, recent, in our industry.
The sample report tells you everything. Look at the depth of finding descriptions, the clarity of remediation guidance, the presence of exploit reproduction steps, and the structure of the executive summary. If the report is largely scanner output, you'll be paying for that.
5. What does your retesting process look like, and is it included?
The right answer is "retesting is included for all findings within a defined window." If retesting is extra, you've discovered a hidden cost line.
6. How do you handle scope discovery?
A test of "the customer portal" usually surfaces a third more attack surface than was originally scoped: APIs, admin paths, integration endpoints. The right vendor flags this in the kickoff and either renegotiates scope or proceeds with documented gaps. The wrong vendor silently misses things.
7. Who actually does the testing?
Some firms route the engagement through senior staff for the kickoff and reporting, but the testing itself is done by junior consultants with limited supervision. Ask explicitly: who tests, who reviews, who signs off, and what are their certifications.
8. Can I speak to a reference client in my regulator's footprint?
Procurement teams ask this too rarely. A CERT-In auditor with strong BFSI references will provide them. One without will deflect.
Red flags
- The vendor cannot produce a sample report.
- Retesting is unbundled.
- Pricing is dramatically below market without an explanation rooted in scope.
- The scoping conversation is rushed.
- Reporting timelines are vague.
- The team handling your engagement doesn't have OSCP, CRTP, or equivalent credentials.
What this looks like at Security Brigade
We've held CERT-In empanelment continuously since 2008. Engagements run through our Lemon platform with documented three-level review (L1 → L2 → L3) on every finding. Reports include exploit reproduction steps, business-impact framing, and remediation code. Retesting is included. We're happy to walk procurement teams through our methodology before they commit. Request a scoping call and we'll set it up.
Considering Security Brigade? Review our CERT-In audit services, methodology and engagement approach.
About the author
Security Brigade Editorial Team
Regulatory and Technical Research · Security Brigade
The editorial team reads the primary sources so you do not have to. Every regulatory piece here is written against the circular, Direction or standard itself and cites the paragraph, and every technical piece is reviewed by the practice lead who runs that kind of engagement.
Regulatory analysis by email
Field notes and new guides, delivered to your inbox.
We email you about this topic only; unsubscribe any time. See our Privacy Policy.
Continue reading
All articles →Paragraph 158: When a Breach Becomes Your Auditor's Deficiency
Three paragraphs of the RBI Directions, 2026 govern how a bank must handle its testing vendor. One of them is new: a later breach of a tested system becomes a recorded deficiency against the auditor, carried into renewal.
RBI Cybersecurity Framework in 2026: What Replaced It, and What Banks Must Do Now
The framework you are looking for was repealed on 31 July 2026, along with 627 other circulars. Six new Directions replaced it, one per class of regulated entity, all in force on issuance. What changed, what carried forward, and the cadence most guidance is stating incorrectly.
VAPT vs Penetration Testing: Which Do You Actually Need?
The terms get used interchangeably in Indian procurement RFPs, but they describe different things. Here is what the distinction means for scoping, cost, and the kind of report you walk away with.