NB Appendix CIP NB-0 - Cyber Security Personnel & Training

Similar documents
NB Appendix CIP NB-0 - Cyber Security Recovery Plans for BES Cyber Systems

CIP Cyber Security Personnel & Training

CIP Cyber Security Configuration Change Management and Vulnerability Assessments

CIP Cyber Security Personnel & Training

CIP Cyber Security Configuration Change Management and Vulnerability Assessments

CIP Cyber Security Configuration Change Management and Vulnerability Assessments

This draft standard is being posted for an initial comment and ballot. The draft includes modifications to meet the directives of FERC Order No. 791.

This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective.

Standard Development Timeline

CIP Cyber Security Security Management Controls. A. Introduction

CIP Cyber Security Systems Security Management

A. Introduction 1. Title: 2. Number: 3. Purpose: 4. Applicability: 4.1. Functional Entities: Balancing Authority Distribution Provider

CIP Cyber Security Configuration Change Management and Vulnerability Assessments

Standard CIP Cyber Security Critical Cyber As s et Identification

CIP Cyber Security Information Protection

Standard Development Timeline

requirements in a NERC or Regional Reliability Standard.

Summary of FERC Order No. 791

CIP Cyber Security Physical Security of BES Cyber Systems

Standard Development Timeline

1. SAR posted for comment on January 15, Standard Drafting Team appointed on January 29, 2014

Standard CIP Cyber Security Critical Cyber As s et Identification

Cyber Threats? How to Stop?

CIP Cyber Security Electronic Security Perimeter(s)

CIP Cyber Security Security Management Controls

Standard Development Timeline

CIP Cyber Security Physical Security of BES Cyber Systems

Standard CIP 004 3a Cyber Security Personnel and Training

Standard CIP Cyber Security Critical Cyber Asset Identification

Standard CIP Cyber Security Critical Cyber Asset Identification

Additional 45-Day Comment Period September Final Ballot is Conducted October/November Board of Trustees (Board) Adoption November 2014

CIP Cyber Security Physical Security of BES Cyber Systems

CIP Cyber Security Configuration Change Management and Vulnerability AssessmentsManagement

requirements in a NERC or Regional Reliability Standard.

CIP Cyber Security Recovery Plans for BES Cyber Systems

Standard Development Timeline

Standard Development Timeline

1. SAR posted for comment on January 15, Standard Drafting Team appointed on January 29, 2014

CIP Cyber Security Systems Security Management

Standard CIP 007 4a Cyber Security Systems Security Management

Standard Development Timeline

Additional 45-Day Comment Period and Ballot November Final Ballot is Conducted January Board of Trustees (Board) Adoption February 2015

CIP Cyber Security Security Management Controls. Standard Development Timeline

Reliability Standard Audit Worksheet 1

CIP Cyber Security Recovery Plans for BES Cyber Systems

Page 1 of 15. Applicability. Compatibility EACMS PACS. Version 5. Version 3 PCA EAP. ERC NO ERC Low Impact BES. ERC Medium Impact BES

A. Introduction. Page 1 of 22

CIP Cyber Security Recovery Plans for BES Cyber Systems

Purpose. ERO Enterprise-Endorsed Implementation Guidance

CIP Cyber Security Configuration Management and Vulnerability Assessments

1. Post for 45-day comment period and pre-ballot review. 7/26/ Conduct initial ballot. 8/30/2010

Lesson Learned CIP Version 5 Transition Program CIP : Communications and Networking Cyber Assets Version: October 6, 2015

Project Cyber Security - Order No. 791 Identify, Assess, and Correct; Low Impact; Transient Devices; and Communication Networks Directives

Standard CIP 007 3a Cyber Security Systems Security Management

Standard Development Timeline

Standard CIP 005 4a Cyber Security Electronic Security Perimeter(s)

Standard CIP Cyber Security Systems Security Management

CIP Information Protection

Standard CIP Cyber Security Systems Security Management

CIP Cyber Security Incident Reporting and Response Planning

Critical Cyber Asset Identification Security Management Controls

Critical Infrastructure Protection (CIP) Version 5 Revisions. Standard Drafting Team Update Industry Webinar September 19, 2014

Standard Development Timeline

CIP Cyber Security Physical Security of BES Cyber Systems

Standard CIP-006-4c Cyber Security Physical Security

Standard CIP Cyber Security Security Management Controls

Frequently Asked Questions November 25, 2014 CIP Version 5 Standards

Implementation Plan. Project CIP Version 5 Revisions. January 23, 2015

Standard INT Dynamic Transfers

TOP-010-1(i) Real-time Reliability Monitoring and Analysis Capabilities

Implementation Plan. Project CIP Version 5 Revisions 1. January 23, 2015

CYBER SECURITY POLICY REVISION: 12

Consideration of Issues and Directives Federal Energy Regulatory Commission Order No. 791 June 2, 2014

Standard INT Dynamic Transfers

Standard CIP Cyber Security Physical Security

Standard CIP 005 2a Cyber Security Electronic Security Perimeter(s)

Standard CIP-006-3c Cyber Security Physical Security

Consideration of Issues and Directives Federal Energy Regulatory Commission Order No. 791 January 23, 2015

A. Introduction. B. Requirements and Measures

NERC-Led Technical Conferences

Violation Risk Factor and Violation Severity Level Justifications Project Modifications to CIP Standards

Draft CIP Standards Version 5

Title. Critical Infrastructure Protection Getting Low with a Touch of Medium. CanWEA Operations and Maintenance Summit 2018.

Project Retirement of Reliability Standard Requirements

Standard CIP Cyber Security Electronic Security Perimeter(s)

Standard CIP Cyber Security Incident Reporting and Response Planning

DRAFT. Standard 1300 Cyber Security

Violation Risk Factor and Violation Severity Level Justification Project Modifications to CIP-008 Cyber Security Incident Reporting

Lesson Learned CIP Version 5 Transition Program

Standard CIP-006-1a Cyber Security Physical Security

Standard TOP Transmission Operations

2017 MRO Performance Areas and an Update on Inherent Risk Assessments

Standard CIP Cyber Security Electronic Security Perimeter(s)

ERO Enterprise Registration Practice Guide: Distribution Provider directly connected Determinations Version 2: July 5, 2018

Supply Chain Cybersecurity Risk Management Standards. Technical Conference November 10, 2016

Project Physical Security Directives Mapping Document

primary Control Center, for the exchange of Real-time data with its Balancing

New Brunswick 2018 Annual Implementation Plan Version 1

VIA ELECTRONIC FILING

5. Effective Date: The first day of the first calendar quarter after applicable regulatory approval.

Transcription:

This appendix establishes modifications to the FERC approved NERC standard CIP-004-5.1 for its specific application in New Brunswick. This appendix must be read with CIP-004-5.1 to determine a full understanding of the requirements of the standard for New Brunswick. Where the standard and appendix differ, the appendix shall prevail. The term BES Cyber Asset as used in this Appendix or CIP-004-5.1 means BPS Cyber Asset as defined in section G. The term BES Cyber System as used in this Appendix or CIP-004-5.1 means BPS Cyber System as defined in section G. The term BES Cyber System Information as used in this Appendix or CIP-004-5.1 means BPS Cyber System Information as defined in section G. A. Introduction 1. Title: Cyber Security Personnel & Training 2. Number: CIP-004-5.1 3. Purpose: To minimize the risk against compromise that could lead to misoperation or instability in the bulk power system from individuals accessing BES Cyber Systems by requiring an appropriate level of personnel risk assessment, training, and security awareness in support of protecting BES Cyber Systems. 4. Applicability: 4.1. Functional Entities: 4.1.1. 4.1.2. Distribution Provider that owns one or more of the following Facilities, systems, and equipment for the protection or restoration of the bulk power system: 4.1.2.1. 4.1.2.1.1. is part of a Load shedding program that is subject to one or more requirements in a New Brunswick Energy and Utilities Board approved reliability standard or Regional Reliability 1

Standard; and 4.1.2.1.2. 4.1.2.2. Each Special Protection System or Remedial Action Scheme where the Special Protection System or Remedial Action Scheme is subject to one or more requirements in a New Brunswick Energy and Utilities Board approved reliability standard or Regional Reliability Standard. 4.1.2.3. Each Protection System (excluding UFLS and UVLS) that applies to Transmission where the Protection System is subject to one or more requirements in a New Brunswick Energy and Utilities Board approved reliability standard or Regional Reliability Standard. 4.1.2.4. 4.1.3. 4.1.4. 4.1.5. 4.1.6. 4.1.7. 4.1.8. 4.2. Facilities: 4.2.1. Distribution Provider: One or more of the following Facilities, systems and equipment owned by the Distribution Provider for the protection or restoration of the bulk power system: 4.2.1.1. 4.2.1.1.1. is part of a Load shedding program that is subject to one or more requirements in a New Brunswick Energy and Utilities Board approved reliability standard or Regional Reliability Standard; and 4.2.1.1.2. 4.2.1.2. Each Special Protection System or Remedial Action Scheme where the Special Protection System or 2

Remedial Action Scheme is subject to one or more requirements in a New Brunswick Energy and Utilities Board approved reliability standard or Regional Reliability Standard. 4.2.1.3. Each Protection System (excluding UFLS and UVLS) that applies to Transmission where the Protection System is subject to one or more requirements in a New Brunswick Energy and Utilities Board approved reliability standard or Regional Reliability Standard. 4.2.1.4. 4.2.2. Responsible Entities listed in 4.1 other than Distribution Providers: All bulk power system Facilities. 4.2.3. Exemptions: 4.2.3.1. 4.2.3.2. 4.2.3.3. 4.2.3.4. 4.2.3.5. 5. Effective Dates: 1. 2. 6. Background: Many references in the Applicability section use a threshold of 300 MW for UFLS 3

and UVLS. This particular threshold of 300 MW for UVLS and UFLS was provided in Version 1 of the CIP Cyber Security Standards. The threshold remains at 300 MW since it is specifically addressing UVLS and UFLS, which are last ditch efforts to save the bulk power system. A review of UFLS tolerances defined within regional reliability standards for UFLS program requirements to date indicates that the historical value of 300 MW represents an adequate and reasonable threshold value for allowable UFLS operational tolerances. Applicable Systems Columns in Tables: 4

B. Requirements and Measures R1. M1. CIP-004-5.1 Table R1 Security Awareness Program Part Applicable Systems Requirements Measures 1.1 R2. M2. CIP-004-5.1 Table R2 Cyber Security Training Program Part Applicable Systems Requirements Measures 2.1 2.2 2.3 R3. 5

M3. CIP-004-5.1 Table R3 Personnel Risk Assessment Program Part Applicable Systems Requirements Measures 3.1 3.2 3.3 3.4 3.5 R4. M4. 6

CIP-004-5.1 Table R4 Access Management Program Part Applicable Systems Requirements Measures 4.1 4.2 4.3 4.4 R5. M5. 7

CIP-004-5.1 Table R5 Access Revocation Part Applicable Systems Requirements Measures 5.1 5.2 5.3 5.4 5.5 8

C. Compliance 1. Compliance Monitoring Process: 1.1. Compliance Enforcement Authority: The New Brunswick Energy and Utilities Board shall serve as the Compliance Enforcement Authority ( CEA ). 1.2. Evidence Retention: 1.3. Compliance Monitoring and Assessment Processes: 1.4. Additional Compliance Information: 9

2. Table of Compliance Elements R # Time Horizon VRF Violation Severity Levels (CIP-004-5.1) Lower VSL Moderate VSL High VSL Severe VSL R1 R2 R3 R4 R5 D. Regional Variances E. Interpretations F. Associated Documents G. New Brunswick Definitions 10

BPS Cyber Asset: A Cyber Asset that if rendered unavailable, degraded, or misused would, within 15 minutes of its required operation, misoperation, or non-operation, adversely impact one or more Facilities, systems, or equipment, which, if destroyed, degraded, or otherwise rendered unavailable when needed, would affect the reliable operation of the bulk power system. Redundancy of affected Facilities, systems, and equipment shall not be considered when determining adverse impact. Each BPS Cyber Asset is included in one or more BPS Cyber Systems. (A Cyber Asset is not a BPS Cyber Asset if, for 30 consecutive calendar days or less, it is directly connected to a network within an ESP, a Cyber Asset within an ESP, or to a BPS Cyber Asset, and it is used for data transfer, vulnerability assessment, maintenance, or troubleshooting purposes.) BPS Cyber System: One or more BPS Cyber Assets logically grouped by a responsible entity to perform one or more reliability tasks for a functional entity. BPS Cyber Information: Information about the BPS Cyber System that could be used to gain unauthorized access or pose a security threat to the BPS Cyber System. BPS Cyber System Information does not include individual pieces of information that by themselves do not pose a threat or could not be used to allow unauthorized access to BPS Cyber Systems, such as, but not limited to, device names, individual IP addresses without context, ESP names, or policy statements. Examples of BPS Cyber System Information may include, but are not limited to, security procedures or security information about BPS Cyber Systems, Physical Access Control Systems, and Electronic Access Control or Monitoring Systems that is not publicly available and could be used to allow unauthorized access or unauthorized distribution; collections of network addresses; and network topology of the BPS Cyber System. 11

Guidelines and Technical Basis NB Appendix Guidelines and Technical Basis Section 4 Scope of Applicability of the CIP Cyber Security Standards Section 4.1. Functional Entities is a list of functional entities to which the standard applies. If the entity is registered as one or more of the functional entities listed in Section 4.1, then the CIP Cyber Security Standards apply. Note that there is a qualification in Section 4.1 that restricts the applicability in the case of Distribution Providers to only those that own certain types of systems and equipment listed in 4.2. Furthermore, Requirement R1: Requirement R2: Requirement R3: Each Responsible Entity shall ensure a personnel risk assessment is performed for all personnel who are granted authorized electronic access and/or authorized unescorted physical access to its BES Cyber Systems, including contractors and service vendors, prior to their being granted authorized access, except for program specified exceptional circumstances that are approved by the single senior management official or their delegate and impact the reliability of the bulk power system or emergency response. Identity should be confirmed in accordance with federal, state, provincial, and local laws, and subject to existing collective bargaining unit agreements. Identity only needs to be confirmed prior to initially granting access and only requires periodic confirmation according to the entity s process during the tenure of employment, which may or may not be the same as the initial verification action. Requirement R4: Requirement R5: Scenario Possible Process 12

Guidelines and Technical Basis Requirement 5.5 specified that passwords for shared account are to the changed within 30 calendar days of the termination action or when the Responsible Entity determines an individual no longer requires access to the account as a result of a reassignment or transfer. The 30 days applies under normal operating conditions. However, circumstances may occur where this is not possible. Some systems may require an outage or reboot of the system in order to complete the password change. In periods of extreme heat or cold, many Responsible Entities may prohibit system outages and reboots in order to maintain reliability of the bulk power system. When these circumstances occur, the Responsible Entity must document these circumstances and prepare to change the password within 10 calendar days following the end of the operating circumstances. Records of activities must be retained to show that the Responsible Entity followed the plan they created. Rationale: Rationale for R1: Rationale for R2: Rationale for R3: Rationale for R4: Rationale for R5: 13

Guidelines and Technical Basis Version History Version NBEUB Approval Date NB Appendix Effective Date Change Tracking Comments 0 mm/dd/yy mm/dd/yy 14