Standards · Industrial cybersecurity

IEC 62443 — Industrial communication networks

Network and system security. Industrial communication networks and the Internet of Things make production facilities and critical infrastructure more vulnerable to IT attacks.

Supervision of a robotic line
The stakes

Opening up systems comes at a price

Industrial automation and control systems (IACS) are usually made up of standardized hardware and software, integrated within a network. But the relative openness that this integration implies increases the risk of manipulation and attacks on the IT infrastructure.

The aim of IEC 62443 is to prevent their effects. It proposes a holistic approach to the IT security of the plant, network security and system integrity.

The standard helps to identify potential vulnerabilities in control technologies and to develop effective protective measures.

Industrial emergency stop control
Structure

Four categories, four audiences

The standard is structured in four main parts: General, Policies and Procedures, System and Component.

Part 1

General

Common, foundational information: concepts, models and terminology. It also includes the documents describing security metrics and IACS security life cycles.

Part 2

Policies and Procedures

Aimed at the asset owner. It covers the various aspects of creating and maintaining an effective IACS security program.

Part 3

System

Documents describing design guidance and requirements for the secure integration of control systems.

Part 4

Component

Technical and development requirements specific to control system products. Intended primarily for vendors, it is also used by integrators and asset owners when purchasing secure products.

Implementation

Securing the code itself

IEC 62443-4-1, dedicated to the secure product development life cycle, requires you to apply secure coding standards (practice SI-2) and to review the implementation to detect security weaknesses, in particular through static analysis (practice SI-1).

Part of the vulnerabilities lies in the source code: secure coding rules not followed, vulnerable third-party dependencies, areas of complexity where defects hide. TiCS brings these measurements together in a single dashboard — code security, compliance with standards, technical debt — and tracks them over time.

Software composition analysis and the SBOM it produces complete this setup, and meet the obligations of the Cyber Resilience Act, applicable since 11 September 2026 for the reporting of exploited vulnerabilities.

Discover TiCS → Evaluate TiCS on a pilot repository

Process supervision screen
TiCS on video

From the developer's workstation to CI

IEC 62443-4-1 describes a secure development life cycle. The animation shows how every defect, code security issues included, is detected from the developer's workstation to continuous integration, where it costs the least.

The 14 TiCS animations →
Sector

Industrial automation

References, testimonials and uses of our tools in automation and process control.

See the sector page →

Other standards

The standards landscape

DO-178C, EN 50716, IEC 60880, IEC 61508, IEC 62304, ISO 26262, ISO 25119: each standard sets its own requirements.

See all standards →