Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is IEC 62443-4-1?

IEC 62443-4-1 defines the secure development lifecycle requirements that a supplier of industrial products must follow, covering eight practices from security management to the handling of reported defects.

Home / Blog / Cybersecurity Terms / What Is IEC 62443-4-1?
17 November 2026

What Is IEC 62443-4-1?

What Is IEC 62443-4-1?

Asset owners spent two decades trying to secure products that had never been designed to be secured. IEC 62443-4-1 is the part of the series that addresses the other end of the problem: it tells the supplier how a product must be developed, and it gives the buyer something concrete to ask for. Where 62443-4-2 describes what a device must be able to do, 4-1 describes how the organisation that built it works.

The Eight Practices

  1. Security management (SM). The spine of the standard: a defined development process with security activities embedded, identified roles and competence, a controlled development environment, protection of the product and its components in the supply chain, and a record that the process was actually followed for each release.
  2. Specification of security requirements (SR). Security requirements derived from an explicit statement of the product’s intended environment and threat model, including the security capability the product claims and the assumptions it makes about the environment around it.
  3. Secure by design (SD). Defence in depth, least privilege, a documented architecture, and a threat model maintained across releases rather than written once at the start.
  4. Secure implementation (SI). Secure coding standards, implementation review, and verification that the design was followed.
  5. Security verification and validation testing (SVV). Functional testing of security capability, threat mitigation testing, vulnerability testing with static and dynamic analysis, and, significantly, penetration testing by people with appropriate independence from development.
  6. Management of security-related issues (DM). Receiving, triaging, tracking, and resolving reported defects, with a disclosure route and a defined response timescale.
  7. Security update management (SUM). Producing, qualifying, documenting, and delivering patches, including the dependency components that most industrial products carry.
  8. Security guidelines (SG). Hardening guidance, defence in depth documentation, and secure decommissioning instructions shipped with the product, so the asset owner can configure it to achieve the claimed level.

Maturity Levels, Not Security Levels

A point of regular confusion: 4-1 uses maturity levels rather than the security levels of 62443-3-3. The four maturity levels follow the familiar capability maturity pattern. At level 1 the activities are performed but ad hoc. At level 2 they are managed through a written process with trained staff. At level 3 the process is practised consistently across the organisation and evidenced. At level 4 the organisation measures and improves it. A supplier claiming conformance states the maturity level achieved per practice, and a buyer should read those numbers rather than the certificate headline.

Why Buyers Should Insist on It

The practical value for an asset owner is not philosophical. A supplier operating to 4-1 has a threat model you can request, a security capability statement you can compare against your target security level, hardening guidance you can hand to the commissioning engineer, a disclosure address that reaches a real team, and a patch process that produces updates you can actually install. A supplier without it will tell you to put a firewall in front of the product.

Two practices deserve particular attention in tender evaluation. Security update management determines whether you will ever be able to patch the device, which is the single biggest determinant of long-term risk in a twenty-year asset. And management of security-related issues determines what happens when a researcher finds something: a vendor with a functioning product security incident response process, aligned to the ISO/IEC standards on vulnerability disclosure and handling, will publish an advisory and a fix, while one without will go quiet.

Certification and the Regulatory Pull

Conformance is certified by accredited bodies under the ISASecure scheme and national certification arrangements, with a process audit followed by surveillance. Certification is increasingly a condition of tender in energy, water, rail, and pharmaceutical manufacturing, which has done more to drive adoption than any argument about good practice.

Regulation is pulling in the same direction. The EU Cyber Resilience Act places obligations on manufacturers of products with digital elements covering secure development, vulnerability handling, and support periods, and 4-1 is the most mature existing process standard against which industrial manufacturers can demonstrate them. In the United Kingdom, the Product Security and Telecommunications Infrastructure Act 2022 takes a narrower, consumer-focused approach, but industrial buyers are free to require 4-1 contractually and increasingly do. The standard also pairs naturally with a published software bill of materials and a verified firmware signing chain, both of which fall out of the update management and secure design practices.

For suppliers, the honest assessment is that 4-1 looks like DevSecOps written for organisations with multi-year release cycles and products in the field for decades. The practices are familiar; the difference is the evidence burden and the expectation that you will still be issuing patches in 2040.

At Privia Security, we support product teams with threat modelling, security verification, and independent testing through our Hardware Penetration Test Services.

FAQ – Frequently Asked Questions

What Is the Difference Between 62443-4-1 and 62443-4-2?

4-1 covers the development process: how the supplier specifies, designs, implements, tests, and maintains the product. 4-2 covers the product itself: the technical security capabilities a component must provide, aligned to the system requirements in 62443-3-3. A certificate against 4-1 says the organisation works properly; a certificate against 4-2 says this device can do particular things.

What Are the Maturity Levels in 62443-4-1?

Four, following the capability maturity pattern. Level 1 means activities are performed but informally. Level 2 means a written, managed process with trained staff. Level 3 means the process is practised consistently across the organisation with evidence. Level 4 adds measurement and continuous improvement. Suppliers state a level per practice, so read the detail rather than the headline.

Does 62443-4-1 Require Penetration Testing?

Yes. The security verification and validation testing practice requires vulnerability testing, including static and dynamic analysis and penetration testing, performed with appropriate independence from the development team. It also requires threat mitigation testing, which checks that the mitigations identified in the threat model actually work rather than merely existing in a document.

Should Asset Owners Require It in Tenders?

For control system equipment with a long service life, yes. It gives you a threat model, a security capability statement you can compare against your target security level, hardening guidance, a working disclosure route, and a patch process. Requiring it also shifts the conversation away from the supplier recommending a firewall as a substitute for product security.

Related Terms

You May Be Interested In These

What Is 5G Network Security?

Cybersecurity Terms

17 November 2026

What Is 5G Network Security?

Read More
What Is PowerShell Empire?

Cybersecurity Terms

17 November 2026

What Is PowerShell Empire?

Read More