GE M60, Инструкция по эксплуатации

Страница: 18 / 676

2-4 M60 MOTOR PROTECTION SYSTEM – INSTRUCTION MANUAL
SECURITY CHAPTER 2: PRODUCT DESCRIPTION
2
• CyberSentry security — Advanced security available using a software option. When purchased, the option is
automatically enabled, and the default Password security and EnerVista security are disabled.
2.2.0.1 EnerVista security
The EnerVista security management system is a role-based access control (RBAC) system that allows an administrator to
manage the privileges of multiple users. This allows for access control of UR devices by multiple personnel within a
substation and conforms to the principles of RBAC as defined in ANSI INCITS 359-2004. The EnerVista security
management system is disabled by default to allow the administrator direct access to the EnerVista software after
installation. It is recommended that security be enabled before placing the device in service.
Basic password or enhanced CyberSentry security applies, depending on purchase.
2.2.0.2 Password security
Password security is a basic security feature present by default.
Two levels of password security are provided: command and setting. Use of a password for each level controls whether
users can enter commands and/or change settings.
The M60 supports password entry from a local or remote connection. Local access is defined as any access to settings or
commands via the front panel interface. This includes both keypad entry and the through the front panel RS232 port.
Remote access is defined as any access to settings or commands via any rear communications port. This includes both
Ethernet and RS485 connections. Any changes to the local or remote passwords enables this functionality.
When entering a settings or command password via EnerVista or any serial interface, the user must enter the
corresponding connection password. If the connection is to the back of the M60, the remote password must be used. If the
connection is to the RS232 port of the front panel, the local password applies.
Password access events are logged in the Event Recorder.
2.2.0.3 CyberSentry security
CyberSentry embedded security is available using software options that provide advanced security services. When an
option is purchased, the basic password security is disabled automatically.
CyberSentry provides security through the following features:
•
An Authentication, Authorization, Accounting (AAA) Remote Authentication Dial-In User Service (RADIUS) client that is
centrally managed, enables user attribution, provides accounting of all user activities, and uses secure standards-
based strong cryptography for authentication and credential protection
• A Role-Based Access Control (RBAC) system that provides a permission model that allows access to UR device
operations and configurations based on specific roles and individual user accounts configured on the AAA server (that
is, Administrator, Supervisor, Engineer, Operator, Observer roles)
• Security event reporting through the Syslog protocol for supporting Security Information Event Management (SIEM)
systems for centralized cybersecurity monitoring
• Strong encryption of all access and configuration network messages between the EnerVista software and UR devices
using the Secure Shell (SSH) protocol, the Advanced Encryption Standard (AES), and 128-bit keys in Galois Counter
Mode (GCM) as specified in the U.S. National Security Agency Suite B extension for SSH and approved by the National
Institute of Standards and Technology (NIST) FIPS-140-2 standards for cryptographic systems
CyberSentry user roles
CyberSentry user roles (Administrator, Engineer, Operator, Supervisor, Observer) limit the levels of access to various UR
device functions. This means that the EnerVista software allows for access to functionality based on the user’s logged in
role.
Example: Administrative functions can be segmented away from common operator functions, or engineering type access,
all of which are defined by separate roles (see figure) so that access of UR devices by multiple personnel within a
substation is allowed.
One role of one type is allowed to be logged in at a time. For example, one Operator can be logged in but not a second
Operator at the same time. This prevents subsets of settings from being changed at the same time.