EU Cyber Resilience Act Guide for Access Control & Physical Security Vendors
Important Class I — access control and identity management products are listed in Annex III
Access control and physical security vendors manufacturing electronic door controllers, card readers, biometric terminals, visitor management systems, and integrated security platforms for the EU market face Important Class I classification under the CRA. Physical access control products that process biometric data, authenticate identities, or control entry to secured facilities present elevated cybersecurity risk — a compromise of these systems can directly enable physical security breaches.
CRA Scope and Classification for Access Control Products
Access control products within CRA scope include network-connected door controllers, smart card and RFID readers, biometric terminals (fingerprint, face recognition, iris scanners), visitor management platforms, electronic lock hardware with management software, and integrated physical security management systems.
Annex III explicitly identifies identity management and access control products as Important Class I. This means virtually all networked access control products — from a single door controller with IP connectivity to an enterprise-scale physical security management system — require third-party conformity assessment. Products that process biometric data are subject to additional obligations under GDPR in parallel with CRA cybersecurity requirements. Vendors must address both sets of obligations: GDPR's data protection by design requirements and CRA's cybersecurity by design requirements simultaneously.
Technical Security Requirements for Access Control Products
Access control products must satisfy CRA Annex I requirements that directly address the security vulnerabilities historically prevalent in physical security systems:
- Elimination of default credentials: Access control panels, door controllers, and management software that ship with default administrative passwords are prohibited. Per-device unique credentials or enforced first-use configuration is required.
- Encrypted communications: Communication between door controllers, readers, and management servers must be encrypted. Legacy Wiegand interfaces are unencrypted by design — vendors using OSDP (Open Supervised Device Protocol) are better positioned.
- Firmware integrity: All firmware updates to access control hardware must be cryptographically signed and verified before installation.
- Biometric data protection: Where biometric data is stored on-device (e.g., fingerprint templates), it must be stored in encrypted, tamper-resistant storage.
- Audit logging: All access events, credential modifications, and administrative actions must be logged with attribution and timestamps, accessible to authorised facility security staff.
CVD Policy and Article 13 for Security Vendors
Physical security vendors have traditionally been reluctant to engage with vulnerability disclosure due to concerns about competitor exploitation of disclosed weaknesses and customer alarm. Article 13 makes this avoidance legally untenable — a formal, publicly accessible CVD policy is mandatory for all products with digital elements.
- Specify the scope of products covered
- Provide a secure submission channel (encrypted email or web form)
- Define a response timeline — particularly important for physical security where a disclosed vulnerability can directly enable facility intrusion
- Commit to coordinated disclosure with customers before public publication, given the physical security implications of unpatched access control vulnerabilities
The CVD policy need not publish technical details that would enable immediate physical attacks. The CRA requires a disclosure process, not immediately weaponisable security advisories. CSAF advisories can be structured to provide patch availability information and risk ratings without full vulnerability details.
Article 14 Incident Reporting for Physical Security Products
Active exploitation of access control vulnerabilities is a particularly serious class of security incident because it can enable physical security breaches — unauthorised access to data centres, government facilities, or critical infrastructure. Article 14's 24-hour ENISA notification requirement applies when exploitation is confirmed.
- Exploitation of management interface vulnerabilities to remotely unlock doors or disable alarm systems
- Cloning of card credentials due to weak authentication protocol implementations
- Compromise of biometric systems to create fraudulent identity enrolments
Vendors must maintain monitoring capabilities that can detect exploitation signals and must have escalation procedures that can generate an ENISA notification within 24 hours. The notification must identify the affected product, the nature of the exploitation, and any immediate mitigations (e.g., network isolation, temporary alternative access procedures). Customer notification in parallel with ENISA reporting is essential given the physical security implications.
Conformity Assessment for Class I Access Control Products
All networked access control products classified as Important Class I require third-party conformity assessment under Article 24. Vendors should plan assessment scope to cover:
- Annex I Part I technical security requirements — particularly authentication, encryption, and update integrity
- Biometric data security provisions (in conjunction with GDPR data protection impact assessment)
- CVD policy operational status
- SBOM completeness, including firmware components and management software dependencies
- Supported lifetime declaration and patch delivery process
Vendors with products certified under IEC 62443 (for industrial-grade access control), FIDO (for biometric authentication), or ONVIF Profile A (for access control interoperability) can leverage those certifications as supporting evidence. Access control vendors serving government and high-security facility markets may also face national security evaluation requirements (e.g., UK NCSC's CAPSS, German BSI schemes) that provide additional conformity evidence.
CVD Portal handles your CRA Article 13 obligations automatically.
Public CVD submission portal, 48-hour acknowledgment tracking, Article 14 deadline alerts, and CSAF advisory generation. Free forever for Access Control & Physical Security Vendors.
Start your free portalFrequently asked
Does the CRA apply to legacy access control systems already installed in buildings?+
The CRA applies prospectively to products placed on the EU market after the enforcement date. Legacy systems already installed are not subject to retroactive CRA conformity requirements. However, if a vendor continues to sell the same legacy product after September 2026, those new placements must be CRA-compliant. Vendors who provide software updates, expansions, or new modules for legacy systems that are treated as new product placements may trigger CRA obligations for the updated system. Customers with legacy systems should discuss CRA transition roadmaps with their vendors.
How do CRA requirements interact with GDPR for biometric access control?+
CRA and GDPR obligations are parallel and cumulative. CRA requires technical security measures to protect biometric data stored on access control devices (Annex I security requirements). GDPR requires a data protection impact assessment (DPIA) for biometric data processing and mandates data protection by design. The two obligations reinforce each other: meeting CRA Annex I security requirements for biometric storage is also a component of GDPR Article 25 (data protection by design). Vendors should address both in their product design and documentation — a DPIA for biometric processing and a CRA technical file are both required.
Are cloud-based access control management platforms within CRA scope?+
Yes. When a vendor provides both the physical access control hardware (door controllers, readers) and a cloud-based management platform, the combined system is a product with digital elements within CRA scope. The hardware device and the cloud management connectivity must both meet Annex I requirements. Specifically, the cloud management API must use strong authentication, the communication channel must be encrypted, and the cloud platform must not introduce attack surface into the physical access control system. Cloud-only access control software without associated hardware may fall outside strict CRA hardware scope but within NIS2 digital service provider obligations.
Compliance checklists for your products
Key CRA articles for Access Control & Physical Security Vendors
Need a CVD policy template for Access Control & Physical Security Vendors?
Download a free CRA-compliant vulnerability disclosure policy and deploy it in minutes.