EU Cyber Resilience Act Guide for HVAC & Climate Control Manufacturers
Default class for most products, including smart thermostats and commercial HVAC controllers. Important Class I for a gateway whose core functionality is an internet router or modem, or a switch (Annex III, point 12)
HVAC and climate control manufacturers placing networked heating, ventilation, air conditioning, and refrigeration systems on the EU market must comply with the EU Cyber Resilience Act. Article 14 incident reporting applies from 11 September 2026, and the remaining obligations apply from 11 December 2027. Connected HVAC controllers, building management system (BMS) integration gateways, and smart thermostats are products with digital elements. Most HVAC products, including smart thermostats and commercial HVAC controllers with BMS integration, are default class, because Annex III lists no HVAC or building automation category. A gateway whose core functionality is a router or a modem for connection to the internet is Important Class I (Annex III, point 12).
Last updated 26 October 2026
CRA Scope and Classification for HVAC Products
HVAC products within CRA scope include: connected room thermostats with WiFi or Zigbee connectivity, commercial HVAC unit controllers with BMS interfaces (BACnet, Modbus, LonWorks), refrigeration controllers with remote monitoring, air handling unit controllers with IP management, and building management system (BMS) gateways integrating HVAC systems into facility management platforms.
Classification follows core functionality (Article 7(1)). Annex III lists no HVAC, refrigeration or building automation category. Residential smart thermostats with consumer WiFi connectivity and companion app control are default class. Commercial and industrial HVAC controllers integrated into building management networks, or connected via BACnet/IP to facility management systems, are also default class. Data centre cooling and pharmaceutical cleanroom HVAC, where temperature and humidity control has direct product quality and safety implications, do not change the class. They raise the risk that the Article 13(2) cybersecurity risk assessment has to address. A BMS gateway whose core functionality is a router or a modem for connection to the internet, or a switch, is Important Class I (Annex III, point 12).
Technical Security Requirements for HVAC Controllers
HVAC controllers in commercial buildings are frequently connected to building management systems that share network infrastructure with IT systems - creating pathways for cyberattacks (multiple documented ransomware incidents entered building systems via HVAC VPN connections). CRA Annex I requirements address this systemic risk:
- Default credential elimination: Commercial HVAC controllers accessed via BACnet, Modbus, or web interfaces must not use factory default credentials. The Target breach (via HVAC contractor VPN access) demonstrated the consequences of poor HVAC access security.
- Encrypted management: Web-based and IP management interfaces must use HTTPS. BACnet/Secure Connect (BACnet over TLS) should replace legacy unencrypted BACnet where technically feasible.
- Authenticated firmware updates: Remote firmware updates to HVAC controllers must be cryptographically authenticated.
- Network segmentation: HVAC controllers must support isolated network configuration - not requiring connection to corporate IT networks for management.
- SBOM maintenance: Embedded RTOS and BMS communication protocol stack components must be documented in a comprehensive SBOM.
CVD Policy and Article 13 for HVAC Vendors
HVAC manufacturers - from large multinational climate companies to specialist controller manufacturers - largely lack formal CVD programmes. Security researchers who discover vulnerabilities in HVAC controllers (a documented research area given the Target breach publicity) find no structured disclosure channel. Article 13 mandates this change.
- Cover all IP-networked HVAC products and BMS integration hardware
- Be accessible via the corporate
security.txtand product security pages - Provide a submission channel for security researchers and building facility managers who identify anomalous HVAC behaviour suggesting compromise
- Define response timelines that account for the building operations context - HVAC vulnerabilities in critical facilities may require emergency response procedures
- Coordinate with building management system integrators who need to apply patches across facility deployments
CVD Portal enables HVAC manufacturers without dedicated security teams to establish a structured CVD programme, with intake, triage, and advisory publication workflows appropriate for organisations managing building technology products.
Article 14 Incident Reporting for HVAC Products
- Exploitation of HVAC controller vulnerabilities as a network entry point into building infrastructure
- Manipulation of temperature or environmental controls in critical facilities (data centres, pharmaceutical storage, hospitals)
- Use of HVAC management credentials to access broader BMS systems controlling fire, access control, and other building safety systems
The 24-hour ENISA notification must be triggered when exploitation is confirmed. For HVAC incidents affecting critical facility operators - hospitals, data centres, pharmaceutical manufacturers - parallel notification to the facility operator and potentially to sectoral CSIRTs is essential given the potential operational safety implications. Manufacturers should pre-establish direct notification protocols with major enterprise and critical facility customers for use in Article 14 scenarios.
Conformity Assessment and BMS Standards
Default-class HVAC products, residential and commercial, can use Module A internal control (Article 32(1)). A gateway whose core functionality is a router or a modem for connection to the internet, or a switch, is Important Class I. It can use Module A only when the manufacturer fully applies a harmonised standard, a common specification or a European cybersecurity certification scheme at assurance level at least substantial (Article 32(2)). No CRA harmonised standard is cited in the Official Journal yet, so today such a product needs a notified body (Module B plus Module C, or Module H). The route follows the class of each product, so a manufacturer with residential and commercial product lines decides it product by product.
- BMS communication security (BACnet/SC, Modbus TCP authentication)
- Web management interface security (HTTPS enforcement, authentication)
- Firmware update authentication mechanism
- SBOM for embedded software components
- CVD policy operational status
Vendors with products certified under BACnet Testing Laboratories (BTL) or with BACnet/Secure Connect implementation can use BTL test reports as supporting evidence for the communication protocol security aspects of CRA assessment.
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
Is a connected residential smart thermostat definitely Default Class under the CRA?+
Yes, in most cases. Connected residential thermostats provide remote temperature control and scheduling via a smartphone app. Annex III lists no thermostat or heating category, so they are default class and can use Module A internal control (Article 32(1)). Classification follows core functionality (Article 7(1)). A thermostat that integrates with a home energy management system for demand response programmes, interfacing with the grid operator, stays default class while its core functionality stays the same. That integration raises the risk that the Article 13(2) cybersecurity risk assessment has to address. A smart meter gateway within a smart metering system is a separate product and is critical (Annex IV, point 2). Manufacturers should document their classification rationale and review it if product capabilities are expanded through software updates.
How does the CRA interact with the F-Gas Regulation and Energy Performance of Buildings Directive?+
The F-Gas Regulation and Energy Performance of Buildings Directive (EPBD) govern the environmental performance and installation requirements for HVAC systems. The CRA is separate and governs cybersecurity of the digital elements in HVAC products. All three regulatory frameworks apply to HVAC manufacturers placing products on the EU market and must be satisfied independently. The EPBD's smart readiness indicator (SRI) framework may intersect with CRA connected HVAC requirements, as SRI credits require connectivity features that expand the CRA-relevant attack surface. HVAC manufacturers should ensure that SRI-qualifying connectivity features are implemented in accordance with CRA Annex I security requirements.
How do HVAC manufacturers handle security patches for controllers installed in buildings with limited IT infrastructure?+
Commercial HVAC controllers installed in buildings with limited IT infrastructure - older sites without enterprise IT support - present a significant patch delivery challenge. The CRA requires manufacturers to provide security updates throughout the declared supported lifetime and to make them reasonably accessible to operators. Practical approaches include: USB-based firmware update delivery for sites without reliable internet connectivity, field technician-assisted update programmes during scheduled maintenance visits, and cloud-based update delivery through secure connections where connectivity is available. Manufacturers should design update delivery mechanisms that account for the range of deployment contexts their products encounter, and must not declare supported lifetimes that exceed their realistic ability to deliver updates to all deployment scenarios.
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.
Need a CVD policy template for HVAC & Climate Control Manufacturers?
Download a free CRA-compliant vulnerability disclosure policy and deploy it in minutes.