Frameworks · India regulatory
CERT-In Directions
CERT-In's cyber security directions set binding obligations. Specified cyber incidents must be reported within six hours of noticing them, and ICT logs kept for a rolling 180 days within the country. System clocks must be synchronised to national time sources, and a designated point of contact maintained.
Who it applies to
Service providers, intermediaries, data centres, body corporates and government organisations operating in India. This includes cloud and managed service providers serving Indian entities.
Main requirements
Incident reporting
Specified incident types reported to the designated authority within six hours of noticing, by a named point of contact.
Log retention
ICT system logs kept for a rolling 180 days and produced on request.
Time synchronisation
System clocks synchronised to the designated national time sources.
Contact and records
A registered point of contact kept up to date, and subscriber and customer records maintained where applicable.
How xmodo supports it
- 1
The incident record counts down the six-hour window and timestamps each step from detection to notification.
- 2
Log retention and clock synchronisation are held as controls with owners, evidence and expiry dates.
- 3
Notification drafts are built from the incident record, so the filing matches the recorded facts.
Related frameworks
CERT-In Directions shares requirements with the frameworks below. Controls you already run for any of them count towards CERT-In Directions as well.
Frequently asked questions
What do the CERT-In directions require?
Specified cyber incidents must be reported within six hours of being noticed, and ICT logs kept for a rolling 180 days in-country. System clocks must be synchronised to national time sources, and a designated point of contact maintained.
How is the six-hour deadline managed?
The countdown starts on the incident record at detection. The owner, deadline and notification trail are kept on the same record, and the filing is built from that evidence.
Does this overlap with sector regulations?
Yes, to a large extent. Reporting and logging obligations map to sector cyber regulations and ISO 27001, so one implementation meets each framework it is mapped to.
Can retention evidence be automated?
Retention settings and periodic checks are held as controls with evidence and expiry dates. xmodo raises a task before a lapse becomes a finding.