← Industry Guides
Industrial & ManufacturingCRA Guide

EU Cyber Resilience Act Guide for Facilities Management & CAFM System Vendors

Default class for most CAFM, IWMS and CMMS software, whatever its integrations with building control systems. Important Class I only for a product whose core functionality is a listed category, such as access control management (Annex III, point 1)

Vendors of computer-aided facilities management (CAFM) software, integrated workplace management systems (IWMS), and IoT-connected building maintenance platforms sold to EU customers are manufacturers of products with digital elements under the CRA. CAFM systems increasingly integrate with building management systems, access control, energy management, and workplace sensor networks - creating complex connected architectures that must be secured under Annex I. Vendors must have incident notification capabilities in place for 11 September 2026, when Article 14 applies, and CVD programmes in place for 11 December 2027.

Article 13Article 14Annex IArticle 13Article 17Article 3
Deadline: 11 December 2027Classification: Default class for most CAFM, IWMS and CMMS software, whatever its integrations with building control systems. Important Class I only for a product whose core functionality is a listed category, such as access control management (Annex III, point 1)

Last updated 26 October 2026

CRA Scope and Classification for CAFM Platforms

CAFM and IWMS software products sold to EU customers - including computerised maintenance management systems (CMMS), workplace booking platforms, IoT-connected occupancy monitoring systems, energy management software, and integrated building operations platforms - are products with digital elements under Article 3(1). Classification follows core functionality (Article 7(1)). Annex III lists no CAFM, IWMS, CMMS, building management system (BMS), HVAC or energy management category, so these products are default class. A CAFM platform that can issue control commands or configuration changes to BMS, HVAC, access control or energy management systems stays default class. The control path raises the risk that the Article 13(2) cybersecurity risk assessment has to address. A product whose core functionality is identity management or access control is Important Class I (Annex III, point 1). Integrating such a component does not by itself make the whole platform an important product (Article 7(1)). Vendors must record the classification of each product.

CRA reference:Article 3(1), Article 7(1), Article 13(2)

Technical Security for Integrated Workplace Management

CAFM and IWMS platforms typically collect and process sensitive operational data - maintenance schedules, occupancy patterns, energy consumption, and access event records - while connecting to building systems across multiple integration interfaces. Annex I requirements include: implementing authenticated and encrypted APIs for all integrations with building systems and IoT sensors; enforcing role-based access control with separation between facilities managers, contractors, and read-only occupants; providing multi-factor authentication for administrator access to the CAFM platform; securing mobile applications used by maintenance personnel with certificate-pinning and encrypted local storage; ensuring all data at rest is encrypted particularly for sensitive occupancy and access event records; and implementing comprehensive audit logs of all maintenance actions, configuration changes, and system access. The SBOM must cover the CAFM application platform, any mobile apps, and middleware components used for building system integration.

CRA reference:Annex I Parts I and II

CVD Policy Under Article 13

Article 13 requires a published CVD policy with a dedicated security reporting channel. For CAFM vendors, the CVD programme must handle: security researcher reports on the platform and its APIs; reports from facilities management professionals who identify unusual system behaviour; and internal security testing findings from periodic platform security reviews. The CVD policy should specify how security advisories are communicated to enterprise customers, many of whom will have their own change management processes governing when software updates can be applied. For vulnerabilities in CAFM components integrated with building control systems, the CVD policy should address coordination with building system vendors and the potential need for coordinated disclosure where the vulnerability spans multiple integrated systems. A machine-readable security.txt file at the vendor's primary domain establishes the standard researcher discovery mechanism.

CRA reference: and , Article 13(7)

Article 14 Incident Reporting

Article 14 requires notification to the relevant national CSIRT within 24 hours of confirmed active exploitation. For CAFM platform vendors, exploitation scenarios include: unauthorised access to building occupancy data enabling criminal targeting of unoccupied properties; compromise of access event records exposing sensitive information about personnel movements; and, for platforms integrated with building control, potentially unauthorised modification of HVAC or access control settings. The incident response plan must include cloud platform monitoring capable of detecting exploitation, a rapid customer notification process for active incidents, and pre-established CSIRT contact details for member states where the platform is deployed. Enterprise customers using the CAFM platform to manage NIS2-regulated facilities will have their own incident reporting obligations - vendor notifications must provide sufficient detail to support customers' regulatory responses.

CRA reference:Article 14(1), Article 14(2)

Conformity Assessment and Enterprise Procurement

Default-category CAFM software may self-declare CRA conformity under Module A (Article 32(1)). The technical file should demonstrate the platform's security architecture, API security controls, data encryption approach, and vulnerability management programme. ISO/IEC 27001 certification of the vendor's information security management system, while not a substitute for CRA conformity, provides valuable supporting evidence and is increasingly expected by enterprise facility management customers. For CAFM vendors seeking to win contracts with public sector organisations (government buildings, hospitals, universities), CRA CE marking will become a standard procurement requirement alongside NIS2 supply chain security questionnaire responses. Vendors should prepare a compliance summary document - covering CRA CE marking status, security update policy, CVD policy URL, and incident notification commitment - for inclusion in enterprise tender responses.

CRA reference:Article 28, Article 32, Annex VIII

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

Our CAFM system integrates with dozens of different BMS and IoT sensor vendors through APIs and middleware. Does the security of these integrations fall under our CRA obligations?+

Your CRA obligations extend to the security of the interfaces your CAFM product exposes and uses. For APIs and integration connectors that your platform provides, you are responsible for ensuring they are secured against authentication bypass, injection attacks, and data exposure. For third-party APIs your platform consumes, you must assess and document the security assumptions and requirements in your threat model. If a third-party integration partner's API is insecure, you should implement validation and sanitisation on data received from that interface and document the limitation. Supply contracts with integration partners should include security requirements aligned with your CRA obligations.

Our CAFM platform is sold as a SaaS product hosted in our data centre. Are we in scope as a SaaS vendor?+

Only in part. The CRA applies to products with digital elements made available on the market, and it does not regulate software as a service as such. It covers remote data processing only when the manufacturer designs it for a product with digital elements, and the absence of that processing would prevent the product from performing one of its functions (Article 3(2)). A SaaS CAFM platform with no software or hardware placed on the market is therefore outside the CRA. Installed software, mobile apps and on-site gateways that you place on the market are products with digital elements, and the cloud backend they need is their remote data processing. For those products, you are the manufacturer responsible for Annex I security requirements, Article 13 CVD policy, and Article 14 notification obligations. Your technical file should document the platform security architecture, your shared responsibility model for customer data security, and your incident response procedures. ISO 27001 and SOC 2 Type II certifications support the technical file but do not replace CRA conformity documentation.

Our CAFM product processes employee location data from IoT occupancy sensors. How does GDPR interact with our CRA obligations?+

Employee location and occupancy data is personal data under GDPR. Your CAFM platform is both a product with digital elements subject to the CRA and a data controller or processor subject to GDPR, depending on the contract structure with your customers. GDPR data protection by design and by default requirements (Article 25) align closely with Annex I security requirements - implementing these effectively satisfies obligations under both frameworks. Specific GDPR obligations include: data minimisation (only collect location data necessary for the stated purpose), access controls preventing unauthorised access to employee location records, retention limits, and data subject rights procedures. CRA and GDPR compliance should be addressed together in your product development and privacy engineering processes.

Guides for related sectors

Food & Beverage Automation System VendorsFood and beverage automation vendors supplying SCADA systems, batch controllers, filling line automation, and quality control inspection systems to EU food manufacturers must comply with the CRA as manufacturers of products with digital elements. The food industry's increasing connectivity - driven by Industry 4.0 adoption and supply chain traceability requirements - significantly expands the attack surface that must be addressed under Annex I. Ransomware attacks on food processing plants have demonstrated the severe operational consequences of inadequate OT security.HVAC & Climate Control ManufacturersHVAC 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).Industrial Automation & PLC VendorsIndustrial automation vendors placing programmable logic controllers, SCADA components, industrial gateways, and HMI 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. Most OT products, including PLCs, DCS, SCADA and HMI, are default class, because Annex III lists no industrial control category. An industrial router, modem or switch is Important Class I (Annex III, point 12). The CRA introduces mandatory CVD policies and incident reporting obligations that many OT vendors currently lack entirely.Robotics & Collaborative Robot ManufacturersRobotics and collaborative robot (cobot) manufacturers placing industrial robots, autonomous mobile robots (AMRs), and cobot platforms on the EU market must address CRA obligations alongside existing Machinery Regulation requirements. Most robots, AMRs and cobot platforms are default-class products under the CRA, because Annex III lists no robot or machinery category and classification follows a product's core functionality (Article 7(1)).

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 Facilities Management & CAFM System Vendors?

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

Browse templates →