CRA vs IEC 62443: how the standard maps to the regulation

IEC 62443 is a voluntary international standard series for securing industrial automation and control systems; the Cyber Resilience Act is binding EU law for all products with digital elements. Parts 4-1 and 4-2 cover much of Annex I, but reporting, SBOMs, support periods and CE marking are CRA-only.

By the Vellaci teamPublished Updated 6 min readOperational guidance, not legal advice

Share:LinkedInXE-mail

Key facts

IEC 62443
Voluntary IEC standard series for industrial automation and control systems (IACS)
CRA
Regulation (EU) 2024/2847 — binding for products with digital elements placed on the EU market
Closest overlap
62443-4-1 (secure development lifecycle) with Annex I Part II and Art. 13; 62443-4-2 (component requirements) with Annex I Part I
CRA-only
Article 14 reporting, SBOM, support period, Annex VII documentation, conformity assessment, declaration and CE marking
Standardisation
CRA amendments to EN IEC 62443-4-1, 4-2 and 3-3, plus IEC 62443-based OT profiles (prEN 50770 series) under M/606
Certification
An IEC 62443 certificate is evidence for a CRA assessment, not a substitute for it

Different instruments, overlapping content

DimensionIEC 62443Cyber Resilience Act
Legal statusVoluntary international standardEU regulation, directly applicable in every Member State
ScopeIndustrial automation and control systems: asset owners, integrators, product suppliersAll products with digital elements placed on the EU market, from apps to PLCs
AddresseesRoles in the IACS lifecycleManufacturers, importers, distributors, open-source stewards
Product-level structure4-1 process practices; 4-2 component requirements with security levels SL 1–4Annex I Part I properties and Part II vulnerability handling
EvidenceAssessment or certification by a certification bodyTechnical documentation, conformity assessment, EU declaration of conformity, CE marking
Consequence of failureLost certificate or contractMarket surveillance measures and fines of up to €15 million or 2.5 % of turnover

IEC 62443-4-1 practices mapped to the CRA

IEC 62443-4-1 defines eight practices for a secure product development lifecycle. Each maps onto CRA obligations; the mapping below is an interpretation for planning, not an official correspondence table.

62443-4-1 practiceWhat it coversCRA counterpart
SM — Security managementProcess scope, roles, secure development governance, component and tool managementArt. 13(1)–(2), (5); Annex VII point 2
SR — Specification of security requirementsProduct security context, threat model, security requirementsArt. 13(2)–(3) risk assessment; Annex I Part I(1)
SD — Secure by designSecure design principles, defence in depth, attack-surface reductionAnnex I Part I(2)(b), (j), (k)
SI — Secure implementationSecure coding standards and implementation reviewsAnnex I Part I(1); Part II(3)
SVV — Security verification and validation testingRequirements testing, threat mitigation testing, vulnerability and penetration testingAnnex I Part II(3); Annex VII point 6 test reports
DM — Management of security-related issuesReceiving, assessing, addressing and disclosing security issuesAnnex I Part II(2), (4)–(6); Art. 13(6)–(7)
SUM — Security update managementQualifying, documenting and delivering security updates on timeAnnex I Part I(2)(c); Part II(7)–(8); Art. 13(9)
SG — Security guidelinesDocumentation for secure integration, configuration and decommissioningAnnex II user information; Art. 13(18)

IEC 62443-4-2 and Annex I Part I

IEC 62443-4-2 specifies component requirements for four component types — software applications, embedded devices, host devices and network devices — grouped under seven foundational requirements and graded by security level. The CRA has no security levels; it asks for an appropriate level of cybersecurity based on the risks, which the risk assessment must justify. The foundational requirements map approximately as follows — our reading for planning, not an official correspondence.

62443 foundational requirementAnnex I Part I point
FR 1 Identification and authentication control(2)(d) protection from unauthorised access
FR 2 Use control(2)(d) access control; (2)(b) secure by default
FR 3 System integrity(2)(f) integrity; (2)(c) secure updates
FR 4 Data confidentiality(2)(e) confidentiality
FR 5 Restricted data flow(2)(j) limited attack surface; (2)(i) impact on other networks
FR 6 Timely response to events(2)(l) security logging and monitoring
FR 7 Resource availability(2)(h) availability, including denial-of-service resilience

What the CRA adds on top of IEC 62443

A mature 62443-4-1 programme covers most of the process side. These obligations have no direct equivalent in the standard and need their own work:

  • Article 14 reporting of actively exploited vulnerabilities and severe incidents to the coordinator CSIRT and ENISA within 24 hours, 72 hours and a final report — in force since 11 September 2026.
  • A software bill of materials in a commonly used, machine-readable format covering at least top-level dependencies (Annex I Part II(1)).
  • A declared support period of at least five years unless expected use is shorter, with its end date shown at purchase, and security updates kept available for at least ten years.
  • Explicit product properties that 4-2 does not single out: no known exploitable vulnerabilities at release, data minimisation and secure deletion of user data.
  • Technical documentation per Annex VII kept for ten years, conformity assessment, the EU declaration of conformity and CE marking.
  • Supply-chain duties for importers and distributors, and market surveillance with penalties.

Where IEC 62443 goes further

The standard covers ground the regulation leaves to others: system-level requirements for integrators (62443-3-3), zones and conduits, risk assessment for system design (62443-3-2), and the asset owner's security programme. Its security levels give a vocabulary for capability that customers in critical infrastructure already use in procurement. None of that conflicts with the CRA; it simply sits outside the manufacturer's legal obligations.

IEC 62443 inside the CRA standards

Under standardisation request M/606, CENELEC TC 65X is preparing CRA-related amendments to EN IEC 62443-4-1, 4-2 and 3-3, and IEC 62443-based security profiles — the prEN 50770 series — for firewalls and intrusion detection or prevention systems, network management systems, network interfaces, VPN products, routers, modems and switches, and SIEM systems. ETSI drafts standards for the same categories for general use. Until references are cited in the Official Journal, applying IEC 62443 is good evidence but gives no presumption of conformity.

Reusing a 62443 programme for the CRA

  1. List which products are placed on the EU market and confirm each is in CRA scope; classify by core functionality — many controllers are default products, OT firewalls are Class II.
  2. Map existing 4-1 process evidence to Annex I Part II and Article 13, practice by practice, and file it per product.
  3. Map each product's 4-2 capabilities to Annex I Part I points in its risk assessment, adding the CRA-only properties.
  4. Add the missing pieces: SBOM per release, the Article 14 runbook, a published support period and Annex VII documentation.
  5. Track the prEN 50770 profile or ETSI standard for each product's category and plan the conformity route accordingly.

Frequently asked questions

Does IEC 62443 certification mean CRA compliance?
No. A 62443-4-1 or 4-2 certificate is strong evidence for the process and product-property parts of Annex I, but CRA conformity also needs reporting, an SBOM, a support period, Annex VII documentation, the prescribed conformity assessment, a declaration of conformity and CE marking.
Is IEC 62443 mandatory under the CRA?
No. The CRA requires conformity with its essential requirements, not with any particular standard. IEC 62443-based standards will give a presumption of conformity only once their references are published in the Official Journal.
Which IEC 62443 parts matter most for product manufacturers?
Part 4-1, for the secure development lifecycle and vulnerability handling, and Part 4-2, for component security capabilities. Part 3-3 matters to manufacturers of systems, and 3-2 is a useful risk-assessment reference.
Does the CRA apply to industrial control systems?
Yes, when they are products with digital elements placed on the EU market and not excluded by sector legislation. They are classified by core functionality: a PLC is often a default product, an industrial firewall an important Class II product.
Our component is certified to IEC 62443-4-2. What else do we need?
A product risk assessment that maps the certified capabilities to Annex I and covers the CRA-only properties; an SBOM per release; the Article 14 reporting process; a declared support period; Annex VII documentation; and the conformity procedure that its classification requires.

Reuse your IEC 62443 work for the CRA.

Map your 62443 process evidence to Annex I and Annex VII per product, then add what the CRA requires on top: SBOMs, reporting and support periods.