Cybersecurity

IEC 62443-4-2

IEC 62443-4-2 framework badge
Summarize with
ClaudeChatGPTPerplexityGoogle AI Mode
In this article
At a Glance
IEC 62443-4-2:2019
  • Classification
    Category
    Cybersecurity
    Domain
    Cybersecurity
    Framework Family
    ISO Industry Standards
  • Regulatory Context
    Type
    Framework
    Legal Instrument
    Standard
    Sector
    Critical Infrastructure
    Industry
    Critical Infrastructure
  • Region / Publisher
    Region
    Global
    Region Detail
    International
    Publisher
    International Electrotechnical Commission (IEC); also published by ISA as ANSI/ISA-62443-4-2-2018
  • Versioning
    Version
    IEC 62443-4-2:2019, Edition 1.0 (with corrigendum COR1:2022)
    Effective Date
    February 27, 2019
    Issue Date
    February 27, 2019 (corrigendum August 30, 2022)
  • Adoption
    Adoption Model
    Industry Requirement
    Implementation Complexity
    High
  • Official Reference
License Information

License included / downloadable: No

IEC 62443-4-2 is a copyrighted standard sold by the IEC and by ISA, and its text is not included with the platform.

Framework text is licensed by its publisher and is included only where stated above.

Official Resources
IEC 62443-4-2:2019 on the IEC Webstore
Edition 1.0 of the technical security requirements for IACS components, published 27 February 2019, with the August 2022 corrigendum noted.
Key takeaways
  • IEC 62443-4-2:2019 sets the technical security requirements for components used in industrial automation and control systems.
  • Edition 1.0 was published February 27, 2019, with a corrigendum in August 2022; ISA publishes the same text as ANSI/ISA-62443-4-2-2018.
  • Its component requirements derive from IEC 62443-3-3 system requirements, which rest on the seven foundational requirements of IEC TS 62443-1-1.
  • The standard defines a component's capability security level, SL-C; target and achieved security levels are out of scope.
  • Suppliers can show conformity through ISASecure CSA certification.

Overview

IEC 62443-4-2:2019 is the international standard for the technical security requirements of the components used in industrial automation and control systems (IACS): software applications, embedded devices, host devices and network devices. The IEC published Edition 1.0 on 27 February 2019, with a corrigendum in August 2022. Product suppliers use it to design and certify components, and system integrators and asset owners use it to specify and buy them.

It is part 4-2 of the IEC 62443 series, prepared by IEC technical committee 65, and ISA publishes the same text as ANSI/ISA-62443-4-2-2018. Its component requirements (CRs) derive from the system requirements of IEC 62443-3-3, which in turn rest on the seven foundational requirements (FRs) of IEC TS 62443-1-1. The standard defines the capability security level of a component, SL-C(component); target and achieved security levels are out of scope (clause 1).

A product supplier builds the CRs and requirement enhancements (REs) into the product for the level it claims, and documents how to integrate it into a system. An integrator sets the target level for each zone under IEC 62443-3-2 and chooses components whose SL-C meets it. Suppliers can show conformity through ISASecure CSA certification.

Why does it matter?

A control system reaches a target security level only if its parts can support it. The Introduction explains that IACS security goals focus on availability, plant protection, plant operations and time-critical response, so a countermeasure must not cause the loss of essential services. IEC 62443-4-2 turns that into requirements a component can be built and tested against.

Key benefits include:

  • Requirements a supplier can build to

Clauses 5 to 11 set out component requirements (CR 1.1 to CR 7.8), each with rationale, requirement enhancements and security levels.

  • A buying specification

System integrators use the standard to specify the security capability level they need from each component when they procure control system components (0.2).

  • Availability protected

The first common component security constraint, CCSC 1, is support of essential functions (4.2), in line with the Introduction's point that countermeasures should not cause loss of essential services.

  • Four component types covered

Clauses 12 to 15 add software application (SAR), embedded device (EDR), host device (HDR) and network device (NDR) requirements.

  • A route to evidence

ISASecure CSA certifies components against the standard, and IEC TS 62443-6-2:2025 gives an evaluation methodology for components assessed against it.

How does it work?

The standard opens with scope, normative references and terms (clauses 1 to 3), then sets four common component security constraints (clause 4). Clauses 5 to 11 cover one foundational requirement each, FR 1 to FR 7, and clauses 12 to 15 give the requirements that differ by component type. Annex A describes device categories and Annex B maps every CR and RE to security levels 1 to 4.

Each CR follows the same pattern: the requirement, rationale and supplemental guidance, requirement enhancements, and the security levels at which it applies (for example 5.3.1 to 5.3.4 for CR 1.1, human user identification and authentication). The combination of CRs and REs determines the security level a component is capable of (0.2).

A component does not have to supply every capability itself. The Introduction gives the example of an embedded device that uses a system-wide authentication and authorization service instead of keeping its own user directory, and the supplier documents how to integrate the component to meet a given target level.

Key Elements

  • Seven foundational requirements

FR 1 identification and authentication control (CR 1.1 to 1.14), FR 2 use control (CR 2.1 to 2.13), FR 3 system integrity (CR 3.1 to 3.14), FR 4 data confidentiality (CR 4.1 to 4.3), FR 5 restricted data flow (CR 5.1 to 5.4), FR 6 timely response to events (CR 6.1 and 6.2), FR 7 resource availability (CR 7.1 to 7.8).

  • Common component security constraints (clause 4)

Four constraints apply to every component: CCSC 1 support of essential functions, CCSC 2 compensating countermeasures, CCSC 3 least privilege and CCSC 4 software development process.

  • Requirement enhancements and security levels

Some CRs carry enhancements (REs). Annex B summarizes, for every CR and RE, the security level from SL 1 to SL 4 at which it applies.

  • Component-specific requirements (clauses 12 to 15)

Software applications have SAR 2.4 and 3.2. Embedded devices add EDR requirements such as tamper resistance (3.11), roots of trust (3.12, 3.13) and boot integrity (3.14). Host devices (HDR) and network devices (NDR) have parallel sets, and network devices add zone boundary protection (NDR 5.2).

  • Device categories (Annex A)

Annex A (informative) describes the categories of devices commonly used in IACS, to help suppliers and integrators decide which component type applies.

  • Evaluation and certification

ISASecure CSA assesses components against the standard through four evaluations, and IEC TS 62443-6-2:2025 specifies a repeatable evaluation methodology for components assessed against IEC 62443-4-2.

What does it cover?

IEC 62443-4-2 applies to the components of an IACS: software applications, embedded devices, host devices and network devices. The Introduction names its audience as asset owners, system integrators, product suppliers and, where appropriate, compliance authorities. It defines capability security levels for components. Target security levels (SL-T) and achieved security levels (SL-A) of a whole system are out of scope, and IEC 62443-2-1 covers the non-technical program requirements for the asset owner.

What are its objectives?

The Introduction and clause 1 set out what the standard is meant to achieve.

Specify the security capabilities that let a component mitigate threats for a given security level without the help of compensating countermeasures.

Define component requirements for the seven foundational requirements described in IEC TS 62443-1-1.

Define the capability security level of a component, SL-C(component).

Let integrators specify the security capability level they need when they procure components.

Guide product suppliers on which requirements can be allocated to other parts of the system and which should be native in the component.

Framework in Context

IEC 62443-4-2 derives its requirements from IEC 62443-3-3, uses the zones and target levels produced under IEC 62443-3-2, and relies on the supplier's secure development process under IEC 62443-4-1 (Practice 8 covers integration documentation). CEN, CENELEC and ETSI's work program for the Cyber Resilience Act standardization request (M/606, 2 April 2025) lists a European amendment to IEC 62443-4-2:2019 among its supporting operational technology deliverables. The IEC lists a stability date of 2027.

Common Framework Mappings

IEC 62443-4-2 is commonly mapped to the system, enterprise and sector frameworks below so that component requirements line up with system and program controls.

Mapped frameworks include:

IEC 62443-3-3

IEC 62443-4-1

ISO 27001:2022

NIST CSF 2.0

NIST SP 800-82

NERC CIP

SMARTSUITE

How SmartSuite Supports IEC 62443-4-2

SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.

Use Cyber & IT Risk to hold the component requirements for each product or purchased component, record the SL-C claimed or required, and link each requirement to the test evidence, open vulnerabilities and supplier that support it.

Component Requirements Library

Hold CR 1.1 to CR 7.8 and their requirement enhancements, grouped by foundational requirement (FR 1 to FR 7) and security level.

Component Type Register

Record whether each component is a software application, embedded device, host device or network device, and apply the SAR, EDR, HDR or NDR set that goes with it.

Security Level Target and Claim

Record the SL-C required for each component and the SL-C the supplier claims, per zone, with the gap and the owner.

Compensating Countermeasure Log

Document any compensating countermeasure used where a component cannot meet a requirement natively (CCSC 2), with approver and review date.

Verification and Test Evidence

Attach functional test results, vulnerability testing and ISASecure CSA or IEC TS 62443-6-2 evaluation evidence to each requirement.

Supplier and Certificate Tracking

Track supplier documentation, certificate scope and expiry for each component, and report open gaps by plant and zone.

Related frameworks

ISO 27001:2022

ISO/IEC 27001:2022 specifies requirements for an information security management system: Clauses 4 to 10, risk treatment, the Statement of Applicability and 93 Annex A controls.

ISO 27002:2022

ISO/IEC 27002:2022 is the reference set of 93 information security controls in four themes, with attributes and implementation guidance, that supports an ISO/IEC 27001 ISMS.

NIST 800-53 Rev.5

NIST SP 800-53 Rev. 5 is the NIST catalog of security and privacy controls in 20 families, mandatory for federal systems under OMB A-130 and FISMA; Release 5.2.0 issued August 27, 2025.

NIST CSF 2.0

NIST CSF 2.0 (CSWP 29, February 26, 2024) is the voluntary cybersecurity framework with six Functions including Govern, 22 Categories, 106 Subcategories, Profiles and Tiers.

NIST 800-82 Rev.3 Moderate OT

Moderate baseline of the NIST SP 800-82 Rev. 3 OT overlay: SP 800-53B moderate controls tailored for moderate-impact OT systems, with the Appendix F additions, removals and tailoring rules.

FAQ

Frequently Asked Questions For IEC 62443-4-2 (Security for Industrial Automation and Control Systems)

IEC 62443-4-2:2019 sets technical security requirements for the components of an industrial automation and control system: software applications, embedded devices, host devices and network devices. Edition 1.0 was published on 27 February 2019 and a corrigendum followed in August 2022. The IEC webstore lists a stability date of 2027 and no newer edition.

They are identification and authentication control (FR 1), use control (FR 2), system integrity (FR 3), data confidentiality (FR 4), restricted data flow (FR 5), timely response to events (FR 6) and resource availability (FR 7), each described in clauses 5 to 11 as a group of component requirements (CR 1.1 to CR 7.8).

The standard defines the capability security level of a component, SL-C(component), from the requirements and enhancements it meets; Annex B maps each one to SL 1 to SL 4. Target levels and achieved levels of a system are out of scope. ISAGCA's guide describes SL 1 as protection against casual or coincidental violation and SL 4 as protection against intentional violation using sophisticated means with extended resources.

Yes, through ISASecure CSA (Component Security Assurance), whose version 1.0.0 took effect on 28 August 2019. A supplier must pass a security development lifecycle assessment for components, and the certification adds artifact, functional security and vulnerability identification evaluations. IEC TS 62443-6-2:2025 separately specifies an evaluation methodology for components against the standard.

Clause 4 sets four constraints that apply to every component: support of essential functions (CCSC 1), compensating countermeasures (CCSC 2), least privilege (CCSC 3) and software development process (CCSC 4). They sit alongside the requirements for each foundational requirement.

Put this framework to work in SmartSuite

Manage controls, risks, evidence, and audits in one platform designed for modern governance, risk, and compliance.