IEC 62443 Explained: Industrial Cybersecurity Basics
IEC 62443 is the international standards series for securing industrial control systems. Here is how its roles, security levels, and zones work.
IEC 62443 is an international series of standards for the security of industrial automation and control systems (IACS). It sets requirements for the organizations that own and operate those systems, the firms that integrate and maintain them, and the companies that build the products inside them. The International Society of Automation (ISA) and the International Electrotechnical Commission (IEC) each publish it, so you will also see it written as ISA/IEC 62443. ISA says the series covers people, processes, and technology across a system's full lifecycle.
Four ideas carry most of the series. A system is divided into zones joined by conduits. A risk assessment gives each zone and conduit a target security level. Products and designs are chosen to reach that target. Defined roles share the responsibility.
In ISA's definition, an IACS includes the personnel, hardware, software, and policies involved in running an industrial process. The standards themselves are sold by ISA and IEC. This explainer relies on public summaries of them: ISA's overview guides, IEC catalogue entries, and U.S. government guidance.
Where the Series Came From
ISA's account dates the work to its ISA99 committee, which first met in Chicago in October 2002. The first standard in what became the series was ISA-99.00.01-2007. Today the ISA99 committee and IEC Technical Committee 65, Working Group 10, work on the documents under a formal liaison, with ISA99 leading most parts and Working Group 10 having developed Part 2-4.
The ISA Global Cybersecurity Alliance says ISA99 first looked at IT standards and found them insufficient, because an attack on a control system can also cost lives or damage the environment. The series began in the process industries. ISA now lists electric power generation and distribution among its uses. ISA announced in November 2021 that the IEC had designated the series a horizontal standard, the IEC's term for technology-independent standards that apply across many technical areas.
How the Series Is Organized
ISA arranges the documents in four groups by primary focus and audience, and NIST SP 800-82 uses the same four names: General, Policies and Procedures, System, and Component. For Parts 1 to 4, the first digit gives the group, so Part 3-2 sits in the System group.
General (Part 1) holds shared material. Part 1-1 covers terminology, concepts, and models. Newer entries add a scheme for security profiles (Part 1-5) and guidance on the Industrial Internet of Things (Part 1-6).
Policies and Procedures (Part 2) covers organizations. Part 2-1 sets security program requirements for asset owners. Part 2-2 gives guidance on a security protection scheme, the technical, physical, and process measures protecting each IACS in operation. Part 2-3 covers patch management. Part 2-4 sets requirements for service providers during integration and maintenance.
System (Part 3) covers whole systems. Part 3-1 is a technical report assessing security technologies. Part 3-2 covers risk assessment and system design. Part 3-3 sets system security requirements and security levels.
Component (Part 4) covers products. Part 4-1 sets requirements for a supplier's secure development lifecycle. Part 4-2 sets technical requirements for components, which ISA groups as embedded devices, host devices, network devices, and software applications.
IEC's catalogue also lists two evaluation documents. Part 6-1 gives a method for evaluating against Part 2-4, and Part 6-2 gives one for evaluating components against Part 4-2.
What Is Current as of November 2026
IEC's list of Technical Committee 65 publications, checked on November 5, 2026, shows these as current. General: TS 62443-1-1:2009, TS 62443-1-5:2023, and PAS 62443-1-6:2025. Policies and Procedures: 62443-2-1:2024 (Edition 2), PAS 62443-2-2:2025, TR 62443-2-3:2015, and 62443-2-4:2023 (Edition 2). System: TR 62443-3-1:2009, 62443-3-2:2020, and 62443-3-3:2013. Component: 62443-4-1:2018 and 62443-4-2:2019. Evaluation: TS 62443-6-1:2024 and TS 62443-6-2:2025.
The prefixes matter. Entries with no prefix are International Standards. TS marks a technical specification, TR a technical report, and PAS a publicly available specification. IEC notes that a PAS is automatically withdrawn after four years.
IEC also lists revisions under way, with forecast publication dates: Part 1-1, retitled Overview and Guidance for the IEC 62443 Series (December 2027); a second edition of Part 4-1 (April 2028); and a third edition of Part 2-4 (May 2028). A project on Part 6-1 is forecast for December 2027.
Two cautions apply. A reference to an IEC 62443-4-2:2026 should be checked, because IEC's list on November 5, 2026 still showed the 2019 edition with a 2022 corrigendum. Separately, the European standards body CENELEC said in 2025 that it was preparing amendments to the European versions of Parts 4-1 and 4-2 for the EU Cyber Resilience Act. The ISA and IEC catalogues also differ in places. ISA describes the two sets as identical, but in November 2026 its list showed a 2018 adoption of the older Part 2-4 text, while IEC listed the 2023 edition.
The Roles
ISA calls shared responsibility an essential building block of automation cybersecurity, and its overview guide names the roles.
The asset owner is the organization accountable and responsible for the IACS. In energy, that is typically the utility or plant operator, since Part 2-1 treats the operator as part of the asset owner. ISA says the asset owner stays ultimately accountable for secure operation and needs support from suppliers and service providers.
The service provider comes in two forms. An integration service provider, often called the integrator, designs, installs, tests, and commissions an automation solution and hands it over. A maintenance service provider supports the solution once it is running. Part 2-4 applies to both.
The product supplier makes and supports hardware or software products. Parts 4-1, 4-2, and 3-3 are its main documents.
The series keeps two things apart. A supplier delivers a control system or component. An automation solution is the realization of a control system at a particular facility.
Zones and Conduits
ISA defines a zone as a grouping of logical or physical assets based on risk or on criteria such as criticality, operational function, location, required access, or responsible organization. A conduit is a logical grouping of communication channels that share common security requirements and connect two or more zones.
The point is to give assets with similar needs one set of requirements and to limit how far a successful attack can spread. Part 3-2 sets the process: define the system under consideration, partition it into zones and conduits, assess the risk of each, set a target security level for each, and document the result. ISA says the asset owner chooses the risk method, and that the standard requires or recommends separating some assets, including safety-related assets, wireless devices, and temporarily connected devices.
Readers often meet zones alongside the Purdue Model. NIST treats levels, tiers, and zones as alternative ways of grouping components before placing isolation devices between them. In practice, a Purdue level describes a position in a reference hierarchy, and a zone is drawn from a specific system's risk assessment. An August 2025 joint guide from the Cybersecurity and Infrastructure Security Agency (CISA) and partner agencies used the series to build an example asset taxonomy for electricity organizations.
Security Levels
ISA defines a security level as a measure of confidence that a system, zone, or conduit is free from vulnerabilities and works as intended. Part 3-3 expresses it in terms of the attacker. ISA's overview gives four levels. Security Level 1 protects against casual or coincidental violation. Level 2 protects against intentional violation using simple means, low resources, generic skills, and low motivation. Level 3 assumes sophisticated means, moderate resources, skills specific to IACS, and moderate motivation. Level 4 assumes sophisticated means, extended resources, IACS-specific skills, and high motivation.
You will often see the scale written as SL 0 to SL 4. ISA and IEC public summaries define levels 1 to 4. The IEC's Smart Energy committee also shows a 0 in an example vector and describes that element as none.
The right level for a zone comes from its risk assessment. As one reference point, a January 2025 guide for operational technology (OT) buyers from CISA and partner agencies says its advice aligns with Security Level 3 of Parts 3-3 and 4-2 for product security features.
Target, Capability, and Achieved
The same scale is used in three ways.
A target security level (SL-T) is the level wanted for a zone or conduit. It comes out of the Part 3-2 risk assessment and is recorded in a cybersecurity requirements specification. A capability security level (SL-C) is what a system or component can provide when properly integrated and configured, without added compensating measures. Part 3-3 defines it for systems and Part 4-2 for components. An achieved security level (SL-A) is the actual level of a zone or conduit, measured after the automation solution is commissioned and in operation.
In short, the owner sets SL-T, the supplier offers SL-C, and the running site has an SL-A. ISASecure, the certification program described below, says a product certificate shows only an SL-C, and the asset owner must add the policies, processes, and skilled people needed to meet SL-A.
The following example is illustrative and comes from no cited source. A utility places a substation's protective relays and remote terminal unit in one zone and treats the link to the control center as a conduit. Its risk assessment sets a target for that zone. It buys relays with a matching capability level. An older device that falls short gets a compensating measure, which Part 2-1 allows for legacy systems. After commissioning, the utility measures what the zone has achieved.
Foundational Requirements
Technical requirements in the series are organized under seven foundational requirements (FRs): identification and authentication control, use control, system integrity, data confidentiality, restricted data flow, timely response to events, and resource availability.
Part 3-3 attaches detailed system requirements to each FR, and Part 4-2 does the same for components. The IEC's Smart Energy committee explains that the security level of a zone or conduit is a vector with one value per FR, for example SL=(3,3,3,1,2,1,3). A zone can therefore need strong integrity and modest confidentiality at once.
ISA's overview adds an OT-specific limit. Part 3-3 says security measures must not adversely affect the essential functions of a high-availability system, such as safety functions, control, and the operator's view of the process, unless a risk assessment supports it.
Maturity Levels
Security levels measure technical strength. Maturity levels measure process: how thoroughly people, policies, and procedures meet a requirement. ISA says Parts 2-1, 2-2, 2-4, and 4-1 use them.
The model is based on Capability Maturity Model Integration (CMMI), with that model's levels 4 and 5 combined. Level 1, Initial, is ad hoc and often undocumented. Level 2, Managed, has written policies and trained staff, though some processes may not yet be in practice. Level 3, Defined or Practiced, has repeatable processes in use with documented evidence. Level 4, Improving, uses metrics and continuous improvement. IEC says the 2024 edition of Part 2-1 added a defined maturity model for evaluating its requirements.
Certification
Separate schemes certify specific things against specific parts. A claim of being 62443 certified means little until you know the part, the scheme, and, for products, the level.
ISASecure is run by the ISA Security Compliance Institute, a nonprofit subsidiary of ISA. Certification bodies accredited under ISO/IEC 17065 perform the assessments. Its product and process programs are Security Development Lifecycle Assurance (Part 4-1), System Security Assurance (Part 3-3), Component Security Assurance (Part 4-2), and an Industrial Internet of Things component program. A newer program, Automation and Control System Security Assurance, evaluates a deployed control system, and the asset owner's related policies and procedures, against Parts 2-1, 2-4, 3-2, and 3-3. ISASecure gives its version 1.0.0 an effective date of February 17, 2026, and ISA announced the program's first accredited certification body in June 2026.
The IEC's route is the Industrial Cyber Security Programme of IECEE, one of its four conformity assessment systems. An IECEE document, OD-2061, describes how assessment applies to the series. Part 6-2 supplies an evaluation method and says it does not define a complete certification scheme. ISA also awards training certificates to individuals, which it says should not be confused with product certification.
How It Relates to NERC CIP
The North American Electric Reliability Corporation's Critical Infrastructure Protection (NERC CIP) standards are enforceable rules for one sector. The Federal Energy Regulatory Commission (FERC) describes Reliability Standards as mandatory, with penalties under Section 215 of the Federal Power Act. NIST describes the CIP set as covering generation and high-voltage transmission above 100 kV, the bulk electric system. IEC 62443 applies to IACS in any sector, and the IEC says adoption of its standards is voluntary, though laws and regulations often reference them. A regulator, contract, or customer can make it binding.
The vocabulary differs. CIP-002 categorizes BES Cyber Systems (BES is the bulk electric system) as high, medium, or low impact, based on the adverse impact their loss, compromise, or misuse could have on reliable operation. IEC 62443 sets a target level per zone from a risk assessment. CIP-005-7, enforceable as of November 2026, specifies a controlled Electronic Security Perimeter for high and medium impact BES Cyber Systems. IEC 62443 uses zones and conduits.
As of November 2026, a text search of all 29 CIP documents NERC listed, from CIP-002 through CIP-015, found no reference to IEC 62443. A web search that month did not turn up an official crosswalk from NERC, FERC, ISA, or IEC. It found vendor comparisons, which we did not rely on.
How It Relates to NIST SP 800-82
NIST Special Publication 800-82 is guidance. Revision 3, published in September 2023, describes OT topologies, threats, and countermeasures. Organizations outside the federal government may use it voluntarily.
The two are closely linked. NIST thanks ISA for allowing portions of the standards to be used, lists the series in an appendix, and maps tasks in its risk management steps to Part 2-1. It points readers to Part 3-2 for OT risk assessment and to Part 2-3 for patch management.
The initial public draft of Revision 4 appeared on September 21, 2026, with comments due November 30, 2026. It reorganizes the guide around the NIST Cybersecurity Framework 2.0 and keeps references to Parts 3-2 and 2-3. It is a draft and may change.
Other References an Energy Reader Will Meet
CISA's Cross-Sector Cybersecurity Performance Goals, version 2.0 (December 2025), say every goal maps to controls in frameworks such as the NIST Cybersecurity Framework and ISA/IEC 62443.
ISO/IEC 27001 is the information security management standard. An ISA Global Cybersecurity Alliance paper from June 2025 calls it complementary to 62443, with 27001 addressing an organization's IT management system and 62443 addressing OT-specific needs. For energy, the IEC's Smart Energy committee says 62443 can be used with ISO/IEC 27019 and IEC 62351.
Related articles
Sources
- International Society of Automation, "ISA/IEC 62443 Series of Standards"
- ISA Global Cybersecurity Alliance, "Quick Start Guide: An Overview of ISA/IEC 62443 Standards" (table status as of June 2025)
- IEC, TC 65 Dashboard: Work programme and Publications tabs (checked November 5, 2026)
- IEC 62443-2-1:2024, webstore abstract
- IEC 62443-2-4:2023, webstore abstract
- IEC 62443-3-2:2020, webstore abstract
- IEC 62443-3-3:2013, webstore abstract
- IEC 62443-4-1:2018, webstore abstract
- IEC 62443-4-2:2019, webstore abstract
- IEC PAS 62443-1-6:2025, webstore abstract
- IEC PAS 62443-2-2:2025, webstore abstract
- IEC TS 62443-6-2:2025, webstore abstract
- IEC, "Cyber security" (horizontal standards, IECEE, OD-2061)
- IEC, "Frequently Asked Questions"
- IEC Systems Committee Smart Energy, "IEC 62443"
- ISA, "The International Electrotechnical Commission Designates ISA/IEC 62443 as a Horizontal Standard" (November 2021)
- ISA InTech, "The ISA-99 Industrial Automation and Control Systems Security standards" (2020)
- ISA, ISASecure "Quick Start Guide: Overview of ISASecure Certification" (2024)
- ISASecure, "ACSSA Certification"
- ISA, "Perseus Information Security Consulting Becomes Fully Accredited Certification Body for ISASecure ACSSA Program" (June 2026)
- CEN-CENELEC, "CRA Standards Unlocked: From EN IEC 62443 to CRA" (webinar notice, September 2025)
- NIST SP 800-82 Rev. 3, "Guide to Operational Technology (OT) Security"
- NIST SP 800-82 Rev. 3 (PDF), including Sections 5 and 6 and Appendix D
- NIST SP 800-82 Rev. 4, initial public draft (September 2026)
- CISA and partners, "Foundations for OT Cybersecurity: Asset Inventory Guidance for Owners and Operators" (August 2025)
- CISA and partners, "Secure by Demand: Priority Considerations for Operational Technology Owners and Operators when Selecting Digital Products" (January 2025)
- CISA, "Cross-Sector Cybersecurity Performance Goals, Version 2.0" (December 2025)
- ISA Global Cybersecurity Alliance, "Applying ISO/IEC 27001, ISO/IEC 27002 and the ISA/IEC 62443 Series for Operational Technology Environments" (June 2025)
- FERC, "Enforcement Reliability"
- NERC, CIP-002-8, "Cyber Security: BES Cyber System Categorization" (PDF; subject to future enforcement July 1, 2028, and the enforced CIP-002-5.1a has the same categorization purpose)
- NERC, CIP-005-7, "Cyber Security: Electronic Security Perimeter(s)" (PDF)
- NERC, CIP reliability standards listing, CIP-002 through CIP-015 (checked November 2026)