Infoteenus
33 SIDETEHNIKA
Uued standardid
EVS-EN 301 406-1 V3.2.1:2026
Raadiotelefonisüsteem (DECT);
Raadiospektrile juurdepääsu harmoneeritud standard;
Osa 1. DECT, DECT Evolution ja DECT ULE
Käsitlusala: The present document specifies technical characteristics and methods of measurements for equipment implementing the Digital Enhanced Cordless Telecommunications (DECT) common interface, as specified in the multi-part technical specification ETSI EN 300 175 including the variants DECT Evolution and DECT ULE (see ETSI EN 300 175-1 for an overview).
The present document applies to the following equipment types:
a) Fixed Part (FP);
b) Portable Part (PP);
c) Cordless Terminal Adapter (CTA);
d) Wireless Relay Station (WRS) (FP and PP combined);
e) Hybrid Part (HyP) (a PP with capability to act as a FP to provide PP to PP communication).
NOTE: This release of the standard covers the WRS type CRFP, but not the WRS type REP.
These radio equipment types are capable of operating in all or any part of the frequency bands given in table 1.
Table 1: Radiocommunications service frequency bands
Radiocommunications service frequency bands
Transmit 1 880 MHz to 1 900 MHz
Receive 1 880 MHz to 1 900 MHz
The DECT service frequency band for transmitting and receiving for all elements is 1 880 MHz to 1 900 MHz. National regulation can allow additional frequency bands.
Details of the DECT Common Interface may be found in the multi-part deliverable ETSI EN 300 175. Further details of the DECT system may be found in the ETSI TR 101 178.
DECT ULE implements, in addition to the DECT Common Interface, the multi-part ETSI TS 102 939 (see ETSI TS 102 939-1 and ETSI TS 102 939-2).
The present document contains requirements to demonstrate that radio equipment both effectively uses and supports the efficient use of radio spectrum in order to avoid harmful interference.
NOTE: The relationship between the present document and essential requirements of article 3.2 of Directive 2014/53/EU is given in annex A.
The present document applies to the following equipment types:
a) Fixed Part (FP);
b) Portable Part (PP);
c) Cordless Terminal Adapter (CTA);
d) Wireless Relay Station (WRS) (FP and PP combined);
e) Hybrid Part (HyP) (a PP with capability to act as a FP to provide PP to PP communication).
NOTE: This release of the standard covers the WRS type CRFP, but not the WRS type REP.
These radio equipment types are capable of operating in all or any part of the frequency bands given in table 1.
Table 1: Radiocommunications service frequency bands
Radiocommunications service frequency bands
Transmit 1 880 MHz to 1 900 MHz
Receive 1 880 MHz to 1 900 MHz
The DECT service frequency band for transmitting and receiving for all elements is 1 880 MHz to 1 900 MHz. National regulation can allow additional frequency bands.
Details of the DECT Common Interface may be found in the multi-part deliverable ETSI EN 300 175. Further details of the DECT system may be found in the ETSI TR 101 178.
DECT ULE implements, in addition to the DECT Common Interface, the multi-part ETSI TS 102 939 (see ETSI TS 102 939-1 and ETSI TS 102 939-2).
The present document contains requirements to demonstrate that radio equipment both effectively uses and supports the efficient use of radio spectrum in order to avoid harmful interference.
NOTE: The relationship between the present document and essential requirements of article 3.2 of Directive 2014/53/EU is given in annex A.
Alusdokumendid: ETSI EN 301 406-1 V3.2.1
EVS-EN 300 392-12-22 V1.7.1:2026
Terrestrial Trunked Radio (TETRA);
Voice plus Data (V+D);
Part 12: Supplementary services stage 3;
Sub-part 22: Dynamic Group Number Assignment (DGNA)
Käsitlusala: The present document defines the stage 3 specifications of the Supplementary Service Dynamic Group Number Assignment (SS-DGNA) for the Terrestrial Trunked Radio (TETRA).
The SS-DGNA enables a user to dynamically define group identities and group related parameters to the TETRA system and to the subscribers in the system. These definitions are used to enable group call invocations to dynamically defined groups. The SS-DGNA specification defines the creation, modification, deletion and interrogation of group definitions in the Switching and Management Infrastructure (SwMI), in the Mobile Station (MS).
The present document does not include the specification for access priority used for random access in uplink and call priority used by SwMI for resource allocation in a group call. Access priority and call priority can be specified and applied for groups using Supplementary Services Access Priority (SS-AP), Priority Call (SS-PC) and Pre-emptive Priority Call (SS-PPC). Thus, the definition procedure of these priorities is outside the scope of the present document.
Man Machine Interface (MMI) and charging principles are also outside the scope of the present document.
Supplementary service stage 3 specification is preceded by the stage 1 and the stage 2 specifications of the service. Stage 1 describes the functional capabilities from the user's point of view. Stage 2 defines the functional behaviour in terms of functional entities and information flows. Stage 3 gives the precise description of the supplementary service from the implementation point of view. It defines the protocols for the service and the encoding rules for the information flows. It defines the processes for the functional entities and their behaviour. The described protocols and their behaviour apply for the SwMI and for the MS and can be applied over the Inter-System Interface (ISI) between TETRA systems.
The SS-DGNA enables a user to dynamically define group identities and group related parameters to the TETRA system and to the subscribers in the system. These definitions are used to enable group call invocations to dynamically defined groups. The SS-DGNA specification defines the creation, modification, deletion and interrogation of group definitions in the Switching and Management Infrastructure (SwMI), in the Mobile Station (MS).
The present document does not include the specification for access priority used for random access in uplink and call priority used by SwMI for resource allocation in a group call. Access priority and call priority can be specified and applied for groups using Supplementary Services Access Priority (SS-AP), Priority Call (SS-PC) and Pre-emptive Priority Call (SS-PPC). Thus, the definition procedure of these priorities is outside the scope of the present document.
Man Machine Interface (MMI) and charging principles are also outside the scope of the present document.
Supplementary service stage 3 specification is preceded by the stage 1 and the stage 2 specifications of the service. Stage 1 describes the functional capabilities from the user's point of view. Stage 2 defines the functional behaviour in terms of functional entities and information flows. Stage 3 gives the precise description of the supplementary service from the implementation point of view. It defines the protocols for the service and the encoding rules for the information flows. It defines the processes for the functional entities and their behaviour. The described protocols and their behaviour apply for the SwMI and for the MS and can be applied over the Inter-System Interface (ISI) between TETRA systems.
Alusdokumendid: ETSI EN 300 392-12-22 V1.7.1
EVS-EN 300 392-3-12 V1.4.1:2026
Terrestrial Trunked Radio (TETRA);
Voice plus Data (V+D);
Part 3: Interworking at the Inter-System Interface (ISI);
Sub-part 12: Transport layer independent
Additional Network Feature Individual Call (ANF-ISIIC)
Käsitlusala: The present document defines the Terrestrial Trunked Radio (TETRA) system supporting Voice plus Data (V+D). It specifies:
• the interworking of individual calls between TETRA networks;
• the supplementary services interaction with individual calls between TETRA networks.
The TETRA V+D interworking - basic operation part defines the interworking between TETRA networks over the corresponding interface: the Inter-System Interface (ISI). It comprises the following sub-parts:
• Transport layer independent General design;
• General Design, PSS1 over E.1;
• General Design, SIP/IP;
• Transport layer independent Additional Network Feature - ISI Individual Call (ANF-ISIIC) (the present document);
• Transport layer independent Additional Network Feature - ISI Group Call (ANF-ISIGC);
• Transport layer independent Additional Network Feature - ISI Short Data service (ANF-ISISDS);
• Transport layer independent Additional Network Feature - ISI Mobility Management (ANF-ISIMM);
• Generic Speech Format Implementation.
The present document is the ANF-ISIIC sub-part.
Like all other Additional Network Feature (ANF) specifications, those of ANF-ISIIC are produced in three stages, according to the method described in Recommendation ITU-T I.130. The present document contains the stage 1 and 2 descriptions of ANF-ISIIC, and stage 3 description. The stage 1 description specifies the ANF as seen by its users, which are essentially the individual call control entities in both TETRA networks. The stage 2 description identifies the functional entities involved in the ANF and the information flows between them. And the stage 3 description of ANF-ISIIC specifies its protocol.
NOTE 1: According to Recommendation ITU-T I.130, the stage 3 description of a bearer or tele-service addresses the network implementation aspects. Consequently, it comprises two steps: the specifications of all protocols at the various reference points involved in any of the service procedures (notably the service operation) are the first step of the stage 3 description, and the specifications of the functions of the corresponding network entities are its second step.
NOTE 2: The SDL diagrams have not been provided since they can be derived from the specification of the functional entity actions in the stage 2 description.
The present document applies to TETRA networks which support inter-TETRA individual calls. More specifically, it applies to their Circuit Mode Control Entities (CMCE), as defined in clause 14.2 of ETSI EN 300 392-2, and to their ANF-ISIIC entities defined in the stage 2 description.
The relation between the ANF-ISIIC and the transport layer protocol is described in the General Design documents.
• the interworking of individual calls between TETRA networks;
• the supplementary services interaction with individual calls between TETRA networks.
The TETRA V+D interworking - basic operation part defines the interworking between TETRA networks over the corresponding interface: the Inter-System Interface (ISI). It comprises the following sub-parts:
• Transport layer independent General design;
• General Design, PSS1 over E.1;
• General Design, SIP/IP;
• Transport layer independent Additional Network Feature - ISI Individual Call (ANF-ISIIC) (the present document);
• Transport layer independent Additional Network Feature - ISI Group Call (ANF-ISIGC);
• Transport layer independent Additional Network Feature - ISI Short Data service (ANF-ISISDS);
• Transport layer independent Additional Network Feature - ISI Mobility Management (ANF-ISIMM);
• Generic Speech Format Implementation.
The present document is the ANF-ISIIC sub-part.
Like all other Additional Network Feature (ANF) specifications, those of ANF-ISIIC are produced in three stages, according to the method described in Recommendation ITU-T I.130. The present document contains the stage 1 and 2 descriptions of ANF-ISIIC, and stage 3 description. The stage 1 description specifies the ANF as seen by its users, which are essentially the individual call control entities in both TETRA networks. The stage 2 description identifies the functional entities involved in the ANF and the information flows between them. And the stage 3 description of ANF-ISIIC specifies its protocol.
NOTE 1: According to Recommendation ITU-T I.130, the stage 3 description of a bearer or tele-service addresses the network implementation aspects. Consequently, it comprises two steps: the specifications of all protocols at the various reference points involved in any of the service procedures (notably the service operation) are the first step of the stage 3 description, and the specifications of the functions of the corresponding network entities are its second step.
NOTE 2: The SDL diagrams have not been provided since they can be derived from the specification of the functional entity actions in the stage 2 description.
The present document applies to TETRA networks which support inter-TETRA individual calls. More specifically, it applies to their Circuit Mode Control Entities (CMCE), as defined in clause 14.2 of ETSI EN 300 392-2, and to their ANF-ISIIC entities defined in the stage 2 description.
The relation between the ANF-ISIIC and the transport layer protocol is described in the General Design documents.
Alusdokumendid: ETSI EN 300 392-3-12 V1.4.1
EVS-EN 300 392-3-9 V1.4.1:2026
Terrestrial Trunked Radio (TETRA);
Voice plus Data (V+D);
Part 3: Interworking at the Inter-System Interface (ISI);
Sub-part 9: Transport layer independent, General design
Käsitlusala: The present document defines the general aspects of interworking at the Inter-System Interface (ISI) for Terrestrial Trunked Radio (TETRA) system supporting Voice plus Data (V+D). Those specify the general concepts which are the basis of the ISI operation between TETRA systems. It introduces the Additional Network Features (ANFs) used at the ISI, and specifies:
• the general protocol mechanism upon which the definition of each ANF is based; and
• the security related functions over the ISI.
The specification of the general transport layer independent protocol mechanism applies to any TETRA Switching and Management Infrastructure (SwMI) which supports the ISI. The security requirements for the ISI only apply to SwMIs which support authentication or end-to-end encryption over the ISI.
Besides the ISI general design, the present sub-part, interworking at the Inter-System Interface comprises the following other sub-parts:
• General design, PSS1 over E.1;
• General design, SIP/IP;
• Transport layer independent Additional Network Feature Individual Call (ANF-ISIIC);
• Transport layer independent Additional Network Feature Group Call (ANF-ISIGC);
• Transport layer independent Additional Network Feature Short Data Service (ANF-ISISDS);
• Transport layer independent Additional Network Feature, Mobility Management (ANF-ISIMM); and
• Generic Speech Format Implementation.
• the general protocol mechanism upon which the definition of each ANF is based; and
• the security related functions over the ISI.
The specification of the general transport layer independent protocol mechanism applies to any TETRA Switching and Management Infrastructure (SwMI) which supports the ISI. The security requirements for the ISI only apply to SwMIs which support authentication or end-to-end encryption over the ISI.
Besides the ISI general design, the present sub-part, interworking at the Inter-System Interface comprises the following other sub-parts:
• General design, PSS1 over E.1;
• General design, SIP/IP;
• Transport layer independent Additional Network Feature Individual Call (ANF-ISIIC);
• Transport layer independent Additional Network Feature Group Call (ANF-ISIGC);
• Transport layer independent Additional Network Feature Short Data Service (ANF-ISISDS);
• Transport layer independent Additional Network Feature, Mobility Management (ANF-ISIMM); and
• Generic Speech Format Implementation.
Alusdokumendid: ETSI EN 300 392-3-9 V1.4.1
EVS-EN IEC 61000-4-30:2025/AC:2026
Elektromagnetiline ühilduvus. Osa 4-30: Katsetus- ja mõõtetehnika. Elektrikvaliteedi mõõtemeetodid
Käsitlusala: Corrigendum to EN IEC 61000-4-30:2025
Alusdokumendid: IEC 61000-4-30:2025/COR1:2026; EN IEC 61000-4-30:2025/AC:2026-08
IEC 61000-4-29:2026
Electromagnetic compatibility (EMC) - Part 4-29: Testing and measurement techniques - Voltage dips, short interruptions and voltage variations on d.c. input power port immunity tests
Käsitlusala: IEC 61000-4-29:2026 defines test methods for immunity to voltage dips, short interruptions and voltage variations at the DC input power port of electrical or electronic equipment. This document is applicable to equipment and systems whose DC input power ports are intended to be connected to low voltage DC networks external to the equipment and systems. The object of this document is to establish a common and reproducible basis for testing electrical and electronic equipment when subjected to voltage dips, short interruptions or voltage variations on DC input power ports.
This document defines:
- the range of test levels;
- the test generator;
- the test set-up;
- the test procedure.
The test described hereinafter applies to electrical and electronic equipment and systems. It also applies to modules or subsystems whenever the equipment under test’s (EUT) rated power is greater than the test generator capacity specified in Clause 6. The ripple at the DC input power port is not included in the scope of this document. It is covered by IEC 61000‑4‑17. This document does not specify the tests to be applied to particular apparatus or systems. Its main aim is to give a general basic reference to IEC product committees. These product committees (or users and manufacturers of equipment) remain responsible for the appropriate choice of the tests and the severity level to be applied to their equipment. This second edition cancels and replaces the first edition published in 2000. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) Increase of the output voltage of the test generator to take into account new DC networks voltages;
b) provision of tolerances for the duration of the voltage changes;
c) limitation of the current when applying short interruptions in low impedance condition;
d) general technical clarifications for the specifications of the test generator and their verification;
e) clarifications regarding the loads used to verify the switching characteristics and the peak inrush current drive capability of the test generator;
f) clarifications regarding the evaluation of test results and test reports;
g) description of the DC environment.
This document defines:
- the range of test levels;
- the test generator;
- the test set-up;
- the test procedure.
The test described hereinafter applies to electrical and electronic equipment and systems. It also applies to modules or subsystems whenever the equipment under test’s (EUT) rated power is greater than the test generator capacity specified in Clause 6. The ripple at the DC input power port is not included in the scope of this document. It is covered by IEC 61000‑4‑17. This document does not specify the tests to be applied to particular apparatus or systems. Its main aim is to give a general basic reference to IEC product committees. These product committees (or users and manufacturers of equipment) remain responsible for the appropriate choice of the tests and the severity level to be applied to their equipment. This second edition cancels and replaces the first edition published in 2000. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) Increase of the output voltage of the test generator to take into account new DC networks voltages;
b) provision of tolerances for the duration of the voltage changes;
c) limitation of the current when applying short interruptions in low impedance condition;
d) general technical clarifications for the specifications of the test generator and their verification;
e) clarifications regarding the loads used to verify the switching characteristics and the peak inrush current drive capability of the test generator;
f) clarifications regarding the evaluation of test results and test reports;
g) description of the DC environment.
Alusdokumendid:
Asendab: IEC 61000-4-29:2000
IEC 61300-3-30:2026
Fibre optic interconnecting devices and passive components - Basic test and measurement procedures - Part 3-30: Examinations and measurements - Endface geometry of rectangular ferrule
Käsitlusala: IEC 61300-3-30 describes a method for measuring the endface geometry of rectangular multifibre ferrules having an IEC defined optical interface. The primary attributes are fibre position relative to the endface, endface angle relative to the guide holes, fibre tip radii and core dip for multimode fibres.
This edition includes the following significant technical changes with respect to the previous edition:
a) clarification of region diameter symbols;
b) introduction of x116 and x132 region of interest (ROI) to support MT-16 and MT-32 ferrule types;
c) preparation of geometry limit (GL) parameter tables for 16-, 24- and 32-fibre ferrules;
d) clarification of the neighbouring fibres definition when computing adjacent height;
e) improvement of figures in Annexes.
This edition includes the following significant technical changes with respect to the previous edition:
a) clarification of region diameter symbols;
b) introduction of x116 and x132 region of interest (ROI) to support MT-16 and MT-32 ferrule types;
c) preparation of geometry limit (GL) parameter tables for 16-, 24- and 32-fibre ferrules;
d) clarification of the neighbouring fibres definition when computing adjacent height;
e) improvement of figures in Annexes.
Alusdokumendid:
Asendab: IEC 61300-3-30:2020
IEC 62351-8:2026
Power systems management and associated information exchange - Data and communications security - Part 8: Role-based access control for power system management
Käsitlusala: IEC 62351-8:2026 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 thus provides 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, a local and automated computer agent, or a built-in human machine interface (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. This is achieved by defining two different encoding approaches to handle the definition of custom roles, either based on specific permissions or based on constraints to existing permissions. The definition on handling custom based roles was started in IEC 62351-90-1 and taken over into the IEC 62351-8:2020. Moreover, additionally to the definition of custom roles based on associated permissions, this document also includes options how to assign permissions to objects in a general way. Referencing documents will provide a mapping to a concrete data model to ensure an interoperability for standard roles used in different data models as well as for custom defined roles. Referencing documents might be standards such as IEC PAS 61850-90-19 or IEC 60870-5-7:2025 or also definitions by an operator.
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, such as:
– definition of usernames and password definitions/policies;
– management of keys and/or key exchange;
– engineering process of roles;
– assignment of roles;
– selection of trusted certification authorities issuing credentials (access tokens);
– defining the tasks of a security officer;
– integrating local policies in RBAC.
Existing standards (see ANSI INCITS 359-2004, IEC 62443 (all parts), and IEEE 802.1X-2020) in process control industry and access control (RFC 2904 and RFC 2905) are not sufficient for addressing specifics of power system automation as none of them specify either the exact role name and associated permissions or the format of the access tokens nor the detailed mechanism by which access tokens are transferred to and authenticated by the target system. This is addressed in this document by defining the access token format, distribution and verification based on existing technology.
Throughout the document security events are defined. These security events are intended to support the error handling and thus to increase system resilience. Implementations need to provide a mechanism for announcing security events.
The information about security events and potential detailed information can only be provided by the entity based on the availability of this information through the underlying platform or utilized components.
It is strongly recommended that the security events defined throughout the document are made available to the operational infrastructure by cyber security events as specified in IEC 62351 14 and/or by monitoring objects as specified in IEC 62351-7. Annex A provides a mapping of the defined events in this document to the notion of IEC 62351-14.
Notices, warnings, errors, and alarms are used to indicate the severity of an event from a security point of view. The following notion from IEC 62351-14 is used:
– A notice refers to a cyber security related activity during the routine use or maintenance of an entity. It does not relate to a cyber security breach or attack or deviation from the normal operating condition of an entity.
– A warning is a deviation from the normal operating condition of an entity but not necessary a cyber-attack.
– An error describes an unforeseen condition, which can indicate unauthorized activity. It might not require immediate action.
– An alarm is an indication of a serious problem, which might indicate unauthorized activity. Action is expected to be taken immediately.
In any case, it is expected that an organization’s security policy determines the final handling of events based on the operational environment. For instance, the assessment of one of more alarms could rise to the level of an incident.
This second edition cancels and replaces the first edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) Removal of mapping of roles to permission to objects based on the target data model and/or protocol to allow for other mappings than IEC 61850. Mapping is delegated to separate documents;
b) Specification of handling of a combination of roles and permissions as operationSet to allow more fine-grained assignments to objects;
c) Specification of a simplified roles assignment to more efficiently handle situations in which roles are used relating to different data models, including examples;
d) Inclusion of new profile to allow for fetching RBAC information from LDAP repositories;
e) Definition of specific security events throughout the document;
f) Alignment of terminology and enhancement with examples.
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 thus provides 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, a local and automated computer agent, or a built-in human machine interface (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. This is achieved by defining two different encoding approaches to handle the definition of custom roles, either based on specific permissions or based on constraints to existing permissions. The definition on handling custom based roles was started in IEC 62351-90-1 and taken over into the IEC 62351-8:2020. Moreover, additionally to the definition of custom roles based on associated permissions, this document also includes options how to assign permissions to objects in a general way. Referencing documents will provide a mapping to a concrete data model to ensure an interoperability for standard roles used in different data models as well as for custom defined roles. Referencing documents might be standards such as IEC PAS 61850-90-19 or IEC 60870-5-7:2025 or also definitions by an operator.
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, such as:
– definition of usernames and password definitions/policies;
– management of keys and/or key exchange;
– engineering process of roles;
– assignment of roles;
– selection of trusted certification authorities issuing credentials (access tokens);
– defining the tasks of a security officer;
– integrating local policies in RBAC.
Existing standards (see ANSI INCITS 359-2004, IEC 62443 (all parts), and IEEE 802.1X-2020) in process control industry and access control (RFC 2904 and RFC 2905) are not sufficient for addressing specifics of power system automation as none of them specify either the exact role name and associated permissions or the format of the access tokens nor the detailed mechanism by which access tokens are transferred to and authenticated by the target system. This is addressed in this document by defining the access token format, distribution and verification based on existing technology.
Throughout the document security events are defined. These security events are intended to support the error handling and thus to increase system resilience. Implementations need to provide a mechanism for announcing security events.
The information about security events and potential detailed information can only be provided by the entity based on the availability of this information through the underlying platform or utilized components.
It is strongly recommended that the security events defined throughout the document are made available to the operational infrastructure by cyber security events as specified in IEC 62351 14 and/or by monitoring objects as specified in IEC 62351-7. Annex A provides a mapping of the defined events in this document to the notion of IEC 62351-14.
Notices, warnings, errors, and alarms are used to indicate the severity of an event from a security point of view. The following notion from IEC 62351-14 is used:
– A notice refers to a cyber security related activity during the routine use or maintenance of an entity. It does not relate to a cyber security breach or attack or deviation from the normal operating condition of an entity.
– A warning is a deviation from the normal operating condition of an entity but not necessary a cyber-attack.
– An error describes an unforeseen condition, which can indicate unauthorized activity. It might not require immediate action.
– An alarm is an indication of a serious problem, which might indicate unauthorized activity. Action is expected to be taken immediately.
In any case, it is expected that an organization’s security policy determines the final handling of events based on the operational environment. For instance, the assessment of one of more alarms could rise to the level of an incident.
This second edition cancels and replaces the first edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) Removal of mapping of roles to permission to objects based on the target data model and/or protocol to allow for other mappings than IEC 61850. Mapping is delegated to separate documents;
b) Specification of handling of a combination of roles and permissions as operationSet to allow more fine-grained assignments to objects;
c) Specification of a simplified roles assignment to more efficiently handle situations in which roles are used relating to different data models, including examples;
d) Inclusion of new profile to allow for fetching RBAC information from LDAP repositories;
e) Definition of specific security events throughout the document;
f) Alignment of terminology and enhancement with examples.
Alusdokumendid:
IEC TR 61000-1-9:2024+AMD1:2026 CSV
Electromagnetic compatibility (EMC) - Part 1-9: General - Evaluation of uncertainty for the measurement of harmonic current emissions
Käsitlusala: IEC TR 61000-1-9:2024+AMD1:2026 CSV which is a Technical Report, provides examples for the evaluation of measurement uncertainty of harmonic emission tests performed using IEC 61000-3-2 and IEC 61000-3-12, and their application to the relevant conformity decisions. It also contains practical formulae to enable calculations in accordance with ISO/IEC Guide 98-3 (GUM).
Alusdokumendid:
IEC 61850-7-1:2011/AMD1:2020/COR1:2026
Corrigendum 1 - Amendment 1 - Communication networks and systems for power utility automation - Part 7-1: Basic communication structure - Principles and models
Käsitlusala:
Alusdokumendid:
IEC TR 61000-1-9:2024/AMD1:2026
Amendment 1 - Electromagnetic compatibility (EMC) - Part 1-9: General - Evaluation of uncertainty for the measurement of harmonic current emissions
Käsitlusala:
Alusdokumendid:
Asendatud standardid
EVS-ETS 300 247/A1:2001
Business Telecommunications (BT) - Open Network Provision (ONP) technical requirements - 2048 kbit/s digital unstructured leased line (D2048U) - Connection characteristics
Käsitlusala: This ETS specifies the technical requirements and test principles for connection characteristics of ONP 2048 kbit/s digital unstructured leased lines. This ETS is applicable for leased lines, including part time leased lines
for which the establishment or release does not require any protocol exchange or other intervention at the NTP by the user.
for which the establishment or release does not require any protocol exchange or other intervention at the NTP by the user.
Alusdokumendid: ETS 300247/A1
EVS-ETS 300 247:2001
Business Telecommunications (BT) - Open Network Provision (ONP) technical requirements - 2048 kbit/s digital unstructured leased line (D2048U) - Connection characteristics
Käsitlusala: This ETS specifies the technical requirements and test principles for connection characteristics of ONP 2048 kbit/s digital unstructured leased lines.This ETS is applicable for leased lines, including part time leased lines
for which the establishment or release does not require any protocol exchange or other intervention at the NTP by the user.
for which the establishment or release does not require any protocol exchange or other intervention at the NTP by the user.
Alusdokumendid: ETS 300247
EVS-ETS 300 248 ed.1:2006
Business Telecommunications (BT);Open Network Provision (ONP) technical requirements;2 048 kbit/s digital unstructured leased line (D2048U) Terminal equipment interface
Käsitlusala: Standardi käsitlusala on leitav standardi tekstist.
Alusdokumendid: ETS 300 248 ed.1:1993+A1:1995
EVS-ETS 300 288/A1:2001
Business TeleCommunications (BTC) - 64 kbit/s digital unrestricted leased line with octet integrity (D64U) - Network interface presentation
Käsitlusala: This ETS specifies the technical requirements and test principles for network interface presentations of ONP 64 kbit/s digital unstructed leased lines with octet integrity.
Alusdokumendid: ETS 300288/A1
EVS-ETS 300 288:2001
Business TeleCommunications (BTC) - 64 kbit/s digital unrestricted leased line with octet integrity (D64U) - Network interface presentation
Käsitlusala: This ETS specifies the technical requirements and test principles for the network interface presentations of ONP 64 kbit/s digital unrestricted leased lines with octet integrity. These presentations are codirectional.
Alusdokumendid: ETS 300288
EVS-ETS 300 289:2001
Business TeleCommunications (BTC) - 64 kbit/s digital unrestricted leased line with octet integrity (D64U) - Connection characteristics
Käsitlusala: This ETS specifies the technical requirements and test principles for connection characteristics of ONP 64 kbit/s digital unrestricted leased lines with octet integrity.
Alusdokumendid: ETS 300289
EVS-ETS 300 290 ed.1:2006
Business TeleCommunications (BTC);64 kbit/s digital unrestricted leased line with octet integrity (D64U);Terminal equipment interface
Käsitlusala: Standardi käsitlusala on leitav standardi tekstist.
Alusdokumendid: ETS 300 290 ed.1:1994+A1:1995
EVS-ETS 300 418:2001
Business TeleCommunications (BTC) - 2048 kbit/s digital unstructured and structured leased lines (D2048U and D2048S) - Network interface presentation
Käsitlusala: This ETS specifies the technical requirements and test principles for the network interpresentations of ONP 2048 kbit/s digital leased lines.
Alusdokumendid: ETS 300418
EVS-ETS 300 420 ed.1:2006
Business TeleCommunications (BTC);2 048 kbit/s digital structured leased lines (D2048S);Terminal equipment interface
Käsitlusala: Standardi käsitlusala on leitav standardi tekstist.
Alusdokumendid: ETS 300 420 ed.1
EVS-ETS 300 448:2001
Business TeleCommunications (BTC) - Ordinary quality voice bandwidth 2-wire analogue leased line (A2O) - Connection characteristics and network interface presentation
Käsitlusala: This ETS specifies the technical requirements and test principles for the connection characteristics and the physical and electrical characteristics of the network interface presentation of ordinary quality, voice bandwidth, 2-wire, analogue leased lines, provided as part of the minimum set under the Council Directive on the application of Open Network Provision (ONP) to leased lines (92/44/EEC).
Alusdokumendid: ETS 300448
EVS-ETS 300 449:2001
Business TeleCommunications (BTC) - Special quality voice bandwidth 2-wire analogue leased line (A2S) - Connection characteristics and network interface presentation
Käsitlusala: This ETS specifies the technical requirements and test principles for the connection characteristics and the physical and electrical characteristics of the network interface presentation of special quality, voice bandwidth, 2-wire, analogue leased lines, provided as part of the minimum set under the Council Directive on the application of Open Network Provision (ONP) to leased lines (92/44/EEC).
Alusdokumendid: ETS 300449
EVS-ETS 300 450 ed.1:2006
Business TeleCommunications (BTC);Ordinary and Special quality voice bandwidth 2-wire analogue leased lines (A2O and A2S);Terminal equipment interface
Käsitlusala: Standardi käsitlusala on leitav standardi tekstist.
Alusdokumendid: ETS 300 450 ed.1
EVS-ETS 300 451:2001
Business TeleCommunications (BTC) - Ordinary quality voice bandwidth 4-wire analogue leased line (A4O) - Connection characteristics and network interface presentation
Käsitlusala: This European Telecommunication Standard (ETS) specifies the technical requirements and test principles for the connection characteristics and the physical and electrical characteristics of the network interface
presentation of ordinary quality, voice bandwidth, 4-wire, analogue leased lines, provided as part of the minimum set under the Council Directive on the application of Open Network Provision (ONP) to leased lines (92/94/EEC)
presentation of ordinary quality, voice bandwidth, 4-wire, analogue leased lines, provided as part of the minimum set under the Council Directive on the application of Open Network Provision (ONP) to leased lines (92/94/EEC)
Alusdokumendid: ETS 300451
EVS-ETS 300 452:2001
Business TeleCommunications (BTC) - Special quality voice bandwidth 4-wire analogue leased line (A4S) - Connection characteristics and network interface presentation
Käsitlusala: This ETS specifies the technical requirements and test principles for the connection characteristics and the physical and electrical characteristics of the network interface presentation of special quality, voice bandwidth, 4-wire, analogue leased lines, provided as part of the minimum set under the Council Directive on the application of Open Network Provision (ONP) to leased lines (92/94/EEC).
Alusdokumendid: ETS 300452
EVS-ETS 300 453 ed.1:2006
Business TeleCommunications (BTC);Ordinary and Special quality voice bandwidth 4-wire analogue leased lines (A4O and A4S);Terminal equipment interface
Käsitlusala: Standardi käsitlusala on leitav standardi tekstist.
Alusdokumendid: ETS 300 453 ed.1
EVS-ETS 300 686 ed.1:2006
Business TeleCommunications (BTC);34 Mbit/s and 140 Mbit/s digital leased lines (D34U, D34S, D140U, D140S);Network interface presentation
Käsitlusala: Standardi käsitlusala on leitav standardi tekstist.
Alusdokumendid: ETS 300 686 ed.1
EVS-ETS 300 687 ed.1:2006
Business TeleCommunications (BTC);34 Mbit/s digital leased lines (D34U and D34S);Connection characteristics
Käsitlusala: Standardi käsitlusala on leitav standardi tekstist.
Alusdokumendid: ETS 300 687 ed.1
EVS-ETS 300 688 ed.1:2006
Business TeleCommunications (BTC);140 Mbit/s digital leased lines (D140U and D140S);Connection characteristics
Käsitlusala: Standardi käsitlusala on leitav standardi tekstist.
Alusdokumendid: ETS 300 688 ed.1
EVS-ETS 300 689 ed.1:2006
Business TeleCommunications (BTC);34 Mbit/s digital leased lines (D34U and D34S);Terminal equipment interface
Käsitlusala: Standardi käsitlusala on leitav standardi tekstist.
Alusdokumendid: ETS 300 689 ed.1
EVS-ETS 300 690 ed.1:2006
Business TeleCommunications (BTC);140 Mbit/s digital leased lines (D140U and D140S);Terminal equipment interface
Käsitlusala: Standardi käsitlusala on leitav standardi tekstist.
Alusdokumendid: ETS 300 690 ed.1
EVS-ETS 300 766 ed.1:2006
Business TeleCommunications (BTC);Multiple 64 kbit/s digital unrestricted leased lines with octet integrity presented at a structured 2 048 kbit/s interface at either or both ends (D64M);Connection characteristics and network interface presentation
Käsitlusala: Standardi käsitlusala on leitav standardi tekstist.
Alusdokumendid: ETS 300 766 ed.1
EVS-EN 300 247:2004
Juurdepääs ja terminalid (AT). 2048 kbit/s digitaalsed struktureerimata rendiliinid (D2048U). Ühenduse karakteristikud
Käsitlusala: Käesolev standard sätestab tehnilised nõuded ja katsetuspõhimõtted vabakasutusvõrkude 2048 kbit/s digitaalse struktureerimata rendiliinide ühenduse karakteristikutele.
Alusdokumendid: EN 300 247 V1.2.1
EVS-EN 300 248 V1.2.1:2002
Access and Terminals (AT); 2 048 kbit/s digital unstructured leased line (D2048U); Terminal equipment interface
Käsitlusala: Standardi käsitlusala on leitav standardi tekstist.
Alusdokumendid: EN 300 248 V1.2.1
EVS-EN 300 288:2004
Juurdepääs ja terminalid. 64 kbit/s digitaalne piiramata oktett terviklikkusega rendiliinid (D64U). Võrguliides
Käsitlusala: Standard sätestab tehnilised nõuded ja katsetuspõhimõtted vabakasutusvõrkude 64 kbit/s oktett terviklusega digitaalsete struktureerimata rendiliinide võrguliidesele. Nimetatud liides on kahesuunaline.
Alusdokumendid: EN 300 288 V1.2.1
EVS-EN 300 289:2004
Juurdepääs ja terminalid (AT). 64 kbit/s digitaalsed piiramata oktett terviklusega rendiliinid (D64U). Ühenduse karakteristikud
Käsitlusala: Standard sätestab tehnilised nõuded ja katsetuspõhimõtted vabakasutusvõrkude 64 kbit/s oktett terviklusega digitaalsete struktureerimata rendiliinide ühenduskarakteristikutele. Rendiliin pakub juurdepääsu täieliku digitaalse 64 kbit/s bitikiiruse ulatuses võrgu ajastusega mõlemal ülekandesuunal ning ilma piiranguteta kahendsisalduse osas.
Alusdokumendid: EN 300 289 V1.2.1
EVS-EN 300 290 V1.2.1:2003
Access and Terminals (AT);64 kbit/s digital unrestricted leased line with octet integrity (D64U);Terminal equipment interface
Käsitlusala: Standardi käsitlusala on leitav standardi tekstist.
Alusdokumendid: EN 300 290 V1.2.1
EVS-EN 300 418:2004
Juurdepääs ja terminalid (AT). 2 048 kbit/s digitaalsed struktureerimata ja struktureeritud rendiliinid (D2048U ja D2048S). Võrguliides
Käsitlusala: Standard sätestab tehnilised nõuded ja katsetuspõhimõtted vabakasutusvõrgu 2 048 kbit/s digitaalsete 120 W liidestega rendiliinide võrguliidesele. Siia kuuluvad 2 048 kbit/s digitaalne struktureerimata rendiliin ja 2 048 kbit/s digitaalne struktureeritud rendiliin informatsiooniedastuskiirusega 1 984 kbit/s olenemata kahendsisaldusest
Alusdokumendid: EN 300 418 V1.2.1
EVS-EN 300 419:2003
Juurdepääs ja terminalid (AT). 2048 kbit/s digitaalsed struktureeritud rendiliinid (D2048S). Ühenduse karakteristikud
Käsitlusala: Standard spetsifitseerib digitaalsete2048 kbit/s struktureeritud rendiliinide korral vabakasutusvõrgus ühenduse karakteristikutele kehtestatavad tehnilised nõuded ja testimise põhimõtted.
Alusdokumendid: EN 300 419 V1.2.1
EVS-EN 300 420 V1.2.1:2004
Access and Terminals (AT); 2 048 kbit/s digital structured leased lines (D2048S); Terminal equipment interface
Käsitlusala: Standardi käsitlusala on leitav standardi tekstist.
Alusdokumendid: EN 300 420 V1.2.1
EVS-EN 300 448:2004
Juurdepääs ja terminalid (AT). Lihtkvaliteediga kõnesagedusala kahejuhtmelised analoogrendiliinid (A2O). ÜhendusE karakteristikud ja võrguliides
Käsitlusala: Standardis määratletakse kõnesagedusalas lihtkvaliteediga kahejuhtmelise analoogrendiliini ühenduskarakteristikute ning võrguliidese füüsikaliste ja elektriliste karakteristikute (välja arvatud ohutuse, liigpinge ja elektromagnetilise ühilduvuse aspektid) tehnilised nõuded ja katsetuspõhimõtted, mis moodustavad osa Nõukogu vabakasutusvõrgu rendiliinide suhtes kohaldamist käsitlevas direktiivis sätestatud minimaalsetest nõuetest (92/44/EMÜ, vt. lisa E).
Alusdokumendid: EN 300 448 V1.2.1
EVS-EN 300 449:2004
Juurdepääs ja terminalid (AT). Erikvaliteediga kõnesagedusala kahejuhtmelised analoogrendiliinid (A2S). Ühenduse karakteristikud ja võrguliides
Käsitlusala: Käesolevas standardis määratletakse kõnesagedusalas erikvaliteediga kahejuhtmelise analoogrendiliini ühenduse karakteristikute ning võrguliidese füüsikaliste ja elektriliste karakteristikute (välja arvatud ohutuse, liigpinge ja elektromagnetilise ühilduvuse aspektid) tehnilised nõuded ja katsetuspõhimõtted, mis moodustavad osa Nõukogu vabakasutusvõrgu rendiliinide suhtes kohaldamist käsitlevas direktiivis sätestatud minimaalsetest nõuetest (92/44/EMÜ) (vt lisa E).
Alusdokumendid: EN 300 449 V1.2.1
EVS-EN 300 450 V1.2.1:2003
Analogue Access and Terminals (AT); Ordinary and Special quality voice bandwidth 2-wire analogue leased lines (A2O and A2S); Terminal equipment interface
Käsitlusala: Standardi käsitlusala on leitav standardi tekstist.
Alusdokumendid: EN 300 450 V1.2.1
EVS-EN 300 451:2004
Juurdepääs ja terminalid (AT). Lihtkvaliteediga kõnesagedusala neljajuhtmelised analoogrendiliinid (A4O). Ühenduse karakteristikud ja võrguliides
Käsitlusala: Käesolevas standardis määratletakse kõnesagedusalas lihtkvaliteediga neljajuhtmelise analoogrendiliini ühenduse karakteristikute ning võrguliidese füüsikaliste ja elektriliste karakteristikute (välja arvatud ohutuse, liigpinge ja elektromagnetilise ühilduvuse aspektid) tehnilised nõuded ja katsetuspõhimõtted, mis moodustavad osa Nõukogu vabakasutusvõrgu kohaldamist rendiliinide suhtes käsitleva direktiivi minimaalsetest nõuetest (92/44/EMÜ) (vt lisa E).
Alusdokumendid: EN 300 451 V1.2.1
EVS-EN 300 452:2004
Juurdepääs ja terminalid (AT). Erikvaliteeediga kõnesagedusala neljajuhtmelised analoogrendiliinid (A4S). Ühenduse karakteristikud ja võrguliides
Käsitlusala: Käesolevas standardis määratletakse kõrgsagedusalas erikvaliteediga neljajuhtmielise analoogrendiliini ühenduse karateristikute ning võrguliidese füüsikaliste ja elektriliste karakteristikute (va ohutuse, liigpinge ja elktromagnetlise ühilduvuse aspektid) tehnilised nõuded ja katsetuspõhimõtted, mis moodustavad osa Nõukogu vabakasutusvõrgu rendiliinide suhtes kohaldamist käsitletava direktiivi minimaalsetest nõuetest (92/44/EMÜ).
Alusdokumendid: EN 300 452 V1.2.1
EVS-EN 300 453 V1.2.1:2003
Access and Terminals (AT); Ordinary and Special quality voice bandwidth 4-wire analogue leased lines (A4O and A4S); Terminal equipment interface
Käsitlusala: Standardi käsitlusala on leitav standardi tekstist.
Alusdokumendid: EN 300 453 V1.2.1
EVS-EN 300 659-1 V1.3.1:2004
Access and Terminals (AT); Analogue access to the Public Switched Telephone Network (PSTN); Subscriber line protocol over the local loop for display (and related) services; Part 1: On-hook data transmission
Käsitlusala: Standardi käsitlusala on leitav standardi tekstist.
Alusdokumendid: EN 300 659-1 V1.3.1
EVS-EN 300 659-2 V1.3.1:2004
Access and Terminals (AT); Analogue access to the Public Switched Telephone Network (PSTN); Subscriber line protocol over the local loop for display (and related) services; Part 2: Off-hook data transmission
Käsitlusala: Standardi käsitlusala on leitav standardi tekstist.
Alusdokumendid: EN 300 659-2 V1.3.1
EVS-EN 300 686 V1.2.1:2003
Access and Terminals (AT); 34 Mbit/s and 140 Mbit/s digital leased lines (D34U, D34S, D140U, D140S); Network interface presentation
Käsitlusala: Standardi käsitlusala on leitav standardi tekstist.
Alusdokumendid: EN 300 686 V1.2.1
EVS-EN 300 687 V1.2.1:2003
Access and Terminals (AT); 34 Mbit/s digital leased lines (D34U and D34S); Connection characteristics
Käsitlusala: Standardi käsitlusala on leitav standardi tekstist.
Alusdokumendid: EN 300 687 V1.2.1
EVS-EN 300 688 V1.2.1:2003
Access and Terminals (AT); 140 Mbit/s digital leased lines (D140U and D140S); Connection characteristics
Käsitlusala: Standardi käsitlusala on leitav standardi tekstist.
Alusdokumendid: EN 300 688 V1.2.1
EVS-EN 300 689 V1.2.1:2003
Access and Terminals (AT); 34 Mbit/s digital leased lines (D34U and D34S); Terminal equipment interface
Käsitlusala: Standardi käsitlusala on leitav standardi tekstist.
Alusdokumendid: EN 300 689 V1.2.1
EVS-EN 300 690 V1.2.1:2003
Access and Terminals (AT); 140 Mbit/s digital leased lines (D140U and D140S); Terminal equipment interface
Käsitlusala: Standardi käsitlusala on leitav standardi tekstist.
Alusdokumendid: EN 300 690 V1.2.1
EVS-EN 300 766 V1.2.1:2004
Access and Terminals (AT); Multiple 64 kbit/s digital unrestricted leased lines with octet integrity presented at a structured 2 048 kbit/s interface at either or both ends (D64M); Connection characteristics and network interface presentation
Käsitlusala: Standardi käsitlusala on leitav standardi tekstist.
Alusdokumendid: EN 300 766 V1.2.1
IEC 61000-4-29:2000
Electromagnetic compatibility (EMC) - Part 4-29: Testing and measurement techniques - Voltage dips, short interruptions and voltage variations on d.c. input power port immunity tests
Käsitlusala: Establishes a common and reproducible basis for testing electrical and electronic equipment when subjected to voltage dips, short interruptions or voltage variations on d.c. power ports.
This standard defines:
- the range of test levels;
- the test generator;
- the test set-up;
- the test procedure.
This standard defines:
- the range of test levels;
- the test generator;
- the test set-up;
- the test procedure.
Alusdokumendid:
Asendatud: IEC 61000-4-29:2026
IEC 62351-8:2020
Power systems management and associated information exchange - Data and communications security - Part 8: Role-based access control for power system management
Käsitlusala: 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.
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.
Alusdokumendid:
Asendatud: IEC 62351-8:2026
IEC 61300-3-30:2020
Fibre optic interconnecting devices and passive components - Basic test and measurement procedures - Part 3-30: Examinations and measurements - Endface geometry of rectangular ferrule
Käsitlusala: IEC 61300-3-30:2020 describes a method of measuring the end face geometry of rectangular multifibre ferrules having an IEC defined optical interface. The primary attributes are fibre position relative to the end face, either withdrawal or protrusion, end face angle relative to the guide pin bores, fibre tip radii and core dip for multimode fibres. This second edition cancels and replaces the first edition published in 2003. This edition constitutes a technical revision.This edition includes the following significant technical changes with respect to the previous edition:
- measurement of the individual fibre tip radii;
- introduction of the geometry limit (GL) metric;
- introduction of the minus coplanarity metric;
- new method for measuring the core dips;
- all measurement regions are now identical for MM and SM fibres;
- the ferrule surface angle sign convention has been changed.
- measurement of the individual fibre tip radii;
- introduction of the geometry limit (GL) metric;
- introduction of the minus coplanarity metric;
- new method for measuring the core dips;
- all measurement regions are now identical for MM and SM fibres;
- the ferrule surface angle sign convention has been changed.
Alusdokumendid:
Asendatud: IEC 61300-3-30:2026
Kavandid
prEN IEC 63652-2:2026
NFC Forum Specifications - Part 2: NFC Data Exchange Format
Käsitlusala: The NFC Data Exchange Format (NDEF) specification defines a message encapsulation format to exchange information between two NFC Forum Devices. NDEF is a lightweight, binary message format that can be used to encapsulate one or more application-defined payloads of arbitrary type and size into a single message construct. Each payload is described by a type, a length, and an optional identifier. Type identifiers can be URIs, MIME media types, or NFC-specific types. This latter format permits compact identification of well known types commonly used in NFC Forum applications, or self-allocation of a name space for organizations that wish to use it for their own NFC-specific purposes. The NDEF Payload Length is an unsigned integer that indicates the number of octets in the payload. A compact, NDEF short-record layout is provided for very small payloads. The optional NDEF Payload Identifier enables association of multiple payloads and crossreferencing between them. NDEF Payloads can include nested NDEF Messages or chains of linked chunks of length unknown at the time the data is generated. NDEF is strictly a message format, which provides no concept of a connection or of a logical circuit, nor does it address head-of-line problems.
Alusdokumendid: IEC 63652-2:2026; prEN IEC 63652-2:2026
prEN IEC 63652-1:2026
NFC Forum Specifications - Part 1: NFC Wireless Charging
Käsitlusala: This document specifies a method and procedures for Wireless Power Transfer between two NFC wireless devices. The provided technical foundations use NFC technology for the initiation, control and execution of 13.56 MHz power transfer.
Alusdokumendid: IEC 63652-1:2026; prEN IEC 63652-1:2026