International Standards and Conformity Assessment for all electrical, electronic and related technologies

TC 57

Power systems management and associated information exchange

 

Detail

Committee
Working Groups
Project Leader

Current

Status

Frcst Pub

Date

Stability

Date

TC 57WG 15Mr Steffen FriesPPUB2020-042022

History

Stage
Document
Downloads
Decision Date
Target Date
ACD
57/1935/RR PDF file 107 kB
2017-10-24 
CD
57/2017/CD
PDF file 942 kB
2018-07-062018-02
PCC
2018-09-282018-09
ACDV
57/2056/CC PDF file 564 kB
Word file 109 kB
2018-10-262019-02
TCDV
2019-02-012019-03
CCDV
57/2069/CDV
PDF file 1007 kB
PDF file 1120 kB
2019-03-222019-03
PRVC
2019-06-142019-06
AFDIS
57/2134/RVC PDF file 696 kB
Word file 84 kB
2019-08-232019-08
TFDIS
2019-08-302019-08
DECFDIS
2019-10-102019-10
RFDIS
2019-11-042019-10
CFDIS
57/2180/FDIS


2020-01-242020-01
PRVD
2020-03-062020-03
APUB
57/2197/RVD PDF file 298 kB
2020-03-132020-03
BPUB
2020-03-132020-03
PPUB
2020-04-282020-04
  

Abstract

IEC 62351-8: 2020 is to facilitate role-based access control (RBAC) for power system management. RBAC assigns human users, automated systems, and software applications (collectively called "subjects" in this document) to specified "roles", and restricts their access to only those resources, which the security policies identify as necessary for their roles.
As electric power systems become more automated and cyber security concerns become more prominent, it is becoming increasingly critical to ensure that access to data (read, write, control, etc.) is restricted. As in many aspects of security, RBAC is not just a technology; it is a way of running a business. RBAC is not a new concept; in fact, it is used by many operating systems to control access to system resources. Specifically, RBAC provides an alternative to the all-or-nothing super-user model in which all subjects have access to all data, including control commands.
RBAC is a primary method to meet the security principle of least privilege, which states that no subject should be authorized more permissions than necessary for performing that subject’s task. With RBAC, authorization is separated from authentication. RBAC enables an organization to subdivide super-user capabilities and package them into special user accounts termed roles for assignment to specific individuals according to their associated duties. This subdivision enables security policies to determine who or what systems are permitted access to which data in other systems. RBAC provides thus a means of reallocating system controls as defined by the organization policy. In particular, RBAC can protect sensitive system operations from inadvertent (or deliberate) actions by unauthorized users. Clearly RBAC is not confined to human users though; it applies equally well to automated systems and software applications, i.e., software parts operating independent of user interactions.
The following interactions are in scope:
– local (direct wired) access to the object by a human user; by a local and automated computer agent, or built-in HMI or panel;
– remote (via dial-up or wireless media) access to the object by a human user;
– remote (via dial-up or wireless media) access to the object by a remote automated computer agent, e.g. another object at another substation, a distributed energy resource at an end-user’s facility, or a control centre application.
While this document defines a set of mandatory roles to be supported, the exchange format for defined specific or custom roles is also in scope of this document.
Out of scope for this document are all topics which are not directly related to the definition of roles and access tokens for local and remote access, especially administrative or organizational tasks.

Project

IEC 62351-8:2020 ED1

Power systems management and associated information exchange - Data and communications security - Part 8: Role-based access control for power system management