Power systems management and associated information exchange - Data and communications security - Part 13: Guidelines on security topics to be covered in standards and specifications
Introduction: This document provides guidelines on what security topics should be covered in standards and specifications (IEC or otherwise) that are to be used in the power industry. These guidelines cannot be prescriptive for every standard, since individual standards and specifications may legitimately have very different focuses, but it should be expected that the combination of such standards and specifications used in any implementation should cover these security topics. These guidelines could therefore be used as a checklist for the combination of standards and specifications used in implementations of systems. The security requirements for human users and software applications are different from the purely technical security requirements found in many communication and device standards. For user security standards, more emphasis should be on “policy and procedures” and “roles and authorization” rather than “bits and bytes” cryptographic technologies that should be included in Information and Communications Technology (ICT). In addition, engineering practices and system configurations should be taken into account, since no cryptography can compensate for poor design. Figure 1 illustrates the relationships between security requirements, threats, and attacks. This document is structured into four sections: Clause 5: Security requirements for standards and specifications which do not address specific cybersecurity technologies but where interactions between human users, software appli
Scope: This part of IEC 62351, which is a Technical Report, provides guidelines on what security topics could or should be covered in standards and specifications (IEC or otherwise) that are to be used in the power industry, and the audience is therefore the developers of standards and specifications. These guidelines cannot be prescriptive for every standard, since individual standards and specifications may legitimately have very different focuses, but it should be expected that the combination of such standards and specifications used in any implementation should cover these security topics. These guidelines are therefore to be used as a checklist for the combination of standards and specifications used in implementations of systems. Out-of-scope are explicit methods for cyber security in product development, implementations, or operations.
Contents:
- FOREWORD
- INTRODUCTION
- Scope