Two operators at a control-room desk with a row of monitors, a laptop and keyboards

OT/ICS security

ISO/IEC 27019: information security controls for the energy utility industry, explained

Last updated:

ISO/IEC 27019, "Information security controls for the energy utility industry," takes the generic ISO/IEC 27002 control catalogue and adapts it for the part of an energy utility's environment that generic IT security guidance tends to fit badly: process control and automation systems controlling the generation, transmission, storage and distribution of electric power, gas, oil and heat. It lets a utility build an ISO/IEC 27001-conformant ISMS that reaches down to the OT layer instead of stopping at the IT boundary.

Scope wording, clause numbers and control names below come from the official sample pages of ISO/IEC 27019:2024 (cover, foreword, introduction, scope and table of contents). The guidance text of each control sits in the purchased standard; check it there before citing a clause in a compliance submission.

Key takeaways

  • Scope wording, clause numbers and control names below come from the official sample pages of ISO/IEC 27019:2024 (cover, foreword, introduction, scope and table of contents).
  • The 2024 scope clause names one exclusion: it "does not apply to the process control domain of nuclear facilities", which is covered by IEC 63096.
  • ISO/IEC 27019 is not a standalone ISMS standard — it is a sector-specific supplement.
  • The table of contents lists twelve ENR controls across three of the four themes; the people theme (clause 6) has none.

What does the 2024 scope cover, and what is excluded?

ISO/IEC 27019:2024 provides information security controls, based on ISO/IEC 27002:2022, for "controlling and monitoring the production or generation, transmission, storage and distribution of electric power, gas, oil and heat." Clause 1 of the official sample lists what that includes:

  • Central and distributed process control, monitoring and automation technology, plus the information systems used to operate it, such as programming and parameterization devices
  • Digital controllers and automation components — control and field devices, PLCs, digital sensors and actuators
  • Supporting information systems in the process control domain, such as data visualization, archiving, historian logging and reporting
  • Communication technology used in the process control domain: networks, telemetry, telecontrol applications and remote-control technology
  • Advanced metering infrastructure (AMI) components such as smart meters, and measurement devices such as those for emission values
  • Digital protection and safety systems: protection relays, safety PLCs, emergency governor mechanisms
  • Energy management systems for distributed energy resources (DER), electric charging infrastructure and customer installations, and distributed smart grid components
  • All software, firmware and applications installed on those systems, the premises housing them, and remote maintenance systems

The 2024 scope clause names one exclusion: it "does not apply to the process control domain of nuclear facilities", which is covered by IEC 63096. Summaries of the 2017 edition also describe telecommunication systems as out of scope; that carve-out does not appear in the 2024 scope clause, so check the purchased text before relying on it. For device makers, the firmware line matters most: software and firmware on meters, protection relays, gateways and chargers sit inside the scope.

How does it relate to ISO/IEC 27001 and 27002?

ISO/IEC 27019 is not a standalone ISMS standard — it is a sector-specific supplement. A utility still certifies against ISO/IEC 27001 for its management system; ISO/IEC 27019 extends ISO/IEC 27002's generic control catalogue. Clause 4 explains how: the document "has the same structure as ISO/IEC 27002:2022" and contains three kinds of entries — controls from 27002 that are unchanged, controls with added energy-sector guidance, and new controls "prefixed with "ENR"". Table A.1 in Annex A lists the energy-specific controls that can be considered when implementing ISO/IEC 27001:2022 in addition to its own Annex A controls, so a utility can carry them into its Statement of Applicability.

The introduction also names the audience directly: people operating energy process control systems, information security managers, "vendors, system integrators and auditors." Suppliers are expected readers, not bystanders.

Which energy-specific (ENR) controls does the 2024 edition add?

The table of contents lists twelve ENR controls across three of the four themes; the people theme (clause 6) has none. The right-hand column is our reading of what a utility is likely to ask a supplier, not text from the standard.

Clause ENR control (2024 title) Likely supplier question
5.38 Identification of risks related to external business partners Who has remote or physical access on your behalf?
5.39 Addressing security when dealing with customers How do customer-side devices (meters, chargers) protect utility systems?
7.15 Securing control centres — (site control)
7.16 Securing equipment rooms Can the cabinet or enclosure be locked and monitored?
7.17 Securing peripheral sites How does the device behave at unmanned substations or pump sites?
7.18 Interconnected control and communication systems Which interfaces connect to other systems, and how are they protected?
8.35 Treatment of legacy systems What is the support period, and what compensating measures apply after it?
8.36 Integrity and availability of safety functions Can security functions interfere with protection or safety logic?
8.37 Securing process control data communication Which protocols are used, and with what authentication or encryption?
8.38 Logical connection of external process control systems How are third-party or customer control systems connected?
8.39 Least functionality Can unused services and ports be disabled?
8.40 Emergency communication Does the product depend on networks that fail in a blackout?

The foreword lists the main changes from 2017: alignment to the organizational, people, physical and technological themes of ISO/IEC 27002:2022; updated guidance to avoid repeating 27002; and "attributes have been added to the controls specific to this document." Annex B gives correspondence tables in both directions between the 2017 and 2024 control numbers.

Which impact criteria does it add for energy supply?

The introduction asks utilities to cover process control security in their information security policies and lists criteria for "a secure energy supply and delivery":

  • impairment of the security of energy supply;
  • restriction of energy flow;
  • affected share of population;
  • danger of physical injury;
  • effects on other critical infrastructures;
  • effects on information privacy;
  • financial impacts.

These criteria fit directly into the consequence step of an IACS risk assessment, for example ZCR 5.3 in IEC 62443-3-2, so one impact scale can serve both the ISMS and the zone-level assessment.

Which edition should you cite?

Year Status Notes
2013 Technical Report Based on DIN SPEC 27009; informative, not a full International Standard
2017 First edition (International Standard) Published 27 November 2017; first full-status release
2019 Corrigendum Technical correction to the 2017 text
2024 Second edition Published October 2024 by ISO/IEC JTC 1/SC 27; "cancels and replaces" the 2017 edition; 12 ENR controls
2025 European adoption EN ISO/IEC 27019:2025, 9 December 2025, supersedes EN ISO/IEC 27019:2020
2026 German edition DIN EN ISO/IEC 27019:2026-03

Treat any procurement or compliance language that just says "ISO/IEC 27019" as ambiguous — specify the 2024 edition (or whichever is current at contract time) explicitly, the same way a utility would cite a specific IEC 62443 part and edition rather than the series name alone.

Where is ISO/IEC 27019 required?

The clearest legal use is in Germany. The Bundesnetzagentur's IT security page (as of 10 August 2026) says its IT security catalogues are based on ISO 27001, 27002 and 27019, and that the updated ISO/IEC 27019 becomes mandatory within the catalogues in October 2026, with a mapping table offered until then. For grid operators, the catalogue page names the core requirement as an ISMS under DIN EN ISO/IEC 27001 and its certification, and states that the existing catalogues stay in force until a new one is published under the NIS-2 implementation law.

Outside Germany. The IEC Systems Committee Smart Energy guidelines call ISO/IEC 27001, 27002 and 27019 "the most relevant standards for the implementation of an ISMS" for the smart grid. The EU network code on cybersecurity for electricity, Regulation (EU) 2024/1366, does not name ISO/IEC 27019. Operators under NIS2 can adopt it as their sector control set, but that is their choice, not an EU requirement.

How does it fit alongside IEC 62443 and IEC 62351 for power utilities?

ISO/IEC 27019 sits at the management-system layer, not the protocol or component layer, which is why utilities typically run it alongside other OT standards rather than instead of them:

  • IEC 62443 — cross-sector industrial automation and control systems security: organizational programs, system requirements and component requirements, applicable to any OT sector, not just energy.
  • IEC 62351 — protocol-specific: secures the actual IEC 61850, IEC 60870-5 and related TC 57 communication protocols a power utility's control systems exchange.
  • ISO/IEC 27019 — management-system layer: extends an ISO/IEC 27001 ISMS with energy-utility-specific controls covering process control technology broadly, independent of which specific protocols or component standards are in use.

A utility aiming for a defensible OT security program typically needs all three working together. For the US reference architecture view, see our NIST SP 800-82 guide and, for DER specifically, NIST SP 1800-32.

Worked example: how would a gateway maker answer a utility questionnaire?

Synthetic example: "SG-10", its maker and the utility are invented for illustration. SG-10 is a substation gateway that converts IEC 60870-5-104 to Modbus for older relays and offers a web page for configuration. A distribution system operator certified under ISO/IEC 27001 with ISO/IEC 27019 sends a supplier questionnaire organised by ENR control.

  1. 8.39 Least functionalityThe maker lists every listening service, shows that the web page and SSH can be disabled, and ships them off by default.
  2. 8.37 Process control data communicationIt states plainly that IEC 60870-5-104 runs without authentication on the device and that it supports TLS per IEC 62351-3 on the upstream link.
  3. 8.35 Legacy systemsIt publishes the support period, the update channel and the measures the operator should apply once updates stop.
  4. 7.17 Peripheral sitesIt documents tamper switches, local logging and behaviour when the uplink is lost.
  5. 8.36 Safety functionsIt shows that gateway restarts or updates do not change relay protection settings.
  6. EvidenceIt attaches a firmware SBOM and a known-vulnerability review of the current release, with the fix release for each finding.

Takeaway. Answer by ENR clause, attach evidence, and say where the operator has to add site controls.

What is a workable starting point?

  1. Confirm which edition a contract or auditor expectsThe 2017 and 2024 editions number their controls differently; use Annex B to map old references.
  2. Scope out nuclear explicitlyIf a utility's portfolio includes nuclear generation, document that IEC 63096 covers that process control domain.
  3. Treat it as an ISO/IEC 27001 extension, not a replacementA utility still needs a conformant ISO/IEC 27001 ISMS; ISO/IEC 27019 supplies the sector-specific controls layered on top, through Table A.1 and the Statement of Applicability.
  4. Pair it with protocol- and component-level standardsIEC 62351 and IEC 62443 cover protocol and component security respectively.
  5. Re-verify clause text against the purchased standardThis guide quotes the official sample pages; the guidance under each control is in the full text.

What are the common pitfalls?

  • Citing 2017 control numbers in 2024-based contracts. The renumbering follows ISO/IEC 27002:2022.
  • Leaving firmware out of scope. The 2024 scope explicitly covers software and firmware on in-scope systems.
  • Answering ENR questions with site controls only. A locked cabinet does not answer 8.39 for a device that ships with every service enabled.
  • Assuming one certificate covers everything. An ISO/IEC 27001 certificate with 27019 controls covers a management system, not a product's security capability.

SoftWSP does not assess an ISMS against ISO/IEC 27019. Its OT Snapshot works from Zeek logs of a site's own traffic capture, without touching live systems, and lists each host with the ports and services it was seen serving, the ICS protocols in use and interactive remote-access sessions crossing the boundary, which helps an engineer scope controls such as 7.18 and 8.38. For supplier evidence like step 6 above, Device & Firmware Security extracts a firmware SBOM as CycloneDX JSON, matches it against NVD, CISA KEV, FIRST EPSS and CISA CSAF ICS advisories, and drafts a cited report for engineer review.

This guide summarises the official sample pages and public regulator and IEC sources on ISO/IEC 27019; it is not a substitute for the standard's own purchased text (available from ISO or national standards bodies) and does not constitute compliance or certification advice.

Put this guide to work

Frequently asked questions

What is ISO/IEC 27019 and who is it for?

ISO/IEC 27019, "Information security controls for the energy utility industry," is a sector-specific extension of the ISO/IEC 27000 family aimed at energy utilities — organizations involved in the generation, transmission, storage and distribution of electric power, gas, oil and heat, and the process control systems that run those operations. Per independent secondary summaries of the standard's own scope text, it is built on ISO/IEC 27002's generic control catalogue but adapts and supplements it for the real-time, safety-critical nature of process control and automation technology, letting a utility implement an ISO/IEC 27001-conformant ISMS that extends from the business level down to the process control (OT) level.

What systems does ISO/IEC 27019 cover, and what is explicitly excluded?

Per corroborated secondary summaries, the scope covers central and distributed process control, monitoring and automation technology and the systems used to operate it (programming/parameterization devices); digital controllers and automation components including PLCs and sensor/actuator elements; supporting information systems and communication technology used in the process control domain (networks, telemetry, telecontrol, remote control); digital protection and safety systems; energy management systems including distributed energy resources and electric-vehicle charging infrastructure; digital metering and measurement devices; and the premises housing this equipment, including remote maintenance systems. Two exclusions are explicit: the process control domain of **nuclear facilities** (covered instead by IEC 63096), and **telecommunication systems and components** used within the process control environment, which fall outside the standard's scope.

How is ISO/IEC 27019 structured relative to ISO/IEC 27002?

It does not replace ISO/IEC 27002's control catalogue — it supplements it. Per secondary summaries of the 2024 second edition, the standard follows ISO/IEC 27002:2022's four-theme control structure (organizational, people, physical, technological) and adds energy-utility-specific supplementary controls within each: reported counts include roughly 2 additional organizational controls, people-control guidance, 4 additional physical controls, and 6 additional technological controls, plus informative annexes giving industry-specific reference material and a correspondence table between editions. ISO/IEC 27019 also directs adopters to adapt the ISO/IEC 27001 risk assessment and treatment process using the sector-specific guidance it provides, rather than applying generic ISO/IEC 27001 risk language unmodified to a process control environment.

Is the 2017 edition still current, and what changed in the 2024 edition?

No — treat the 2024 edition as the current one. ISO/IEC 27019 began life as a 2013 Technical Report (based on DIN SPEC 27009), was published 27 November 2017 as the first full International Standard, received a 2019 corrigendum, and was then revised into a second edition published in 2024 to realign with the restructured ISO/IEC 27002:2022 control set, reportedly adding around 12 new or re-scoped controls in the process. The edition history above is cross-checked against two independent secondary sources rather than ISO's own listing — confirm the current edition and exact control count against iso.org or a purchased copy before citing a specific clause number in a compliance document.

Sources

  1. ISO: ISO/IEC 27019:2024 catalogue record (official standard page; second edition, supersedes the withdrawn 2017 edition)
  2. ISO27k Toolkit (iso27001security.com): ISO/IEC 27019 summary — scope, structure, relationship to ISO/IEC 27002, edition history
  3. Wikipedia: ISO/IEC 27019 — scope, exclusions, publication history (2013 TR, 2017 IS, 2019 corrigendum, 2024 second edition)
  4. IEC SyC Smart Energy: ISO/IEC 27000 series in the smart energy cybersecurity standards landscape
  5. ISO/IEC 27019:2024 official sample pages (cover, foreword, scope, clause 4, table of contents), via iTeh Standards
  6. iTeh Standards: ISO/IEC 27019:2024 catalogue entry (published 17 October 2024, ISO/IEC JTC 1/SC 27)
  7. iTeh Standards: EN ISO/IEC 27019:2025 catalogue entry (9 December 2025, supersedes EN ISO/IEC 27019:2020)
  8. DIN Media: DIN EN ISO/IEC 27019:2026-03
  9. Bundesnetzagentur: IT-Sicherheit im Energiesektor (IT security catalogues; Stand 10.08.2026)
  10. Bundesnetzagentur: IT-Sicherheitskatalog for grid operators
  11. IEC SyC Smart Energy: Cyber Security and Resilience Guidelines for the Smart Energy Operational Environment (PDF)
Was this guide helpful?

In this cluster

ISO/IEC 27019: information security controls for the energy utility industry, explained