According to the European Commission, the reporting obligations for actively exploited vulnerabilities and severe incidents under Article 14 of the Cyber Resilience Act (Regulation (EU) 2024/2847) have applied since 11 September 2026, and the main obligations apply from 11 December 2027. Many Taiwanese manufacturers of IoT, networking, industrial PC (IPC) and embedded devices that export to the EU are still waiting, usually for the same reason: "The EN 40000 harmonised standards are not complete yet, so we will start once they are."
The author's assessment is that this is a high-risk misjudgement. EN 40000-1-1 (vocabulary) and EN 40000-1-2 (principles for cyber resilience) were published in November 2026, but EN 40000-1-3 on vulnerability handling is still in formal vote and EN 40000-1-4 on generic security requirements is expected only in 2027. By the time the full series is in place, very little time will remain before full application.
First, the legal obligations come from the CRA itself, not from standards. Manufacturers must meet the essential cybersecurity requirements of Annex I; under Article 27, a harmonised standard offers a presumption of conformity only once its reference is published in the Official Journal of the EU. Incomplete standards do not postpone the obligations.
Second, the management system needs time to mature. Building a secure development lifecycle (SDL), threat modelling, automated SBOM generation, PSIRT vulnerability reporting and Annex VII technical documentation from scratch involves R&D, quality assurance, legal and suppliers, and cannot be completed in the few months after a standard appears.
Under Article 31 and Annex VII, the technical documentation must be completed before the product is placed on the market; under Article 13, it must be kept together with the EU declaration of conformity for at least 10 years or for the support period, whichever is longer. The core contents, usable directly as a project acceptance checklist:
- Product overview and support period statement: model, hardware and firmware versions, intended purpose, network interface architecture, and the start and end of the support period (at least 5 years in principle, unless the expected period of use is shorter).
- Security processes for design, development and production: SDL procedures, version control and code review records, firmware signing (Secure Boot, code signing), and design documents mapped to IEC 62443-4-1.
- Cybersecurity risk assessment: attack surface, threat scenarios and mitigations, with the applicability of each Annex I requirement and the rationale.
- SBOM: top-level dependencies in a machine-readable format such as CycloneDX or SPDX, covering in-house modules, open-source components and commercial SDK versions.
- Vulnerability handling process: intake, verification, remediation timelines and disclosure policy aligned with ISO/IEC 30111 and ISO/IEC 29147, plus Article 14 reporting drill records.
- Test and verification reports: static and dynamic scan records, penetration test reports, retest evidence after fixes, and records showing no known exploited vulnerabilities remain.
- EU declaration of conformity and user information: the Annex V declaration, secure configuration (hardening) guide, security update method and security contact.
Stop submitting a hand-maintained spreadsheet as the SBOM. Part II of Annex I requires an SBOM in a commonly used, machine-readable format that allows newly disclosed vulnerabilities to be matched quickly. Generate it automatically in the CI/CD pipeline with at least component name, exact version, package identifier (PURL or CPE), supplier, dependency relationships and licence, and connect it to tools such as Grype, Trivy or Dependency-Track for daily matching against NVD and the CISA KEV catalogue. The CRA does not require the full SBOM to be made public to consumers, but it must be provided when a market surveillance authority requests it.
Five pitfalls Taiwanese manufacturers most often fall into:
- Waiting for the full EN 40000 series: the first two parts are published, but vulnerability handling and generic security requirements are not complete, and Official Journal citation comes later still. Build on IEC 62443-4-1, IEC 62443-4-2, ISO/IEC 30111 and Annex I now, and map to the standards once they are cited.
- Treating an existing certificate as a CRA pass: neither EN 18031 nor IEC 62443 automatically covers the support period statement, SBOM maintenance or Article 14 reporting; a full gap analysis is still needed.
- Scanning once before shipment with no post-market reporting chain: Article 14 already applies, so if an upstream open-source component turns out to be actively exploited after shipment, a company without a PSIRT and reporting drills is immediately in breach.
- Unclear OEM and ODM roles and companion-app boundaries: contracts must state who is the manufacturer in law and who maintains Annex VII and support-period updates, and must include mobile apps and remote data processing that come with the hardware.
- Assigning work to the wrong party: under Article 39, a notified body must remain independent and must not provide consultancy to the companies it assesses; building the management system and third-party conformity assessment should be handled by different parties.
Of course, some companies argue that waiting for cited standards and doing everything once avoids rework. The concern is reasonable, but the Annex I requirements will not change with the standards. Processes built now on IEC 62443 and ISO/IEC 30111 will only need a delta mapping later, whereas a late start squeezes design changes, retesting and technical documentation into the same period.
Deadline: Article 14 reporting has applied since 11 September 2026, so the 24-hour early warning and 72-hour notification capability is needed now; by 11 December 2027, every product placed on the EU market needs complete Annex VII technical documentation.
Priorities: start with product lines already sold in the EU that have network functions and a high share of open-source components, then new products; rank by shipment volume and exposure to exploited vulnerabilities.
Prerequisites (to finish before the deadline): determine product applicability and classification, set up automated SBOM generation in CI/CD, and appoint a PSIRT owner and reporting procedure.
Institutional ownership: the head of R&D owns SDL and SBOM, the CISO or head of quality owns the PSIRT and Article 14 reporting, and legal owns manufacturer responsibilities in OEM and ODM contracts.
The head of R&D and the CISO should hold a cross-functional meeting this quarter to integrate the CRA with existing ISO 27001, IEC 62443, ISO/IEC 30111 or NIS2 work into one management framework, and appoint an overall owner for the Annex VII technical documentation.
(Disclosure: Winners Consulting Services provides integrated CRA, IEC 62443 and NIS2 consulting, covering applicability and classification, threat modelling, SBOM and vulnerability handling processes, Article 14 reporting drills and Annex VII technical documentation. Winners Consulting Services is an independent consultancy and not an EU notified body.)
Media outlets are welcome to republish this article in full, unedited, with attribution to: Winners Consulting Services Co., Ltd.
FAQ
- When did CRA Article 14 reporting obligations start to apply?
- On 11 September 2026, regardless of when the product was placed on the market. After becoming aware of an actively exploited vulnerability or a severe incident, the manufacturer must submit an early warning within 24 hours and a notification within 72 hours; the final report on a vulnerability is due within 14 days after a corrective measure is available. Reports go through the ENISA Single Reporting Platform.
- Can a company work on CRA compliance before the EN 40000 series is complete?
- Yes, and it should start now. The obligations come from Annex I of the CRA, not from standards; under Article 27, harmonised standards give a presumption of conformity only after citation in the Official Journal. Build secure development and vulnerability handling processes on IEC 62443-4-1, IEC 62443-4-2 and ISO/IEC 30111, then map them to the standards once cited.
- Does the CRA require the SBOM to be made public?
- No. Part II of Annex I requires manufacturers to draw up an SBOM in a commonly used, machine-readable format covering at least the top-level dependencies, include it in the technical documentation, and provide it to market surveillance authorities on request. In practice, generate it automatically in CI/CD with CycloneDX or SPDX and match it daily against known exploited vulnerabilities.
Was this article helpful?
Related Services & Further Reading
Related Services
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.
Want to apply these insights to your enterprise?
Get a Free Assessment