Join our Newsletter — 33% off our NHI Course
Home› Guides› IEC 62443-4-1 and 4-2 Secure Product Development Guide:…
Guide OT & IoT Security

IEC 62443-4-1 and 4-2 Secure Product Development Guide: Building and Proving Secure Industrial Components

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 14 min read
On this page

Industrial products are still shipped with default passwords, unsigned firmware and no plan for patches, and asset owners cannot compensate for that at every site. IEC 62443-4-1 and 62443-4-2 are the two parts of the series that put security obligations on the product supplier: 4-1 defines how the product must be developed and maintained, and 4-2 defines the technical security capabilities a component must have. This guide explains both parts in practical depth for product security teams, PSIRTs, engineering managers and the buyers who write them into contracts. It covers the eight 4-1 practices, the 4-2 requirement families and component types, identity and credential requirements, how certification works, and how the parts relate to the EU Cyber Resilience Act. For the series as a whole, security levels and zones, see the IEC 62443 Guide.

Key takeaways

  • 4-1 is about process, 4-2 is about product capability. 4-1 applies to the development organisation and its lifecycle; 4-2 is assessed per component version against a capability security level (SL-C).
  • A component cannot claim an SL-C without a 4-1 process behind it. ISASecure Component Security Assurance (CSA) certification requires both 4-2 capability and 4-1 compliance at every level.
  • Identity requirements are the hardest to retrofit. Unique accounts, changeable authenticators, device authentication and certificate support (CR 1.1 to CR 1.9) shape firmware architecture and must be designed in.
  • Security guidelines are a deliverable. 4-1 requires hardening and integration documentation for users; a capable component deployed at default settings does not reach its rated level.
  • Both editions date from 2018 and 2019. IEC lists a stability date of 2027 for both, and EU product law is raising the bar, so plan for revision rather than treating today's text as final.

What it is and who it applies to

IEC 62443-4-1 Edition 1.0 (published 15 January 2018) is titled "Secure product development lifecycle requirements". The IEC abstract states that the requirements apply to the developers and maintainers of a product, not to integrators or users, and cover hardware, software and firmware from requirements definition through secure design, implementation, verification and validation, defect management, patch management and end of life. ISA publishes the same text as ANSI/ISA-62443-4-1-2018.

IEC 62443-4-2 Edition 1.0 (published 27 February 2019) is titled "Technical security requirements for IACS components". It defines component requirements (CRs) mapped to the seven foundational requirements (FRs) of IEC TS 62443-1-1, and the capability security level of a component, SL-C(component). It does not set target or achieved levels: those belong to the asset owner and system integrator under 62443-3-2 and 3-3. IEC lists a stability date of 2027 for both parts.

RoleWhat 4-1 means for youWhat 4-2 means for you
Product supplier (PLC, RTU, HMI software, switch, gateway, IIoT device)Run and evidence a secure development lifecycle across all in-scope productsDesign each component to meet CRs at a declared SL-C
System integratorAsk for evidence of the supplier's 4-1 process (for example an SDLA certificate)Select components whose SL-C meets the zone SL-T from the risk assessment
Asset owner and buyerWrite 4-1 practices into procurement (patch timelines, disclosure, end of support)Specify required SL-C per FR and component type in tenders
Certification bodyAssess the documented process and sampled artefactsTest component capability and known vulnerabilities

Structure and key requirements

IEC 62443-4-1: eight practices

PracticeRequirement prefixWhat auditors look for
1. Security managementSMDefined SDL with roles, training, tool and environment integrity, protection of private keys, management of third-party components, continuous improvement
2. Specification of security requirementsSRProduct security context, a threat model, security requirements derived from it, and review of requirements
3. Secure by designSDSecure design principles including defence in depth, documented trust boundaries and interfaces, design reviews
4. Secure implementationSICoding standards, static analysis and implementation reviews
5. Security verification and validation testingSVVTesting of security requirements, threat mitigation testing, vulnerability testing (fuzzing, known vulnerability scanning), penetration testing and tester independence
6. Management of security-related issuesDMReceiving and triaging reports, assessing and addressing issues, disclosure, and reviewing defect trends
7. Security update managementSUMQualified updates, documented update process, authenticity of updates, timely delivery and dependent component updates
8. Security guidelinesSGDefence in depth and integration guidance, hardening, secure configuration, decommissioning, account management and documentation review

Each practice is assessed for maturity rather than for a security level. The ISA Global Cybersecurity Alliance describes the maturity scale as CMMI based: Initial, Managed, Defined (Practiced) and Improving. A supplier with an ad hoc process can still ship a strong product, but cannot show it will do so repeatedly.

IEC 62443-4-2: requirement families and component types

4-2 organises requirements by FR. Each requirement may have requirement enhancements (REs); the combination of a CR and its REs decides the SL-C reached for that FR. Requirements apply to four component types, with type-specific variants where the generic CR is not enough:

Component typeExamplesPrefixTypical type-specific concerns
Software applicationEngineering software, historian, HMI applicationSARMobile code, application allowlisting interaction, session handling
Embedded devicePLC, RTU, safety controller, IED, smart sensorEDRBoot integrity, update support, physical diagnostic and test interfaces
Host deviceEngineering workstation or server running an operating systemHDRMalicious code protection, boot integrity, OS hardening
Network deviceIndustrial switch, firewall, router, wireless access pointNDRZone boundary protection, access via untrusted networks, denial of service

Common component security constraints (CCSCs) sit across all requirements. CCSC 1 requires that security measures support essential functions, so an account lockout must not stop an operator acting during a process upset. The others cover compensating countermeasures where a component cannot meet a CR itself, least privilege, and the software development process: 4-2 assumes the component was built under a 4-1 process.

Identity and NHI requirements

Most requirements under FR1 (identification and authentication control) and FR2 (use control) are about non-human identity as much as human: devices, processes, update services and integration accounts all authenticate to each other.

RequirementWhat it asks of the componentDesign implication
CR 1.1 Human user identification and authenticationIdentify and authenticate all human users on all interfacesNo shared, hidden or undocumented maintenance logins; the enhancement for unique identification raises SL-C
CR 1.2 Software process and device identification and authenticationIdentify and authenticate software processes and devicesDevice certificates or keys per unit, not one key per product line
CR 1.5 Authenticator managementInitial authenticator content, change of defaults, protection of stored authenticatorsForce change of default credentials at commissioning; never store authenticators in clear
CR 1.7 Strength of password-based authenticationConfigurable password strengthPolicy that operators can set without firmware change
CR 1.8 Public key infrastructure certificatesOperate with a PKI according to accepted practiceSupport for owner-issued certificates and renewal, not only a vendor self-signed certificate
CR 1.9 Strength of public key-based authenticationValidate certificates, check revocation, protect private keysSecure key storage (secure element or TPM where hardware allows)
CR 1.14 Strength of symmetric key-based authenticationProtect and manage shared symmetric keysPer-device keys and a rotation route for fieldbus and wireless protocols
CR 2.1 Authorization enforcementEnforce authorisations for all identified users and processesRole model that separates operator, engineer and administrator, and integration accounts with only the rights they need

On the development side, 4-1 security management requires protection of private keys used for code signing and update authenticity, and SUM requires that users can verify update authenticity. The MSI signing keys leak shows why: private firmware signing keys for 57 products and Boot Guard keys for 116 products appeared in data stolen in a ransomware attack, and keys burned into shipped hardware are hard to revoke. ATT&CK for ICS v20 tracks the abuse of weak product identity design as T1694.001 Default Credentials and T1694.002 Hardcoded Credentials, and malicious firmware as T1693.001 System Firmware. See the Code Signing Security Guide and the Device and IoT Identity Guide.

Implementation steps

  1. Scope the development organisation (month 1): name the business units, product lines and sites in scope. SDLA certification is granted to a named development organisation for a specific, version-controlled process, so the scope statement matters.
  2. Gap assess against 4-1 (months 1 to 2): for each practice, record the current process, evidence, owner and maturity. Typical early gaps are third-party component management, threat modelling and security guidelines.
  3. Write the SDL down (months 2 to 4): one controlled document set with gates per release (threat model reviewed, static analysis clean to threshold, vulnerability testing complete, guidelines updated). Link it to your Secure Software Development Lifecycle (SSDLC) Guide practices where the product line also ships IT software.
  4. Stand up the PSIRT and update path: intake, triage and disclosure (DM) and qualified, signed updates (SUM). Publish a disclosure policy and supported versions list. See the PSIRT Guide.
  5. Choose target SL-C per product: decide per FR, based on the zones customers will deploy into. A network device at a zone boundary often needs a higher FR5 level than a field sensor.
  6. Close 4-2 gaps by design: prioritise FR1 and FR3 (identity, integrity) because they change firmware architecture: unique credentials, certificate support, signed boot and signed updates.
  7. Pilot one product end to end: run the full SDL on one release, collect the artefacts, then commission a readiness review before formal assessment.
  8. Roll out and maintain: extend to other product lines, keep a defect trend review (DM) and re-run gap assessment annually. If a release cannot meet a gate, record the exception and its compensating measure rather than silently shipping.

Small versus large suppliers: a small vendor with one product line can run 4-1 with a handful of named roles and one SDL document, and may start with SDLA before component certification. A large vendor with acquired product lines should certify the common process first, then bring each acquired line into scope; inconsistent processes across lines are the most common reason scope is narrowed.

Evidence and assessment

The ISASecure schemes run under ISO/IEC 17065 through chartered certification bodies. As described on the ISASecure site:

SchemeStandardWhat is assessedOutput
SDLA (Security Development Lifecycle Assurance), version 3.0.0 effective 16 June 202062443-4-1The documented lifecycle process, plus representative artefacts from in-scope products chosen by the certifierCertificate for a named development organisation and process version
CSA (Component Security Assurance), version 1.0.0 effective 28 August 2019, replacing EDSA62443-4-2 and 4-1SDLPA-C (process), SDA-C (lifecycle artefacts for the component), FSA-C (functional security capabilities), VIT-C (known vulnerability scanning)Certificate stating component type and capability level, for example "Capability Security Level 2 (Embedded Device)"

Evidence a certifier or customer will ask for:

  • Process: the SDL document set, role assignments, training records and process change history.
  • Per release: threat model, security requirements trace to tests, static analysis results, fuzzing and penetration test reports, open defect list with risk acceptance.
  • Supply chain: third-party and open source component inventory, often delivered as an SBOM. See the SBOM Guide.
  • Customer facing: security guidelines, hardening guide, supported versions and end-of-support dates, advisories with VEX or CSAF where used.

Measures that show the programme works: median days from vulnerability report to fixed release by severity; percentage of releases passing all SDL gates without exception; percentage of products whose firmware updates are signed and verified on device; percentage of shipped units that force default credential change at commissioning; and the count of open known vulnerabilities in third-party components at release.

Buyers should check that a certificate names the exact product version and firmware, and should still follow the supplier's security guidelines. See the ISA/IEC 62443 Certification Guide for the people certification route, which is separate from product certification.

Mapping to other frameworks

62443-4-1 or 4-2 areaNIST SP 800-53 Rev. 5NIST CSF 2.0EU Cyber Resilience Act (Regulation (EU) 2024/2847)
SM, SR, SD, SI (lifecycle and design)SA-3, SA-8, SA-15PR.PS-06Annex I Part I essential requirements (security by design, risk assessment)
SVV (testing)SA-11, RA-5PR.PS-06Annex I: no known exploitable vulnerabilities at release
SM third-party componentsSR-4, SR-11GV.SC-05Annex I Part II: identify and document components, including an SBOM
DM (issue handling and disclosure)RA-5ID.RA-08Annex I Part II vulnerability handling; reporting obligations under Article 14
SUM (security updates)SA-10, SI-7PR.PS-02Annex I Part II: security updates distributed securely and without delay
4-2 FR1 and FR2 (identity, use control)IA-2, IA-3, IA-5PR.AA-01, PR.AA-03Annex I Part I: protection from unauthorised access, secure by default configuration
4-2 FR3 (integrity, signed boot and updates)SI-7PR.PS-02Annex I Part I: integrity of data, programs and configuration

CRA status, checked 27 October 2026: the CRA is dated 23 October 2024 and entered into force on 10 December 2024. Reporting obligations apply from 11 September 2026 and the main obligations from 11 December 2027. Presumption of conformity comes only from harmonised standards whose references are published in the Official Journal; 62443-4-1 and 4-2 are widely used as a basis for that work, but do not assume a presumption of conformity until a citation exists for your product category. See the EU Cyber Resilience Act Guide. In the US, 4-1 lines up closely with the NIST Secure Software Development Framework (SSDF, SP 800-218) Guide, and buyers increasingly ask for both. ATT&CK for ICS mitigation M0813 Software Process and Device Authentication maps directly to CR 1.2.

Common pitfalls

  • Certifying one product and marketing the brand: a CSA certificate covers a component version. Customers find out when they buy the next model.
  • A threat model written once: SR requires the threat model to drive requirements and be reviewed; a static document from the first release does not reflect new interfaces such as cloud connectivity.
  • One credential or key per product line: a single default password or symmetric key across all units makes one disclosure a fleet-wide compromise, and fails CR 1.5 and CR 1.14 intent.
  • Signing keys on a build server: keys held as files on shared CI infrastructure, without hardware protection or access logging, undermine every SUM control. The MSI case above is the warning.
  • Security guidelines as an afterthought: a capable component deployed with every service enabled does not achieve its rated level. SG deliverables need the same review as code.
  • Ignoring open source in firmware: unmanaged third-party components are the most common source of known vulnerabilities found in VIT-C style scanning.

Practitioner checklist

  • Write a scope statement naming the development organisation, product lines and process version.
  • Gap assess all eight 4-1 practices with owners, evidence and maturity per practice.
  • Make the threat model and security requirements a release gate, reviewed when interfaces change.
  • Ship unique per-device credentials or force change of defaults at commissioning.
  • Protect code and firmware signing keys in hardware with logged, approved use.
  • Sign firmware and updates, and verify signatures on the device before install and at boot.
  • Publish a disclosure policy, supported versions, end-of-support dates and an SBOM per release.
  • Declare SL-C per FR and component type, and keep the evidence for each CR and RE claimed.
  • Deliver security guidelines covering hardening, integration and decommissioning, and test them.
  • Track CRA harmonised standard citations and plan for revised 62443-4 editions.

Standards and references

Related NHI Mgmt Group resources: IEC 62443 Guide · IEC 62443-3-2 OT Risk Assessment Guide · OT Product Procurement Guide · EU Cyber Resilience Act Guide · PSIRT Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.