Skip to content
13/19StandardOut of scope

IEC 62443 explained

The cybersecurity standard for industrial and OT environments.

See current catalog counts, technical check coverage, and remaining gaps

This reference explains the framework. Product coverage depends on the bundled catalog, connected evidence, and assessment scope; a technical mapping is not full compliance.

What it is

A series of standards for the security of industrial automation and control systems (IACS/OT) — covering asset owners, integrators, and product suppliers across plants, ICS, and connected machinery.

Certifiable?

Yes — certification schemes exist for products and organizations.

Where it's used

Manufacturing, energy, utilities, industrial plants, connected machinery.

Effort level

Heavy and specialized.

Typical trigger

You operate or build industrial/OT systems.

Related frameworks

OT counterpart to the IT-focused frameworks.

Why it matters

IEC 62443 is the definitive standard for securing industrial and operational technology. As OT environments become more connected, it provides the security framework that keeps physical processes — power plants, factories, water systems — safe.

When is it needed?

When building, integrating, or operating industrial automation systems; when OT/ICS environments need a security program; when selling industrial products that require security certification.

Use cases

  • Securing industrial control systems (ICS/SCADA)
  • Manufacturing plant cybersecurity programs
  • Energy and utility infrastructure protection
  • Industrial product development (PLCs, RTUs, HMIs)
  • System integrator security assurance

Who asks for it?

  • Industrial asset owners and operators
  • OT/ICS security teams
  • System integrators building automation solutions
  • Regulatory bodies for critical infrastructure
  • Industrial product buyers requiring security ratings

Benefits

  • Covers the full industrial lifecycle (owner, integrator, supplier)
  • Security Level (SL) ratings for components and zones
  • Certification schemes for products and organizations
  • Addresses IT/OT convergence challenges
  • Risk-based zone and conduit model
  • Recognized globally in industrial sectors

Legal requirements

Increasingly referenced in critical infrastructure regulations (NIS2, KRITIS). Some sectors (nuclear, defense) mandate IEC 62443 compliance for control system procurement.

Key control areas

Security management system for IACS
Zone and conduit segmentation model
Security Level (SL) target and achieved ratings
Product development security requirements
System integration security practices
Patch management for industrial systems

Want to see how WardBee maps your environment to IEC 62443?

What's new · v1.0.0

ScanComb and WardBee 1.0: compliance checks, TISAX and SOC 2 readiness, and a new public site

This is the first release of ScanComb and WardBee. WardBee brings automated compliance checks, framework workspaces, reports and task tracking for engineering, security and compliance teams. scancomb.com adds free checks and a TISAX readiness check, plus guides and news.

Highlights

  • TISAX readiness check Answer a public questionnaire and get a free readiness score by email. A paid report adds findings, an action plan for each chapter, a roadmap and a PDF. You can import the gaps into a WardBee workspace as tasks.
  • Dedicated TISAX section in WardBee Manage TISAX in one place. Set the scope, keep a self-assessment register, follow an action plan with tasks, track audits and labels, and manage suppliers and exports.
  • SOC 2 readiness Work through a readiness questionnaire, criterion guidance, a policy pack and reviews. Criteria are explained in plain words and questions can be answered in the side drawer. You can download a SOC 2 readiness report as a PDF.
  • Sovereignty Profile free check Run the free Sovereignty Profile check and get a report. The scores are explained in plain words.
  • Projects with a shared scan pool Run several projects or clients in separate workspaces that share one pool of scans. A For consultants page explains the setup.

Improvements

  • Resource inventory See an inventory of your resources with filters, saved views and notifications.
  • EU Cyber Resilience Act support Prepare for the EU Cyber Resilience Act with product classification and a continuous technical file.
  • NIS2 Supplier Check Assess suppliers against NIS2 with the NIS2 Supplier Check.
  • Free AI security check and AI Shield playbooks Take a free AI security check and read practical playbooks on AI agent permissions, prompt injection, shadow AI and more.
  • Manual control verification Verify controls that cannot be checked automatically, using a clearer drawer for manual controls.
  • Clearer controls and findings Findings and resource names are easier to read, you can filter to checks-only scans, and you can compare one scan with the previous one.
  • Faster control and dashboard pages Controls, the dashboard and risks load faster. App pages show a loading state right away.
  • Better start for new workspaces New workspaces start with ISO 27001 and SOC 2, with an explanation of what scans do. If no frameworks are chosen, a Choose frameworks step guides you.
  • Support tickets, announcements and notification bell Open support tickets inside WardBee and get email updates. Announcements appear in a header bell.
  • New site design, menu and guides scancomb.com has a new look and a grouped menu with News, Free checks and Guides. WardBee uses the same visual style, and the in-app docs are task-focused guides.
  • What's New and Framework Watch A What's New dialog shows release notes on scancomb.com. A weekly Framework Watch news issue is also published.
  • Team invitations and two-factor sign-in Invite teammates by email with consistent role names. Two-factor setup includes a QR code.

Fixes

  • Security improvements to sign-up and sign-in Sign-up and sign-in are now better protected.
  • More accurate AWS multi-factor authentication checks All MFA device types are now recognized, and users who only use programmatic access are no longer flagged.
  • Confirmed failures are shown correctly A confirmed failure now outranks an error in a control's status.
  • One critical-control email per scan You now get a single critical-control email per control for each scan.
  • Smoother onboarding and failed checks Workspaces without frameworks are sent to setup. Checks that fail are refunded, and queued checks show as Queued.
  • Correct access errors Signed-out or unauthorized requests now get a proper access error instead of a server error.