Start with the organisation’s current status, then check whether its proposed team and audit scope fit your requirement. A comparable proposal should explain what will be tested, what evidence you will receive and how unresolved findings will be handled. Use the checklist below to record the questions still open before selection.
Checking an organisation? Follow CERT-In’s official empanelment page to its current organisation list, match the exact legal name and record the verification date. CERT-In official empanelment page
Verify the organisation, then define the work
Where an applicable requirement calls for a CERT-In empanelled information-security auditing organisation, check the current official list and the exact legal entity. Empanelment is not a personal credential for every team member, and it does not by itself define the audit you need. CERT-In: empanelment of information-security auditing organisations
Resolve these scope risks before selection
Check the proposed team’s competence for the system and methods involved. The organisation’s empanelment does not demonstrate experience with every cloud, application, industrial or legacy environment.
Define scope before selection so bidders price the same systems, methods and deliverables. An unclear boundary can leave an important integration outside the contracted assessment. Define the validation scope
Assign internal owners for access, evidence and operational coordination. Agree realistic availability for interviews, testing and remediation rather than assuming the audit can run without the system owner.
Carry forward unresolved findings and prior closure evidence. Explain system changes since the previous review so the next assessment does not rely on a stale scope.
What a better process looks like
Define the audit objective and applicable requirement before approaching candidates. Record mandatory coverage separately from optional assurance work.
Ask empanelled candidates for relevant experience with comparable systems specifically, not just confirmation of their empanelment status, since empanelment is necessary but not sufficient evidence of fit for a particular engagement.
Plan for the department’s own resourcing during the audit window, treating it as an internal project with a named coordinator, not an external activity that runs on its own.
Track remediation from one audit cycle into the next, so each audit builds on documented progress rather than restarting the evidence-gathering exercise from scratch.
Where this connects to a broader programme
Depending on scope, this usually connects to a wider responsibility and evidence matrix — clarifying control ownership, escalation and coordination requirements across departmental boundaries — which is the same foundation that makes each audit cycle faster and more useful than the one before it. Map control ownership and evidence
A procurement pack that can be compared fairly
Audit selection and scope checklist
This is a proposed procurement worksheet, not an official CERT-In form. Adapt it to your tender and operating constraints. Complete the decision column before comparing final proposals.
| Decision | Evidence to request | Suggested internal owner | Record before selection |
|---|---|---|---|
| Which organisation is bidding? | Legal name and current status-verification reference | Procurement | Entity matched; check date recorded |
| What is included? | Asset and interface inventory, environments and tested roles | System owner | Included and excluded systems agreed |
| How will testing be controlled? | Authorised methods, windows, stop conditions and escalation contacts | Security and operations | Production constraints and permissions agreed |
| What will be delivered? | Proposed reporting format and handling arrangements | Security lead | Evidence, limitations and recipients agreed |
| How will findings be closed? | Action ownership, retest scope and remaining-risk record | Risk and system owners | Closure and acceptance responsibilities agreed |
Use the same completed worksheet for each bidder. If a response is unclear, record the clarification needed instead of treating the box as complete. Keep sensitive access information and detailed findings out of a public procurement worksheet.

