The CER Directive, formally the Critical Entities Resilience Directive (Directive (EU) 2022/2557), is the European Union law that requires member states to identify critical entities providing essential services and obliges those entities to prevent, absorb and recover from disruptive incidents. Within cybersecurity law and the wider field of tech regulation, it is the physical and all-hazards counterpart to NIS2: NIS2 governs network and information security, while the CER Directive addresses natural hazards, terrorism, sabotage, insider threats and public health emergencies.
The directive was adopted in December 2022, entered into force on 16 January 2023 and had to be transposed into national law by 17 October 2024. It repealed Directive 2008/114/EC on European critical infrastructure, which had covered only energy and transport and focused on assets rather than on the continuity of services.
How the CER Directive identifies critical entities
The CER Directive works through a national identification process, not through self-assessment by companies. Each member state first adopts a national resilience strategy and carries out a national risk assessment by 17 January 2026, and then designates its critical entities by 17 July 2026, notifying each designated entity within one month.
An entity is designated when three criteria are met: it provides one or more essential services, it operates and has infrastructure on the territory of that member state, and an incident would have significant disruptive effects on the provision of the service. Authorities judge significance using factors such as the number of users relying on the service, dependence of other sectors, market share, geographic reach and the availability of alternatives.
The directive covers eleven sectors, listed in its annex together with subsectors and entity categories. The following table groups them and gives typical entities.
| Sector | Typical entities | Interplay with other EU law |
|---|---|---|
| Energy | Electricity, district heating, oil, gas and hydrogen operators | Also essential entities under NIS2 |
| Transport | Air, rail, water and road operators, ports, traffic management | Also essential entities under NIS2 |
| Banking | Credit institutions | Resilience duties largely covered by DORA |
| Financial market infrastructure | Trading venues, central counterparties | Resilience duties largely covered by DORA |
| Health | Hospitals, laboratories, pharmaceutical manufacturers | Also within NIS2 |
| Drinking water and waste water | Water suppliers, sewage treatment operators | Also within NIS2 |
| Digital infrastructure | Internet exchange points, DNS, cloud and data centers | Cyber duties under NIS2, physical duties partly exempted |
| Public administration | Central government bodies | National security functions excluded |
| Space | Operators of ground-based infrastructure | Also within NIS2 |
| Food | Large-scale production, processing and distribution | Not covered by NIS2 in the same way |
Obligations of designated critical entities
Once notified, a critical entity must manage all relevant risks to the continuity of its essential service, whether natural or man-made, accidental or intentional. The duties follow a fixed sequence with statutory deadlines measured from the date of notification.
| Obligation | Deadline or trigger | Substance |
|---|---|---|
| Entity risk assessment | Within 9 months of notification | All-hazards analysis, repeated at least every 4 years |
| Resilience measures | Within 10 months of notification | Technical, security and organizational measures |
| Resilience plan | Alongside the measures | Documented description of measures adopted |
| Liaison officer | On designation | Single point of contact with the authority |
| Initial incident notification | Within 24 hours of awareness | Basic facts of a significant disruption |
| Detailed incident report | Within 1 month | Causes, impact and response, where relevant |
The required resilience measures fall into four groups: preventing incidents through disaster risk reduction and climate adaptation; ensuring adequate physical protection through fencing, barriers, detection and access control; responding to and mitigating incidents through crisis management procedures and alert routines; and recovering through business continuity and alternative supply chains. Entities must also manage employee security, including the categories of personnel who may undergo background checks where national law permits.
Incident notification applies when an event significantly disrupts or could significantly disrupt the essential service. Authorities weigh the number and share of affected users, the duration of the disruption and the geographic area affected. Where an incident has or may have a significant impact on six or more member states, the authority informs the other states concerned.
Supervision, enforcement and European coordination
Each member state designates one or more competent authorities and a single point of contact for cross-border cooperation. Authorities may carry out on-site inspections, off-site supervision and audits, and may order entities to remedy deficiencies within a set period.
The directive does not fix fine amounts. Member states must lay down effective, proportionate and dissuasive penalties, so the size of sanctions varies considerably between countries. This differs from NIS2, which sets explicit maximum administrative fines.
At Union level, the Critical Entities Resilience Group, composed of member state representatives and the Commission, supports implementation and exchanges best practices. A further category, critical entities of particular European significance, applies to entities that provide the same or similar essential services to or in six or more member states. For these entities, the Commission can organize advisory missions to assess their resilience measures on request of the designating state or with the agreement of the entity.
How the CER Directive relates to NIS2 and DORA
The CER Directive and NIS2 were negotiated as a coordinated package and are designed to be read together. A designated critical entity is automatically treated as an essential entity under NIS2, so its cybersecurity risk management falls under NIS2 while its physical and non-cyber resilience falls under the CER Directive.
In the banking, financial market infrastructure and digital infrastructure sectors, much of the CER resilience chapter does not apply, because DORA and NIS2 already impose equivalent duties. Member states still identify such entities, which keeps them visible in national resilience planning.
| Feature | CER Directive | NIS2 | DORA |
|---|---|---|---|
| Legal form | Directive | Directive | Regulation |
| Risk focus | All hazards, mainly physical | Network and information security | ICT risk in finance |
| How scope is set | National designation | Size and sector rules | Type of financial entity |
| Initial incident notice | 24 hours | 24 hours early warning | Set by technical standards |
| Fines | Set by member states | Maximums set in the directive | Set by member states |
Practical challenges and common misconceptions
Implementation has proven uneven. Many member states missed the October 2024 transposition deadline, and the Commission opened infringement procedures against a large number of them. Organizations operating across borders therefore face staggered national timelines and differing interpretations of significance thresholds.
- Not a cybersecurity-only law: the directive deliberately targets physical and operational threats, while cyber risk is left to NIS2.
- No automatic scope by size: an entity is covered only after formal designation, unlike the size-cap mechanism of NIS2.
- Not only infrastructure owners: the focus is on the continuity of essential services, so operators without large physical assets can still be designated.
- Supply chains matter: resilience planning must consider dependencies on suppliers and other sectors, not only the entity’s own premises.
In simple terms
The CER Directive is the EU rulebook for keeping vital everyday services running when something goes badly wrong. Think of electricity, drinking water, hospitals, trains and food supply. Floods, storms, sabotage or a pandemic can interrupt them just as a hacker can.
Each country picks the companies whose failure would hurt society most. Those companies must study their risks, put protections and backup plans in place, and tell the authorities quickly when a serious disruption happens. In short, the law moves society from hoping nothing breaks to planning for the day something does.
A practical example
A regional drinking water utility serving about 900,000 residents is notified in mid-2026 that it has been designated a critical entity. Within nine months, its risk team completes an all-hazards risk assessment that identifies three main threats: river flooding at its main treatment plant, a long power outage and unauthorized access to remote pumping stations.
Over the following month, the utility adopts its resilience plan: flood barriers and raised electrical switchgear at the plant, backup generators with 72 hours of fuel, intrusion detection at the pumping stations and background checks for control-room staff. It names a liaison officer for the national authority.
When a storm later cuts power to two pumping stations for six hours, the utility sends an initial notification within 24 hours and a detailed report within a month. Because the generators started automatically, supply to residents continued without interruption, and the authority closed the case without corrective orders.