Key takeaways
- ISO 27001 answers how the company manages information security risk. IEC 62443 answers how a control system, its integrators and its components are secured.
- Use ISO 27001 when customers want a certificate or you need one governance system. Use 62443 for zone design, security levels and OEM requirements.
- The 2024 edition of IEC 62443-2-1 removed its overlap with an ISMS, which makes running both easier.
- The most common mistake is extending IT ISMS controls blindly to OT: monthly patching, agents on HMIs and vulnerability scans on live controllers.
- One risk method, one register, one management review. Two sets of technical requirements, each where it fits.
"Should we do ISO 27001 or IEC 62443?" comes up in almost every mid-market manufacturer once a customer questionnaire or NIS2 lands on the CIO's desk. It is the wrong question. The two standards answer different things. ISO 27001 tells you how to run information security as a managed system across the company. IEC 62443 tells you how to secure industrial control systems and what to demand from the people who build and supply them. Most manufacturers need some of both. The trick is not doing everything twice.
The short version
- ISO/IEC 27001:2022 is a management system standard. It sets requirements for establishing, running and improving an information security management system (ISMS). It is certifiable and widely recognized by customers.
- ISA/IEC 62443 is a series of standards for industrial automation and control systems (IACS). It covers the asset owner's security program, risk assessment by zones and conduits, system security requirements and security levels, integrator practices and product development. It is technical, OT-specific and role-based.
Side-by-side comparison
| ISO/IEC 27001:2022 | ISA/IEC 62443 | |
|---|---|---|
| What it is | One management system standard, with a control annex | A series of standards and technical reports |
| Main question | Is information security risk managed systematically? | Is this control system and its supply chain secured to the right level? |
| Scope | Any organization, any information | Industrial automation and control systems |
| Priorities | Confidentiality, integrity and availability, set by your risk assessment | Safety, availability and integrity first in practice; confidentiality usually lower |
| Who it addresses | The organization | Asset owner, service provider/integrator, product supplier |
| Risk approach | Your own method, meeting the standard's requirements | Zones and conduits with target security levels (3-2) |
| Technical controls | Generic Annex A reference controls | Detailed system and component requirements under seven foundational requirements (3-3, 4-2) |
| Levels | None | Security levels 1 to 4; maturity levels for processes |
| Certification | Organization's ISMS, by accredited certification bodies | Mainly products, systems and supplier processes (e.g. ISASecure); site assessments are less common |
| Typical buyer signal | Customer and corporate requirements | OEM, integrator and OT-specific requirements |
| Cost to access | One standard plus guidance | Several paid parts; you rarely need all |
When each fits
ISO 27001 fits when:
- customers ask for a certificate in their supplier questionnaires,
- you need one governance system for IT, OT, engineering data and HR,
- you have no consistent risk process, policy set or management review today,
- your group already runs an ISMS and the plants need to join it.
IEC 62443 fits when:
- your plants have flat networks and you need a defensible segmentation design,
- you are buying new lines, machines or a DCS and need to specify security to OEMs and integrators,
- you need to set and justify security levels for zones such as SIS-adjacent networks or remote access,
- you make industrial products and need a secure development basis, which also supports the Cyber Resilience Act.
For most mid-market manufacturers, the answer is "both, layered". See the full IEC 62443 guide for the parts that matter.
How to run both: ISMS umbrella, 62443 for OT
ISO 27001 ISMS (whole company)
- policy, scope, roles, risk method, risk register
- internal audit, management review, improvement
|
+-- IT controls (Annex A as reference)
|
+-- OT security program (IEC 62443-2-1)
- zones and conduits per site (62443-3-2)
- target SLs and system requirements (62443-3-3)
- integrator requirements (62443-2-4)
- component requirements to OEMs (62443-4-1/4-2)
How to make that work in practice:
- One scope. Write the ISMS scope to include the plants and their control systems. Say explicitly that OT controls are specified using IEC 62443.
- One risk method, two lenses. Keep one risk register. For OT entries, use the 62443-3-2 zone and conduit assessment as the method, and record the result as a register entry with an owner. Include safety, environmental and production impacts, not just data loss.
- Statement of Applicability that points to 62443. For Annex A controls that apply in OT, reference how they are met there. For example, access control in the plant points to the zone design and FR1 and FR2 requirements.
- Separate technical baselines. Keep an IT hardening and patching standard and an OT one. Do not merge them.
- One audit and management review cycle. Internal audits cover OT using 62443-based checklists. Management review sees both.
The 2024 edition of IEC 62443-2-1 helps here. IEC states that it restructured requirements into security program elements and removed overlap with an ISMS, so the asset-owner program is designed to sit next to a management system rather than duplicate it.
Plant-floor reality: The ISMS will produce policies that make sense in the office and break things in the plant. Give the OT lead or a senior controls engineer a formal sign-off on any policy that applies to Level 0 to 3. That one rule prevents most of the friction.
Common mistakes: extending IT controls blindly to OT
These are the ones we see most in mid-market plants:
- Monthly patching mandates for OT. Controllers and HMIs are often patched during planned shutdowns, after OEM approval and testing. Write an OT patch standard that ties to maintenance windows and uses compensating controls in between.
- Endpoint agents on every Windows box. Some HMIs and SCADA servers are vendor-validated configurations. An unapproved agent can void support or cause outages. Use OEM-approved tools, application allowlisting or network monitoring instead.
- Active vulnerability scans on live control networks. Scanning can crash old controllers. Use passive discovery and planned, coordinated active checks.
- Password rotation rules on shared HMI logins and device accounts. Fix the shared login problem first. Rotation on a line HMI at 3 a.m. with no one who knows the new password is a safety risk.
- Confidentiality-first risk scoring. A data-centric method underrates a malicious logic change that could damage equipment or hurt someone. Add safety and production impact scales.
- Ignoring OEM remote access. Supplier relationship controls get applied to software vendors but not to the machine builder's always-on router in the cabinet.
- Certificate scope that quietly excludes the plants. A certificate for "head office IT" does not tell customers anything about the factory.
Watch out: An ISO 27001 certificate whose scope excludes OT can create false comfort at board level. Make sure leadership knows what is and is not in scope.
A note on versions
ISO/IEC 27001:2022 is the current edition, amended in 2024 with climate action changes. Its Annex A has 93 controls in four themes: organizational, people, physical and technological. The transition period for certificates under the 2013 edition ended on October 31, 2025.
For 62443, editions differ between the ISA and IEC catalogs. As of November 2026, IEC lists 62443-2-1 Edition 2.0 (2024) and 62443-2-4 Edition 2.0 (2023). Always cite the exact edition in contracts and audit scopes.
What good looks like
A year in, a manufacturer running both well can show:
- one ISMS scope statement that names every plant, with OT included rather than carved out,
- one risk register where OT entries carry safety and production impact, owned by named plant leaders,
- a zone and conduit drawing per site, with a target security level per zone and a list of accepted gaps,
- a Statement of Applicability that points to 62443-based OT procedures instead of repeating IT text,
- purchasing templates that ask OEMs and integrators for 62443 evidence before the order, not at SAT,
- internal audit reports that include at least one plant visit per year, done with a controls engineer.
None of this needs a large team. It needs clear ownership and the discipline to keep IT and OT technical rules separate under one management system.
Effort and cost
For a manufacturer with 3 to 5 plants and 500 to 1,500 staff:
- ISO 27001 from scratch: typically 9 to 18 months to certification with a small internal team and some outside support, plus annual surveillance audits.
- 62443 asset-owner basics (2-1, 3-2) at one site: 2 to 4 months for an inventory, zone model and target SLs. Roll out site by site after that.
- Adding OT to an existing ISMS: mostly scope, risk method and SoA changes, plus OT technical baselines. Months, not years, but the network work it uncovers takes longer.
How this connects to everything else
- NIST CSF 2.0 is a good board-level structure on top of both.
- The framework crosswalk and crosswalk workbook map ISO 27001, 62443, CSF, NIS2 and the CRA so one control produces evidence for several.
- Governance between IT and OT is covered in IT/OT convergence governance.
Where to start: Monday-morning checklist
- Check whether you have an ISMS today, and what its scope really includes.
- Ask your top customers what they require: a certificate, a questionnaire, or 62443 evidence.
- Pick one plant and draw its zones and conduits with the zones and conduits worksheet.
- Review your IT patching, scanning and endpoint policies for anything that would hurt a live line.
- Give the OT lead sign-off on policies that apply to the plant floor.
- Run the OT security maturity assessment to set the order of work.
If you rely on either standard to meet a legal or contractual duty, confirm the approach with counsel.
Sources and further reading
- ISO/IEC 27001:2022 Information security management systems (ISO)
- ISO/IEC 27001:2022/Amd 1:2024 Climate action changes (ISO)
- ISA/IEC 62443 Series of Standards (ISA)
- IEC 62443-2-1:2024 Security program requirements for IACS asset owners (IEC Webstore)
This guide is general information for manufacturers, not legal advice. Confirm regulatory obligations with qualified counsel.
FAQ
Frequently asked questions
Can ISO 27001 cover OT and production systems?
Yes. ISO/IEC 27001 is scope-neutral. You can include plants and control systems in the ISMS scope. The Annex A controls are generic, so on their own they say little about PLCs, safety systems or zones and conduits. Most manufacturers that include OT add IEC 62443 or NIST SP 800-82 as the technical reference for how controls are applied in the plant.
Is IEC 62443 certification the same as ISO 27001 certification?
No. ISO 27001 certification is of an organization's management system, audited by an accredited certification body. IEC 62443 certification is most established for products, systems and supplier processes, for example through ISASecure or IECEE schemes. Asset owners more often get an assessment against 62443-2-1 and 3-2 than a site certificate. The two answer different questions for different audiences.
Which should a mid-sized manufacturer do first?
If customers or regulators ask for a certificate, or you have no security governance at all, start with an ISO 27001-style ISMS scoped to include the plants. If you already have reasonable governance but the plants are flat networks with uncontrolled OEM access, start with the 62443 risk assessment and zones and conduits. Many companies do the ISMS core and a 62443 pilot site in parallel.
Do ISO 27001 Annex A controls map to IEC 62443?
Partly. Many topics overlap: access control, asset management, supplier relationships, incident management, backup and logging. But 62443 adds concepts ISO 27001 lacks, such as zones and conduits, security levels and component capability requirements, and it treats safety and availability as primary. A crosswalk helps you avoid duplicate evidence, but it is not one-to-one.
Related guides
Frameworks
IEC 62443 for mid-market manufacturers: a practical guide
ISA/IEC 62443 is the main international series for securing industrial automation and control systems.
Guide · 8 min read
Frameworks
NIST CSF 2.0 for manufacturers: one language for IT, OT and the board
NIST Cybersecurity Framework (CSF) 2.0 is a voluntary, outcome-based framework that organizes cybersecurity into six functions: Govern, Identify, Protect, Detect, Respond and Recover.
Guide · 7 min read
Frameworks
AI and OT security framework crosswalk for manufacturers
No single framework covers AI governance and OT security.
Guide · 8 min read
OT Security
IT/OT convergence governance: who owns what in a mid-market plant
IT/OT convergence fails on ownership, not technology.
Guide · 7 min read