Industrial software vendors and machine builders in DACH increasingly face IEC 62443 requirements from their customers, and since 11 September 2026 the reporting obligations of the Cyber Resilience Act apply to manufacturers of products with digital elements. When part of the development is done by an external team, a common mistake is to ask the vendor whether they are IEC 62443 certified and stop there. Certification of a service provider tells you little about how your product is built. The better approach is to translate the secure development lifecycle of IEC 62443-4-1 into specific requirements, deliverables and evidence for the external team, so that your own process remains complete. This guide shows how.

The threat picture in numbers

The business case for a disciplined secure development lifecycle is now written in figures. In Bitkom's 2025 economic protection study, about 87 percent of German companies reported being affected by data theft, espionage or sabotage, with total damage of 289.2 billion euros, of which 202.4 billion euros, or 70 percent, was attributed to cyberattacks. Industrial software sits in the middle of this exposure. Bitkom's 2026 Industrie 4.0 study found that 97 percent of German manufacturers with 100 or more employees use at least one Industrie 4.0 application and 45 percent use digital twins, so connected products are the norm, not the exception. The Cyber Resilience Act, covered in detail below, turns this into market access law, with fines for breaches of the essential requirements of up to 15 million euros or 2.5 percent of worldwide annual turnover, whichever is higher. The engineers who can do this work are scarce: Bitkom counted 79,000 unfilled IT positions in Germany in 2026.

Which parts of IEC 62443 are relevant

The IEC 62443 series has several parts. For an external development team building or extending an industrial product, three matter most.

  • IEC 62443-4-1 defines secure product development lifecycle requirements for product suppliers, organised in eight practices, and a maturity model from 1 to 4.
  • IEC 62443-4-2 defines technical security requirements for components (embedded devices, host devices, network devices, software applications) against security levels 1 to 4.
  • IEC 62443-2-4 defines requirements for service providers that integrate and maintain automation solutions. It becomes relevant if the external team also does integration or maintenance at operator sites.

Your organisation is the product supplier under 4-1. The external team works inside your lifecycle. Their contribution must produce the evidence each practice requires.

The eight practices as requirements for the external team

Practice (IEC 62443-4-1)What the external team must doEvidence
SM: Security managementFollow your defined process, named security contact, training records for engineers on the productTraining log, role assignment
SR: Specification of security requirementsDerive security requirements from the threat model for each featureRequirements linked to threats in the ALM tool
SD: Secure by designDocument trust boundaries and defence in depth for new componentsArchitecture records with security review sign-off
SI: Secure implementationCoding guidelines, static analysis, peer reviewCI reports, review records per merge
SVV: Security verification and validation testingSecurity requirement tests, fuzzing of protocol parsers, vulnerability scanningTest reports per release
DM: Management of security-related issuesTriage and fix vulnerabilities within agreed timeframesIssue tracker with severity and timestamps
SUM: Security update managementProduce tested, signed patches and release notesSigned artefacts, update test records
SG: Security guidelinesContribute hardening and configuration guidance for product documentationReviewed user documentation sections

Two items deserve particular attention. First, SM requires that people working on the product are trained in the process. Second, DM and SUM require response timelines. Both must be written into the contract, otherwise they will not be met under pressure.

The Cyber Resilience Act raises the stakes

Regulation (EU) 2024/2847 applies to manufacturers of products with digital elements placed on the EU market, regardless of where development takes place. Since 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe incidents: an early warning within 24 hours of becoming aware, a notification within 72 hours, and a final report later (for vulnerabilities, within 14 days after a corrective or mitigating measure is available). Most other obligations, including the essential cybersecurity requirements and conformity assessment, apply from 11 December 2027.

For a setup with an external team, the 24-hour window is the practical constraint. If the engineers who understand the affected component sit in another time zone and learn about a vulnerability through a weekly meeting, you will miss it. The DM practice must include an escalation path that reaches the external team within hours, and the team must be able to support the technical assessment the same day.

Remote access to operational technology

External development teams sometimes need access to test plants, customer systems or field devices. In OT environments, the rule is simple: no direct access from external networks. Recommended pattern:

  • Access only via a jump host in a DMZ controlled by you or the operator, never via a VPN directly into the control network.
  • Named accounts with multi-factor authentication, no shared credentials.
  • Access windows approved per session, with recording.
  • No write access to production controllers by default. Changes to PLC programs follow the operator's management of change process.
  • Test systems with production-like configuration, so that most work never needs production access.

Contract clauses that make it real

Under a Werkvertrag, the following items work well as part of the Leistungsbeschreibung and acceptance criteria:

  1. The contractor works according to the client's documented secure development process (reference to process version).
  2. All engineers assigned complete the client's process training before receiving repository access.
  3. Every release delivery includes static analysis results with no open findings above the agreed severity, a software bill of materials, and security test results.
  4. Vulnerabilities reported to the contractor are forwarded to the client's PSIRT contact within a defined number of hours.
  5. For critical vulnerabilities, the contractor provides technical assessment support within one business day.
  6. Signing keys and release authority remain with the client.

Set the maturity target realistically

IEC 62443-4-1 uses maturity levels from 1 (initial) to 4 (improving). Many product suppliers aim for level 3, where the process is defined and practised consistently across projects. An external team cannot be more mature than the process it works in. If your own lifecycle is still at level 1 or 2, use the engagement to formalise it: the external team's need for written rules often forces the documentation that an internal team never wrote down.

Where an external pod adds the most value

SVV and SUM are labour-intensive and often under-resourced in mid-sized industrial software companies: fuzzing harnesses, security regression suites, SBOM generation, patch backporting across product versions. These are well suited to an external team working inside your process. A workable split is for one senior role to own the evidence structure across the eight practices while engineers build the test and release automation. Our own controls are summarised on the security page.

This article is general information and not legal advice. For binding statements on CRA obligations for your products, consult a qualified lawyer.

Under the CRA, the evidence of a secure development lifecycle becomes part of what you sell, and external contributors either strengthen that evidence or dilute it. A niogod™ pod works inside your IEC 62443-4-1 process under a Werkvertrag whose sprint Abnahme includes the security artefacts, with the Senior Consultant accountable for the evidence structure across the eight practices. If 11 December 2027 is a date your product roadmap has to meet, it is a conversation worth having early.

Talk to niogod™

Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.

Book consultation
← All insights