← CRA Compliance Checklists
SafetyDeadline: 11 December 2027

CRA Compliance Checklist: Perimeter Security & Smart Barriers

Default class for most perimeter security products, because Annex III lists no barrier, fence or perimeter detection category. Important Class I for a product whose core functionality is an access control reader (Annex III, point 1)

Perimeter security systems - including IP-connected vehicle barriers, automated gate systems, electric perimeter fencing with smart controllers, and ground radar detection systems - are safety-critical physical security products with digital elements. Most are default-class products, because classification follows core functionality (Article 7(1)) and Annex III lists no perimeter security category. Critical infrastructure deployment does not change the class. It raises the risk that the Article 13(2) risk assessment must address. Their compromise could enable physical security breaches at sensitive facilities.

14
checklist items
13
high priority
11 December 2027
deadline
Safety
sector
CRA Classification:Default class for most perimeter security products, because Annex III lists no barrier, fence or perimeter detection category. Important Class I for a product whose core functionality is an access control reader (Annex III, point 1)

Last updated 26 October 2026

1. Scope & Classification

Classify each perimeter product by its core functionality (Article 7(1))

highArticle 7(1), Annex III

Annex III lists no barrier, fence or perimeter detection category, so these products are default class. Use at nuclear, utility or government sites does not change the class. Address it in the Article 13(2) risk assessment. An access control reader is Important Class I (Annex III, point 1).

Use Module A internal control for default-class perimeter products

highArticle 32(1), Annex VIII

A Class I product, such as an access control reader, 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 yet, so today it needs a notified body.

Assess intersection with Construction Products Regulation for fixed perimeter infrastructure (bollards, barriers) installed in buildings or public spaces

mediumArticle 6, CRA / CPR (EU) 305/2011

Fixed vehicle barriers and gates installed as construction products may require CPR compliance alongside CRA. Coordinate both compliance tracks.

Compile SBOM covering barrier controller firmware, access control integration software, detection system firmware, and monitoring platform components

high

Perimeter security systems integrate barrier controllers, access control, CCTV, and monitoring platforms. Track all software components across the integrated system.

2. Product Security (Annex I Part I)

Implement strong authentication and authorisation for all barrier and gate control commands - prevent unauthorised barrier operation

highAnnex I, Part I(2)

Unauthorised control of vehicle barriers or gates could enable forced entry or trap legitimate users. All control commands must be authenticated and authorised. MFA for all remote access.

Implement hardware fail-safe behaviour - barriers must revert to a safe default state (secure-closed for access barriers) if network connection is lost or tampered

high

Safety and security critical perimeter hardware must have fail-safe behaviour independent of network status. Define safe defaults for each barrier type and implement in hardware.

Encrypt all perimeter system communications - barrier control commands, sensor data, and monitoring traffic

high

An attacker able to intercept and replay barrier control commands could operate barriers without authorisation. Encrypt all communications and implement command replay protection.

Implement tamper-evident logging for all barrier operations, configuration changes, and access events

high

Perimeter security audit logs are critical for security investigation and regulatory compliance. Logs must be forwarded to a centralised, tamper-evident system.

3. CVD Policy & Vulnerability Handling

Publish a CVD policy and security contact - perimeter security vulnerabilities have national security implications for critical infrastructure deployments

highArticle 13(1)

Perimeter security vulnerabilities are particularly sensitive. A confidential, expedited CVD process with physical security expertise is essential.

Define security support lifecycle appropriate to perimeter security infrastructure - minimum 10 years for commercial, 15 years for critical infrastructure

high

Perimeter security infrastructure is a long-term capital investment. Publish per-product security support end dates and provide migration planning support.

4. Article 14 Incident Reporting

Define Article 14 triggers - any exploitation affecting barrier control, perimeter detection effectiveness, or access authorisation is highest severity

highArticle 14(1)

Exploitation enabling unauthorised barrier operation or perimeter detection bypass at critical infrastructure is a national security incident requiring immediate Article 14 notification.

Coordinate Article 14 reporting with national security authorities for incidents at classified or critical infrastructure facilities

highArticle 14(2)

Perimeter security incidents at critical facilities require parallel notification to ENISA (CRA Article 14) and national security authorities. Pre-establish communication channels with relevant authorities.

5. CE Marking & Conformity Assessment

Complete the conformity assessment before CE marking and market placement

highArticle 32, Annex VIII

Under Module A, the manufacturer carries out the assessment and keeps the evidence in the technical file (Article 32(1)). A Class I access control reader needs a notified body today, because no CRA harmonised standard is cited yet (Article 32(2)).

Prepare technical file documenting barrier control security architecture, fail-safe design, authentication mechanisms, SBOM, and cryptographic specifications

highArticle 31, Annex VII

Technical documentation should clearly demonstrate fail-safe behaviour under adversarial conditions: network loss, power failure, tamper detection, and command injection attempts.

Track your Perimeter Security & Smart Barriers compliance progress in CVD Portal.

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 vehicle barriers operate on a standalone local controller with no internet connectivity - does CRA still apply?+

Yes. CRA applies to the product as placed on the market, not its deployment configuration. A standalone barrier controller with local network connectivity is a product with digital elements. Even if the customer does not connect it to the internet, the product must meet CRA requirements. Furthermore, many 'standalone' systems have temporary connections for commissioning, configuration, or maintenance that create real attack surfaces.

We supply smart barriers to government and defence sites - does CRA apply to defence applications?+

Products developed or modified exclusively for national security or defence purposes are outside the CRA (Article 2(7)). However, if your barriers are general commercial products also sold to non-defence customers, those civilian variants are in scope. Dual-use products require careful classification. If you supply the same product to both defence and commercial customers, the commercial product line is in CRA scope.

Our perimeter detection uses AI for vehicle classification - does the EU AI Act also apply?+

AI systems used in security screening and surveillance may be high-risk under EU AI Act Annex III. Perimeter detection AI that makes access control decisions or biometric identification could be subject to AI Act requirements including registration, conformity assessment, and transparency obligations. Both CRA and AI Act requirements must be met. Coordinate your compliance programmes for both regulations.

This checklist is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.

Need a CVD policy for Perimeter Security & Smart Barriers?

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

Browse templates →