← Industry Guides
TransportCRA Guide

EU Cyber Resilience Act Guide for Parking Management & Smart Parking Vendors

Default class for most products, including sensors, barrier controllers, ANPR cameras, pay stations and management software. Critical (Annex IV, point 1) for a physical payment terminal with a tamper-protected security box. Important Class I for an access control reader (Annex III, point 1) or an internet router or modem (Annex III, point 12)

Smart parking products, such as IoT-connected parking sensors, access barrier controllers, payment terminals with network connectivity and installed parking management software, are products with digital elements subject to the CRA. A cloud parking platform is in scope as a remote data processing solution when it serves the vendor's own parking products (Article 3(2)). Most parking products are default class. A physical payment terminal with a tamper-protected security box is a critical product (Annex IV, point 1). Vendors serving EU municipalities, airports, and commercial operators must implement Annex I security requirements, establish CVD policies, and prepare for CE marking before 11 December 2027, when those obligations apply. Payment data processing in parking systems adds PCI-DSS obligations that run alongside CRA requirements.

Article 13Article 14Annex IArticle 13Article 17Article 3
Deadline: 11 December 2027Classification: Default class for most products, including sensors, barrier controllers, ANPR cameras, pay stations and management software. Critical (Annex IV, point 1) for a physical payment terminal with a tamper-protected security box. Important Class I for an access control reader (Annex III, point 1) or an internet router or modem (Annex III, point 12)

Last updated 26 October 2026

CRA Scope and Classification for Parking Systems

Smart parking products sold to EU operators are products with digital elements under Article 3(1). Examples are IoT parking space sensors, barrier control units with network interfaces, ANPR (automatic number plate recognition) cameras with onboard processing, payment kiosks with internet connectivity and installed parking management software. A cloud parking platform is part of a product as its remote data processing solution when the vendor designs it for its own parking products and those products cannot perform one of their functions without it (Article 3(2)).

Classification follows core functionality (Article 7(1) and Article 8(1)). Annex III lists no parking, barrier or ANPR category, so most parking products are default class. Integration with municipal traffic signal control or smart city platforms does not change the class. It raises the risk that the Article 13(2) cybersecurity risk assessment has to address. Some products differ. A physical payment terminal whose components sit in a tamper-protected security box is a critical product (Annex IV, point 1), as Commission Implementing Regulation (EU) 2025/2392 describes. A pay station that integrates a payment terminal from another manufacturer stays default class, but the integrated terminal stays a critical product. An access control reader, such as a card reader for car park entry, is Important Class I (Annex III, point 1). A gateway whose core functionality is a router or a modem for connection to the internet is Important Class I (Annex III, point 12). Vendors should document their classification rationale for each product.

CRA reference:Article 3(1), Article 3(2), Article 7(1), Article 8(1), Article 13(2), Annex III, Annex IV

Technical Security Requirements for Parking IoT Infrastructure

Parking systems present several distinct security challenges addressed by Annex I. Barrier controllers and parking sensors are deployed in public spaces with physical access by the public, making tamper-resistance a physical security requirement that must be documented alongside cyber controls. Required security measures include: eliminating default credentials on all field devices and management consoles; encrypting all communications between field sensors, barriers, and cloud back-ends; ensuring firmware update mechanisms for field hardware are authenticated and can be executed remotely without physical access to each device; implementing access control on payment and operator APIs; and providing audit logs of all access events and configuration changes. For parking systems that process vehicle registration plate data or payment card information, additional data minimisation requirements under GDPR and PCI-DSS scope the security requirements beyond the CRA baseline.

CRA reference:Annex I Parts I and II

CVD Policy Under Article 13

Article 13 requires vendors to publish a coordinated vulnerability disclosure policy and maintain a dedicated security reporting channel. For parking management vendors, this is often a new operational requirement - the sector has not historically attracted significant security researcher attention, but cloud-connected payment and access control systems are increasingly in scope for security research. The CVD policy must specify how vulnerability reports are received and acknowledged, the expected remediation timeline, and how security advisories are communicated to operator customers. Because parking systems often process payment card data and vehicle tracking information, vulnerabilities affecting data privacy will attract regulatory attention beyond the CRA. Vendors should ensure their CVD policy addresses vulnerabilities affecting personal data processing and includes coordination with the relevant data protection authority where appropriate.

CRA reference: and , Article 13(7)

Article 14 Incident Reporting Obligations

When a parking management system vulnerability is actively exploited, Article 14 requires notification to the relevant national CSIRT within 24 hours. For parking vendors, active exploitation scenarios include: unauthorised access to barrier control systems enabling toll evasion; payment terminal compromise resulting in payment card data exfiltration; ANPR database access exposing vehicle movement data; and denial-of-service attacks on cloud platforms disrupting parking operations for multiple operators. Vendors must have incident response procedures that can identify exploitation, assess impact scope across the customer base, and generate regulatory notifications within the 24-hour window. Municipal operator customers may also have separate NIS2 incident reporting obligations where parking infrastructure is part of broader smart city or transport authority systems.

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

Conformity Assessment and CE Marking Pathway

Default-class parking products can use Module A internal control (Article 32(1)). ETSI EN 303 645 (for IoT components including parking sensors and barrier controllers) and ISO/IEC 27001 supplemented by product-specific threat modelling are useful references. They are not harmonised standards under the CRA and give no presumption of conformity. The technical file must include: system architecture diagrams showing all network interfaces and data flows; threat model and risk assessment; SBOM for all software components including cloud-side platform; evidence of security testing; documented CVD policy; and the declaration of conformity. Vendors operating across multiple EU member states should note that market surveillance authorities can request the technical file in the member state's language - preparation of translated documentation should be factored into compliance planning. An Important 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 in the Official Journal yet, so today a Class I product needs a notified body (Module B plus Module C, or Module H). A critical payment terminal needs a European cybersecurity certificate when a delegated act under Article 8(1) requires one. No such delegated act is adopted yet, so today it follows the Class II procedures, Module B plus Module C, Module H or a European cybersecurity certification scheme specified under Article 27(9) at assurance level at least substantial, for the requirements it covers (Article 32(4)).

CRA reference:Article 8(1), 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 parking sensors are simple Bluetooth or NB-IoT devices with no user interface. Are they in scope?+

Yes. The CRA applies to any product with digital elements that can connect to a network or other device, regardless of complexity or whether it has a user interface. Battery-powered parking sensors communicating via NB-IoT, LoRaWAN, or Bluetooth are in scope as products with digital elements. The security requirements are proportionate to the product's risk profile - a simple sensor with no actuator function and no payment data processing carries lower risk than a barrier controller, but still requires a published CVD policy, SBOM, and basic security controls under Annex I. A default-class sensor can use Module A internal control (Article 32(1)).

We provide parking management software as a SaaS platform to municipal operators. Are we in scope as a software manufacturer?+

It depends on what you supply. A pure SaaS platform is a service, and the CRA does not regulate it as a product (recitals 11 and 12). A cloud platform is in scope as a remote data processing solution when you design it for your own parking products and those products cannot perform one of their functions without it (Article 3(2)). Software you place on the market for installation, such as an on-premises management server or an operator app, is a product with digital elements in its own right. For in-scope products, you are the manufacturer responsible for Annex I security requirements, the CVD policy () and incident notification under Article 14. A SaaS provider of medium size or larger can fall under Directive (EU) 2022/2555 (NIS2) as a cloud computing service provider (recital 12). Municipal operator customers who use your platform to fulfil their own regulatory obligations under NIS2 will increasingly require evidence of your security practices as part of supply chain security assessments.

Our parking terminals process credit card payments. How does PCI-DSS interact with CRA security requirements?+

Check the CRA class first. A physical payment terminal with a tamper-protected security box is a critical product (Annex IV, point 1). A parking terminal that integrates a payment terminal from another manufacturer stays default class, and the integrated terminal stays a critical product of its own manufacturer. PCI-DSS and the CRA are complementary but distinct frameworks. PCI-DSS addresses payment card data security specifically; the CRA addresses product security broadly. Areas of overlap - encryption, access control, patch management, logging - can typically be addressed by a single set of controls that satisfies both frameworks. Where PCI-DSS is more prescriptive than the CRA (e.g. specific cryptographic requirements for cardholder data environments), the PCI-DSS requirement applies. Your CRA technical file can reference PCI-DSS compliance evidence for payment security controls, reducing duplication. Maintaining both frameworks in parallel requires clear documentation of which controls satisfy which regulatory obligation.

Guides for related sectors

Railway Signalling & Train Control VendorsRailway signalling and train control systems represent some of the highest-consequence digital products in EU critical infrastructure, and their manufacturers face both CRA obligations and stringent rail-specific safety certification requirements under the ERA framework. Vendors of ETCS, CBTC, interlocking systems, and level crossing controllers must navigate the intersection of functional safety requirements and the CRA's cybersecurity mandate. Most signalling and train control products are default-class products, because Annex III lists no railway, signalling or safety category and classification follows core functionality (Article 7(1)). Safety integrity raises the risk that the Article 13(2) cybersecurity risk assessment has to address. It does not change the class.Smart Traffic Management System VendorsSmart traffic management systems, including adaptive traffic signal controllers, urban traffic control platforms, variable message signs and connected intersection management systems, are default-class products under the CRA in most cases. Annex III lists no traffic category, and classification follows core functionality (Article 7(1)). The direct role of these systems in public safety raises the risk that the Article 13(2) cybersecurity risk assessment has to address. Vendors must implement robust security-by-design controls, establish mandatory CVD programmes, and prepare for notified body assessment where applicable. Traffic management systems in EU cities are increasingly targeted in demonstrations of disruptive cyberattack capability, making security programme maturity a reputational as well as regulatory imperative.

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 Parking Management & Smart Parking Vendors?

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

Browse templates →