CERT-In Audit & Safe-to-Host
What it is & who needs it
CERT-In empanelled audits underpin safe-to-host certificates, government hosting approvals and the CERT-In Directions of 2022, which among other things require covered entities to report notified cyber incidents within six hours and retain logs for 180 days. As an empanelled auditor, we conduct these audits and help you meet the Directions.
Who needs it: Government bodies and any organisation needing a CERT-In empanelled security audit.
What the CERT-In regime involves
- Security audits by empanelled firms for safe-to-host and regulatory sign-off
- Incident reporting of notified incident types within six hours
- Log retention for 180 days, available to CERT-In on request
- Time synchronisation of system clocks to approved sources
- Re-validation testing before a clean certificate is issued
How Virtual Caim helps
- Scope the systems needing an audit or Directions compliance
- Security audit of applications and infrastructure per CERT-In methodology
- Report with severity-ranked findings and fix guidance
- Remediation support, including incident-reporting and log-retention readiness
- Free re-test of every fix
- Clean final report / safe-to-host certificate for your acceptor
How we get you compliant
Audit, Governance & Compliance
Directions 2022 readiness: reporting workflows and log retention.
View service →VAPT & Offensive Security
The empanelled testing behind safe-to-host certificates.
View service →This is our home turf: Virtual Caim is CERT-In empanelled, with methodology, people and reporting vetted by India's national CERT, and 564+ audits delivered since 2021.
Don’t take our word for it
Virtual Caim Private Limited is listed in the official register of empanelled information security auditing organisations maintained by CERT-In, the Indian Computer Emergency Response Team. The register is public, so you can check us against it any time.
Opens the official CERT-In register at our listing (page 38).
CERT-In Directions 2022: who is covered, the six-hour clock, logs and consequences
Service providers, intermediaries, data centres, body corporate and Government organisations. The Directions were issued under section 70B(6) of the Information Technology Act, 2000 and became effective 60 days after issue, on 27 June 2022. The text names body corporate without any size threshold, so a company with an ICT estate should assume it is covered unless advised otherwise.
The incident types in Annexure I, which include targeted scanning of critical networks, compromise of critical systems, unauthorised access, website defacement, malicious code and ransomware, attacks on servers and network devices, identity theft and phishing, DoS and DDoS, attacks on critical infrastructure, SCADA and OT, data breach and data leak, attacks on IoT, attacks on digital payment systems and fake or malicious mobile apps. The six hours run from noticing the incident or being told of it, and the Directions allow reporting by email, phone or fax.
Entities must enable logs for all their ICT systems and keep them securely for a rolling 180 days within Indian jurisdiction. The logs must be provided to CERT-In with an incident report or when it orders them. Typical examples include firewall, IPS, SIEM, web, database, mail and VPN logs. Cloud-hosted estates need log export arrangements that satisfy the in-India condition.
All ICT system clocks must sync to the NTP servers of NIC or NPL, or to servers traceable to them. Entities with infrastructure in several geographies may use another accurate source if it does not deviate from NPL and NIC. Each entity must also designate a Point of Contact and send CERT-In its details in the Annexure II format, updating it as needed. CERT-In's requests for information go to that person.
Data centres, VPS providers, cloud service providers and VPN service providers must keep validated subscriber names, period of hire, allotted IPs, registration email and IP with timestamp, purpose of hire, validated address and contact numbers, and ownership pattern for five years after cancellation or withdrawal of registration. Virtual asset service providers, exchange providers and custodian wallet providers must keep KYC and financial transaction records for five years, with enough detail to reconstruct each transaction.
Failure to furnish information or non-compliance with the Directions may invite punitive action under section 70B(7) of the IT Act and other applicable laws. Separately, when CERT-In orders information or assistance in a set format and timeframe, missing that timeframe is treated as non-compliance.