EU Cyber Resilience Act Guide for Electronic Lock & Smart Door Manufacturers
Important Class I for smart home door locks that can be controlled or managed remotely (Annex III, point 17) and for access control readers, and for door controllers whose core functionality is authentication or authorisation (Annex III, point 1). Integration with building security or fire alarm systems does not change the class
Electronic lock and smart door manufacturers placing network-connected access control products on the EU market must comply with the CRA. Smart locks with Bluetooth, Wi-Fi, or Z-Wave connectivity, electronic door access controllers, and cloud-connected access management platforms are products with digital elements. These products control physical access to homes, offices, and facilities - meaning security failures can translate directly to physical security breaches. Manufacturers must implement robust cryptographic security, establish CVD programmes, and address the specific challenge of long-lifecycle physical security hardware.
Last updated 26 October 2026
CRA Scope and Classification for Access Control Products
Electronic access control products placed on the EU market - including smart padlocks, Bluetooth door locks, Wi-Fi enabled deadbolts, NFC access card readers, cloud-based access management platforms, and networked door access controllers - are products with digital elements under Article 3(1). Classification follows core functionality (Article 7(1)). A consumer smart lock for residential use that can be controlled or managed remotely is Important Class I (Annex III, point 17). Commission Implementing Regulation (EU) 2025/2392 also places in point 17 the hardware and software that centrally control such residential security products. NFC access card readers are Important Class I (Annex III, point 1). Networked door access controllers and access management software are Important Class I when their core functionality is authentication or authorisation (Annex III, point 1). Integration with building management, alarm and CCTV infrastructure does not change the class. Use at critical infrastructure facilities, such as data centres, utilities and government buildings, does not change it either. Both raise the risk that the Article 13(2) cybersecurity risk assessment has to address. An access card is a critical product when its chip is a secure element designed to at least AVA_VAN.4 (Annex IV, point 3). Consumer smart locks are also subject to the RED Delegated Act cybersecurity requirements from August 2025, creating a pre-CRA compliance baseline that manufacturers should leverage.
Technical Security Requirements: Physical Consequences of Cyber Vulnerabilities
Smart locks and electronic access systems present a unique security challenge: the consequence of a cybersecurity failure is physical access to protected spaces. This elevates the risk profile significantly compared to purely digital products. Annex I requires: eliminating default shared credentials - each device must be uniquely provisioned or require credential setup before activation; implementing cryptographic authentication for all lock/unlock commands, whether delivered via Bluetooth, Wi-Fi, NFC, or cloud API; protecting against replay attacks on wireless unlock signals; ensuring firmware update mechanisms are authenticated and cannot be used to deliver malicious firmware; implementing rollback protection preventing downgrade to vulnerable firmware versions; providing transparent access logs to device owners; and designing for graceful failure - the device behaviour on network or power failure must be documented and controllable. The SBOM must cover all wireless communication stacks and cloud connectivity libraries.
CVD Policy Under Article 13 for Physical Security Products
Article 13 requires a published CVD policy. For electronic lock manufacturers, the CVD programme is particularly important because vulnerabilities in smart locks - authentication bypass, Bluetooth replay attacks, firmware downgrade attacks - directly enable physical crime. Security researchers actively scrutinise smart lock products, and multiple high-profile disclosure events have demonstrated the reputational damage that results from inadequate CVD practices. The CVD policy must: establish a dedicated security reporting channel; commit to rapid response timelines given the physical security implications of lock vulnerabilities; specify how security updates are delivered to consumer products where users may not actively check for updates; and address how vulnerabilities are communicated to building managers and enterprise customers responsible for large-scale access control deployments. Coordinating with law enforcement where active exploitation is enabling physical crime is a prudent addition to the CVD policy.
Article 14 Incident Reporting
Article 14 requires notification to the relevant national CSIRT within 24 hours of confirmed active exploitation. For smart lock manufacturers, active exploitation - a vulnerability being used to gain unauthorised physical access to properties - may simultaneously constitute a criminal offence requiring law enforcement notification. The incident response plan must address both regulatory notification and law enforcement notification channels. Because smart lock exploits enabling physical crimes may not be immediately visible to the manufacturer (unlike cloud service exploits that generate server-side logs), vendors should implement telemetry that provides visibility into unusual unlock patterns, failed authentication attempts, and anomalous firmware query behaviour that might indicate active exploitation at scale. Consumer products require different monitoring approaches than enterprise access systems.
Long-Lifecycle Hardware and Security Support Obligations
Physical access control hardware has a long expected product lifetime - smart locks installed in residential properties or commercial buildings are commonly expected to last 5–10 years. Annex I Part II requires manufacturers to support products with security updates for the expected lifetime or 5 years, whichever is shorter. For smart lock manufacturers, this means maintaining cloud-side update infrastructure, backend authentication services, and security patch development pipelines for products sold over a long period. The support period must be clearly communicated at point of sale. When a product reaches end-of-support, manufacturers must notify customers in advance and cannot leave consumers with connected devices that are no longer receiving security updates without providing migration options. For cloud-dependent smart locks, the implications of cloud service termination for product functionality must be explicitly disclosed.
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 smart lock uses Bluetooth Low Energy for unlock commands. Are wireless protocol attacks in scope for our Annex I obligations?+
Yes. Annex I requires that all attack surfaces are addressed, including wireless communication interfaces. Bluetooth Low Energy vulnerabilities - relay attacks, replay attacks, MITM attacks on the pairing process - are documented attack vectors against smart locks and must be addressed in your product security design. Appropriate mitigations include: implementing rolling codes or challenge-response authentication for unlock commands; using encrypted BLE connections with proper key management; implementing proximity-based additional verification where feasible; and providing users with guidance on securing their Bluetooth unlock configuration. Security testing for your technical file should include wireless protocol security testing by a qualified penetration tester.
Our cloud backend provides the authentication service for all our smart locks. What happens to CRA compliance if we shut down the cloud service?+
If your smart locks are dependent on your cloud service for authentication, shutting down the cloud service effectively renders the locks inoperable or unsecured. The CRA requires that you maintain the product in a secure state for the declared support period. Cloud service termination before the support period ends is a significant CRA compliance issue. Manufacturers should design locks with local fallback authentication that operates independently of cloud connectivity, provide customers with advance notice of service termination sufficient to allow migration to alternative solutions, and document the impact of cloud service dependency clearly at point of sale. Regulatory authorities are likely to scrutinise premature cloud service terminations for connected consumer security products.
Our enterprise access controller is installed in an office building and integrated with the fire alarm system. Does this affect our CRA classification?+
No. Classification follows core functionality (Article 7(1)), and integration with a fire alarm system does not change it. A networked door access controller whose core functionality is authentication or authorisation is Important Class I (Annex III, point 1). An access control system that unlocks emergency exits on fire alarm activation performs a function that affects occupant safety in an emergency. That raises the risk that the Article 13(2) cybersecurity risk assessment has to address. A Class I product can use Module A self-assessment only when the manufacturer fully applies a harmonised standard, a common specification or a European cybersecurity certification scheme at assurance level substantial or higher (Article 32(2)). No CRA harmonised standard is cited in the Official Journal yet, so today it needs a notified body. The technical file must specifically address the security implications of the fire alarm integration, including what happens if the access control system is compromised during a fire emergency, and how the fail-secure/fail-open behaviour is configured and protected.
Compliance checklists for your products
Key CRA articles for Electronic Lock & Smart Door 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.
Need a CVD policy template for Electronic Lock & Smart Door Manufacturers?
Download a free CRA-compliant vulnerability disclosure policy and deploy it in minutes.