- Introduction
- 1. Why Cybersecurity Is Important in IEC 61850 Substations
- 2. Understanding the IEC 61850 Cybersecurity Environment
- 3. Understanding IEC 62351
- 4. Network Segmentation in MiCOM Substations
- 5. Access Control for MiCOM Protection Relays
- 6. Authentication and Secure Communication
- 7. Securing GOOSE Communication
- 8. Securing MMS Communication
- 9. Engineering Workstation Security
- 10. Configuration File Security: ICD, CID, IID and SCD
- 11. Remote Access Security for Substation Maintenance
- 12. Network Monitoring and Cybersecurity Event Logging
- 13. Practical Example: Protecting a MiCOM IEC 61850 Feeder Network
- 14. Common Cybersecurity Problems and Troubleshooting
- 15. Cybersecurity Commissioning Checklist
- 16. Conclusion
- Practical MiCOM Protection and IEC 61850 Training by Dr Saeed Roostaee – Elec-Engg
Introduction
Modern electrical substations increasingly depend on Ethernet-based communication between protection relays, bay control units, SCADA systems, engineering workstations and station-level servers. IEC 61850 makes this communication more flexible and interoperable, but it also introduces cybersecurity requirements that must be considered during system design, commissioning and maintenance.
MiCOM protection relays connected to substation networks may exchange information through MMS, GOOSE and other supported communication services. These communication paths must be protected against unauthorized access, configuration changes, network disruption and malicious activity.
Cybersecurity is not simply an IT issue. An unauthorized change to a protection relay, an interruption of GOOSE communication or an unavailable engineering workstation can affect the operation and reliability of the electrical power system.
This article explains the main cybersecurity considerations for IEC 61850-based MiCOM installations, including network segmentation, access control, authentication, IEC 62351, secure engineering practices and practical commissioning checks.
Important: Cybersecurity features vary between MiCOM product families, models, communication interfaces and firmware versions. Do not assume that a particular MiCOM relay supports every IEC 62351 feature. Verify the supported security functions using the exact product documentation, firmware release notes and cybersecurity advisories.
1. Why Cybersecurity Is Important in IEC 61850 Substations
A substation communication network carries operational information that can directly affect electrical equipment.
Examples include:
- Protection indications.
- Circuit breaker status.
- Interlocking signals.
- Remote control commands.
- Measurements and alarms.
- GOOSE messages exchanged between IEDs.
- Engineering and configuration information.
If an unauthorized person gains access to these systems, possible consequences include:
- Unauthorized modification of relay settings.
- Changes to protection logic.
- Incorrect communication configuration.
- Interruption of GOOSE or MMS communication.
- Unauthorized breaker-control attempts.
- Loss of SCADA visibility.
- Loss or manipulation of event records.
- Disruption of engineering and maintenance activities.
Cybersecurity engineering must therefore protect both the communication network and the devices connected to it.
2. Understanding the IEC 61850 Cybersecurity Environment
IEC 61850 defines communication models and services for substation automation. It does not, by itself, guarantee that every communication path is secure.
A typical substation may include:
| System | Cybersecurity concern |
|---|---|
| MiCOM protection relays | Unauthorized access and configuration changes |
| SCADA servers | Unauthorized operation and data access |
| Ethernet switches | Network access and traffic manipulation |
| Engineering workstations | Malware and unauthorized engineering |
| Time synchronization servers | Incorrect or disrupted time distribution |
| Remote access gateways | Unauthorized external access |
| Configuration files | Unauthorized modification or replacement |
Cybersecurity must be considered across the entire architecture rather than focusing only on the protection relay.
3. Understanding IEC 62351
IEC 62351 is a series of standards addressing cybersecurity for power system information exchange.
It complements communication standards used in electrical power systems, including IEC 61850.
The IEC 62351 series addresses different security topics, such as:
- Security for communication protocols.
- Authentication and access control.
- Key management.
- Network and system management.
- Security monitoring.
- Security for selected IEC 61850 communication services.
The relevant parts depend on the communication protocol and security function being implemented.
3.1 IEC 62351 and IEC 61850
IEC 61850 defines how IEDs exchange information. IEC 62351 provides security-related mechanisms for protecting supported communication services.
For example, security mechanisms may be relevant to:
- MMS communication.
- Client authentication.
- Access authorization.
- Communication integrity.
- Security event monitoring.
- Selected GOOSE and Sampled Values security applications.
However, support is not universal. Engineers must confirm the specific IEC 62351 requirements and capabilities of the devices and software involved.
3.2 IEC 62351 is not a single security switch
A common engineering misunderstanding is to treat IEC 62351 as one feature that can simply be enabled in every relay.
In reality, it is a collection of standards covering different security requirements.
A system may support some security functions while not supporting others.
The security design must therefore identify the required protection mechanisms and verify compatibility across the complete communication system.
4. Network Segmentation in MiCOM Substations
Network segmentation separates systems into different logical or physical network areas.
It reduces unnecessary communication between devices and limits the potential impact of a security incident.
A typical substation may separate:
- Protection and control IEDs.
- Station-level SCADA systems.
- Engineering workstations.
- Network management equipment.
- External or corporate network connections.
4.1 VLAN-based segmentation
VLANs can separate communication groups within a managed Ethernet network.
For example:
| VLAN | Example function |
|---|---|
| VLAN 10 | Protection IED communication |
| VLAN 20 | Station-level SCADA |
| VLAN 30 | Engineering access |
| VLAN 40 | Network management |
These are illustrative values, not mandatory IEC 61850 assignments.
VLANs provide logical separation, but they are not a replacement for firewalls, access control or properly configured network security policies.
4.2 Firewalls and controlled communication paths
Firewalls can control communication between network security zones.
For example, an engineering workstation may be allowed to access specific relay management services while ordinary user systems are prevented from reaching the protection network.
Firewall rules should be based on:
- Source and destination addresses.
- Required communication services.
- Approved ports and protocols.
- Operational requirements.
- Security policies.
MMS commonly uses TCP port 102, but opening this port does not mean unrestricted access should be permitted.
Only necessary communication should be allowed.
5. Access Control for MiCOM Protection Relays
Access control determines who can interact with a relay and which operations they are allowed to perform.
A protection engineer may need to change settings, while an operator may only need to monitor status information.
These activities should not necessarily have identical access permissions.
5.1 Typical access categories
Depending on the product and project configuration, access roles may include:
- Read-only monitoring.
- Operator access.
- Engineering access.
- Configuration administration.
- Maintenance access.
The exact role names and available permissions vary between devices.
5.2 Password management
Good password practices include:
- Replace factory-default credentials where applicable.
- Use strong, unique passwords.
- Avoid sharing engineering accounts.
- Restrict administrative access.
- Store credentials in an approved secure location.
- Change credentials when personnel access changes.
- Follow the organization’s password and account policies.
Never place relay passwords in publicly accessible documents, commissioning reports or shared configuration files.
5.3 Role-based access control
Role-based access control assigns permissions according to job responsibilities.
For example:
| Role | Example permission |
|---|---|
| Operator | View measurements and indications |
| Protection engineer | Access approved engineering functions |
| Administrator | Manage authorized device and user settings |
| Maintenance technician | Perform permitted maintenance operations |
These examples describe a general access-control approach. The actual permissions must be based on the capabilities of the relay and the site’s operational policy.
6. Authentication and Secure Communication
Authentication is the process of verifying the identity of a user or system before granting access.
In a substation, authentication may be required for:
- Engineering workstation access.
- Device configuration.
- Remote maintenance.
- SCADA client connections.
- Administrative network access.
Depending on the supported implementation, security mechanisms may include:
- Username and password authentication.
- Certificate-based authentication.
- Mutual authentication.
- Secure communication sessions.
- Centralized identity management.
6.1 MMS security
MMS is commonly used for communication between IEC 61850 clients and IED servers.
Traditional MMS communication over TCP port 102 should not automatically be assumed to provide encryption or strong authentication.
IEC 62351-related security mechanisms can provide additional protection where supported and correctly configured.
The engineering team should verify:
- Which MMS security mechanisms are supported.
- Whether authentication is required.
- Whether secure transport is available.
- How certificates or credentials are managed.
- Whether the SCADA client and relay support compatible security configurations.
6.2 Certificate management
Where certificate-based security is supported, certificate management becomes an important part of system maintenance.
Engineers should consider:
- Certificate issuance.
- Certificate installation.
- Certificate validity periods.
- Trust relationships.
- Renewal procedures.
- Revocation procedures.
- Private-key protection.
A certificate that has expired or is not trusted may prevent an otherwise correctly configured secure communication session from being established.
7. Securing GOOSE Communication
GOOSE is widely used in digital substations for exchanging protection and control signals between IEDs.
Because GOOSE messages can carry important operational information, unauthorized access to the Ethernet network must be prevented.
Potential risks include:
- Unauthorized devices transmitting Ethernet frames.
- Manipulation of network traffic.
- Denial-of-service attacks.
- Incorrect network configuration.
- Unauthorized changes to GOOSE publisher or subscriber settings.
- Interruption of multicast traffic.
7.1 Protecting GOOSE communication
Recommended measures include:
- Restrict physical access to protection network ports.
- Use managed switches with appropriate access controls.
- Separate protection networks from general-purpose networks.
- Restrict access to switch configuration interfaces.
- Monitor unexpected multicast traffic.
- Maintain approved GOOSE configuration records.
- Test communication after any network or relay configuration change.
7.2 GOOSE authentication and integrity
IEC 62351 includes security mechanisms relevant to GOOSE and other power system communication applications.
However, implementation depends on the applicable standard edition, device capability and project requirements.
Do not assume that every MiCOM relay supports authenticated GOOSE communication.
Where cryptographic protection is required, verify that the publisher, subscriber and supporting engineering tools implement compatible security mechanisms.
7.3 Practical GOOSE security checks
During commissioning, engineers should verify:
- Only approved IEDs are connected to the protection network.
- Publisher and subscriber configurations match the approved design.
- Unused switch ports are disabled or restricted.
- Unexpected GOOSE publishers are investigated.
- Network traffic is monitored.
- Configuration changes are controlled and recorded.
8. Securing MMS Communication
MMS is used for communication between IEC 61850 clients and servers.
In a MiCOM installation, this may include communication between the protection relay and a SCADA or SAS system.
Potential security risks include:
- Unauthorized client connections.
- Unauthorized access to data objects.
- Unauthorized control commands.
- Manipulation of communication sessions.
- Network scanning and service exploitation.
- Denial-of-service attacks.
8.1 Restricting MMS access
A good network security design should identify which systems are permitted to communicate with each relay.
For example:
| Source | Destination | Communication | Policy |
|---|---|---|---|
| SCADA server | MiCOM relay | Required MMS services | Allow |
| Approved engineering workstation | MiCOM relay | Supported engineering services | Controlled access |
| General office network | MiCOM relay | No operational requirement | Deny |
| Unknown external device | MiCOM relay | Unapproved access | Deny |
This is an illustrative policy table. The actual rules must be based on the approved network architecture and required device services.
8.2 Limiting unnecessary services
Where supported, disable unused services and interfaces.
Examples include:
- Unused communication protocols.
- Unnecessary remote-access services.
- Unused network ports.
- Unneeded administrative interfaces.
Disabling a service must be preceded by an assessment of its operational dependencies. Some services may be required for protection, monitoring, maintenance or time synchronization.
9. Engineering Workstation Security
Engineering workstations are particularly important in protection systems because they can be used to access relay settings, logic, communication parameters and configuration files.
A compromised engineering workstation may create risks beyond the workstation itself.
9.1 Common risks
- Malware infection.
- Unauthorized software installation.
- Insecure remote-access tools.
- Uncontrolled USB devices.
- Unapproved configuration changes.
- Loss of engineering files.
- Use of shared administrator accounts.
9.2 Recommended protection measures
For MiCOM engineering environments:
- Use dedicated engineering workstations where practical.
- Restrict software installation.
- Apply approved operating-system security updates.
- Use endpoint protection compatible with the engineering environment.
- Control USB and removable-media access.
- Restrict internet connectivity where unnecessary.
- Maintain secure configuration backups.
- Use individual accounts where supported.
- Record engineering activities.
- Keep approved versions of engineering software.
9.3 S1 Agile and configuration security
S1 Agile is used for engineering supported MiCOM devices.
The security of the engineering process should include:
- Controlled access to the software.
- Protection of project files.
- Verification of the correct relay model.
- Review of setting changes.
- Backup of the original configuration.
- Approval before applying changes.
- Recording the final configuration version.
The exact engineering and security functions depend on the software release and supported relay family.
10. Configuration File Security: ICD, CID, IID and SCD
IEC 61850 engineering relies on configuration files that describe IED capabilities, device configurations and substation communication arrangements.
These files are important operational assets.
An unauthorized or incorrect modification may affect:
- Logical device definitions.
- Logical node configuration.
- MMS datasets.
- Report control blocks.
- GOOSE publisher configuration.
- GOOSE subscriber references.
- Communication parameters.
10.1 Protecting SCL files
Recommended practices include:
- Keep approved original and final SCL files.
- Restrict editing permissions.
- Maintain version-controlled configuration records.
- Record the person responsible for each change.
- Compare files before applying modifications.
- Validate the SCL structure.
- Confirm compatibility with the actual IED.
- Back up the configuration before commissioning changes.
10.2 Configuration revision management
The confRev parameter associated with a GOOSE control block indicates the configuration revision of the relevant GOOSE configuration.
It is not the relay firmware version.
When the dataset or associated GOOSE configuration changes, the configuration revision must be handled according to the applicable IEC 61850 engineering process and device implementation.
A mismatch between publisher and subscriber configuration can prevent correct GOOSE processing.
10.3 Why configuration backups matter
A secure backup strategy should include:
- Relay settings.
- Protection logic configuration.
- Communication configuration.
- SCL files.
- Switch configuration.
- SCADA configuration.
- Engineering software version information.
Backups should be protected against unauthorized modification and periodically tested for recoverability.
11. Remote Access Security for Substation Maintenance
Remote access can help protection engineers diagnose problems, review relay settings and support commissioning activities.
However, direct uncontrolled remote access to a protection network creates significant cybersecurity risks.
11.1 Recommended remote access architecture
A controlled remote access arrangement may include:
Authorized Engineer
|
Secure VPN Access
|
Remote Access Gateway
|
Firewall / DMZ
|
Approved Engineering PC
|
Substation OT Network
|
MiCOM Protection
Relays
This is a conceptual architecture. The final design must follow the site’s cybersecurity requirements.
11.2 Remote access requirements
A secure remote maintenance arrangement should consider:
- Approval before access.
- Individual user authentication.
- Multi-factor authentication where supported.
- Time-limited access.
- Controlled access to specific devices.
- Session logging.
- Monitoring of remote activity.
- Secure termination of sessions.
- Restrictions on file transfer.
Remote access should never be permanently enabled without an operational and security justification.
12. Network Monitoring and Cybersecurity Event Logging
Cybersecurity requires continuous visibility of network and device activity.
A substation network should be monitored for unusual communication behavior and unauthorized access attempts.
12.1 What should be monitored?
Examples include:
- Unexpected IP addresses.
- Unknown MAC addresses.
- Unusual MMS connections.
- Unexpected GOOSE traffic.
- Excessive broadcast or multicast traffic.
- Repeated failed access attempts.
- Unauthorized configuration changes.
- Switch-port status changes.
- Abnormal communication interruptions.
12.2 Network monitoring tools
Depending on the project, engineers may use:
- Managed switch diagnostics.
- Network management systems.
- Syslog servers.
- Security information and event management systems.
- Network traffic analyzers.
- Wireshark.
- Approved industrial intrusion detection systems.
Monitoring systems should be configured carefully to avoid generating unnecessary traffic or interfering with protection communication.
12.3 Wireshark for security investigation
Wireshark can help identify communication patterns and unexpected traffic.
Useful display filters include:
MMS traffic
tcp.port == 102
GOOSE traffic
goose
GOOSE Ethernet frames
eth.type == 0x88b8
TCP retransmissions
tcp.analysis.retransmission
TCP reset packets
tcp.flags.reset == 1
Traffic from a specific IP address
ip.addr == 192.168.10.21
These filters help investigate traffic but do not, by themselves, determine whether an activity is malicious.
Engineers should correlate packet captures with relay diagnostics, switch logs, SCADA logs and approved network configurations.
13. Practical Example: Protecting a MiCOM IEC 61850 Feeder Network
Consider a substation with the following equipment:
- Two MiCOM feeder protection relays.
- One MiCOM transformer protection relay.
- One IEC 61850 SCADA server.
- Two managed Ethernet switches.
- One engineering workstation.
- One network time server.
The objective is to protect the communication network while maintaining normal protection and SCADA operation.
Step 1 – Identify communication requirements
Prepare a communication matrix identifying the required connections.
| Source | Destination | Purpose |
|---|---|---|
| SCADA server | MiCOM relays | MMS monitoring and reporting |
| MiCOM relay 1 | MiCOM relay 2 | GOOSE exchange |
| MiCOM relays | Time server | Time synchronization |
| Engineering workstation | MiCOM relays | Approved engineering access |
| Network management system | Switches | Network monitoring |
This matrix should reflect actual project requirements and supported services.
Step 2 – Separate network zones
Create appropriate network zones for protection, station-level communication and engineering access.
Use VLANs and firewall policies according to the approved network design.
Step 3 – Restrict access
Allow only approved systems to access the required relay services.
Disable unused switch ports and restrict administrative access.
Step 4 – Secure engineering workstations
Use controlled user accounts, approved software and secure configuration storage.
Maintain backups of relay and network configurations.
Step 5 – Verify communication
Confirm that:
- MMS communication operates correctly.
- GOOSE communication operates correctly.
- Time synchronization remains available.
- Engineering access is restricted to authorized systems.
- Network monitoring is operational.
Step 6 – Test security controls
Under an approved test plan, verify that unauthorized access paths are blocked without interrupting essential protection and control communication.
14. Common Cybersecurity Problems and Troubleshooting
| Problem | Possible cause | Recommended action |
|---|---|---|
| Engineering software cannot access relay | Access restrictions or network policy | Verify approved access rules and device configuration |
| MMS communication is blocked | Firewall or ACL configuration | Check permitted source, destination and service |
| GOOSE communication stops after network changes | VLAN or multicast filtering change | Compare switch configuration with approved design |
| Remote access fails | VPN, authentication or certificate problem | Check gateway logs and credentials |
| Secure communication cannot be established | Certificate or compatibility issue | Verify trust, validity and supported security profiles |
| Unexpected relay configuration changes | Uncontrolled engineering access | Review access records and configuration backups |
| Unknown device appears on network | Unauthorized connection or asset inventory error | Identify the device and investigate its connection |
| Excessive network traffic | Misconfiguration or abnormal traffic | Analyze packet captures and switch statistics |
| Time synchronization is disrupted | Network policy or server access change | Verify the timing communication path |
| Security monitoring reports an alarm | Policy violation or abnormal behavior | Investigate logs and correlate with operational events |
15. Cybersecurity Commissioning Checklist
Relay security
- Confirm the exact MiCOM model and firmware.
- Review available security features.
- Change default credentials where applicable.
- Configure approved user access.
- Restrict administrative functions.
- Verify unused interfaces and services.
Network security
- Confirm the approved network architecture.
- Configure VLANs and network zones.
- Apply firewall and ACL rules.
- Restrict access to MMS services.
- Protect GOOSE communication paths.
- Secure switch management interfaces.
- Disable unused network ports.
Engineering security
- Use approved engineering software.
- Restrict workstation access.
- Control removable media.
- Maintain configuration backups.
- Record setting and communication changes.
- Verify SCL file integrity and revisions.
Monitoring and maintenance
- Enable appropriate network monitoring.
- Review switch and device logs.
- Monitor unexpected communication.
- Review remote access activity.
- Maintain approved firmware records.
- Review relevant cybersecurity advisories.
- Test backup restoration procedures.
- Document security commissioning results.
16. Conclusion
Cybersecurity is an essential part of modern IEC 61850 substation engineering. MiCOM protection relays must be integrated into a controlled network environment that protects communication, configuration data and engineering access.
IEC 62351 provides important security standards for power system communication, but actual implementation depends on the supported capabilities of the installed devices and software.
A reliable cybersecurity design combines network segmentation, access control, secure engineering workstations, controlled remote access, configuration management and continuous monitoring.
For protection engineers, cybersecurity should be considered throughout the complete relay lifecycle—from initial configuration and commissioning to operation, maintenance and future system upgrades.
Practical MiCOM Protection and IEC 61850 Training by Dr Saeed Roostaee – Elec-Engg
Elec-Engg provides practical training for protection, commissioning and substation automation engineers.
Relevant training topics include:
- MiCOM protection relay configuration.
- IEC 61850 communication and engineering.
- MMS and GOOSE communication.
- SCL configuration and system integration.
- Ethernet networking and VLAN configuration.
- IEC 62351 cybersecurity fundamentals.
- Secure engineering and configuration management.
- Wireshark-based communication analysis.
- Practical commissioning and troubleshooting.
Training is available through video courses, structured self-paced training, face-to-face courses and customized in-house programs.
Visit Elec-Engg for practical power system protection and substation automation training.
