Law and standards: timeline, Annex I requirements, post-market reporting and penalties
Legal timeline
| Date | What applies | Basis |
|---|---|---|
| 10 Dec 2024 | Entry into force | Article 71(1) |
| 11 Jun 2026 | Notification of conformity assessment bodies (Chapter IV) applies | Article 71(2) |
| 11 Sep 2026 | Reporting of actively exploited vulnerabilities and severe incidents, including products placed on the market before 11 Dec 2027 | Articles 14 and 69(3) |
| 11 Dec 2027 | Full application. Products placed on the market earlier are re-assessed under the CRA only after a substantial modification | Articles 71(2) and 69(2) |
| 11 Jun 2028 | EU 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 otherwise | Article 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
| Reference | Requirement | Suggested evidence (good practice) |
|---|---|---|
| I(1) | Designed, developed and produced to ensure an appropriate level of cybersecurity based on the risks | Article 13(2) risk assessment; treatment of risks not covered by the other items |
| I(2)(a) | Made available without known exploitable vulnerabilities | Pre-release vulnerability scan matched against the SBOM (Annex VII point 6) |
| I(2)(b) | Secure by default configuration, including reset to the original state | Default 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 postponement | Update 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 access | Access control design; authentication tests; unauthorised access alerts |
| I(2)(e) | Confidentiality of stored, transmitted or processed data, e.g. encryption at rest and in transit | Cryptography and key management description; transport encryption tests |
| I(2)(f) | Integrity of data, commands, programs and configuration against unauthorised modification, reporting corruptions | Signature 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-service | Resilience design; load and DoS tests |
| I(2)(i) | Minimise negative impact on the availability of services provided by other devices or networks | Network behaviour and rate-limiting design |
| I(2)(j) | Limit attack surfaces, including external interfaces | Interface and port inventory; evidence unused services are disabled |
| I(2)(k) | Reduce the impact of an incident using exploitation mitigation mechanisms | Compiler 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-out | Log design, retention and opt-out |
| I(2)(m) | Users can securely and easily remove all data and settings permanently, and transfer them securely where applicable | Data wipe function and test record |
Part II: vulnerability handling requirements
| Reference | Requirement | Suggested 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 dependencies | CycloneDX 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 updates | Vulnerability handling procedure; remediation time records |
| II(3) | Apply effective and regular security tests and reviews | Test 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 policy | Published CVD policy |
| II(6) | Facilitate sharing of vulnerability information, including in third-party components, and provide a contact address for reporting | Reporting contact (e.g. security.txt); upstream reporting records |
| II(7) | Mechanisms to securely distribute updates, automatically for security updates where applicable | Signed 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 take | Update 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. 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. 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. 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. 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. 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. 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
| Stage | Actively exploited vulnerability | Severe incident affecting product security |
|---|---|---|
| Early warning | Within 24 hours of becoming aware | Within 24 hours of becoming aware |
| Notification | Within 72 hours of becoming aware | Within 72 hours of becoming aware |
| Final report | Within 14 days after a corrective or mitigating measure is available | Within 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. 2 | Breach 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. 3 | Breach of obligations in Articles 18–23, 28, 30, 31, 32, 33 and others listed | EUR 10,000,000 or 2%, whichever is higher |
| Para. 4 | Incorrect, incomplete or misleading information to notified bodies or market surveillance authorities | EUR 5,000,000 or 1%, whichever is higher |
Standards and common misconceptions
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.
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.
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.
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.
| Item | Nature | Who and where | Mandatory? | 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 duties | Mandatory; reporting from 11 Sep 2026, full application 11 Dec 2027 | Conformity 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 above | Mandatory; 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:2022 | International information security management standard (certifiable) | Any organisation, any region; governs the organisation's security system | Voluntary; commonly required by customers and supply chains | Third-party certificate, 3-year cycle |
| IEC 62443 series | International 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 integrators | Voluntary; often specified by grid, process and machinery customers | Certificates 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
- 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.
- 02 Reporting first
Article 14 24/72-hour reporting and user information process, with a tabletop exercise. Acceptance: drill records and templates.
- 03 Risk assessment and gap analysis
Article 13(2) risk assessment and an Annex I gap analysis. Acceptance: risk assessment report and remediation plan.
- 04 Requirements and technical documentation
SBOM, security updates, support period, user information and technical documentation. Acceptance: evidence for every Annex VII item.
- 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.
- Budgeting for the EU CRA next year: how to estimate itCRA complexity is not about how many products you have, but about the combination of each product family's class and each product line's supply-chain role. Estimate internal effort, consulting, external assessment and ongoing cost from that combination.
- How long does CRA compliance take, and which steps cannot be compressed?Reporting obligations have applied since 11 September 2026; the main obligations apply from 11 December 2027. Harmonised standards matter, but waiting for their official publication before starting is too late.
- Who should lead CRA compliance, and which units need to support it?Under the CRA the obligations fall on the "manufacturer", not on the IT department. Articles 13 and 14 split the work across R&D, procurement, product security, quality and legal; a responsibility matrix assigns it, and the IIA Three Lines Model separates oversight from assurance.
- How to choose an EU Cyber Resilience Act (CRA) consultant in Taiwan: nine criteriaWhen choosing a CRA consultant, first check whether they can classify each product family and determine your supply-chain role for each product line, and whether they can handle legal compliance, process and security technology together. Criteria and questions you can put to any consultant.
- How to choose an IEC 62443 consultant in Taiwan: eight criteriaWhen choosing an IEC 62443 consultant, first check whether they can determine which parts apply to your role (2-1, 2-4, 3-3, 4-1, 4-2), whether they understand the order of 4-1 and 4-2, and that they do not present IEC 62443 certification as equivalent to complying with the EU CRA.
- How to choose a NIS2 consultant in Taiwan: eight criteriaWhen choosing a NIS2 consultant, first check whether they can determine your status: a directly regulated essential or important entity, or a supplier to EU customers. Then check whether they can build the ten Article 21 measures and the 24-hour, 72-hour and one-month reporting on your existing ISO 27001.
- How to choose a GDPR consultant in Taiwan: eight criteriaWhen choosing a GDPR consultant, first check whether they can determine how far the GDPR applies to you and whether you are a controller or a processor; then whether they can turn records of processing, impact assessments, 72-hour breach notification and international transfers into a working system that shares one document set with Taiwan's Personal Data Protection Act and ISO 27701.
- How to choose an ISO/IEC 29147 consultant in Taiwan: eight criteriaWhen choosing an ISO/IEC 29147 vulnerability disclosure consultant, first check whether they can set up a reporting channel that outsiders can find, with response times, and a coordinated vulnerability disclosure policy; then check whether it connects to ISO/IEC 30111 internal handling and to EU CRA reporting obligations.
- How to choose an ISO/IEC 30111 consultant in Taiwan: eight criteriaWhen choosing an ISO/IEC 30111 vulnerability handling consultant, first check whether they can turn intake, verification, prioritisation, remediation and release into a process with owners and time limits; then check whether it connects to the SBOM, security updates and the EU CRA requirement to handle vulnerabilities throughout the support period.
- How to choose a DORA consultant in Taiwan: eight criteriaWhen choosing a DORA consultant, first check whether they can determine if you are an EU financial entity directly regulated by DORA or an ICT third-party service provider to financial entities; then check whether they can build contract terms, the register of information, incident reporting and resilience testing on your existing ISO 27001 and business continuity systems.
- How to choose an EU AI Act consultant in Taiwan: eight criteriaWhen choosing an EU AI Act consultant, first check whether they can determine your role in each AI system (provider, deployer, importer or distributor) and its risk level; then check whether they can explain the application dates as amended by the Digital Omnibus, the high-risk obligations and the conformity assessment route, and what ISO/IEC 42001 can and cannot do.
- CTO regulatory priorities: EU CRA and 8 more requirements, and three decisions we suggest you make firstIf your products go to the EU, carmakers or industrial control customers, given your responsibility for R&D, we suggest building the EU CRA, IEC 62443, ISO/SAE 21434 and other requirements into your existing development process. Below: a suggested order for 9 requirements and the impact of leaving them unaddressed, plus trade secret protection for R&D output and the ESG evaluation.
- A product manager's regulatory priorities: 8 requirements, and the three points we suggest you confirm firstWith a smooth EU launch as the goal, the EU CRA decides whether a product can be sold, and fines are based on global annual turnover. This page sets out 8 requirements in order, covering scope, the pre-launch list, the support period and commitments to customers.
Official sources
- Regulation (EU) 2024/2847 (Cyber Resilience Act), OJ L, 20.11.2024
- Commission Implementing Regulation (EU) 2025/2392 — technical description of important and critical product categories, OJ L, 1.12.2025
- Commission Implementing Decision (EU) 2025/138 — harmonised standards (EN 18031) under the Radio Equipment Directive
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 consultantRequest 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 scopeApply 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 PoCDivision 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
🏆Certification Services
💡Latest InsightsView all →
No articles yet
Related Deep Insights
In-depth analysis by Winners consultants, 6,000+ words per article
