This article explores the security architecture of IEC 61850, an industrial communication standard, focusing on its distinct communication models: MMS, GOOSE, and Sampled Values. It highlights how each protocol's underlying transport and communication paradigms (client/server vs. direct Ethernet) introduce unique attack surfaces and security considerations, making traditional security assessments inadequate. The research dissects protocol semantics and configuration to uncover potential manipulation points.
Read original on Dev.to #architectureIEC 61850 is a critical standard for substation automation and modern electrical grids. Unlike a single protocol, it's an ecosystem of communication models, each with different architectural implications for security. Understanding these distinctions is crucial for designing robust and secure Industrial Control Systems (ICS).
The standard defines three primary communication areas, each operating at different layers and with distinct security boundaries:
IEC 61850 Laboratory
┌────────────────┼────────────────┐
│ │ │
▼ ▼ ▼
SCL / Station Bus Process Bus
Configuration
│ │ │
┌─────┴─────┐ │ │
│ MMS GOOSE SV │
│ TCP/102 Ethernet Ethernet │The Substation Configuration Language (SCL), an XML-based language, defines IED capabilities, data models, and communication parameters. This configuration itself is part of the attack surface, as it provides the structural baseline for interpreting observed network behavior. Understanding the configured data model is essential for identifying potential manipulation points before any network packets are exchanged.
MMS focuses on client/server interactions. While it enforces application semantics (e.g., correct data typing for control operations), it often lacks sufficient authorization mechanisms at the application layer. An attacker who can establish an anonymous session may be able to enumerate the operational model and manipulate control points if proper authentication and authorization are not explicitly enforced. This highlights a critical distinction: correct protocol implementation does not automatically imply secure authorization.
GOOSE and Sampled Values operate at Layer 2, making traditional TCP/IP security assumptions irrelevant. There are no TCP sessions to authenticate. Security relies heavily on source identity (MAC addresses), state numbers (`stNum`), sequence numbers (`sqNum`), timing (`TAL`), and cryptographic protection. Manipulation of these fields can lead to a subscriber misinterpreting system state or accepting illegitimate traffic, demonstrating a shift from connection-oriented attacks to data integrity and authenticity attacks at a lower layer.