Services in this category
Seven governance dimensions of technology compliance
Foundation advisory earns a certificate against one ISO standard. Advanced advisory starts from EU law and customer reviews, with CSA 2.0 as the through-line, and links those certificates into product- and supply-chain-level evidence. Each row links to the matching foundation service.
| Dimension | Main EU laws | Legal routes to presumption of conformity (harmonised standards and official certification) | Foundation service |
|---|---|---|---|
| AI governance | AI Act (as amended by the AI Omnibus, Regulation (EU) 2026/1744) | AI Act (standardisation request M/613, CEN-CENELEC JTC 21) Cited in the Official Journal: EN 18286:2026 quality management system (Article 17; (EU) 2026/2274, presumption of conformity from 14 October 2026) In development: prEN 18228 risk management (Article 9, under approval, CEN publication planned 28 February 2027); prEN 18229-1 logging (Article 12), -3 human oversight (Article 14), -2 transparency, -4 accuracy, -5 robustness; prEN 18282 cybersecurity (Article 15); prEN 18284 data quality and prEN 18283 bias management (Article 10); prEN 18285 conformity assessment | |
| Chip and technology export controls | European Chips Act (Chips Act 2.0 proposed); Dual-Use Regulation (EU) 2021/821; FDI Screening Regulation (EU) 2026/1386 (applies 2028) | Dual-Use Regulation, European Chips Act and FDI Screening Regulation: no harmonised standards; export licences, investment screening and funding reviews are decided case by case | — |
| Product security | CRA; General Product Safety Regulation (GPSR); Radio Equipment Directive (RED); Machinery Regulation; Ecodesign for Sustainable Products Regulation (ESPR, digital product passport); Batteries Regulation; Product Liability Directive (PLD) | CRA (standardisation request M/606): EN 40000-1-1 vocabulary and -1-2 principles and risk management were ratified by CEN on 2 November 2026 and are scheduled for publication in November 2026 (CEN expects no Official Journal citation); -1-3 vulnerability handling is in development (citation expected; due 30 August 2026, with a Commission draft proposing 31 October 2026); -1-4 generic security requirements is in development (due 30 October 2027) CRA product categories: 17 ETSI standards, EN 304 617 to 636 (browsers, operating systems, routers, smart home, wearables and others), in ETSI's approval procedure since 13 August 2026; industrial prEN 50770 series (firewalls, VPNs, routers and switches and others) in development; chips prEN 40004-3 (ASICs, FPGAs) at public enquiry from 25 September 2026; no CRA harmonised standard has been cited in the Official Journal yet CRA official certification: EUCC ((EU) 2024/482), presumption of conformity under CRA Article 27(8) Radio equipment (RED), cited: EN 18031-1/-2/-3 ((EU) 2025/138, with restrictions) Machinery Regulation (EU) 2023/1230 (applies 20 January 2027): no harmonised standard cited under the new Regulation yet; the Commission expects the first list before the end of 2026; EN 50742:2026 on protection against corruption completed its formal vote on 9 October 2026 General product safety (GPSR), cited: European standards for consumer products listed in (EU) 2026/901 Digital product passport (ESPR), cited: EN 18216 and EN 18219 to 18223:2026 ((EU) 2026/1736, presumption of conformity from 15 July 2026); EN 18239 access rights and security and EN 18246 data authenticity published 16 September 2026, citation pending Batteries Regulation, cited: EN 18060:2025 EV battery performance and durability ((EU) 2026/2048); battery passport mandatory from 18 February 2027 Product Liability Directive (PLD): no harmonised standards | |
| Cybersecurity | NIS2; DORA; GDPR; Cybersecurity Act (2.0 proposed) | NIS2: no EU-level harmonised standards; Implementing Regulation (EU) 2024/2690 sets technical requirements for digital service providers; Belgium officially recognises ISO/IEC 27001 certification from an accredited body for presumption of conformity, alongside the CyFun framework GDPR: certifications approved under Article 42, such as the Europrivacy European Data Protection Seal (extended to non-EU organisations and approved as a transfer tool by EDPB Opinions 14 and 15/2026 in April 2026) DORA: no certification regime; statutory regulatory technical standards apply Cybersecurity Act: EUCC adopted ((EU) 2024/482); the EUCS cloud and EU5G schemes are still drafts; Cybersecurity Act 2 (COM(2026) 11) is in the legislative process | |
| Trade secrets | Trade Secrets Directive (EU) 2016/943; Data Act (EU) 2023/2854 trade-secret safeguards in data sharing | Trade Secrets Directive: no official certification regime Data Act ((EU) 2023/2854) data-sharing interoperability (standardisation request M/614): EN 18235-1:2026 on trusted data transaction terminology published; -2 trustworthiness requirements has completed its vote; neither is cited in the Official Journal yet | |
| Corporate governance | CSRD; CSDDD (as amended by (EU) 2026/470); NIS2 management accountability | CSRD: ESRS, the statutory reporting standards (revised by (EU) 2026/1563, from financial year 2027); the limited assurance standard will be set by Commission delegated act, under consultation from 12 November 2026 and due by 1 July 2027 CSDDD and NIS2 management accountability: no harmonised standards | |
| Enterprise risk management | DORA; NIS2; CSDDD | No harmonised standards or official certification: DORA, NIS2 and the CSDDD are supervised by the authorities against their statutory measures |
In the EU, only harmonised standards cited in the Official Journal and statutory certification carry a legal presumption of conformity; an ISO certificate is evidence, not proof of compliance.
The table maps governance aims and control measures; it does not mean EU and US laws can replace each other legally. Status as of 18 November 2026. Not legal advice.
Decide with evidence first: decision tools in this service line
Every page in this line uses the same ten-section structure: applicability → law and standards → deliverables → method → cases → decision tools → qualifications → FAQ → next steps. Use the tool to see where you stand, then decide whether to talk to us.
Applicable Standards
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.
Intended Beneficiaries
- ✓Connected product manufacturers (IoT devices, industrial sensors, smart meters) targeting EU market export
- ✓Makers of aftermarket or separately marketed connected automotive products (components of type-approved vehicles are outside the CRA)
- ✓AI system developers (recruitment screening, predictive maintenance, medical decision support) entering EU markets
- ✓OT/ICS equipment manufacturers (PLCs, SCADA components) requiring IEC 62443 critical infrastructure compliance
- ✓Taiwan enterprises handling EU personal data requiring GDPR cross-border transfer compliance mechanisms
The Difference Between Acting and Waiting
✅ When you act
The CRA applies in full from 11 December 2027, and the obligation to report actively exploited vulnerabilities and severe incidents applies from 11 September 2026; classifying products and preparing technical documentation early avoids last-minute rework before placing products on the market.
❌ When you wait
For products within the CRA, from 11 December 2027 products that do not meet the essential cybersecurity requirements, have not completed conformity assessment and do not bear the CE marking cannot be placed on the EU market; breaching the essential requirements can be fined up to EUR 15 million or 2.5% of worldwide annual turnover, whichever is higher (Article 64).
✅ When you act
Automotive ECU suppliers with ISO/SAE 21434 cybersecurity engineering capability can address OEM cybersecurity requirements for ECU suppliers. ECUs in type-approved vehicles are outside the CRA (Art. 2(2)(c) excludes products covered by Regulation (EU) 2019/2144); their cybersecurity is governed by UN R155/R156.
❌ When you wait
Suppliers that treat ISO 26262 as proof of cybersecurity, or assume in-vehicle ECUs need CRA compliance, expose gaps in OEM supply-chain security reviews under UN R155; aftermarket and separately sold connected automotive products still fall under the CRA.
✅ When you act
Winners first confirms whether a product falls within the CRA at all (components of type-approved vehicles, for example, are excluded), then builds one documentation system from the shared requirements of the CRA, NIS2 and the EU AI Act.
❌ When you wait
Applying the CRA without confirming scope, or building each regulation separately, produces inconsistent documentation and the largest audit gap.
Framework Comparison & Implementation Strategy
IEC 62443-4-x (Cybersecurity)
A primary CRA-aligned technical standard. Conformity with IEC 62443-4-1/4-2 substantially reduces the conformity burden (M/606 harmonised-standards list still in development). Applies to all connected products, OT/ICS equipment, IoT manufacturers.
ISO 26262 (Functional Safety)
Vehicle functional safety standard addressing random electronic failures; unrelated to the CRA. Components of type-approved vehicles are outside the CRA (Art. 2(2)(c)); their cybersecurity is governed by UN R155 (ISO/SAE 21434 is the related engineering standard).
Common Misconception
Believing ISO 27001 equals CRA compliance, or that system-level IEC 62443 is sufficient, while overlooking the product component-level (4-2) specific technical requirements that CRA actually demands.
The Winners Approach
Starting from product type, precisely mapping CRA Annex I Essential Requirements to IEC 62443-4-2 Component Requirements (CR), establishing SBOM, vulnerability disclosure, and security update processes, and plan the applicable conformity assessment procedure for each product class.
Service Delivery Process (Four Stages)
Product Diagnosis & Regulatory Scope
Confirm product compliance pathway (CRA core / NIS2 supply-chain obligations / AI high-risk), identify applicable regulations, assess current gaps, and deliver a written diagnostic report.
Integrated Risk Assessment (SRA × NIS2 × AI risk management)
Execute pathway-appropriate risk assessment: IEC 62443-3-2 SRA for connected products; cybersecurity risk-management measures assessment for NIS2 entities; EU AI Act Article 9 risk management system for AI systems.
Cybersecurity Controls & SDL Implementation
Implement IEC 62443-4-1 eight SDL practices including threat modeling, SAST/DAST testing, penetration testing, and SBOM construction, mapped item by item to the CRA Annex I essential requirements and the EN 40000 series.
Unified Technical Documentation
Build complete CRA Annex VII technical documentation (Article 31), mapped item by item to the Annex I essential requirements. For products also subject to the EU AI Act, the same architecture supports AI Act technical documentation — one document satisfying dual audits, avoiding duplicated build effort.
CE Marking & Post-Market Obligations
Choose the conformity assessment procedure by product class: default products can use internal control (module A); important products in class I without full use of harmonised standards, class II products and critical products require a third-party procedure (Article 32). Then sign the EU declaration of conformity, affix the CE marking, and set up vulnerability handling, security updates and the 24-hour early warning and 72-hour notification process for actively exploited vulnerabilities, with 90-day follow-up after go-live.
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.
Frequently Asked Questions
What is Winners' track record in EU Trusted Supply Chain Integration — CSA 2.0 × CRA × NIS2?▼
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.
How is Winners Consulting different from other consulting firms?▼
Winners Consulting Services Co., Ltd. is a hands-on, practitioner-led team. Unlike single-discipline firms, Winners integrates process optimization, legal compliance, and cybersecurity engineering in one team: engagements are executed personally by VP-level or above consultants — never outsourced — from system design and regulatory mapping through to technical implementation and certification. Winners’ VP- and director-level consultants guide each engagement so that the management system genuinely works in day-to-day operations.
How long does EU compliance consulting take?▼
Depending on product type and existing organizational maturity, typically 7–12+ months. Connected products via IEC 62443 to CRA: approximately 7–10 months with solid existing security foundation; 10–14+ months when building SDL from scratch. AI systems adding EU AI Act requirements: 9–12+ months depending on complexity. Winners Consulting provides a personalized estimate after the free assessment.
Can IEC 62443 or ISO 26262 satisfy EU CRA?▼
IEC 62443 (parts 4-1/4-2) is a primary CRA-aligned technical standard that substantially reduces the conformity burden (the CRA harmonised-standards list under M/606 is still being developed; formal presumption of conformity applies only once standards are officially harmonised). ISO 26262 is a functional safety standard, not a CRA Harmonised Standard, and cannot satisfy CRA alone. Separately, ECUs in type-approved vehicles are outside the CRA (Art. 2(2)(c)); their cybersecurity is governed by UN R155 (ISO/SAE 21434 is the related engineering standard), and no CRA CE marking applies.
We already have ISO 27001. What else is needed for CRA?▼
ISO 27001 is an organizational-level ISMS standard, not a CRA Harmonised Standard. CRA requires product-level cybersecurity mapped by IEC 62443-4-1/4-2: no known exploitable vulnerabilities, secure-by-default configuration, SBOM, and vulnerability disclosure mechanisms. ISO 27001 provides a stronger SDL foundation, but product-level IEC 62443 requirements still need independent implementation.
Do EU AI Act and EU CRA apply simultaneously?▼
Yes. Connected AI systems (factory predictive maintenance equipment, connected smart cameras) are subject to both EU AI Act and EU CRA simultaneously. The technical documentation structures overlap significantly — Winners Consulting designs a unified architecture built once to satisfy both regulatory audits.
Will Taiwan software firms be barred from selling to the EU once the CRA fully applies in December 2027?▼
Yes, but products in scope must comply first. The CRA (Regulation (EU) 2024/2847) was published in the Official Journal on 20 November 2024, entered into force on 10 December 2024 and applies in full from 11 December 2027, with reporting obligations from 11 September 2026. Products with digital elements (software, hardware with firmware, and remote data processing essential to a product function) must meet the Annex I essential cybersecurity requirements, complete conformity assessment, carry an EU declaration of conformity and the CE marking before being placed on the EU market; the support period is in principle at least five years. Ordinary SaaS cloud services unrelated to product functions fall outside the CRA (medium-sized and larger providers may fall under NIS2). Breaching the essential requirements can be fined up to EUR 15 million or 2.5% of worldwide annual turnover, whichever is higher. Winners helps Taiwan software firms and firmware-based hardware makers with scoping, gap analysis, SBOM and vulnerability handling processes.
Why was Meta fined €1.2B by the EU? What does Schrems II mean for Taiwanese companies?▼
In May 2023, the EU DPC fined Meta Ireland €1.2B for transferring EU user data to the US in violation of Schrems II (2020 ECJ ruling). Impact on Taiwan companies: (1) using AWS/Azure/GCP to process EU user data requires Schrems II cross-border transfer risk assessment; (2) adopt SCCs plus supplementary measures (end-to-end encryption); (3) evaluate data localization. Winners delivers GDPR × Schrems II integrated compliance assessment.
Does NIS2 apply to non-EU companies? What must Taiwan IT service providers do?▼
NIS2 applies to all entities providing services within the EU (extraterritorial), even Taiwan-headquartered. Covers 18 sectors of essential and important entities. Fines: up to €10M or 2% revenue (essential) / €7M or 1.4% (important). Taiwan IT providers serving EU customers must complete: (1) risk assessment and governance, (2) 24-hour early warning + 72-hour notification, (3) supply chain security, (4) executive accountability. Winners provides one-engagement compliance.
Enquire About This Service
EU Trusted Supply Chain Integration — CSA 2.0 × CRA × NIS2
Request a Complimentary ConsultationBefore 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.
