TroutTrout
Back to Blog
IEC 62443NIST

OT Cybersecurity Frameworks: IEC 62443, NIST CSF and More

Trout TeamLast updated: 5 min read

Which framework to use for OT

Which cybersecurity framework should you use for OT? Use IEC 62443 if you need an OT-specific zone and conduit architecture. Use NIST CSF if you need a flexible risk management approach that covers both IT and OT. You can use them together, because each one covers ground the other does not. This article explains each framework and how to map one to the other.

What IEC 62443 covers

Overview of IEC 62443

The IEC 62443 series is a set of standards from the International Electrotechnical Commission (IEC) written for industrial automation and control systems (IACS). It covers the security of OT environments across the whole lifecycle of an IACS. The standard has several parts: general requirements, policies and procedures, system requirements and component requirements.

Key Components of IEC 62443

  1. Security Levels (SLs): Security levels set how much protection each part of an industrial system needs, from SL 1 (basic protection) to SL 4 (advanced protection).

  2. Zones and Conduits: The standard divides the network into zones and controls the traffic between them through conduits, so a threat in one zone cannot spread freely.

  3. Security Policies and Procedures: The standard requires written security policies and procedures that fit the industrial environment, and requires you to keep them current.

Implementing IEC 62443 in Practice

To implement IEC 62443:

  • Run a risk assessment to find vulnerabilities and set the security level for each zone.
  • Write and enforce security policies that meet the standard's requirements.
  • Use network segmentation and access controls to build the zones and conduits.
  • Review and update your security measures on a schedule as new threats appear.

What NIST CSF covers

Overview of the NIST Cybersecurity Framework

The NIST Cybersecurity Framework (CSF) was first written for IT environments, and OT teams now use it too. It takes a flexible, risk-based approach to managing cybersecurity risk, which you can adapt to industrial systems.

Core Functions of the NIST Framework

The NIST CSF is built around five core functions:

  1. Identify: Understand your organization's environment so you can manage cybersecurity risk to systems, assets, data and capabilities.

  2. Protect: Put safeguards in place so critical infrastructure services keep running.

  3. Detect: Set up the activities that spot a cybersecurity event when it happens.

  4. Respond: Set up the activities that act on a detected cybersecurity event.

  5. Recover: Keep plans for resilience and restore the capabilities or services that an incident impaired.

Tailoring NIST for OT Environments

To apply the CSF in an OT environment:

  • Identify: Map all OT assets and their connections to understand the risk.
  • Protect: Use defense in depth and Zero Trust to protect OT assets.
  • Detect: Use monitoring built for OT threats, such as anomaly detection for industrial protocols.
  • Respond and Recover: Write an incident response plan with OT steps, such as running a line in manual, and a recovery plan for each process.

How IEC 62443 and NIST CSF compare

Strengths and Limitations

  • IEC 62443 is written for OT, so it applies directly to industrial environments. Its zones and conduits give you a structured way to segment the network.
  • NIST CSF is broader and more flexible, and it adapts to many sectors, including OT. Its risk-based method suits organizations that want to run IT and OT security as one program.

Choosing the Right Framework

The choice between IEC 62443 and NIST depends on what you need:

  • If your work centers on industrial automation, IEC 62443 applies more directly.
  • If you want one program that covers both IT and OT, NIST CSF fits better.

How to use IEC 62443 and NIST CSF together

Harmonizing Frameworks

Use IEC 62443 for the network design and NIST CSF for the program. In practice:

  • Map the security levels from IEC 62443 to the NIST risk management process.
  • Use the technical controls from IEC 62443 inside the NIST risk management strategy.
  • Follow the NIST cycle of continuous monitoring and improvement.

What combining them gives you

One control set can answer several audits, because a control mapped to both frameworks counts for each standard and regulator that references them.

Where to start

Start by mapping your current OT security controls to both IEC 62443 and NIST CSF. Find the gaps where one framework covers a requirement the other does not. Use the IEC 62443 zone and conduit model for your network architecture and the five NIST CSF functions (Identify, Protect, Detect, Respond, Recover) for the structure of your security program. If CMMC or NERC CIP also applies to you, cross-reference those requirements so you do not do the same work twice.

Other Articles

Cold ChainOT Security

CISA Fact Sheet on Industrial Refrigeration and Cold Chain Controllers: The Eight Mitigations as a Checklist

On November 5, 2026, CISA, the FBI, HHS, USDA and DOT published a joint fact sheet on malicious activity against industrial refrigeration and cold chain monitoring systems. Attackers go after unpatched or internet-accessible temperature controllers and push units into continuous heating and defrost. The fact sheet lists eight mitigations. Most of them come down to taking the controllers off the internet and controlling how the refrigeration contractor connects.

ICS AdvisoriesOT Security

Hitachi Energy TRO600: Unauthenticated File Read Exposes Router Passwords (ICSA-26-302-02)

On October 29, 2026, CISA republished Hitachi Energy advisory 8DBD000224 as ICSA-26-302-02. It covers two CVEs in the TRO600 series of industrial cellular routers: an unauthenticated file read that exposes configuration files and password data, and a port-forwarding bypass that lets a logged-in user reach services meant for localhost only. Version 9.2.2.1 fixes both.

ICS AdvisoriesOT Security

Siemens SIMATIC WinCC, PCS 7 and Process Historian: NTLM Relay With No Fix (ICSA-26-321-08)

CISA's ICSA-26-321-08 republishes Siemens SSA-970803: CVE-2026-58114, an NTLM relay weakness in SIMATIC WinCC V7.5 to V8.1, WinCC Runtime Professional V17 to V21, PCS 7 V9.1, BATCH V9.1, Process Historian and Information Server. An on-path attacker can take over a user's session and run code with that user's rights. No product has a fix, and four will not get one, so the SQL traffic has to be encrypted and the servers closed off from every host that does not need them.