EU Cyber Resilience Act (CRA) Compliance Advisory: law, standards and implementation method

This page answers which legal and standard requirements apply, what the timeline and obligations are, and the phases Winners Consulting uses to get you there.

Law and standards: timeline, Annex I requirements, post-market reporting and penalties

Legal timeline

DateWhat appliesBasis
10 Dec 2024Entry into forceArticle 71(1)
11 Jun 2026Notification of conformity assessment bodies (Chapter IV) appliesArticle 71(2)
11 Sep 2026Reporting of actively exploited vulnerabilities and severe incidents, including products placed on the market before 11 Dec 2027Articles 14 and 69(3)
11 Dec 2027Full application. Products placed on the market earlier are re-assessed under the CRA only after a substantial modificationArticles 71(2) and 69(2)
11 Jun 2028EU type-examination certificates and approval decisions on cybersecurity issued under other Union harmonisation legislation (e.g. the Radio Equipment Directive) remain valid until this date, unless they expire earlier or that legislation provides otherwiseArticle 69(1)

Annex I traceability

Each item of Annex I Part I(2) applies on the basis of the Article 13(2) risk assessment and where applicable; the Part II vulnerability handling requirements apply at placing on the market and throughout the support period (Article 13(8)).

Part I: cybersecurity requirements for the product

ReferenceRequirementSuggested evidence (good practice)
I(1)Designed, developed and produced to ensure an appropriate level of cybersecurity based on the risksArticle 13(2) risk assessment; treatment of risks not covered by the other items
I(2)(a)Made available without known exploitable vulnerabilitiesPre-release vulnerability scan matched against the SBOM (Annex VII point 6)
I(2)(b)Secure by default configuration, including reset to the original stateDefault configuration list; reset function test record
I(2)(c)Vulnerabilities addressable through security updates; automatic updates on by default where applicable, with opt-out, notification and postponementUpdate mechanism design; tests of auto-update and opt-out
I(2)(d)Protection from unauthorised access by control mechanisms such as authentication and identity or access management, reporting possible unauthorised accessAccess control design; authentication tests; unauthorised access alerts
I(2)(e)Confidentiality of stored, transmitted or processed data, e.g. encryption at rest and in transitCryptography and key management description; transport encryption tests
I(2)(f)Integrity of data, commands, programs and configuration against unauthorised modification, reporting corruptionsSignature verification and secure boot design; integrity check tests
I(2)(g)Process only data adequate, relevant and limited to the intended purpose (data minimisation)Data flow inventory mapped to purposes
I(2)(h)Availability of essential and basic functions, also after an incident, including resilience against denial-of-serviceResilience design; load and DoS tests
I(2)(i)Minimise negative impact on the availability of services provided by other devices or networksNetwork behaviour and rate-limiting design
I(2)(j)Limit attack surfaces, including external interfacesInterface and port inventory; evidence unused services are disabled
I(2)(k)Reduce the impact of an incident using exploitation mitigation mechanismsCompiler and runtime hardening settings (e.g. memory protections)
I(2)(l)Record and monitor relevant internal activity to provide security information, with a user opt-outLog design, retention and opt-out
I(2)(m)Users can securely and easily remove all data and settings permanently, and transfer them securely where applicableData wipe function and test record

Part II: vulnerability handling requirements

ReferenceRequirementSuggested evidence (good practice)
II(1)Identify and document vulnerabilities and components, including an SBOM in a commonly used, machine-readable format covering at least top-level dependenciesCycloneDX or SPDX SBOM (check it with the tool below)
II(2)Address and remediate vulnerabilities without delay; where feasible, provide security updates separately from functionality updatesVulnerability handling procedure; remediation time records
II(3)Apply effective and regular security tests and reviewsTest plan and periodic review records (Annex VII point 6)
II(4)Once an update is available, publicly disclose fixed vulnerabilities: description, affected products, impact, severity and remediation (may be delayed in duly justified cases)Security advisory template and publication records
II(5)Put in place and enforce a coordinated vulnerability disclosure policyPublished CVD policy
II(6)Facilitate sharing of vulnerability information, including in third-party components, and provide a contact address for reportingReporting contact (e.g. security.txt); upstream reporting records
II(7)Mechanisms to securely distribute updates, automatically for security updates where applicableSigned update delivery and channel design
II(8)Security updates disseminated without delay and, in principle, free of charge, with advisory messages on actions users should takeUpdate release records and user notices

Requirements are summaries of the official English text; suggested evidence is Winners Consulting's good practice, not legal text.

Post-market vulnerability handling and reporting (PSIRT)

A product security incident response team (PSIRT) needs these six steps as a process that can be rehearsed and evidenced. Each step maps to the articles.

  1. 1. Receive and record

    Publish a reporting contact and a coordinated vulnerability disclosure policy; record vulnerabilities from internal and external sources. Report vulnerabilities found in third-party or open-source components to whoever manufactures or maintains them.

    Annex I Part II(5) and (6); Article 13(6) and (7)

  2. 2. Assess

    Is the vulnerability actively exploited? Is the incident severe: does it affect the availability, authenticity, integrity or confidentiality of sensitive or important data or functions, or lead to malicious code being introduced or executed?

    Article 14(1), (3) and (5)

  3. 3. Report

    Early warning within 24 hours, notification within 72 hours, final report within the deadline. Submit through the single reporting platform to the coordinating CSIRT, simultaneously accessible to ENISA.

    Article 14(2), (4) and (7); Article 16

  4. 4. Inform users

    Inform impacted users (and where appropriate all users) of the vulnerability or incident and of mitigation and corrective measures they can deploy, where appropriate in a structured, machine-readable format.

    Article 14(8)

  5. 5. Fix and distribute

    Remediate without delay according to risk; disseminate security updates without delay and, in principle, free of charge, separately from functionality updates where technically feasible. Keep each security update available for at least 10 years or the rest of the support period, whichever is longer.

    Annex I Part II(2), (7) and (8); Article 13(9)

  6. 6. Disclose and update documentation

    Once an update is available, publicly disclose the fixed vulnerability and remediation; update the risk assessment and technical documentation. Keep the technical documentation and EU declaration of conformity for at least 10 years or the support period, whichever is longer.

    Annex I Part II(4); Article 13(7) and (13)

A manufacturer with no main establishment in the EU (as for most Taiwanese exporters) reports to the coordinating CSIRT of the first Member State that applies: (a) where the authorised representative acting for the highest number of its products is established; (b) where the importer placing the highest number of its products is established; (c) where the distributor making available the highest number of its products is established; (d) where the highest number of users are located (Article 14(7)).

Article 14 deadlines

StageActively exploited vulnerabilitySevere incident affecting product security
Early warningWithin 24 hours of becoming awareWithin 24 hours of becoming aware
NotificationWithin 72 hours of becoming awareWithin 72 hours of becoming aware
Final reportWithin 14 days after a corrective or mitigating measure is availableWithin one month after the 72-hour notification

Under the Commission's draft guidance, exploitation known before 11 Sep 2026 does not have to be reported retroactively.

Penalties (Article 64)

Para. 2Breach of Annex I essential requirements, Article 13 (manufacturer obligations) or Article 14 (reporting)EUR 15,000,000 or 2.5% of worldwide annual turnover, whichever is higher
Para. 3Breach of obligations in Articles 18–23, 28, 30, 31, 32, 33 and others listedEUR 10,000,000 or 2%, whichever is higher
Para. 4Incorrect, incomplete or misleading information to notified bodies or market surveillance authoritiesEUR 5,000,000 or 1%, whichever is higher

Standards and common misconceptions

"EN 18031 proves CRA conformity"

The EN 18031 series are harmonised standards under the Radio Equipment Directive Delegated Regulation (EU) 2022/30 (Implementing Decision (EU) 2025/138), not CRA harmonised standards. EU type-examination certificates on cybersecurity issued under other Union harmonisation legislation remain valid until 11 Jun 2028 under Article 69(1), unless they expire earlier or that legislation provides otherwise; this is a transitional rule on the certificates' validity, and presumption of conformity under the CRA still follows Article 27.

"IEC 62443 certification gives presumption of conformity"

Presumption of conformity comes only from harmonised standards published in the OJ, common specifications or designated certification schemes (Article 27). IEC 62443 is a strong reference for implementation and gap analysis, but not a presumption of conformity in itself.

"Only pure SaaS is exempt"

Web applications are generally not products themselves, but Article 2 also excludes medical devices, vehicles, aviation, marine equipment, defence and spare parts, and open-source depends on monetisation. Conversely, cloud processing a product needs is brought into the product's scope.

"A built-in firewall makes a product class II"

The class follows the core functionality of the whole product. A router with a firewall is still a router (class I); only a firewall module sold separately is classified on its own.

EU regulatory watch (continuously monitored)

Official sources (European Commission, EUR-Lex, ENISA, CEN-CENELEC, ETSI, EDPB) are monitored continuously; only items relevant to this service are listed. Fed by our on-premise intelligence pipeline; the site refreshes every minute.

Loading…

CRA, NIS2, ISO/IEC 27001, IEC 62443: product law, entity law, organisational standard, product standard

"We hold ISO 27001 / IEC 62443 certificates, so we pass the CRA?" No. The four target different things: two are EU laws, two are certifiable standards; first ask whether you sell products or services and where your customers are.

ItemNatureWho and whereMandatory?How it is proven
CRA (Regulation (EU) 2024/2847)EU product law (regulation)Products with digital elements placed on the EU market (hardware, software, remote data processing), manufacturers wherever established; importers and distributors also have dutiesMandatory; reporting from 11 Sep 2026, full application 11 Dec 2027Conformity assessment (default and most class I may self-assess), EU declaration of conformity, CE, Annex VII technical documentation, SBOM
NIS2 (Directive (EU) 2022/2555)EU entity law (directive transposed nationally, deadline 17 Oct 2024)Essential and important entities providing services in the EU (energy, transport, health, digital infrastructure, manufacturing and other Annex I/II sectors), medium size and aboveMandatory; penalties set in national law (essential entities up to €10M / 2%)Registration with national authorities, risk management measures (Article 21), incident reporting (24h / 72h / 1 month); no EU-level certificate
ISO/IEC 27001:2022International information security management standard (certifiable)Any organisation, any region; governs the organisation's security systemVoluntary; commonly required by customers and supply chainsThird-party certificate, 3-year cycle
IEC 62443 seriesInternational industrial/product security standards (certificates via IECEE and others)Asset owners, integrators and product suppliers of industrial automation and control systems; 4-1 secure development, 4-2 component requirements, 3-3 system requirements, 2-4 integratorsVoluntary; often specified by grid, process and machinery customersCertificates from certification bodies under IECEE CB / ISASecure schemes; not a presumption of conformity for the CRA

Key differences

  • The CRA looks at whether this product meets Annex I; 27001 at the organisation's system; NIS2 at the entity's network and information system risk management — three different objects.
  • No ISO/IEC certificate equals CRA conformity: presumption of conformity comes only from harmonised standards cited in the Official Journal (Article 27); check the latest Official Journal for which have been cited.
  • IEC 62443-4-1/4-2 is the closest technical evidence for CRA Annex I and shortens documentation considerably, but class II and non-self-assessable class I still need a notified body.
  • When a NIS2 entity procures products with digital elements, the CRA SBOM and vulnerability handling are exactly the supply-chain evidence NIS2 Article 21 asks for — the two laws complement each other.

How to choose

  • Selling hardware or software into the EU → CRA first; with a 62443-4-1 process, map it directly to Annex I.
  • Providing services or operating infrastructure in the EU → NIS2 (under the member state's law) first; 27001 is the backbone for Article 21.
  • Customers only require a security management certificate → 27001; add 62443 if products go into industrial markets.
  • Both a manufacturer and a NIS2 entity (e.g. an energy equipment maker operating its own services) → one 27001 base plus CRA product processes and NIS2 reporting.

What to share when implementing together

Share one base: risk methodology (27001 clause 6 = CRA Article 13 = NIS2 Article 21), supplier management (27001 A.5.19–23 = CRA SBOM / third-party components = NIS2 supply chain), incident management (27001 A.5.24–28 = CRA Article 14 24h/72h = NIS2 Article 23 24h/72h), secure development (27001 A.8.25–31 = 62443-4-1 = CRA Annex I). Only statutory procedures differ: CRA conformity assessment and CE, NIS2 registration and national reporting channels.

How Winners works

Winners supports all four: CRA classification and technical documentation, NIS2 gap analysis and reporting flows, ISO 27001 implementation and audit support, IEC 62443 development processes and product assessment preparation. The first step is to clarify whether you sell products or services and in which markets, then recommend which ones, in what order, or one system that carries them all.

Either entry works: start from your industry's pain points or from the standard you plan to adopt — we first clarify the differences, then give you the information and support.

Method: five dependent phases

  1. 01 Classification and roles

    Class per product family, supply-chain role per product line. Acceptance: every combination has a documented basis mapped to the articles.

  2. 02 Reporting first

    Article 14 24/72-hour reporting and user information process, with a tabletop exercise. Acceptance: drill records and templates.

  3. 03 Risk assessment and gap analysis

    Article 13(2) risk assessment and an Annex I gap analysis. Acceptance: risk assessment report and remediation plan.

  4. 04 Requirements and technical documentation

    SBOM, security updates, support period, user information and technical documentation. Acceptance: evidence for every Annex VII item.

  5. 05 Conformity assessment and operation

    Self-assessment or a notified body slot; ongoing vulnerability handling and reporting. Acceptance: EU declaration of conformity and operating records.

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)]

Before choosing a consultant or budgeting: decision guides

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

Official sources

Also referenced: Commission draft CRA guidance C(2026) 5252 (content approved 27 Jul 2026; applies once formally adopted in all languages).

Checked against the official texts on 2026-11-07

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.

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.

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