← Industry Guides
Safety & SecurityCRA Guide

EU Cyber Resilience Act Guide for Video Surveillance & CCTV Vendors

Important Class I for smart home security cameras and the home NVRs and apps that centrally control them (Annex III, point 17). Default class for professional and commercial IP cameras, NVRs, DVRs, video management software and analytics appliances, unless their core functionality is another listed category, such as an access control reader (Annex III, point 1)

Video surveillance and CCTV vendors placing IP cameras, network video recorders, video management systems, and cloud-based surveillance platforms 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. IP cameras have been among the most heavily exploited connected devices globally - Mirai and its variants specifically targeted IP cameras with default credentials - making CRA compliance both a regulatory obligation and a fundamental product security baseline for this sector.

Article 13Article 14Annex IAnnex IIIArticle 13Article 6
Deadline: 11 December 2027Classification: Important Class I for smart home security cameras and the home NVRs and apps that centrally control them (Annex III, point 17). Default class for professional and commercial IP cameras, NVRs, DVRs, video management software and analytics appliances, unless their core functionality is another listed category, such as an access control reader (Annex III, point 1)

Last updated 26 October 2026

CRA Scope and Classification for Surveillance Products

IP cameras, network video recorders (NVRs), digital video recorders (DVRs), video management software (VMS), cloud-based video surveillance platforms, and AI-based video analytics appliances are all products with digital elements within CRA scope. Classification follows core functionality (Article 7(1)). Annex III, point 17 lists smart home products with security functionalities, including security cameras. Commission Implementing Regulation (EU) 2025/2392 describes them as products that protect the physical security of consumers in a residential setting and that are remotely controllable or managed, together with the hardware and software that centrally control them. A consumer smart home security camera is therefore Important Class I. A home NVR or an app that centrally controls such cameras is also Important Class I. Point 17 covers smart home products only. A professional or commercial CCTV camera, an NVR, a DVR, video management software and an AI video analytics appliance for business premises match no Annex III point and are default class. A camera or reader whose core functionality is access control, such as a biometric reader at a door, is Important Class I (Annex III, point 1).

The documented exploitation history of IP cameras and the privacy implications of compromised surveillance systems do not change the class. They raise the risk that the Article 13(2) cybersecurity risk assessment has to address. An attacker gaining access to a building's IP camera infrastructure can surveil occupants, gain intelligence for physical security bypass, or use compromised cameras as botnet nodes. Vendors must assess each product line. A standalone analog PTZ camera with no network interface is outside scope. A WiFi-connected IP camera with cloud recording is within scope. It is Important Class I when it is a smart home product and default class when it is a professional CCTV product.

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

Technical Security Requirements for Surveillance Products

IP camera and NVR vendors have historically faced severe criticism for default credentials, unencrypted video streams, and absent update mechanisms. CRA Annex I Part I directly mandates remediation of these systemic weaknesses:

  • No default credentials: Each camera or NVR must ship with a unique device-specific credential or must require credential configuration at first setup. Shared default passwords are prohibited and have been responsible for mass exploitation events.
  • Encrypted video streams: Video data transmitted over IP networks must be encrypted. Unencrypted RTSP streams are a privacy violation and a CRA non-conformity.
  • Authenticated firmware updates: Camera firmware updates must be cryptographically authenticated. Firmware delivered without signature verification is a persistent exploit path used by threat actors to install persistent malware on IP cameras.
  • ONVIF security profile compliance: Cameras supporting ONVIF should implement ONVIF Security Profile compliance where relevant.
  • SBOM maintenance: Camera firmware typically contains extensive open-source components including embedded Linux distributions, media processing libraries, and network stacks. Complete SBOM documentation is required.
CRA reference:Annex I

CVD Policy and Article 13 for Surveillance Vendors

Video surveillance vendors have historically been slow to establish CVD programmes, with many vulnerability disclosures going unacknowledged or met with legal threats rather than coordinated remediation. Article 13 makes a formal, publicly accessible CVD policy a legal requirement for all products with digital elements.

  • Be publicly accessible via a security.txt file and a dedicated disclosure page
  • Cover all IP-enabled surveillance products
  • Provide a secure submission channel accessible to security researchers and facility security operators who may identify anomalous camera behaviour
  • Commit to acknowledgement within 5 business days and to security update delivery
  • Include a process for notifying end-users and system integrators who may have deployed vulnerable products

Given the scale of deployed IP camera installations, vendors should invest in automated update delivery mechanisms that can push security patches to installed camera populations without requiring manual intervention by end-users. The CVD policy advisory process must include direct operator notification, not only passive advisory publication.

CRA reference:Article 13(1), and

Article 14 Incident Reporting for Surveillance Products

IP cameras are among the most commonly exploited IoT devices globally. Article 14 requires manufacturers to notify ENISA within 24 hours of confirming active exploitation of a product vulnerability. For surveillance vendors, exploitation events often occur at massive scale due to the large installed base of devices and the historical prevalence of default credentials.

  • Mass scanning and exploitation of a product vulnerability is confirmed (e.g., via threat intelligence feeds)
  • A researcher or national CERT provides evidence of active exploitation in customer installations
  • Unusual firmware replacement activity indicating malware installation is detected via product telemetry

Vendors should implement telemetry collection (where legally permissible under GDPR) that can detect exploitation signals across the installed base. The 72-hour ENISA detailed report must include the affected product versions, the exploitation method, and the status of patch availability. For large installed bases, the final report, due no later than 14 days after a corrective or mitigating measure is available (Article 14(2)(c)) should address the deployment rate of the remediation patch.

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

Conformity Assessment and GDPR Privacy Obligations

A default-class professional camera, NVR or VMS can use Module A internal control (Article 32(1)). A Class I smart home security camera can use Module A only when it 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 a Class I camera needs a notified body for now (Module B plus Module C, or Module H). For vendors of cameras with AI-based analytics (facial recognition, behaviour analysis), CRA conformity assessment is additive to the GDPR privacy obligations and, where applicable, the EU AI Act obligations for high-risk AI systems.

  1. Authentication and credential management mechanisms
  2. Encrypted communication for video streams and management traffic
  3. Firmware update authentication and delivery mechanism
  4. SBOM for embedded firmware components
  5. CVD policy operational status and advisory publication history

Vendors should be aware that market surveillance authorities are expected to focus particularly on the surveillance sector given its documented exploitation history. Products that cannot demonstrate remediation of default credential and unencrypted stream issues before 11 December 2027 will face market withdrawal risk. Plan conformity assessment with sufficient lead time - Class I assessment processes typically require 3–6 months.

CRA reference: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

Do cloud-based surveillance-as-a-service platforms require CRA compliance?+

Cloud-based video surveillance platforms that include both hardware cameras and a cloud management service are within CRA scope for the camera hardware components. When the camera cannot perform one of its functions without the cloud service, and the manufacturer designed and developed that service, the service is a remote data processing solution and part of the product in CRA scope (Article 3(2)). Directive (EU) 2022/2555 (NIS2) can also apply to the provider of the cloud service. Vendors offering camera-plus-cloud packages must ensure CRA compliance for the physical cameras and their firmware, as well as securing the cloud management integration against the Annex I requirements. Pure cloud platforms without associated hardware products are primarily NIS2-governed.

Are AI-based video analytics cameras (face recognition, behaviour analysis) subject to additional regulations beyond the CRA?+

Yes. AI-based video analytics systems that process biometric data (facial recognition) or conduct behavioural surveillance are subject to the EU AI Act as high-risk AI systems and in some cases are subject to restrictions or prohibitions under the AI Act. GDPR applies to the processing of biometric data. CRA applies to the cybersecurity of the digital elements in the camera and analytics system. Vendors must satisfy all three regulatory frameworks. The AI Act's requirements for high-risk AI systems include conformity assessment, technical documentation, and transparency obligations that overlap with but are separate from CRA requirements.

How do we notify thousands of system integrators and end-users when a camera vulnerability is discovered?+

Large-scale customer notification for IP camera vulnerabilities is an operational challenge that vendors should address in their CVD policy before a vulnerability occurs. Mechanisms include: email notification to registered system integrators and product owners, push notifications via the companion app or cloud management platform, and publication of advisories in CSAF 2.0 format that can be automatically processed by integrator vulnerability management tools. Where cameras support remote update, an automatic security update push to all affected devices is the most effective remediation delivery mechanism. Vendors who cannot reach their end-user population with security updates have a fundamental CRA compliance problem that requires business process investment to resolve.

Guides for related sectors

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

Start a CRA risk assessment for Video Surveillance & CCTV Vendors

A pre-filled classification, asset inventory and STRIDE threat analysis for this product type, free to copy or seed into the app.

Open the starter →