← CRA Compliance Checklists
NetworkingDeadline: 11 December 2027

CRA Compliance Checklist: Network Attached Storage (NAS)

Default class for consumer and enterprise NAS devices, because Annex III lists no storage category. Important Class I for a NAS operating system placed on the market as a standalone software product (Annex III, point 11)

Network attached storage devices are high-value targets - they store critical personal, business, and infrastructure data and are frequently targeted by ransomware and data exfiltration actors. Consumer and enterprise NAS devices are default class, because Annex III lists no storage category and classification follows core functionality (Article 7(1)). NAS vendors have a poor historical track record on patching, making CRA obligations in this area particularly significant.

15
checklist items
15
high priority
11 December 2027
deadline
Networking
sector
CRA Classification:Default class for consumer and enterprise NAS devices, because Annex III lists no storage category. Important Class I for a NAS operating system placed on the market as a standalone software product (Annex III, point 11)

Last updated 26 October 2026

1. Scope & Classification

Confirm all NAS devices with network connectivity are products with digital elements in CRA scope

highArticle 3(1)

All NAS devices - consumer, SMB, and enterprise - with network interfaces and updateable firmware are in scope. Both the hardware platform and the NAS OS software are covered.

Confirm the class of consumer and enterprise NAS products from their core functionality (Article 7(1))

highArticle 7(1), Annex III

Annex III lists no storage category, so NAS devices are default class. Marketing for business-critical storage, backup or DR use does not change the class. The integrated NAS operating system does not raise the class of the device. A NAS operating system sold as a standalone software product is Important Class I (Annex III, point 11).

Compile a full SBOM covering NAS OS (often Linux-based), Samba, NFS, web interface, and all bundled applications

high

NAS operating systems are complex: Linux kernel, Samba, NFS, web framework, backup agents, cloud sync clients, media servers, and more. All must be tracked.

2. Product Security (Annex I Part I)

Require unique per-device admin credentials or forced credential creation during setup - never ship with shared default passwords

highAnnex I, Part I(2)

Default NAS credentials (admin/admin, admin/password) are the primary attack vector for ransomware groups. CRA prohibits insecure defaults. Enforce unique credentials at first setup.

Disable remote (WAN) access by default - remote access must require explicit user opt-in and strong authentication

high

NAS devices directly exposed to the internet are a primary ransomware target. Remote access (QuickConnect equivalents, VPN, direct exposure) must be disabled by default and require MFA when enabled.

Implement automatic security update notifications and support for automated update installation

high

NAS vendors have a poor historical record on patching. CRA requires vulnerabilities to be remediated without undue delay. Implement prominent update notifications and consider auto-update defaults.

Implement network share access controls with least-privilege principles - prevent unauthenticated share access

highAnnex I, Part I(2)

Guest share access must be disabled by default. All shares should require authentication. Implement share-level permissions distinct from system admin credentials.

Provide ransomware resilience features - immutable snapshots, write-once storage options, and anomaly detection for mass file encryption

high

Ransomware is the primary threat to NAS devices. Immutable snapshots that cannot be deleted by ransomware significantly reduce impact. Consider making snapshot configuration prominently recommended in setup.

3. CVD Policy & Vulnerability Handling

Publish a CVD policy and security.txt - NAS platforms receive significant security researcher attention

highArticle 13(1)

NAS platforms are well-documented research targets. Multiple critical vulnerabilities have been published for major NAS vendors. A responsive CVD process is essential.

Define security support lifecycle per device model - consumer NAS minimum 5 years, enterprise NAS minimum 7 years from last sale

high

NAS devices are often used for 5–10 years. Publish per-model security support end dates prominently. Announce end-of-security-support at least 12 months in advance.

Issue CVE IDs and public advisories for all vulnerabilities fixed in NAS firmware updates

high

Generic release notes are insufficient. Formal CVE IDs and security bulletins enable customers to assess risk and prioritise patching.

4. Article 14 Incident Reporting

Monitor for active exploitation of NAS vulnerabilities - particularly pre-auth RCE and ransomware campaigns targeting your platform

highArticle 14(1)

NAS-targeting ransomware campaigns (Deadbolt, QLocker, etc.) demonstrate active exploitation patterns. Subscribe to threat intelligence feeds and monitor for your platform-specific campaigns.

Prepare and test the 24h / 72h / 14-day Article 14 notification process with named owners

highArticle 14(2)

Mass exploitation campaigns against NAS fleets require rapid response. Pre-prepare notifications and test the process before an incident occurs.

5. CE Marking & Technical Documentation

Prepare technical file with NAS OS security architecture, SBOM, penetration test results, and CVD policy documentation

highArticle 31, Annex VII

Given the history of significant NAS vulnerabilities, market surveillance authorities may scrutinise NAS technical files carefully. Invest in thorough documentation.

Issue EU Declaration of Conformity and affix CE marking before EU market placement

highArticle 20, Article 28

DoC must reference the CRA. NAS products with Wi-Fi should also reference the Radio Equipment Directive.

Track your Network Attached Storage (NAS) 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 NAS was placed on the market before September 2026 - do we need to issue security updates for legacy models?+

Most CRA obligations apply from 11 December 2027. A NAS model placed on the market before that date is subject to the CRA requirements only when it gets a substantial modification after that date (Article 69(2)). Article 14 reporting is the exception. From 11 September 2026 it applies to all in-scope products, including models placed on the market earlier (Article 69(3)). Security updates for legacy models still in use are good practice and may be required by existing consumer protection law. When CRA-era products reach their published end-of-support date, the obligation ends.

We enable UPnP on our NAS by default to make remote access easier - is this a problem under CRA?+

UPnP enabled by default is a significant CRA compliance risk. UPnP can automatically open port forwarding on routers, exposing NAS management interfaces to the internet without user awareness. CRA requires products to limit attack surfaces, including external interfaces, and requires a secure by default configuration. UPnP should be disabled by default, with clear user guidance on the security implications if enabled.

Our NAS OS is open-source (e.g. based on OpenMediaVault or TrueNAS) - how does this affect our CRA obligations?+

Using open-source NAS software as a base does not reduce your CRA obligations as the product manufacturer. You are responsible for the security of the complete product you place on the market. You must include all open-source components in your SBOM, monitor them for CVEs, and deliver patches. You may contribute security fixes back upstream, but your customers look to you for security support, not the open-source project.

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 Network Attached Storage (NAS)?

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

Browse templates →