Computer Security and SCADA Requirements (Chapter 9)
A module-by-module review of Chapter 9 of the FERC Security Program for Hydropower Projects — covering who must comply, the two-step applicability process, cyber asset classification tiers, baseline and enhanced security measures, and how Chapter 9 is reviewed during Dam Safety Inspections.
Module 1: Introduction — Who Must Follow Section 9.0
Section 9.1 establishes why FERC regulates cyber and SCADA security for hydropower, what consequences drive the requirements, and which facilities are subject to them.
- Section 9.0 (Computer Security and SCADA) was thoroughly revised for Revision 3 and became effective January 1, 2016.
- FERC's focus for cyber security at hydropower is limited to two critical consequences: (1) the unintentional release of all or part of the reservoir, and (2) the non-operation of a licensed facility (loss of significant power generation).
- Because of this narrow scope, not all licensees are required to follow Section 9.0 — applicability depends on whether the facility uses remote or automated control of critical functions.
- A flowchart process (Figure 9.1 in the guidance) determines cyber asset criticality and whether Section 9.0 applies. Facilities whose cyber assets are determined to be "non-critical" do not need to adhere to Section 9.0, though voluntary conformance strengthens business continuity.
- All Security Group 1 and Group 2 dams must complete the FERC Hydro Cyber/SCADA Security Checklist (Form 3), Questions 1–4, to determine cyber asset designation, and discuss results with the FERC project engineer at the next Operation Inspection.
- Security Group 3 dams are subject to Section 9.0 only if they are interconnected to the operational or critical cyber assets of a Group 1 or Group 2 dam.
- Even if a facility is determined to be non-critical, FERC encourages voluntary compliance as a best practice for strengthening operational resilience.
Module 2: Step 1 — Remote Operation Determination (§9.1.1.1)
The first step in determining whether Section 9.0 applies is answering four questions about the facility's use of remote or automated control systems. Any "Yes" answer requires proceeding to the Consequence Determination step.
- Every Group 1 and 2 dam must answer the four Remote Operation Determination questions on Form 3 (Questions 1–4) before the next Dam Safety Inspection.
- A "Yes" answer to any of these four questions means the licensee must proceed to the Cyber/SCADA Consequence Determination (Section 9.1.1.2) to assess whether the facility's consequences exceed the criticality thresholds.
- Question 4 includes a key note: if a virtual (system) interconnection exists to another facility already subject to Section 9.0, that interconnected facility is also automatically included in Section 9.0 requirements.
- If all four answers are "No," the facility's cyber assets are likely non-critical and Section 9.0 does not apply — though this must be re-evaluated annually as systems change.
| Form 3 Q# | Remote Operation Determination Question |
|---|---|
| 1 | Does the facility/project utilize automated or remote (off-site) control of data acquisition, such as critical instrumentation or operation data? |
| 2 | Does the facility/project utilize automated or remote control of power generation data or power generation controls? |
| 3 | Does the facility/project utilize automated or remote control of water management data or direct control of water retention features? |
| 4 | Is there an interconnection of computer systems from/to this facility/project to other dam(s)? |
Module 3: Step 2 — Consequence Determination and Asset Classification (§9.1.1.2–9.1.1.3)
If any Remote Operation question is answered "Yes," the licensee must evaluate the potential consequences of losing that capability. Consequence thresholds determine whether cyber assets are Critical, Operational, or Non-Critical — and therefore which security measures apply.
- The consequence evaluation considers both unintentional misoperation and intentional attack scenarios (insider and external).
- For gate-loss scenarios, the analysis must assume all gates are fully open with no remediation response for 48 hours.
- For dam failure potential, consider whether cascading operational losses could cause the dam to fail — referencing the 2009 Sayano-Shushenskaya accident as an example of cascading failure.
- Consequences should correlate with DAMSVR (or similar methodology) results to ensure consistency across the security program.
- Generating capacity thresholds determine criticality tier: ≥ 1,500 MW connected to one cyber asset = Critical; 100–1,499 MW = Operational; < 100 MW = Non-Critical. Black-start capable units are Operational regardless of capacity.
- Interconnected Group 3 dams must meet the same protection level (baseline or baseline + enhanced) as the Group 1 or 2 dam's cyber asset criticality.
| Consequence Scenario | Critical Threshold | Asset Tier if Exceeded |
|---|---|---|
| Population at Risk (PAR) within 3 miles of dam | > 60 people | Critical |
| Population at Risk (PAR) within 60 miles of dam | > 800 people | Critical |
| Total PAR from reservoir release scenario | > 12,500 people | Critical |
| Total economic losses (replacement/revenue + downstream damages) | > $300 Million | Critical |
| Disruption of essential services (power, navigation, water) | > Municipal-wide disruption | Critical or Operational (see capacity thresholds) |
| Installed generating capacity per cyber asset | ≥ 1,500 MW | Critical |
| Installed generating capacity per cyber asset | 100 MW – 1,499 MW | Operational |
| Installed generating capacity per cyber asset | < 100 MW | Non-Critical |
| Black-start capability | Any generating capacity | Operational (minimum) |
Module 4: Cyber Asset Definitions and Inventory Requirements (§9.1.1.4 & §9.2)
Section 9.0 uses specific definitions for cyber assets and control systems. After classification, licensees must maintain a current inventory of all cyber assets organized by criticality tier.
- System — Interconnected hardware and software components (computers, databases, applications, monitoring devices) that together perform a related set of functions.
- Control Systems — Refers to Supervisory Control and Data Acquisition (SCADA) systems, Process Control Systems (PCS), and Distributed Control Systems (DCS). For FERC purposes, SCADA also includes remote operation of water retention features such as spillway gates and penstocks.
- SCADA System — A specialized computer system that gathers real-time data on hydroelectric generation and water management, transfers it to a central location, alerts operators to abnormal conditions, and executes necessary analysis and control actions.
- Cyber Asset — An individual computerized system that performs operational tasks at hydroelectric and water management facilities.
- Critical Cyber Asset — Essential to the safety and/or objectives of the project and exceeds the consequence thresholds in Table 9.1c.
- Operational Cyber Asset — Essential to the safety and/or objectives of the project but does not exceed the critical consequence thresholds.
- Non-Critical Cyber Asset — Isolated from remote monitoring and controls; does not meet the criteria for critical or operational classification.
- After classification, licensees must develop and maintain an accurate inventory of all cyber assets and cyber systems. When it is more convenient to classify assets as a group, they may be classified as a "cyber system."
- Legacy components with few or no security features must have compensating controls applied as part of an overall defense-in-depth approach.
Module 5: Baseline Cyber Security Measures — Table 9.3a
Baseline measures apply to all cyber assets or cyber systems subject to Section 9.0, regardless of whether assets are classified as Operational or Critical. These measures are organized below by the categories used in Form 3 (Questions 18a–18g).
| Category | Baseline Measure Required | Key NIST Reference |
|---|---|---|
| General | Provide physical security and access controls to cyber assets. | NIST SP 800-82 §6.2.1 |
| General | Monitor and periodically review (not to exceed 18 months) all network connections, including remote and third-party connections. | — |
| General | Evaluate and reassess the risk of wireless networking before implementation. | NIST SP 800-153 |
| General | Review and reassess all cyber security procedures annually; update as necessary. | — |
| General | Review and reassess cyber asset criticality at least every 12 months, and when any new cyber asset is added. | — |
| Coordination & Responsibilities | Develop a cross-functional cyber security team with an operational framework ensuring coordination and accountability across control systems and enterprise networks. | NIST SP 800-82 §4.2 |
| Coordination & Responsibilities | Define cyber security roles, responsibilities, and lines of communication among operations, IT, and business groups, including outsourcers and third-party contractors. | — |
| System Lifecycle | Establish and document cyber security standards for acquisitions; encourage vendors to use secure software development practices. | NIST SP 800-82 §6.2.15; 800-23; 800-36; 800-64 |
| System Lifecycle | Incorporate security into cyber system design and operation for all new and modified systems; mitigate known hardware/software deficiencies. | NIST SP 800-27; 800-64; 800-70 |
| System Lifecycle | Establish and document policies for system configuration management, change tracking, and patch/upgrade management for control system networks. | NIST SP 800-40 |
| System Lifecycle | Establish and document policies for secure disposal of equipment and associated media. | NIST SP 800-82 §6.2.10; 800-88 |
| Restoration & Recovery | Plan and prepare for timely restoration and recovery of control systems in accordance with the facility's recovery procedures. | NIST SP 800-82 §5.13, §6.2.6; 800-34; 800-100 |
| Restoration & Recovery | Review and test the restoration and recovery plan for control systems annually. | — |
| Intrusion Detection & Response | Establish policies and procedures for cyber intrusion monitoring, detection, incident handling, and reporting. | NIST SP 800-61; 800-82 §5.1, §5.16; 800-83; 800-94 |
| Training | Provide annual information security awareness training for all control system users before granting access. Personnel with significant cyber security roles must receive advanced role-specific training. | NIST SP 800-16; 800-82 §6.2.2; 800-50 |
| Access Control & Functional Segregation | Segregate and protect the control systems network from the business network and Internet using firewalls and other protections — for both wired and wireless networks. | NIST SP 800-82 §5.2, 5.3, 5.5, 5.6 |
| Access Control & Functional Segregation | Use control system servers and desktop computers only for approved control system activities. | — |
| Access Control & Functional Segregation | Establish and enforce access control policies for local users, remote users, guests, and customers. Maintain procedures for approving and controlling remote and third-party connections to control networks. | NIST SP 800-82 §6.2.1, §6.2.7 |
Module 6: Enhanced Measures, FERC Inspection, and NERC-CIP Coordination (§9.3b & §9.4)
Critical cyber assets require enhanced measures beyond the baseline. This module also covers how Section 9.0 is reviewed during FERC Dam Safety Inspections and how NERC-CIP compliance relates to FERC's requirements.
Enhanced Cyber Security Measures — Table 9.3b (Critical Assets Only)
- Restrict physical and logical access to control systems and networks through a combination of locked facilities, passwords, secured communication gateways, access control lists, authenticators, separation of duties, and least-privilege practices. (NIST SP 800-82 §6.2.1, §6.2.16)
- Conduct a formal risk assessment to weigh the benefits of wireless networking against exploitation risks; evaluate the need for enhanced networking controls before any wireless implementation. (NIST SP 800-115 §6; 800-82 §3)
- Conduct periodic vulnerability assessments of control system security — including assessments in non-production environments — not to exceed 12 months between assessments. (NIST SP 800-40; 800-82 §6.2.14; 800-115)
FERC Dam Security Inspection — Cyber/SCADA Review (§9.4)
- Form 3 (FERC Hydro Cyber/SCADA Security Checklist) must be completed by the licensee before the Operation/Security Inspection and reviewed with the FERC Engineer during the inspection.
- FERC D2SI's scope is limited to ICS/SCADA assets involved in dam operation and remote project control. It does not extend into the corporate business network unless inadequate access controls allow the business network to influence operations.
- Inspection discussions are focused on remote operations that could impact water retention structures (dam, spillway gates, penstocks) and power generation — not on electric reliability or grid-level assets.
- Licensees must demonstrate that cyber security plans and measures are in place, and that proper coordination has been established with the FBI. The FBI maintains an incident database and coordinates technical protection for cyber-controlled systems.
- Cyber systems must be updated consistent with current security best practices and, where applicable, with NERC-CIP requirements.
NERC-CIP Coordination
- NERC-CIP standards (enforced by the FERC Office of Electric Reliability) focus on reliability of the Bulk Electric System — not on downstream population impacts from dam misoperation.
- A specific cyber asset may fall under both FERC D2SI and NERC-CIP jurisdiction. In this case, meeting NERC-CIP requirements satisfies D2SI's criteria for that asset.
- The CIP standards being met for any dual-jurisdiction asset must be referenced in the Security Plan and discussed with the FERC project engineer during the Dam Safety Inspection.
- If a NERC-CIP compliance inspection has been performed, the results, identified deficiencies, and corrective actions must be available for review during the Dam Safety Inspection to confirm Section 9.0 compliance and prevent duplication of effort.