← CRA Compliance Checklists
IndustrialDeadline: 11 December 2027

CRA Compliance Checklist: Energy Management Systems

Default class for most energy management systems, because Annex III lists no energy management category. Critical for a smart meter gateway within a smart metering system as defined in Directive (EU) 2019/944 (Annex IV, point 2). Important Class I for a gateway whose core functionality is an internet router or modem (Annex III, point 12)

Energy management systems (EMS), including building energy management, industrial energy optimisation, and grid-connected demand response systems, are products with digital elements under the CRA. Most EMS products are default class, because Annex III lists no energy management category (Article 7(1)). Grid connection and control of significant energy loads do not change the class. They raise the risk that the Article 13(2) cybersecurity risk assessment must address. A smart meter gateway within a smart metering system as defined in Directive (EU) 2019/944 is critical (Annex IV, point 2). Manufacturers must also address the intersection with the NIS2 Directive for operators in the energy sector.

16
checklist items
16
high priority
11 December 2027
deadline
Industrial
sector
CRA Classification:Default class for most energy management systems, because Annex III lists no energy management category. Critical for a smart meter gateway within a smart metering system as defined in Directive (EU) 2019/944 (Annex IV, point 2). Important Class I for a gateway whose core functionality is an internet router or modem (Annex III, point 12)

Last updated 26 October 2026

1. Scope & Classification

Classify each EMS product by its core functionality (Article 7(1))

highArticle 7(1), Annex III, Annex IV

Annex III lists no energy management category, so EMS software and controllers are default class. Control of industrial loads, smart meter interfaces and grid demand response raise the risk that the Article 13(2) risk assessment must address. A smart meter gateway within a smart metering system as defined in Directive (EU) 2019/944 is critical (Annex IV, point 2). A smart meter is not listed. A gateway whose core functionality is an internet router or modem is Important Class I (Annex III, point 12).

Choose the conformity assessment procedure for each EMS product by its class

highArticle 32, Annex VIII

A default-class EMS product can use Module A internal control (Article 32(1)). A Class I gateway needs a notified body today, because no CRA harmonised standard is cited yet (Article 32(2)). A smart meter gateway follows Article 32(4). No delegated act under Article 8(1) is adopted yet, so the Class II procedures apply. Where you need a notified body, select one with industrial cybersecurity expertise.

Assess intersection with NIS2 Directive obligations for customers in the energy sector

highArticle 6, CRA / NIS2 Directive

Energy sector operators are NIS2 essential entities. Your EMS must support their NIS2 security requirements. Align your product security architecture with IEC 62443 industrial cybersecurity standards.

Compile a full SBOM including EMS software, communication protocols (Modbus, DNP3, IEC 61850), and cloud platform components

high

EMS software stacks include industrial communication protocols with known vulnerabilities. Every component must be tracked and monitored for CVEs.

2. Product Security (Annex I Part I)

Implement strong authentication for all EMS interfaces - operator consoles, web portals, and API access

highAnnex I, Part I(2)

Weak authentication on EMS interfaces has led to major industrial incidents. MFA is required for all remote access. Local console access must also require authentication.

Encrypt all industrial communications including historian data, SCADA telemetry, and remote management traffic

high

Legacy industrial protocols (Modbus, DNP3) often lack native encryption. Use encrypted transport layers (TLS tunnels, VPN) for all EMS communications over untrusted networks.

Implement input validation and rate limiting on all EMS APIs to prevent injection and denial-of-service attacks

high

EMS APIs that accept energy consumption data or control commands must validate all inputs. A DoS attack on an EMS can disrupt industrial production.

Provide network segmentation capabilities to isolate EMS from corporate IT networks

high

EMS should operate in a dedicated OT network segment, not bridged to corporate IT. Provide clear deployment guidance and network architecture recommendations.

3. CVD Policy & Vulnerability Handling

Publish a CVD policy with a dedicated OT security contact and defined response timelines

highArticle 13(1)

Industrial EMS vulnerabilities can have broad impact across multiple customer sites. A responsive CVD process with OT security expertise is essential.

Provide a secure patch delivery mechanism supporting industrial maintenance windows and offline update capability

high

Industrial sites may not have reliable internet connectivity or the ability to apply patches immediately. Support cryptographically verified offline patch delivery.

Define a minimum 10-year security support period for industrial EMS products reflecting typical asset lifecycles

high

Industrial energy systems have 15–25 year asset lifecycles. A 10-year minimum security support commitment is appropriate; clearly publish per-product support end dates.

4. Article 14 Incident Reporting

Define Article 14 triggers for EMS incidents - focus on energy supply disruption, safety system impact, and data exfiltration from grid infrastructure

highArticle 14(1)

An actively exploited vulnerability in an EMS controlling grid-connected loads is a high-severity Article 14 trigger. Pre-define criteria to enable fast decisions.

Coordinate Article 14 ENISA reporting with customer NIS2 incident reporting obligations - incidents may require parallel notifications

highArticle 14(2)

An incident affecting an energy sector EMS customer may simultaneously trigger your Article 14 obligations and the customer's NIS2 reporting duties. Pre-agree coordination procedures with major customers.

5. CE Marking & Conformity Assessment

Complete the conformity assessment procedure for the product's class before CE marking and market placement

highArticle 32, Annex VIII

Default-class EMS products can complete Module A internal control (Article 32(1)). Where Article 32 requires a notified body, do not CE mark or place the product on the EU market without its certificate.

Prepare technical file aligned with IEC 62443 security levels to demonstrate comprehensive industrial cybersecurity

highArticle 31, Annex VII

IEC 62443 is the de facto standard for industrial cybersecurity. Aligning your CRA technical file with IEC 62443 Security Level 2 gives it a systematic structure. IEC 62443 is not a cited CRA harmonised standard, so it gives no presumption of conformity.

Issue EU Declaration of Conformity and affix CE marking - ensure DoC references the CRA

highArticle 20, Article 28

DoC must reference the CRA alongside any other applicable legislation (e.g. Low Voltage Directive, EMC Directive).

Track your Energy Management Systems compliance progress in CVD Portal.

Classify each product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.

Frequently asked

Is a building energy management system (BEMS) for a single office building the same classification as a grid-connected EMS?+

Yes. Both are default class unless their core functionality matches an Annex III or Annex IV category. Grid connection does not change the class (Article 7(1)). The risk differs. An EMS that connects to smart grid infrastructure, participates in demand response programmes, or controls significant grid-connected loads has greater potential for widespread impact. Your Article 13(2) risk assessment must address that. A smart meter gateway within a smart metering system as defined in Directive (EU) 2019/944 is critical (Annex IV, point 2).

Does the CRA require us to support legacy industrial protocols like Modbus?+

The CRA does not mandate or prohibit specific protocols. It requires that your product meet the Annex I security requirements, including encrypted communications. If your EMS must support legacy protocols like Modbus that lack native encryption, you must implement compensating controls. These include encrypted transport tunnels, network isolation, and access controls. You must document these in your risk assessment.

Our EMS vendor supplies the software and we integrate it into our hardware platform - who holds the CRA obligations?+

The entity that places the integrated product on the market is the manufacturer for CRA purposes and holds primary obligations. If you integrate third-party EMS software into your hardware platform and sell it as a product, you must ensure the combined system complies. You should obtain CRA compliance commitments and SBOM data from your software vendor and incorporate them into your technical documentation.

This checklist is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.

Need a CVD policy for Energy Management Systems?

Download a free CRA-compliant disclosure policy template and deploy it in minutes.

Browse templates →