Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
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.
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.
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.
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.
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.
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.
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.
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.
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.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.