Article · 6 min read

IEC 62443 or NIST CSF: which one should you start with?

They answer different questions. Use one to run the programme and the other to secure the plant, and keep one list of controls for both.

The short answer

Most small and mid-sized operators ask us this question in the first call. The answer is that you do not choose one. The two frameworks answer different questions, and a utility under NIS2 needs answers to both.

NIST CSF answers "is our security programme complete, and who is accountable?". IEC 62443 answers "how do we protect the systems that run the process?". If you start with only one, you get either a good policy with an unprotected plant, or a well-segmented plant that nobody in management owns.

The trick is to avoid two projects. Use one list of controls, and map each control to the framework that it comes from.

What each one is

NIST Cybersecurity Framework (CSF) 2.0

The US National Institute of Standards and Technology publishes the CSF. Version 2.0 came out in 2024. It is free, short and used in every sector. It groups security into six functions:

  • Govern: strategy, roles, accountability, policy and supply chain risk. This function is new in 2.0.
  • Identify: assets, risks and improvement.
  • Protect: access control, training, data security, platform security.
  • Detect: monitoring and analysis of events.
  • Respond: incident management, analysis, reporting.
  • Recover: restoring systems and communication after an incident.

CSF tells you what to cover. It does not tell you how to segment a SCADA network or which security level a PLC zone needs. For that detail in OT, NIST points to its own OT guide (SP 800-82) and to IEC 62443.

IEC 62443

IEC 62443 is a series of international standards for the security of industrial automation and control systems. It is written for plants, not offices. For an operator, four parts matter most:

  • 62443-2-1: the security programme of the asset owner, which is you.
  • 62443-2-4: security requirements for service providers. Use it for your integrators and maintenance contractors.
  • 62443-3-2: risk assessment, and how to divide the plant into zones and conduits.
  • 62443-3-3: the technical requirements for a system, by security level.

The standards are not free, and they are detailed. You do not need to read all of them. A small operator gets most of the value from the zones and conduits method and from the integrator requirements.

Side by side

NIST CSF 2.0IEC 62443
AnswersIs the programme complete and governed?Are the control systems protected?
Written forAny organisationIndustrial automation and control systems
Who reads itManagement, the security lead, auditorsAutomation engineers, integrators, the security lead
CostFreePaid, per part
Gives youA profile: where you are and where you want to beZones, conduits, security levels, requirements for suppliers
CertificationNonePossible for products and processes, not needed to start

Where NIS2 fits

NIS2 does not tell you to use a specific standard. Article 21 lists the measures you must have, and the directive encourages European and international standards. In practice:

  • The management duties (Article 20) fit CSF Govern. Approval, supervision, training and a named owner are all Govern topics.
  • The measures (Article 21) cover both. Risk analysis, incident handling and business continuity fit CSF. Access control, network security and supply chain security in the plant fit IEC 62443.
  • The authority checks evidence, not the framework name. A control register that shows each measure, its owner and its proof is what an inspector can use.

What we recommend for a utility like yours

  1. Use CSF 2.0 as the frame. Make a simple profile: for each CSF category, where you are today and where you need to be. This is the page for the board, and it covers the NIS2 management duties.
  2. Use IEC 62443-3-2 for the plant. Draw the zones (office, DMZ, control, safety) and the conduits between them. Start with the conduit that matters most: remote access from outside.
  3. Use IEC 62443-2-4 for your integrators. Put its requirements into contracts and access rules. In our sectors, vendor remote access is where many incidents start.
  4. Keep one control register. One line per control, with its owner, its evidence, and the reference to CSF, IEC 62443 and NIS2 Article 21. One list, three views.

The first 90 days

  1. Weeks 1 to 2: a short CSF profile with the operations lead and IT. One day of workshops.
  2. Weeks 3 to 6: a network drawing with zones and conduits, checked on site.
  3. Weeks 7 to 10: the control register, with the top ten gaps and an owner for each.
  4. Weeks 11 to 12: a one-page summary for the board, and the plan for the next year.

This order gives you a board-level picture in two weeks and a plant-level picture in six, without buying anything.

Common mistakes

  • Chasing a certificate first. A certificate does not protect a pump station. Start with the gaps.
  • ISO 27001 for the office only. It is a good management system, but if its scope stops at IT, the plant stays out of the programme.
  • Two projects, two teams. One team does CSF for management, another does IEC 62443 for OT, and nobody joins them. Keep one register.
  • Buying a tool to "become compliant". A tool can help with one control. It cannot replace the programme.

Where to start

Take the NIS2 readiness check for a first picture by area, or download the30-point OT security checklist. If you want help with the first 90 days, book a 30-minute call.

NIST CSF 2.0 is published by the US National Institute of Standards and Technology. IEC 62443 is published by the International Electrotechnical Commission. This article is a plain-language summary, not legal advice.

Not sure where you stand on cybersecurity and regulations?

Book a 30-minute call. Tell us about your operations. We tell you if we can help, and when we cannot.