EU CRA | Regulation (EU) 2024/2847

EU CRA compliance advisory: from scope and classification to technical documentation and post-market reporting

We help manufacturers, brand owners and importers determine, from the official text, the class of each product family and the supply-chain role of each product line, and build a system that passes conformity assessment and keeps running afterwards.

The CRA entered into force on 10 December 2024. Article 14 reporting of actively exploited vulnerabilities and severe incidents has applied since 11 September 2026, including products already on the EU market. The remaining main obligations apply from 11 December 2027; products placed on the market afterwards need a conformity assessment, an EU declaration of conformity and the CE marking.

11 Sep 2026
Article 14 reporting already applies, including products already on the market
11 Dec 2027
Full application: conformity assessment, EU declaration of conformity, CE marking
€15M / 2.5%
Maximum fine for breaching Annex I or Articles 13 and 14 (whichever is higher)
≥ 5 years
Minimum support period, unless the expected use time is shorter

Scope check: in scope or not, which class, which assessment route

Start with the first check, then compare with the scope and classes below. The class decides which conformity assessment procedures are available: module A (internal control), module B+C (EU-type examination plus internal production control) or module H (full quality assurance).

CRA scope and conformity route: a 60-second first check

Each question follows the official legal text. Everything runs in your browser; nothing is sent anywhere.

1. Product type

First-check result

Answer the questions above; the result updates instantly.

This is a first check based on the official text, not legal advice. Core functionality follows the technical descriptions in Implementing Regulation (EU) 2025/2392 and the facts of each case.

Who must comply and who does not

In scope (data connection in the intended purpose; supplied on the EU market in a commercial activity)

  • Software downloaded or installed on the user side: mobile apps, desktop programs, browser extensions
  • Hardware with firmware: IoT devices, network equipment, industrial controllers, chips and modules
  • Hardware together with the app or software it needs, even when downloaded separately
  • Remote data processing designed by the manufacturer that the product needs (cloud back-end)
  • Open-source software monetised through payment, ads, subscriptions or mandatory personal data processing

Out of scope or covered by other rules

  • Websites and web applications used only through a browser that are not remote data processing of any product
  • Medical devices and in vitro diagnostic medical devices (MDR / IVDR)
  • Systems and components exclusively for M, N, O-category (and, by delegated act, L-category) vehicles
  • Aviation products certified under Regulation (EU) 2018/1139; equipment under the Marine Equipment Directive
  • Products developed exclusively for national security, defence or classified information; identical spare parts
  • Open-source software openly shared and not monetised (legal persons sustaining it may have steward obligations)

Product classes and conformity assessment procedures

ClassBasis and examplesProcedures available (Article 32)
DefaultCore functionality not listed in Annex III or IV, e.g. most appliances, sensors, ordinary apps and desktop softwareModule A self-assessment (stricter procedures may be chosen voluntarily)
Important, class I19 Annex III class I categories: identity and access management, browsers, password managers, anti-malware, VPN, network management, SIEM, boot managers, PKI, network interfaces, operating systems, routers and switches, MPU / MCU / ASIC / FPGA with security functions, virtual assistants, smart home security products, connected toys, health and children's wearablesSelf-assessment only with full application of harmonised standards published in the OJ, common specifications or a certification scheme at least "substantial"; otherwise module B+C or H with a notified body
Important, class II4 Annex III class II categories: hypervisors and container runtimes, firewalls and intrusion detection/prevention systems, tamper-resistant MPUs, tamper-resistant MCUsModule B+C, module H, or a certification scheme at least "substantial"
Critical3 Annex IV categories: hardware devices with security boxes, smart meter gateways and other advanced security devices, smartcards and secure elementsEU cybersecurity certification where required by a delegated act under Article 8(1); otherwise Article 32(3)

The class follows the core functionality of the product as a whole (Articles 7 and 8; Implementing Regulation (EU) 2025/2392). Integrating an operating system or firewall component does not change the class of the whole product: a router with a built-in firewall is still a router (class I). Open-source software with public technical documentation may use the Article 32(1) procedures (Article 32(5)).

Deliverables, mapped to the legal requirements

Scope and classification determination
Articles 2, 7, 8; Implementing Regulation (EU) 2025/2392
Supply-chain role determination (manufacturer, importer, distributor; own brand, ODM, OEM)
Articles 13, 19, 20, 21, 22
Cybersecurity risk assessment
Article 13(2) and (3)
Annex I gap analysis and remediation plan
Annex I Parts I and II
SBOM and component due-diligence records
Annex I Part II(1); Article 13(5)
Coordinated vulnerability disclosure policy, handling procedure and reporting drill records
Annex I Part II; Article 14
Support period rationale
Article 13(8); Annex VII point 4
Technical documentation, EU declaration of conformity, user information
Annexes VII, V and II; Articles 28 and 31

The most cost-effective path to full compliance

The law requires an outcome, not the most expensive method. Below is the lightest lawful path from the official text and our practice, the evidence you can reuse, the steps you can merge, and what must never be cut — cutting it voids the whole compliance.

Lightest lawful path

  • Confirm scope first: web apps used only through a browser, components exclusively for type-approved vehicles and MDR/IVDR medical devices are outside the CRA; do not build for products it does not cover.[Basis:Articles 2, 3(1); draft guidance §2.2, §9.3]
  • Classify by core functionality of the whole product, not by embedded components: a router with a built-in firewall is class I, not II; most ordinary apps, sensors and appliances are default products that can use module A self-assessment with no notified body.[Basis:Articles 7, 8, 32; Annex III]
  • For class I, fully applying CRA harmonised standards once they are published in the OJ allows self-assessment and saves the notified body fee and queue; prepare the Annex I evidence now so it can be mapped the day the standards appear.[Basis:Article 27, Article 32(2)]
  • Products placed on the market before 11 Dec 2027 and not substantially modified afterwards need no re-assessment; separate them when you inventory product lines and invest only in the models that need it.[Basis:Article 69(2)]
  • Set the support period at the expected use time (at least five years) rather than promising longer by default, and document the rationale in the technical documentation.[Basis:Article 13(8); Annex VII point 4]

Evidence you can reuse

  • ISO 27001 risk methodology, incident management and supplier procedures can serve as the organisational baseline for the Article 13 risk assessment and the Annex I Part II vulnerability handling process.[Basis:Article 13(2); Annex I Part II]
  • IEC 62443-4-1 secure development and 4-2 technical requirements can serve as implementation evidence for Annex I Part I (without presumption of conformity).[Basis:Article 27; Annex I Part I]
  • One SBOM serves the CRA technical documentation, customer procurement requirements and AI Act technical documentation.[Basis:Annex I Part II(1); AI Act bridge in Article 12]
  • A high-risk AI system meeting CRA Annex I with a declaration of conformity is presumed to meet AI Act Article 15 cybersecurity; no second set is needed.[Basis:CRA Article 12]

Steps you can merge

  • Merge Article 14 reporting with your existing security incident response (ISO 27001 incident management, NIS2 reporting) into one flow; only the 24h/72h/final-report deadlines and the single reporting platform are added.[Basis:Articles 14, 16]
  • Merge the Annex VII technical documentation with the technical files of other CE directives (RED, LVD, Machinery); the CRA adds only the cybersecurity chapter.[Basis:Annex VII; Article 31]
  • One risk assessment and one determination per product family, with model differences in annexes.[Basis:Article 13(2); draft guidance §6]

Never cut (cutting voids compliance)

  • Article 14 reporting has applied since 11 Sep 2026 including products already on the market; having no reporting mechanism is a current breach (€15M / 2.5%).[Basis:Articles 14, 69(3), 64(2)]
  • Class II, and class I that cannot self-assess, always need a notified body; an IEC 62443 or ISO 27001 certificate cannot replace it.[Basis:Article 32]
  • No known exploitable vulnerabilities at placing on the market, security updates free of charge and separate from functionality updates, vulnerabilities handled throughout the support period: hard Annex I requirements.[Basis:Annex I Part I (2)(a), Part II (2)(8); Article 13(8)]
  • Keep the technical documentation and declaration of conformity for at least 10 years or the support period, whichever is longer.[Basis:Article 13(13)]

Cases and evidence

Anonymised summaries; client names are withheld under NDA.

IoT equipment exporter

Completed the CRA product classification assessment, confirmed the product as an Annex III class I important product, and established the SBOM, vulnerability disclosure process and 72-hour ENISA notification mechanism.

Industrial automation equipment manufacturer

Completed the Annex I security requirements gap analysis, integrated the IEC 62443 industrial cybersecurity standard, and established a product security update mechanism (minimum five years of support).

Enterprise security SaaS vendor (with desktop client)

Initially assumed pure SaaS was out of scope. Winners Consulting's diagnosis confirmed that the Windows/macOS desktop client bundled with the SaaS is installed on the user side and is a product with digital elements in the CRA default category. Completed the desktop client SBOM and the security update mechanism design, and entered European enterprise procurement lists.

Mobile app developer (connecting to enterprise IoT devices)

Completed the Annex I security requirements gap analysis, the SBOM and the vulnerability disclosure policy; passed the EU distributor's CRA compliance review and launched on the European market on schedule.

Named clients (published with client authorisation)

As of 2026-10, Winners has 6 EU Cyber Resilience Act (CRA) compliance engagements (names withheld under NDA).

Other engagements are anonymised by industry under NDA.

Decision tools: check your SBOM and technical documentation

Both tools run in your browser; files are not uploaded and nothing is stored. For scope and class, use the 60-second first check in section 02.

SBOM check against the minimum in Annex I Part II(1)

Choose a CycloneDX or SPDX JSON file. It is analysed in your browser only; nothing is uploaded or stored.

Matching against known vulnerabilities and ongoing monitoring require querying vulnerability databases, which this page does not do so that your file never leaves your browser. Ahura's SBOM vulnerability management runs on-premises in your environment and is open for PoC booking. Apply for an Ahura PoC

Technical documentation check (Annex VII)

Tick what you already have. Ticks stay on this page only; nothing is sent or stored.

0/13 ready

Point 1(c) applies to hardware only; the SBOM under point 8 is provided on a reasoned request from a market surveillance authority.

Cross-service evidence reuse matrix

This matrix shows which management system evidence can be shared among ISO 27001, ISO 27701 and ISO 42001, and which privacy-, AI- or product-specific obligations must be built independently. CRA, GDPR and the EU AI Act are laws, not management system standards; an ISO certificate cannot replace fulfilment of legal obligations.

Legend:Primary — Primary: core requirement of that standard — must be built.Shared — Shared: if already built for ISO 27001, can be directly extended without rebuilding.Partial — Partial: provides supporting context, but the corresponding legal obligation still needs to be fulfilled separately.
Evidence typeISO 27001ISO 27701:2025ISO 42001:2023CRA (law)
A. Management system core
Governance policies, objectives and KPIs (ISMS / privacy / AI policy)
Note: ISO 27701 and 42001 can extend the 27001…

ISO 27701 and 42001 can extend the 27001 policy with privacy or AI statements rather than rebuilding the whole framework. CRA is a product law with no management-system policy requirement.

PrimarySharedShared—
Risk assessment method and records
Note: ISO 27701 privacy risk and ISO 42001 AI …

ISO 27701 privacy risk and ISO 42001 AI risk can share the 27001 risk framework method, but each has its own risk sources (privacy threats, AI bias etc.) that must be assessed separately.

PrimarySharedShared—
Supplier and third-party management procedure
Note: 27701 adds processor contract clauses (G…

27701 adds processor contract clauses (GDPR Art. 28); 42001 adds AI supplier responsibility allocation (A.10). CRA upstream component obligations (SBOM, notification) are product duties and must be built separately.

PrimarySharedSharedPartial
Internal audit and management review records
PrimarySharedShared—
Document control, record retention, training records
PrimarySharedShared—
Security incident management procedure (including breach notification)
Note: CRA Art. 14 has its own 24/72-hour vulne…

CRA Art. 14 has its own 24/72-hour vulnerability and serious-incident notification to ENISA, separate from ISMS incident management. Existing incident procedures can inform a PSIRT baseline, but CRA-specific requirements must be built on top.

PrimarySharedSharedPartial
B. Privacy-specific (ISO 27701 / GDPR)
PII inventory and data flow mapping (RoPA)
Note: GDPR Art. 30 requires controllers and pr…

GDPR Art. 30 requires controllers and processors to maintain a RoPA; ISO 27701 provides the management framework for building it, but the mandatory fields and maintenance obligation come from the legal text of GDPR.

—Primary——
Data subject rights procedures (access, erasure, objection, etc.)
—Primary——
Privacy impact assessment (DPIA) report
Note: ISO 27701 privacy risk assessment maps c…

ISO 27701 privacy risk assessment maps closely to the GDPR Art. 35 DPIA obligation, but when a DPIA is mandatory, the nine EDPB WP248 criteria and the obligation to consult the supervisory authority (Art. 36) are legal requirements outside ISO 27701.

—Primary——
Cross-border transfer mechanisms (SCC, TIA, supplementary measures)
Note: ISO 27701 requires identification and re…

ISO 27701 requires identification and recording of cross-border transfers, but which SCC module (Commission Decision (EU) 2021/914) to use, the transfer impact assessment (TIA) and supplementary measures are legal determinations under GDPR Arts. 44–49, requiring legal expertise.

—Partial——
C. AI-specific (ISO 42001 / EU AI Act)
AI system inventory (in-house, purchased, SaaS, generative AI)
Note: EU AI Act Art. 49 requires high-risk AI …

EU AI Act Art. 49 requires high-risk AI system registration in the EU database; the AI system inventory is the foundation for that registration, but the registration obligation itself is a legal requirement.

——Primary—
AI risk assessment and AI system impact assessment (ISO 42005)
Note: ISO 42001 A.5 and ISO/IEC 42005 (28 May …

ISO 42001 A.5 and ISO/IEC 42005 (28 May 2025) provide the impact assessment method; EU AI Act Art. 27 fundamental rights impact assessment (FRIA) can reuse the same facts and analysis, but the FRIA itself is a legal obligation, particularly for deployers of high-risk systems.

——Primary—
Data and model life-cycle controls (A.6, A.7)
——Primary—
Third-party AI and generative AI usage governance (A.9, A.10)
——Primary—
D. Product-specific (CRA legal obligations)
Software bill of materials (SBOM) and component vulnerability tracking
Note: CRA Annex I Part II §1 requires manufact…

CRA Annex I Part II §1 requires manufacturers to identify and document components (including open source); SBOM is a product-level obligation with no direct counterpart in a management system; it cannot be substituted by ISO 27001 or 42001 documents.

———Primary
Coordinated vulnerability disclosure policy (CVD) and six-step PSIRT process
Note: Existing ISMS incident management can in…

Existing ISMS incident management can inform the PSIRT design, but CRA Annex I Part II specific requirements (disclosure channel, obligation to notify component maintainers, 14-day final report) must be built independently.

———Primary
24/72-hour notification mechanism to ENISA and drills
Note: CRA Art. 14 §2, 4; applicable from 11 Se…

CRA Art. 14 §2, 4; applicable from 11 Sep 2026 (including already-marketed products). Taiwanese manufacturers without a principal EU establishment notify per Art. 14 §7 to the CSIRT of the country of the authorised representative or the importer.

———Primary
Annex VII technical documentation and EU declaration of conformity
Note: CRA Annex VII requires documentation of …

CRA Annex VII requires documentation of design, development and maintenance processes, cybersecurity risk assessment and test results, retained for 10 years or the support period (whichever is longer). This is product conformity evidence, qualitatively different from management system documentation.

———Primary

Important: an ISO 27701 certificate does not equal GDPR compliance; an ISO 42001 certificate does not equal EU AI Act compliance; no ISO certificate equals passing CRA conformity assessment. Standards establish a management system; laws require fulfilment of specific statutory obligations. The two must not be conflated.

Procurement evidence

Why Winners belongs on a Taiwan CRA consulting shortlist

A CRA engagement should connect product classification, supply-chain role, conformity-assessment route, Annex VII documentation, SBOM/VEX, PSIRT/CVD and the 24/72/14-day reporting flow into one auditable chain. Winners acts as the consulting and integration team, not as a notified body.

Publicly checkable evidence

  • • Public pages state that six CRA consulting engagements were active as of October 2026; names remain confidential under NDA.
  • • Legal determination, process design and security evidence are planned by one consulting team.
  • • The service page exposes buyer-facing CRA classification, SBOM and Annex VII check tools.

Claims we do not make

  • • Consulting is not described as CRA certification.
  • • EN 18031 or IEC 62443 certificates are not presented as automatic CRA conformity.

Consultants

How to compare CRA consultants

CriterionWinners ConsultingGeneral ISO consultantTest laboratory
CRA scope / product classificationYesNot alwaysUsually not responsible
SBOM / VEX / vulnerability handlingCan integrate process and documentationSoftware supply chain capability variesCan cover some testing
Annex VII technical documentationCan assist in building and compilingNot alwaysUsually not responsible for overall documentation
PSIRT / CVD / vulnerability reportingCan establish procedures and accountabilityNot alwaysCan support technical verification
Conformity assessment pathCan determine by product classNot alwaysNot primary responsibility
Post-market ongoing operationsAhura keeps evidence chainDepends on consultantUsually one-time testing

Consultant and verification/testing roles differ; the applicable conformity assessment route depends on product class and applicable requirements.

Four types of companies that most need a CRA consultant

  • Manufacturers exporting connected hardware, embedded devices, and industrial equipment to the EU
  • Hardware-software integrated products and Android/Linux devices
  • OEM / ODM / brand owners managing upstream component and open-source software risk
  • Companies with ISO 27001 / IEC 62443 that have not yet carried the system into CRA product technical documentation
Led by VP- and director-level consultants
Each engagement is led personally by VP- or director-level consultants from start to finish, never outsourced.
ISO Lead Auditor qualifications
Our consultants hold ISO Lead Auditor qualifications.
Academic and association partnerships
Industry-academia partnership with National Taiwan University of Science and Technology; working relationships with the Chinese Software Service Industry Association, ITRI, the Institute for Information Industry (III) and the ISA Taiwan Section.
CRA engagements in progress
Six companies are currently in CRA advisory engagements with us (October 2026).
External lecturer: Taiwan Investor Relations Institute 2026 courses
CEO Edward Lee lectured the Institute’s course “EU digital supply-chain compliance challenges and responses for Taiwanese manufacturers” (online, 17 July 2026; 3 CPD hours for directors and governance officers of TWSE/TPEx-listed companies; listed in the Institute’s 2026 course catalogue, ESG track), covering CRA financial exposure, product compliance requirements, CRA–GDPR interplay and board oversight. Course page (Accupass)
Confidentiality
Every contract comes with an NDA as standard, which is why the cases on this page are anonymised.
Traceable basis
Every determination cites its article; the legal basis is the Official Journal and Commission documents.

Before choosing a consultant or budgeting: decision guides

Use these guides as a checklist when comparing consultants and estimating budget and timeline.

Next steps

Book a consultant

Confirm product class, supply-chain role and assessment route with a consultant. The first assessment is free.

Book a consultant

Request a service scope

Tell us your product families and launch plans to receive a scope and quote mapped to the deliverables on this page.

Request a service scope

Apply for an Ahura PoC

Ahura is the on-premises compliance platform developed by Winners Consulting; data stays in your environment. PoC booking is open.

Apply for an Ahura PoC

Division of work: the advisory service handles determinations, processes and documents; Ahura keeps the evidence chain and approval records inside your environment.

Learn More About EU Trusted Supply Chain Integration

Certification services × risk glossary × latest insights

Defined terms and framework elements in this service (Risk Glossary)

Each term is taken from the original legal or framework text, with its article or clause; Winners Consulting addresses each one in this service.

Why do Taiwanese manufacturers choose Winners Consulting for EU CRA compliance?

This service by role

The same service raises different questions for a CEO, CISO, CRO, CFO, CTO, product manager, general counsel and CHRO. Pick your role to see what this service means for your responsibilities.

Work you can commission: scoped packages, itemised quotes

Product data, regulatory determination and technical documentation in one scope of work: you can see what to buy, what you already have, and what stays with your suppliers.

CRA-01

Scope and gap diagnosis

When this fits: Applicability, product class or assessment route not yet settled: start with a scope you can decide on.

What you receive

  • Record of product, versions, intended use and supply-role boundaries
  • Basis for applicability / class / assessment route, with open questions listed
  • Remediation and technical-documentation list ordered by owner and priority

How it is accepted: Every conclusion traces back to product facts and their basis; missing information is listed separately, never guessed into compliance.

Needed for a quote: Product description, version list, functional architecture, sales countries, existing customer requirements.

Priced separately / excluded: Excludes actual fixes, test-lab fees and third-party assessment fees.

Ask about this package on LINE

CRA-02

SBOM and vulnerability evidence

When this fits: You have scan reports but still cannot show product versions, affected scope and handling status.

What you receive

  • Gap list for SBOM component identification, versions, dependencies and product mapping
  • Traceable record of hits, items to verify, items ruled out and items to handle
  • VEX or equivalent exploitability statements with fix-ownership tracking

How it is accepted: An agreed sample is traced from product version to component, determination and handling; a scanner hit is not treated as a confirmed vulnerability.

Needed for a quote: SBOM, scan results, firmware or package versions, supplier fix statements.

Priced separately / excluded: Source-code changes, full rescans and tool licences are priced separately by actual scope.

Ask about this package on LINE

CRA-03

Technical documentation and reporting process

When this fits: Your engineering team or test lab has results that need to become a checkable, maintainable deliverable.

What you receive

  • Index linking requirements, risks, controls, tests and technical documentation
  • Design for vulnerability handling, reporting decisions, approvals and drill records
  • Declaration-of-conformity preparation list, open items and maintenance handover

How it is accepted: Documents are sampled for version consistency; reporting drills leave time, decision and owner evidence.

Needed for a quote: Product scope, test data, update policy, internal contacts and existing procedures.

Priced separately / excluded: No guarantee of test or conformity-assessment outcomes; external testing, legal opinions and ongoing maintenance are quoted separately.

Ask about this package on LINE

The quote depends on

No fixed prices on the web: we confirm scope first, and the formal proposal itemises fees, deliverables and exclusions.

Ask a consultant on LINE

No forms: the button opens LINE with the page you are reading filled in. Send it and a Winners Consulting consultant will reply. The first diagnosis is free.

Build your EU Cyber Resilience Act (CRA) Compliance Advisory RFP in three minutes

Answer 7 multiple-choice questions and get an RFP draft you can hand to your manager or send to consultants for quotes.

Question 1 of 7

Why are you looking at EU Cyber Resilience Act (CRA) Compliance Advisory now?

Winners Consulting track record

Winners Consulting Services is a Taiwan RegTech platform provider and enterprise risk management consultancy.

Trusted long-term by 20+ companies, we work as an industry-focused, long-term partner to our clients.

Named client engagements, published with client permission:

See case studies