Key takeaways
- No, not in GOOSE and Sampled Values' base specification — and this is the gap a separate standard exists to close.
- Two advisories published in 2026 show where the practical risk actually sits: implementation bugs in vendor stacks, not a break of IEC 62351's authentication design.
- Confirm IEC 62351-6 authentication is actually configured, not just available in the product's documentation.
IEC 61850 standardizes how substation devices — protection relays, bay controllers, merging units — talk to each other using three message types (GOOSE, Sampled Values and MMS), but the standard's two fastest message types, GOOSE and Sampled Values, carry no authentication or encryption in their own base specification, because they were designed in an era of isolated substation networks with sub-millisecond timing budgets that full cryptography would jeopardize. Security for IEC 61850 traffic is a separate standard, IEC 62351-6, and two CISA ICS advisories published in 2026 show the practical risk sits in vendor implementations of the stack, not in breaking any cryptography the base protocol never had.
What is IEC 61850, and what do GOOSE, Sampled Values and MMS actually carry?
IEC 61850 is maintained by IEC Technical Committee 57 (TC 57) and, per IEC's own current bundled catalogue listing (IEC 61850:2026 SER), spans 47 separate publications — core parts, substation configuration language, data/function models and technical reports — covering communication inside a substation and, via later extensions, beyond it. Three message types matter most in practice:
| Message type | What it carries | Transport | Typical latency budget |
|---|---|---|---|
| GOOSE (Generic Object-Oriented Substation Event) | Peer-to-peer protection/control events — a trip command, a breaker status change | Layer 2 Ethernet multicast (EtherType 0x88B8) | Low single-digit milliseconds |
| Sampled Values (SV) | Continuous stream of time-synchronized current/voltage measurement samples, from a merging unit up to protection/bay-level IEDs | Layer 2 Ethernet multicast | Sub-millisecond, per sample |
| MMS (Manufacturing Message Specification) | Client-server control, reporting and configuration traffic between station-level SCADA and bay-level IEDs | TCP/IP — can cross routers and firewalls | Not time-critical in the same way |
GOOSE and SV are standardized in IEC 61850-8-1 and IEC 61850-9-2 respectively; per IEC's own catalogue text, IEC 61850-9-2:2011 "defines the specific communication service mapping for the transmission of sampled values" using the same Layer 2 mapping approach as 8-1. Because GOOSE and SV were built to replace hard-wired copper connections between protection devices with an Ethernet equivalent at the same speed, the design prioritized deterministic low latency over the cryptographic overhead that authentication or encryption would add.
Does IEC 61850 have built-in authentication or encryption?
No, not in GOOSE and Sampled Values' base specification — and this is the gap a separate standard exists to close. Widely corroborated independent technical analysis of the published IEC 62351-6:2020 standard describes why: GOOSE and SV's sub-4-millisecond delivery requirements make full encryption's added processing latency a real operational risk, so IEC 62351-6 instead specifies message authentication (an HMAC or AES-GMAC computed over a pre-shared group key) to protect integrity and authenticity without the latency cost encryption would add. MMS traffic, which runs over ordinary TCP/IP and isn't bound by the same microsecond timing, can instead use the TLS profile IEC 62351-3 defines for any TC 57 protocol riding over TCP/IP.
A separate extension, IEC TR 61850-90-5, defines routable versions of these messages — R-GOOSE and R-SV — carried over UDP/IP so wide-area protection and synchrophasor applications can span more than one substation's LAN. Per independent technical summaries of that technical report, R-GOOSE/R-SV security is configurable with three options: none, signature (authentication only), or signature-plus-encryption, keyed through the GDOI group-key management protocol that IEC 62351-9 extends for IEC 61850 use. None of this is in the base IEC 61850-8-1/9-2 text itself — it is layered on by the separate IEC 62351 series, which our IEC 62351 guide covers part by part, including how it compares to NERC CIP-013 and IEC 62443.
What have real CISA advisories against IEC 61850 products found in 2026?
Two advisories published in 2026 show where the practical risk actually sits: implementation bugs in vendor stacks, not a break of IEC 62351's authentication design.
| Advisory | Vendor / product | CVE(s) | CVSS | What it actually allowed |
|---|---|---|---|---|
| ICSA-26-211-10 (30 July 2026) | MZ Automation GmbH libiec61850 (open-source stack), versions < 1.6.2 | 8 CVEs, all CWE-125 (Out-of-Bounds Read) | 6.5–7.5 (v3.1); up to 8.7 (v4.0) | An unauthenticated, specially crafted GOOSE Layer-2 multicast frame — e.g. an undersized timestamp field or an oversized inner-element length — triggers a heap out-of-bounds read that crashes the GOOSE subscriber process (denial of service) |
| ICSA-26-120-01 (30 April 2026, initial 13 April 2026) | ABB System 800xA / Symphony Plus, IEC 61850 MMS-client stack (CI868/AC800M, CI850, PM 877, S+ Operations) | CVE-2025-3756 (CWE-1284) | 6.5 (v3.1) | An attacker with IEC 61850 network access sends a specially crafted packet, forcing affected Communication Interfaces into fault mode or taking S+ Operations' 61850 connectivity offline (denial of service); CISA's advisory states GOOSE communication itself is not affected |
Both findings require network access to the IEC 61850 segment and neither breaks IEC 62351's authentication mechanism — the MZ Automation bugs are memory-safety flaws in parsing an untrusted GOOSE frame (which GOOSE's lack of sender authentication lets any node on the segment send), and the ABB finding is a malformed-packet handling bug in the MMS stack specifically, unrelated to GOOSE.
What should an asset owner check first?
Inventory every IED, merging unit, bay controller and station computerspeaking GOOSE, Sampled Values or MMS, along with its exact firmware/software version — both advisories above affect specific version ranges only, and neither can be assessed without that detail. Confirm IEC 62351-6 authentication is actually configured, not just available in the product's documentation. A standard that supports message authentication is not the same claim as a substation where it is turned on. Patch against the specific CVEs aboveMZ Automation recommends updating libiec61850-based products to version 1.6.2; ABB's fix timeline for the affected products runs from S+ Operations 3.4 (released January 2026) through CI868's planned Q2 2027 release — check the current CISA advisory for the latest status on your exact model. Segment IEC 61850 traffic away from business networks and the internetGOOSE and SV were designed for a trusted substation LAN, not public exposure; ABB's own advisory recommends firewalling with minimal exposed ports and requiring a VPN for any remote access. Re-check after any firmware updatewhether GOOSE/SV authentication settings and network segmentation survived the change — a patch that fixes one CVE is not a substitute for verifying the surrounding configuration is still as intended.
A passive pcap capture from a substation LAN's mirror port is a practical way to build the inventory in step 1 and confirm which IEC 61850 message types are actually in use, without connecting anything to a live protection circuit: SoftWSP's OT Snapshot identifies devices and the protocols they speak from that capture, maps them against published CISA ICS advisories, and flags risky patterns such as unauthenticated GOOSE traffic reaching an unexpected segment — with an engineer reviewing every finding and the AI-assisted report citing the specific traffic each finding is based on — see OT Snapshot.
This guide draws on IEC's own catalogue and scope text for the IEC 61850 and IEC 62351-6 series, two CISA ICS advisories fetched directly (ICSA-26-211-10 and ICSA-26-120-01), widely corroborated independent technical analysis of IEC 62351-6's published authentication mechanism, and NIST SP 800-82 Revision 3. The full paywalled text of IEC 61850's individual parts and IEC TR 61850-90-5 was not purchased or independently re-verified for this guide; treat granular cryptographic-mechanism claims as general description, to be confirmed against the primary IEC text before an implementation or compliance decision. This guide is general information, not a substitute for a current CISA ICS advisory search for your exact hardware and firmware version or for the purchased IEC standard text.
Sources
- IEC: IEC 61850:2026 SER — Communication networks and systems for power utility automation — ALL PARTS (bundled catalogue record, 47 publications, TC 57)
- IEC: IEC 61850-9-2:2011, Part 9-2: Specific communication service mapping (SCSM) — Sampled values over ISO/IEC 8802-3 (catalogue record and scope, Edition 2.0, published 2011-09-22)
- IEC: IEC 62351-6:2020, Part 6: Security for IEC 61850 (catalogue record and scope, Edition 1.0, published 2020-10-20)
- CISA ICS Advisory ICSA-26-211-10: MZ Automation GmbH libiec61850 (released 30 July 2026; CVE-2026-66720 and 7 related CVEs)
- CISA ICS Advisory ICSA-26-120-01: ABB System 800xA, Symphony Plus IEC 61850 (released 30 April 2026; CVE-2025-3756)
- NIST Special Publication 800-82 Revision 3, Guide to Operational Technology (OT) Security (September 2023)
Frequently asked questions
What is IEC 61850, and does the standard itself include security?
IEC 61850, "Communication networks and systems for power utility automation," is the IEC Technical Committee 57 (TC 57) series that standardizes how intelligent electronic devices (IEDs) inside a substation — protection relays, bay controllers, merging units — exchange data with each other and with a station-level SCADA system. IEC's own bundled catalogue listing (IEC 61850:2026 SER) counts 47 distinct publications spanning the core parts, functional data models, communication service mappings and technical reports, maintained by TC 57 and first published (as "Communication networks and systems in substations") in the mid-2000s. The standard was built for an era when substation networks were isolated and proprietary, and its two fastest, most time-critical message types — GOOSE and Sampled Values — carry no authentication or encryption of their own in their base specifications (IEC 61850-8-1 for GOOSE, IEC 61850-9-2 for Sampled Values). Security for IEC 61850 traffic is instead the job of a separate standard, IEC 62351-6, bolted on afterward rather than built in from the start.
Why aren't GOOSE and Sampled Values messages simply encrypted?
Timing. GOOSE carries protection and control events (like a circuit breaker trip command) and Sampled Values carry a continuous stream of time-synchronized current/voltage measurements, and both run as Layer 2 Ethernet multicast frames with delivery deadlines in the single-digit milliseconds — fast enough that full encryption's added processing latency can jeopardize the real-time guarantee the protocols exist to provide. Widely corroborated independent technical analysis of the published IEC 62351-6:2020 standard (this guide has not purchased the full paywalled text) describes the chosen tradeoff: instead of encrypting payload, Part 6 relies on message authentication — an HMAC or AES-GMAC computed over a pre-shared group key — to protect the integrity and authenticity of GOOSE and Sampled Values frames without adding full encryption's latency. A separate mechanism, IEC TR 61850-90-5, defines a routable variant (R-GOOSE and R-SV, carried over UDP/IP for wide-area protection and synchrophasor applications beyond a single substation LAN) with its own security options — none, signature, or signature-plus-encryption — keyed through the GDOI group-key protocol IEC 62351-9 extends for this purpose. Treat the specific cryptographic parameters as **to be confirmed** against the purchased IEC text before an implementation decision; our [IEC 62351 guide](/guides/iec-62351-power-systems-communications-security/) covers the full security series part by part.
What have real CISA ICS advisories against IEC 61850 products found in 2026?
Two unrelated vulnerability classes, both in vendor implementations rather than in the IEC 61850 base protocol or IEC 62351's security design. CISA's ICSA-26-211-10 (released 30 July 2026) covers MZ Automation GmbH's open-source libiec61850 stack, versions before 1.6.2: eight separate CVEs (CVE-2026-66720, -66369, -63550, -65421, -66364, -66349, -56758 and -66360), all classified CWE-125 Out-of-Bounds Read, with CVSS v3.1 scores of 6.5 or 7.5 and v4.0 scores up to 8.7. Per CISA's description, the most representative of the eight is a GOOSE subscriber flaw where "a specially crafted GOOSE frame containing an undersized timestamp field can trigger a heap out-of-bounds read during message processing, causing the process to crash" — a single unauthenticated Layer-2 multicast frame on the process bus is enough, since GOOSE has no sender authentication to prevent an untrusted frame from reaching the parser in the first place. CISA's ICSA-26-120-01 (released 30 April 2026, initial 13 April 2026) covers ABB System 800xA and Symphony Plus products' IEC 61850 MMS-client communication stack — CVE-2025-3756, CVSS v3.1 6.5 (CWE-1284, Improper Validation of Specified Quantity in Input) — where an attacker with IEC 61850 network access can send a specially crafted packet to force affected Communication Interfaces (CI868/AC800M, CI850, PM 877, S+ Operations) into fault mode, a denial-of-service condition; CISA's advisory is explicit that GOOSE communication itself is not impacted by this particular finding.
What should an asset owner running IEC 61850 substation equipment check first?
Inventory every IED, merging unit, bay controller and station computer that speaks GOOSE, Sampled Values or MMS, along with the exact firmware/software version of each — none of the findings above, or any future advisory, can be assessed without that detail, and the ABB and MZ Automation findings above each affect only specific version ranges. Confirm whether IEC 62351-6 message authentication is actually configured on your GOOSE/SV traffic rather than assuming the standard's existence on paper means it is active in your substation — per FieldComm-style industry practice elsewhere in OT, security features that exist in a specification are routinely shipped disabled by default. Patch libiec61850-based and ABB IEC 61850 products against the CVEs above (MZ Automation recommends updating to 1.6.2; ABB's patch timeline runs from S+ Operations 3.4, released January 2026, through CI868's planned Q2 2027 fix) or any newer CISA ICS advisory matching your exact product and version. Segment substation LANs carrying GOOSE/SV/MMS traffic from business networks and the internet, since IEC 61850 traffic was never designed to be exposed outside a trusted local network, and ABB's own advisory recommends firewalling control networks and using a VPN for any required remote access rather than direct exposure.
In this cluster


