Reg (EU) 2024/2847Generate dossier — €149
LIVE — Enforcement tracker · Deadline dashboard · Transposition status — Updated weekly from EUR-Lex, Safety Gate, OEIL & 12 official sourcesView regulatory intelligence →

You manufacture IoT devices in Southeast Asia and sell them to buyers in the European Union. It does not matter whether your factory is in Indonesia, the Philippines, Cambodia, or Myanmar — Regulation (EU) 2024/2847 applies to the product, not to the manufacturer's location. Every connected device on the EU market needs cybersecurity documentation under Annex VII by 11 December 2027. CRACheck generates it.

The Cyber Resilience Act does not have geographical exemptions. A connected sensor manufactured in Jakarta faces the same documentation requirements as one made in Munich. Article 2(1) applies to any product with digital elements placed on the EU market — a direct or indirect data connection to a device or network is sufficient. If your IoT devices contain firmware, connect via WiFi, Bluetooth, LoRa, or cellular, and reach EU buyers through any channel, you need an Annex VII dossier. CRACheck generates 8 documents in 15–25 minutes. €149 per device type. All processing happens in your browser.

Generate CRA dossier — €149Free: check your product classification

€149 one-time · 8-document ZIP · 15–25 minutes · Browser-side

Regulation (EU) 2024/2847 · Art. 31 + Annex VII · 8 documents · 100% browser-side

Key numbers

Art. 2(1)
Applies to any product with digital elements on the EU market
11 Dec 2027
Full enforcement deadline
€149
Per device type, one-time

How CRACheck works

You enter your product data. CRACheck structures the documentation per Article 31 + Annex VII.

1
Classify your IoT device
CRACheck determines if it is Default or Important under Annex III based on its function and connectivity
2
Enter device specifications
Sensor type, connectivity protocol, firmware version, data handling, power management, user interaction
3
Map cybersecurity features
How your device meets Annex I requirements: authentication, encryption, secure update, data minimisation, secure defaults
4
Document vulnerability handling
Your process for identifying, patching, and disclosing firmware vulnerabilities
5
Define support period
At least 5 years of security updates from market placement, or expected device lifetime if shorter (Art. 13(8))
6
Generate the 8-document dossier
Structured per Art. 31 + Annex VII for your specific device category
7
Provide to your EU buyer
The dossier supports their importer verification under Article 19

Common mistakes

SIZE EXEMPTION MYTH

"We are a small company — the CRA targets large manufacturers"

Regulation (EU) 2024/2847 applies based on product type, not company size. A connected sensor from a 20-person company in Manila faces the same essential cybersecurity requirements (Annex I) as one from a multinational. Article 13 does not scale obligations by company revenue. The regulation applies equally to all manufacturers who place products with digital elements on the EU market.

B2B ONLY ASSUMPTION

"We sell to system integrators, not end consumers — the CRA does not apply"

Article 2(1) covers products made available on the EU market through any channel. B2B sales to EU-based integrators, distributors, or OEMs are within scope. Your IoT sensor sold to a European smart building integrator is placed on the EU market at the point of that B2B transaction.

LOW-VALUE EXEMPTION

"Our devices cost under €10 — CRA compliance is disproportionate"

The CRA does not set minimum product value thresholds. A €5 connected sensor with firmware has the same documentation obligations as a €500 gateway. The proportionality principle applies to penalty calculation (Art. 64(6) considers the size of the undertaking), not to documentation obligations.

What the ZIP contains

8 PDF documents generated from your data. Each cites the specific article of Regulation (EU) 2024/2847 it complies with.

1

Product Classifier

Evaluates your IoT device against Annex III categories. IoT gateways may qualify as network management systems (Class I, item 6). Sensors with security functions may match other categories. Default devices use Module A self-assessment.

2

Technical Documentation

Art. 31 + Annex VII dossier for your IoT device: hardware and firmware design, connectivity, security architecture, production controls.

3

Risk Assessment

Annex I Part I analysis for IoT devices: remote exploitation, data interception, firmware tampering, battery-powered device constraints on security updates.

4

User Information

Annex II documentation: deployment guide, security configuration, update instructions, data handling transparency, support period, end-of-life procedure.

5

Declaration of Conformity

Art. 28 + Annex V. Your EU buyer needs this before market placement.

6

CVD Policy

Vulnerability disclosure for IoT devices: reporting channel, acknowledgement timelines, patch distribution, coordination with downstream users.

7

Notification Template

Art. 14 ENISA notification for actively exploited vulnerabilities in your IoT devices. Art. 14(2): early warning within 24h, notification within 72h, final report within 14 days.

8

Obligations Calendar

Enforcement timeline, support period, update milestones.

Mira antes de comprar — Descargar dossier de muestra (PDF, empresa ficticia) — Estructura real, artículos reales, formato real. Datos ficticios.

Generated from your data, in your browser. No data leaves your device.

What you pay

🧾 INTERNATIONAL REGULATORY CONSULTANCY
$8,000–$18,000
6–14 weeks. Few consultants cover Southeast Asian manufacturers for EU cybersecurity regulation. Requires remote engagement and document translation. Output: generic compliance report.
✓ Last regulatory check: 1 May 2026 · No substantive changes detected · View history