SEL-3045 Security Policy Schweitzer Engineering Laboratories, Inc. Version: 0.14 Copyright 2009-2010 Schweitzer Engineering Laboratories, Inc. May be reproduced only in its original entirety [without revision]. SEL-3045 Security Policy Contents  1  Definitions and Acronyms ............................................................................................................................... 4  2  References ....................................................................................................................................................... 4  3  Module Overview ............................................................................................................................................ 4  3.1  SSCP ............................................................................................................................................................................. 6  3.2  SEAP............................................................................................................................................................................. 6  3.3  Security Level ............................................................................................................................................................... 6  4  Modes of Operation ........................................................................................................................................ 7  4.1  FIPS Approved Mode of Operation .............................................................................................................................. 7  4.2  Approved and Allowed Algorithms .............................................................................................................................. 7  5  Ports and Interfaces ........................................................................................................................................ 8  5.1  Physical Ports .............................................................................................................................................................. 8  5.2  Logical Ports ................................................................................................................................................................ 9  6  Identification and Authentication Policy ....................................................................................................... 12  6.1  Assumption of Roles .................................................................................................................................................. 12  7  Access Control Policy ..................................................................................................................................... 14  7.1  Roles and Services ..................................................................................................................................................... 14  7.2  Definition of Critical Security Parameters (CSPs) ....................................................................................................... 15  7.3  Definition of Public Keys ............................................................................................................................................ 16  7.4  Definition of CSPs Modes of Access ........................................................................................................................... 16  8  Operational Environment .............................................................................................................................. 18  9  Security Rules ................................................................................................................................................ 18  10  Physical Security Policy .................................................................................................................................. 20  10.1  Physical Security Mechanisms .............................................................................................................................. 20  10.2  Operator Required Actions ................................................................................................................................... 20  11  Mitigation of Other Attacks Policy ................................................................................................................ 20    SEL-3045 Security Policy Page 2 of 20 SEL-3045 Security Policy Tables  Table 1: Module Security Level Specification........................................................................................................... 6  Table 2: FIPS Approved Algorithms Used in Current Module .................................................................................. 7  Table 3: FIPS Allowed Algorithms Used in Current Module ..................................................................................... 7  Table 4: Non‐Callable Functions Present in Current Module .................................................................................. 8  Table 5: Physical Ports  ............................................................................................................................................. 9  . Table 6: Logical Ports ............................................................................................................................................... 9  Table 7: Dorado Pins and FIPS 140‐2 Ports and Interfaces .................................................................................... 10  Table 8: Roles ......................................................................................................................................................... 12  Table 9: Identity Authentication Mechanism ........................................................................................................ 12  Table 10: Roles and Service Matrix ........................................................................................................................ 14  Table 11: CSPs ........................................................................................................................................................ 15  Table 12: Public Keys .............................................................................................................................................. 16  Table 13: CSP Access Rights within Roles & Services ............................................................................................. 16  Figures  Figure 1: Image of the Cryptographic Module ......................................................................................................... 5  Figure 2: Point to Point Network ............................................................................................................................. 5  Figure 3: Point to Multipoint Network ..................................................................................................................... 5  Figure 4: Module Block Diagram .............................................................................................................................. 9  SEL-3045 Security Policy Page 3 of 20 SEL-3045 Security Policy 1 Definitions and Acronyms ABI – Asynchronous Bus Interface SCADA – Supervisory Control And Data Acquisition SEAP – SEL Encryption and Authentication Protocol SSCP – Secure SCADA Communication Protocol USB – Universal Serial Bus 2 References “Secure SCADA Communication Protocol Specification” 3 Module Overview The Schweitzer Engineering Laboratories, Inc. SEL-3045 (hereafter referred to as the module) is a multi-chip standalone cryptographic module encased in a hard, opaque, tamper evident PCMCIA style case. The cryptographic boundary is the entire module. No components are excluded from the cryptographic boundary. The module is a cryptographic protocol daughter card designed to reside in a host device to secure its data on a particular communication network. The SEL-3045 implements the SSCP specification to protect the data in transit. The SEL-3045 is designed to protect devices that send and receive critical, sensitive data such as electric power revenue meters, protective relays, Programming Logic Controllers (PLC), Remote Terminal Units (RTU), and SCADA equipment from unauthorized access, control, monitoring, and malicious attack. The module provides a plaintext port to connect to a device that requires data protection (e.g. the SCADA unit, RTU, or a computer). The cryptotext port connects to a distrusted channel (e.g. a modem connected to a leased phone line or network connection device) where it can communicate with a remote module to provide a secure channel over an insecure network. The configuration of hardware and firmware for this validation is: Hardware: v1.0 Firmware: R100 SEL-3045 Security Policy Page 4 of 20 SEL-3045 Security Policy Figure 1: Image of the Cryptographic Module Modem SEL-3045 Remote Modem Client SEL-3045 Local Figure 2: Point to Point Network SEL-3045 Remote SEL-3045 Remote Distrusted Network SEL-3045 Remote Client SEL-3045 Local Figure 3: Point to Multipoint Network SEL-3045 Security Policy Page 5 of 20 SEL-3045 Security Policy 3.1 SSCP The Secure SCADA Communications Protocol (SSCP) secures serial control system communication through the use of symmetric key cryptography. The module uses SSCP to communicate with remote modules. The SSCP secures control system network communications by encapsulating the original message within a header and authenticator. In order to ensure perfect forward secrecy, each pair of communicating devices utilizes a secured Diffie-Hellman key agreement method to establish a session and generate ample cryptographic key material for session authentication and encryption keys. During the session negotiation, a static encryption key is used to secure portions of the Diffie-Hellman key agreement and an authentication key is used to authenticate remote modules. The Diffie-Hellman key agreement establishes two symmetric authentication session keys which are used to provide message authenticity of network data. An additional set of symmetric encryption keys can be used for optional network data encryption. The cryptographic authentication key of the message recipient is used to create an un-transmitted nonce that provides a unique value for each packet. The cryptographic authentication key of the message originator is used by a secure hash algorithm to calculate a hashed message authentication code based upon the header, nonce, and original message. 3.2 SEAP The SEAP protocol secures the operator communication channel with strong message encryption and authentication. SEAP allows operators to securely log into the module to input configuration items (e.g. CSPs) and view status. Each operator has a static AES encryption key, HMAC authentication key, user name, and password. These parameters uniquely identify each operator. The encryption key provides confidentiality during the session negotiation process. The authentication key provides authentication during the session negotiation process. During the session negotiation process, the user name and password are securely provided to the module to authenticate the operator and assign appropriate access privileges. Session encryption and authentication keys are transported by the module and are used to provide confidentiality and authenticity of each frame for the remainder of the session. These keys are transported encrypted using AES CBC and the operator’s AES encryption key. 3.3 Security Level The cryptographic module meets the overall requirements applicable to Level 2 security of FIPS 140-2. Table 1: Module Security Level Specification Security Requirements Section Level Cryptographic Module Specification 3 Module Ports and Interfaces 2 Roles, Services and Authentication 3 Finite State Model 2 Physical Security 2 Operational Environment N/A Cryptographic Key Management 2 SEL-3045 Security Policy Page 6 of 20 SEL-3045 Security Policy EMI/EMC 3 Self-Tests 2 Design Assurance 3 Mitigation of Other Attacks N/A 4 Modes of Operation 4.1 FIPS Approved Mode of Operation The module only provides a FIPS Approved mode of operation, comprising all services described in this document. The module will enter FIPS Approved mode following successful power up initialization. The view status command can be used by an operator to verify that the firmware version number matches the FIPS Approved firmware version listed in this document. The operator may inspect the module label to verify the hardware version matches the FIPS Approved hardware version listed in this document. 4.2 Approved and Allowed Algorithms The cryptographic module supports the following FIPS Approved algorithms. Table 2: FIPS Approved Algorithms Used in Current Module FIPS Approved Algorithm Validation Number AES 1272 Modes: ECB, CBC, CTR (Key Sizes: 128/256 bits) SHS 1170 Modes: SHA-1, SHA-256 DSA 412 Modes: Signature Verification (Mod 1024, SHA-1) RNG 710 Modes: FIPS 186-2 General Purpose ( x-Original, SHA-1) HMAC 739 Modes: SHA1, SHA-256 (Key Sizes: KS