← CRA Compliance Checklists
Safety & SecurityDeadline: 11 December 2027

CRA Compliance Checklist: Smart Cameras & Video Surveillance

Important Class I for consumer smart home security cameras, baby monitors and the hardware and software that centrally control them (Annex III, point 17). Default class for professional or commercial CCTV cameras, NVRs and video management software unless their core functionality is another listed category

Smart cameras and IP video surveillance systems are frequently compromised via default credentials and unpatched firmware - they were among the first device classes targeted by Mirai and similar botnets. The CRA's prohibition on default passwords and requirement for secure update mechanisms directly target these failure modes. Manufacturers must also consider GDPR obligations around video data and the NIS2 implications for critical infrastructure deployments.

19
checklist items
17
high priority
11 December 2027
deadline
Safety & Security
sector
CRA Classification:Important Class I for consumer smart home security cameras, baby monitors and the hardware and software that centrally control them (Annex III, point 17). Default class for professional or commercial CCTV cameras, NVRs and video management software unless their core functionality is another listed category

Last updated 26 October 2026

1. Scope & Classification

Confirm all IP cameras, NVRs, and video management software are in scope as products with digital elements

highArticle 3(1)

Any camera with network connectivity (Ethernet, Wi-Fi, LTE) is in scope. Analogue cameras without network interfaces are not.

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

highArticle 7(1), Annex III, point 17

A consumer smart home security camera or baby monitor is Important Class I (Annex III, point 17). A video doorbell is in the same point when its core functionality is home security. Hardware and software that centrally control these products, such as a home NVR or hub, are also in point 17 (Commission Implementing Regulation (EU) 2025/2392). A professional or commercial CCTV camera matches no Annex III point and is default class. Critical infrastructure or government use does not change the class. It raises the risk that the Article 13(2) risk assessment must address.

Compile SBOM for all camera firmware - including embedded OS, video codec libraries, and ONVIF implementation

high

Camera firmware typically includes complex video processing stacks with many open-source dependencies. Each must be tracked for CVEs.

2. Default Credentials & Authentication

Eliminate all default, hardcoded, or shared credentials - require unique credentials or forced setup on first access

highAnnex I, Part I(2)

Default credentials are the primary attack vector for IP cameras. Mirai and variants specifically exploit default camera credentials. This is explicitly prohibited by the CRA.

Require password change on first login - refuse access until a strong password is set

highAnnex I, Part I(2)

Cameras must not allow access with factory credentials beyond initial setup. Force password creation before full functionality is enabled.

Implement account lockout after repeated failed authentication attempts

high

Rate-limit and lock authentication endpoints to prevent credential brute-force attacks.

Support certificate-based authentication for API and ONVIF integration

medium

Enterprise and integration use cases require certificate-based authentication. Support both password and certificate auth.

3. Video Data Security

Encrypt all video streams in transit using TLS 1.2+ or DTLS for SRTP

high

Unencrypted video streams allow eavesdropping. RTSP over TLS (RTSPS) or WebRTC with SRTP/DTLS is required.

Encrypt video stored on-device (SD card) and in cloud storage

high

Video recordings may contain sensitive personal data. Storage encryption prevents data exposure if physical access is obtained.

Disable remote access and cloud services by default - require explicit user opt-in

high

Remote access features significantly increase attack surface. They should be opt-in, not enabled by default.

4. Firmware Security

Implement cryptographically signed firmware updates - reject unsigned or tampered updates

high

Camera firmware updates must be signed. The device must verify the signature before applying any update to prevent malicious firmware injection.

Enable automatic security update notifications or opt-in automatic updates

high

Camera owners rarely manually update firmware. Implement update notification and ideally automatic security patch delivery.

Implement secure boot to verify firmware integrity at startup

medium

Secure boot prevents running modified firmware even if an attacker has physical access to the device.

Disable unused services and ports (Telnet, UPnP, unnecessary HTTP APIs) by default

high

Camera attack surface must be minimal by default. Disable all services that are not required for core function.

5. CVD & Vulnerability Management

Publish a CVD policy and security.txt - camera firmware is heavily researched by the security community

highArticle 13(1)

IP cameras are among the most targeted consumer devices. A clear CVD policy is essential for receiving and responding to vulnerability reports.

Establish monitored vulnerability intake with 48h acknowledgment SLA

highArticle 13(3)

Camera vulnerabilities are frequently weaponised quickly. A fast intake and acknowledgment process is critical.

Define firmware support lifecycle - minimum 5 years from product launch

high

Cameras are often deployed for many years. Support periods must reflect realistic deployment lifetimes. Publish end-of-life dates.

6. Article 14 Incident Reporting

Monitor threat intelligence for active exploitation of your camera models

highArticle 14(1)

Camera CVEs are actively exploited by botnet operators. Subscribe to ICS-CERT, CISA KEV, and vendor-specific threat feeds.

Document Article 14 notification process for camera vulnerability exploitation events

highArticle 14(2)

Camera botnet recruitment is a common Article 14-triggering event. Pre-prepare your escalation and ENISA notification process.

Track your Smart Cameras & Video Surveillance 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

Do smart doorbells and baby monitors fall under the same requirements as professional CCTV?+

The Annex I requirements are the same. The conformity assessment route is different. A baby monitor and a consumer smart home security camera are Important Class I (Annex III, point 17). A smart doorbell with a camera is in the same point when its core functionality is home security. Such a product 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 camera needs a notified body. A professional CCTV camera matches no Annex III point. It is default class, so Module A internal control is open (Article 32(1)).

We use ONVIF for camera interoperability - does CRA compliance affect ONVIF implementation?+

ONVIF Profile S, T, and G implementations often involve unauthenticated or weakly authenticated interfaces. CRA Annex I requires that management interfaces use authenticated, encrypted communication. You must ensure your ONVIF implementation supports and enforces authentication, and disable ONVIF access without credentials.

Our cameras use UPnP for automatic router port forwarding - can we keep this?+

UPnP-based automatic port forwarding creates significant security risks by exposing cameras to the internet without explicit user action. CRA requires products to limit attack surfaces, including external interfaces. UPnP auto-port-forward should be disabled by default or removed entirely, with manual port forwarding or VPN as the recommended access method.

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 Smart Cameras & Video Surveillance?

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

Browse templates →