Services > Security
IEC 62443 compliance analysis for industrial manufacturers
Find out where your products and development processes stand against IEC 62443, what needs to change, and which improvements to prioritize before customer assessments or certification.
- Secure development processes
- Component security
- Remediation roadmap
Our approach
Evidence-based assessment. Proportionate remediation.
We assess your development processes against IEC 62443-4-1 and your products against IEC 62443-4-2. You walk away with documented gaps, prioritized actions and a clearer path to the assessment or certification outcome you need.
Where remediation is needed, we scope the work to the applicable security requirements, the actual risks and the engineering constraints of your product. If you want our engineers to help with implementation, we can. If not, you keep the roadmap and carry out the work internally.
Delivered IEC 62443 work
Danfoss Drives: IEC 62443 Security Level 1 readiness without hardware redesign
Our work with Danfoss Drives shows how cybersecurity requirements can be addressed on established industrial platforms. We combined risk analysis with firmware and software engineering to implement the necessary security controls on the VLT® drives and the MCT 10 tool while preserving product usability.
Role-based access control, audit logging and authentication were implemented through firmware and desktop software upgrades. The solution passed a TÜV SÜD audit with no major issues, without hardware redesign.
What we assess
Assessment against the applicable IEC 62443 requirements
Depending on your goals, we assess your secure development practices against IEC 62443-4-1, your industrial automation components against IEC 62443-4-2, or both. The findings inform a prioritized remediation roadmap.
Development processes
IEC 62443-4-1
- Secure development lifecycle practices
- Security requirements, design and verification
- Vulnerability and security defect management
- Security updates and release processes
- Process documentation and supporting evidence
Deliverable: documented development-process gaps and recommended improvements.
Products and components
IEC 62443-4-2
- Threat modeling (STRIDE)
- Security risk and attack-path analysis, including MITRE ATT&CK for ICS
- Software composition and vulnerability analysis
- Static source-code security analysis
- Gap analysis against the applicable component security requirements and capability levels
Deliverable: documented technical security gaps and recommended remediation actions.
STRIDE, MITRE ATT&CK for ICS, software composition analysis and static code analysis are methods we apply where appropriate, not mandatory steps of every assessment.
How an IEC 62443 engagement runs
Where you stand, what must change and how to address it
A typical engagement starts with a fixed-scope assessment. Everything after that is shaped by what the assessment finds, including whether you want engineering remediation from us at all.
Documented gaps. Clear next steps.
-
Step 1
Assess
Review the applicable development-process and product requirements and document the gaps. Fixed scope.
-
Step 2
Prioritize
Define the remediation roadmap, considering risks, requirements and engineering feasibility. Delivered with phase 1.
-
Step 3
Implement
Our engineers help close the gaps, or you implement the roadmap internally. Optional.
FAQ
IEC 62443: the questions we hear most
IEC 62443 is an international series of standards for the cybersecurity of industrial automation and control systems. It covers both technical security requirements and the processes used to develop, integrate and operate these systems. Different parts apply to different roles: product suppliers, system integrators and asset owners.
They’re different instruments. The CRA is an EU regulation that sets cybersecurity requirements for products with digital elements sold in the EU. Its reporting obligations have applied since 11 September 2026, and its full requirements apply from 11 December 2027. IEC 62443 is a voluntary standard. Following it doesn’t automatically make a product CRA-compliant, but the two overlap considerably in areas such as secure development, vulnerability handling and security by design, so work done for one supports the other.
For device and component manufacturers, two parts are usually most relevant. IEC 62443-4-1 sets requirements for a secure product development lifecycle. IEC 62443-4-2 sets technical security requirements for components such as embedded devices, network components and software applications. IEC 62443-3-3 covers security requirements at the system level and is more relevant to system integrators. We help you establish which requirements apply to your product before the assessment starts.
Often, yes, but it depends on the product. For Danfoss Drives, we brought legacy drives to IEC 62443 Security Level 1 readiness through software changes alone, with no hardware redesign. Where software can close a gap, we recommend doing it in software. Hardware changes are only proposed where they’re actually needed.
We scope each assessment around your goals: your secure development processes (IEC 62443-4-1), a product or component against its technical requirements (IEC 62443-4-2), or both. We agree the scope with you before the assessment starts.
It depends on your product’s intended use, the threats it faces and what your customers or target markets require. Part of the assessment is establishing which level your product actually needs, so you invest where it matters and avoid over-engineering.
Get in touch
Share your IEC 62443 assessment needs
Tell us which parts of the standard apply to you and what triggered the need for an assessment. We'll set up a short online call to see whether we're the right partner.
Terry London
Product Manager & Partner
Languages: EST, ENG