EU Cyber Resilience Act Guide for Smart Meter & AMI Manufacturers
Default class for smart meters, head-end systems, MDMS and in-home displays. Critical for a smart meter gateway within a smart metering system as defined in Directive (EU) 2019/944 (Annex IV, point 2), including a data concentrator whose core functionality is that of a smart meter gateway
Smart meter and Advanced Metering Infrastructure (AMI) manufacturers placing electricity, gas, and water metering products on the EU market must comply with the CRA. A smart meter is a default-class product, because Annex III and Annex IV list no meter category. A smart meter gateway within a smart metering system as defined in Directive (EU) 2019/944 is a critical product (Annex IV, point 2). Smart meters are deployed at scale across EU households - making systematic vulnerabilities in metering hardware or the AMI communication network a critical infrastructure concern that regulators will scrutinise closely.
Last updated 8 November 2026
CRA Scope and Classification for Smart Metering Products
Smart meters (electricity, gas, water), data concentrators, AMI head-end systems, meter data management systems (MDMS), and in-home display units with network interfaces are products with digital elements within CRA scope. Classification follows core functionality (Article 7(1)). Annex III and Annex IV list no meter category, so a smart meter is a default-class product. Critical infrastructure context, remote disconnect commands and deployment scale do not change the class. They raise the risk that the Article 13(2) cybersecurity risk assessment has to address. Annex IV, point 2 lists smart meter gateways within smart metering systems as defined in Directive (EU) 2019/944. Commission Implementing Regulation (EU) 2025/2392 describes them as gateways that control communication between the components of a smart metering system and authorised third parties, such as utility providers, and that protect the data flows with cryptography and firewalling. A smart meter gateway is therefore a critical product. A data concentrator is critical only when its core functionality matches this description. A communication module sold as a separate product is Important Class I when its core functionality is a network interface (Annex III, point 10) or a modem for connection to the internet, such as a cellular modem (Annex III, point 12). Integrating such a module into a meter does not change the class of the meter (Article 7(1)).
The scale of smart meter deployment - each unit communicating metering data and receiving remote commands from the DSO - makes the CRA's security requirements particularly consequential. A vulnerability affecting a widely deployed smart meter model could potentially be exploited at scale across millions of installations. Manufacturers must assess each product generation independently: the communication module (RF mesh, PLC, cellular), the meter head firmware, the data concentrator, and any associated AMI software are all products with digital elements requiring compliance.
Technical Security Requirements for Metering Products
Smart meter security has been subject to industry standards for years - DLMS/COSEM, PRIME, G3-PLC, and various national metering security specifications. CRA Annex I formalises and extends these requirements:
- Authenticated metering data: All metering data transmitted to DSO head-end systems must be authenticated and integrity-protected. DLMS/COSEM security suites provide the mechanism. Enable them by default.
- Encrypted command channels: Remote disconnect, tariff management, and firmware update commands must be encrypted and authenticated. Unauthenticated disconnect commands in metering protocols are a known attack vector.
- Firmware update authentication: Over-the-air firmware updates via RF mesh or PLC should be cryptographically signed. Avoid unauthenticated broadcast firmware updates.
- Key management: Long-lived symmetric keys shared across meter populations represent a systemic risk. Manufacturers should support unique per-device keys or PKI-based asymmetric authentication.
- Tamper detection: Physical tamper events must be logged and reported to the DSO management system.
CVD Policy and Article 13 in the Metering Sector
Smart meter manufacturers typically supply products to distribution system operators (DSOs) under tightly specified procurement contracts. This B2B-only distribution model does not exempt manufacturers from Article 13's CVD policy requirement - the policy must be publicly accessible regardless of the customer base.
- Cover all products including meter heads, communication modules, data concentrators, and head-end software
- Be accessible to energy sector security researchers and national CERTs who monitor metering infrastructure
- Define a response process that coordinates with DSO customers, who are the operators of the metering systems and have independent NIS2 obligations for their infrastructure security
- Commit to security advisory publication in CSAF 2.0 format, enabling automated processing by DSO vulnerability management systems
Given the scale of deployment, meter manufacturers should establish direct notification relationships with major DSO customers to ensure that patches reach the field before public disclosure where possible.
Article 14 Incident Reporting for Metering Vulnerabilities
An actively exploited smart meter vulnerability affecting millions of units simultaneously constitutes a potential critical infrastructure incident. Article 14's 24-hour early warning must be integrated into a multi-track incident response process:
- Coordinator CSIRT and ENISA (CRA Article 14) - one notification through the ENISA Single Reporting Platform reaches both at the same time. The early warning is due within 24 hours.
- DSO customers - immediate direct notification, as DSOs may need to implement emergency operational procedures. Each DSO reports its own significant incidents under NIS2.
- Impacted users - Article 14(8) requires the manufacturer to inform them and, where needed, give mitigation measures.
Manufacturers should pre-agree incident response coordination protocols with their major DSO customers so that Article 14 notifications and operational responses are synchronised. The 72-hour vulnerability notification must describe the affected product versions, exploitation method, and available mitigations including any emergency firmware update availability.
Conformity Assessment and Metering Standards Alignment
Smart meter manufacturers face a complex standards landscape: OIML (measurement accuracy), IEC 62056 (DLMS/COSEM), EN 62052/62053 (metering standards), and national metering standards coexist with the CRA's cybersecurity conformity requirements. The CRA conformity assessment is additive to measurement accuracy certification - both are required for market placement.
- The metering product's digital elements (communication module, firmware) must be assessed against Annex I Part I requirements
- The vulnerability management process (Annex I Part II) must demonstrate SBOM maintenance, patch delivery capability, and CVD policy operation
- The technical file must document the security architecture, including the key management approach and communication protocol security configuration
Manufacturers supplying into multiple EU member states must be aware that some national smart metering specifications include cybersecurity requirements that may be more stringent than the CRA minimum. Where national requirements exceed CRA requirements, both must be satisfied. A default-class smart meter can use Module A internal control (Article 32(1)). A smart meter gateway is a critical product. It needs a European cybersecurity certification scheme where a delegated act under Article 8(1) requires one. No such delegated act is adopted yet, so a smart meter gateway uses the Class II procedures (Article 32(4)). These are EU-type examination (Module B plus Module C), full quality assurance (Module H) or a European cybersecurity certification scheme specified under Article 27(9) at assurance level substantial or higher, for the requirements it covers (Article 32(3)). Plan notified body engagement for a smart meter gateway early, and complete the assessment before 11 December 2027, when the CRA conformity obligations apply.
Work through the CRA for each product in one workspace.
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
Are smart gas and water meters subject to the CRA, or only electricity meters?+
All smart meters with network interfaces and digital processing capabilities are products with digital elements within CRA scope - including gas, water, and heat meters. Gas, water and heat meters are default-class products, like electricity meters, because Annex III and Annex IV list no meter category. A smart meter gateway is a critical product (Annex IV, point 2). Commission Implementing Regulation (EU) 2025/2392 states that this category can include gateways for gas or heat metering that meet its description. Gas and water metering manufacturers should note that the metering accuracy certification requirements (under MID - Measuring Instruments Directive) apply separately and concurrently with CRA requirements. Both sets of conformity requirements must be satisfied before CE marking.
Who bears CRA responsibility when a DSO specifies the meter design and the manufacturer builds to spec?+
The entity placing the product on the EU market bears primary CRA responsibility as the manufacturer. If the manufacturer places the smart meter on the market under their own brand name - even when built to DSO specifications - the manufacturer is responsible for CRA conformity. A DSO becomes the manufacturer only if it places the product on the market under its own name or trademark, or substantially modifies it (Articles 21 and 22). In practice, most DSO procurement contracts specify that the meter supplier is responsible for regulatory compliance. Manufacturers should review their contracts and ensure that CRA compliance is explicitly allocated and that the DSO's security specifications are aligned with CRA Annex I requirements.
How do we manage the long deployment lifecycle of smart meters under the CRA?+
Smart meters have operational lifetimes of 10–20 years, far exceeding typical consumer electronics. The CRA requires manufacturers to provide security updates throughout the declared supported lifetime. For metering manufacturers, this means: declaring a realistic supported lifetime aligned with DSO contract terms (typically 15–20 years for utility infrastructure), establishing a security update delivery infrastructure that can operate for that full period, maintaining vulnerability monitoring capabilities for legacy meter generations, and planning the economic model for long-term support before products are placed on market. The cost of CRA-compliant lifecycle support must be factored into metering product pricing and DSO contract terms.
Key CRA articles for Smart Meter & AMI Manufacturers
Guides for related sectors
Free CRA tools
This industry guide is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.
Start a CRA risk assessment for Smart Meter & AMI Manufacturers
A pre-filled classification, asset inventory and STRIDE threat analysis for this product type, free to copy or seed into the app.