Q-Cyber Magazine

Critical infrastructure and energy · 17 September 2026 · 3 min read

Incident reporting for operators of essential systems

Operators of energy, industrial and communications systems that are covered by CERT-In's 2022 directions must still report specified incidents within six hours and retain logs for 180 days, a duty later sector frameworks continue to invoke.

Abstract graphic of layered document sheets in Knowlcom blue

When a power, industrial or communications system is affected by a cyber incident, the first failure is often not technical. It is a late or incomplete report, because no one had agreed what "awareness" meant, or which clock had started.

The baseline has not been quietly replaced

Sector texts have multiplied, which can create the impression that the 2022 directions were a temporary measure. They were not. They remain the national CSIRT's standing instruction, and newer documents invoke them rather than retire them. An energy or industrial operator that is a body corporate, a service provider or a government organisation is in the covered class. A satellite or telecom provider is reminded of the same clocks in the 2026 space framework. A bank has a parallel supervisory channel, not an exemption.

The practical design is a single awareness event that fans out. The person or function who first notices a specified incident starts the clock. The point of contact can file the CERT-In report, and, where a sector supervisor exists, the parallel notice, without waiting for a complete forensic narrative. Logs that have been kept, time-synchronised, and held in India for 180 days make the follow-up possible. Logs that were never enabled do not.

Exhibit 1

Reporting channels that sit on top of, or beside, the 2022 CERT-In baseline

InstrumentWho it addresses in this contextReporting expectation
CERT-In directions, 28 April 2022Service providers, intermediaries, data centres, bodies corporate, government organisationsSpecified incidents within 6 hours; 180-day logs in India; current point of contact
CERT-In space and SatCom framework, February 2026Satellite providers, ground-station operators, government and private space entitiesReaffirms the 6-hour and 180-day duties for that estate
RBI cybersecurity directions, 31 July 2026Commercial banks (and parallel texts for other licences)Within 6 hours of detection on DAKSH, and notice to CERT-In
SEBI CSCRF, 20 August 2024SEBI regulated entitiesTimely reporting on the SEBI incident portal, with an incident-response plan and CCMP

Source: Official texts cited below. This table describes reporting channels; it does not assign unofficial sector-incident statistics.

Implications

  1. Define "noticing" for each essential system, in writing, and rehearse it on a holiday timetable.
  2. Keep a current, empowered point of contact who can file without a long internal chain.
  3. Enable and retain 180-day logs in India, with synchronised time, before the first incident.
  4. Map any sector portal (DAKSH, SEBI, or others) as a parallel path, not as a substitute for CERT-In where both apply.

What this means for critical infrastructure and energy

Essential-system operators will be judged, in the first hours, on whether they can report accurately and on time. The 2022 directions already tell them how. The later sector texts do not loosen that duty; they add channels. A rehearsed clock is the control.

Sources

  1. CERT-In Directions, 28 April 2022
  2. CERT-In space and SatCom framework, February 2026
  3. RBI commercial-bank cybersecurity directions, 2026
  4. SEBI CSCRF, 20 August 2024