Engineering Papers⌕ Search

Engineering topics

Hadley, Mark D.

Publications and source records attributed to Hadley, Mark D..

Software-defined Networking for Energy Delivery Systems (SDN4EDS): An Architectural Blueprint (Final Report)

This is the initial version of a reference for suppliers and energy companies of all sizes to deploy networks based on software-defined networking technology (SDN) to improve reliability, reduce cyber security attack surface, and facilitate mitigation of adversarial behavior. It is a living document and will progress over the life cycle of the Software-Defined Networking for Energy Delivery Systems (SDN4EDS) project. Version 2 of this report provides information on the Red Team tabletop assessment performed against the initial reference architecture. Version 3 of this report updates the reference architecture with lessons learned from the Red Team tabletop assessment, as well as provides additional details for the use cases. It also provides information on the decision process that could be used by an organization when considering deploying SDN in their environment. The final version of this report consolidates all the interim reports generated by the project into a final report. It also draws from PNNL’s experience in deploying SDN to make recommendations on how SDN could be deployed in a utility environment, and provides rationale for those decisions allowing individual utilities to make risk-based and knowledge-based decisions on how to best deploy SDN in their own environment

97 MATHEMATICS AND COMPUTING↗

Software-defined Networking for Energy Delivery Systems (SDN4EDS): An Architectural Blueprint (Final Summary Report)

This is the initial version of a reference for suppliers and energy companies of all sizes to deploy networks based on software-defined networking technology (SDN) to improve reliability, reduce cyber security attack surface, and facilitate mitigation of adversarial behavior. It is a living document and will progress over the life cycle of the Software-Defined Networking for Energy Delivery Systems (SDN4EDS) project. Version 2 of this report provides information on the Red Team tabletop assessment performed against the initial reference architecture. Version 3 of this report updates the reference architecture with lessons learned from the Red Team tabletop assessment, as well as provides additional details for the use cases. It also provides information on the decision process that could be used by an organization when considering deploying SDN in their environment. The final version of this report consolidates all the interim reports generated by the project into a final report. It also draws from PNNL’s experience in deploying SDN to make recommendations on how SDN could be deployed in a utility environment, and provides rationale for those decisions allowing individual utilities to make risk-based and knowledge-based decisions on how to best deploy SDN in their own environment. This summary report provides a higher-level overview of the project reports. Readers interested in additional detail, including results of the Red Team assessments and the final configuration, are encouraged to read the full final report.

97 MATHEMATICS AND COMPUTING↗

Deploying Software-Defined Networking in Operational Technology Environments

Software Defined Networking for Operational Technologies, referred to as OT-SDN, is a leading technology to secure critical infrastructure and command and control (C2) systems. As the name implies, OT-SDN networks are programmable, which allows system owners to utilize the characteristics of their physical process to inform the security of their network. There are best practices for deploying OT-SDN into an environment, whether it is all at once or over time (hybrid) that the network is converted to SDN technologies. Through the development of data mining tools and standardized process control, OT-SDN can be deployed reliably. These tools will minimize or eliminate any communication failures during the transition and provide the network owner with complete documentation of their environment. This documentation could enable or facilitate the network owner to pass any audits or policy checks (Authority to Operate) before being allowed to utilize the OT-SDN infrastructure.

Software Defined Networking, Operational Technolog↗

Software-Defined Networking Traffic Engineering Process for Operational Technology Networks

Network design goals are often functional with little consideration for security. Growth and maintenance of critical infrastructure mission-focused networks can be ad hoc and preclude large-scale technology replacements, reconfigurations, or even patching. These restrictions are contributing factors to increased vulnerabilities. Over 90% of all attacks begin with phishing and include lateral movement (Frinke 2019). Adopting a software-defined networking (SDN) approach is an effective mitigation strategy for many existing vulnerabilities. SDNs deny-by-default approach to networking restricts an adversary’s freedom of movement without impacting an organization’s mission. SDN implementations require a process that identifies an organization’s mission-specific network communications. A well-defined traffic engineering process ensures that only known devices communicate with each other on specific ports.

Software Defined Networking, Situational Awareness↗

Enabling Situational Awareness in Operational Technology Environments through Software Defined Networking

Network situational awareness has long been associated with the task of aggregating system logs to determine activity and events ongoing in the network. This current method of obtaining situational awareness however does not clearly address the mission of a facility or organization, the key customers at stake, and the real-time statuses of the critical infrastructures. Software-defined networking provides the capability of allowing the collection of system information of deployed network elements and enabling a global view of the network topology, with near-real-time knowledge of network activities, allowing for key points of the network to be identified and secured appropriately. KEYWORDS: Software Defined Networking, Situational Awareness, Network Security, Cyber Security, Operational Technology

Chang, Laurence H.↗

Utility Assessment Report for SPIDERS Phase 2: Ft. Carson (Rev 1.0)

This document contains the Utility Assessment Report (UAR) for the Phase 2 operational Demonstration (OD) of the Smart Power Infrastructure Demonstration for Energy Reliability and Security (SPIDERS) Joint Capability Technology Demonstration (JCTD). The UAR for Phase 2 shows that the SPIDERS system was able to meet the requirements of the Implementation Directive at Ft. Carson.

97 MATHEMATICS AND COMPUTING↗

Integrated Assessment Plan Template and Operational Demonstration for SPIDERS Phase 2: Fort Carson

This document contains the Integrated Assessment Plan (IAP) for the Phase 2 Operational Demonstration (OD) of the Smart Power Infrastructure Demonstration for Energy Reliability (SPIDERS) Joint Capability Technology Demonstration (JCTD) project. SPIDERS will be conducted over a three year period with Phase 2 being conducted at Fort Carson, Colorado. This document includes the Operational Demonstration Execution Plan (ODEP) and the Operational Assessment Execution Plan (OAEP), as approved by the Operational Manager (OM) and the Integrated Management Team (IMT). The ODEP describes the process by which the OD is conducted and the OAEP describes the process by which the data collected from the OD is processed. The execution of the OD, in accordance with the ODEP and the subsequent execution of the OAEP, will generate the necessary data for the Quick Look Report (QLR) and the Utility Assessment Report (UAR). These reports will assess the ability of the SPIDERS JCTD to meet the four critical requirements listed in the Implementation Directive (ID).

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

AMI Communication Requirements to Implement Demand-Response: Applicability of Hybrid Spread Spectrum Wireless

While holistically defining the smart grid is a challenge, one area of interest is demand-response. In 2009, the Department of Energy announced over $\$$4 billion in grant and project funding for the Smart Grid. A significant amount of this funding was allotted to utilities for cost sharing projects to deploy Smart Grid technologies, many of whom have deployed and are deploying advanced metering infrastructure (AMI). AMI is an enabler to increase the efficiency of utilities and the bulk power grid. The bulk electrical system is unique in that it produces electricity as it is consumed. Most other industries have a delay between generation and consumption. This aspect of the power grid means that there must be enough generation capacity to meet the highest demand whereas other industries could over produce during off-peak times. This requires significant investment in generation capacity to cover the few days a year of peak consumption. Since bulk electrical storage doesn't yet exist at scale another way to curb the need for new peak period generation is through demand-response; that is to incentivize consumers (demand) to curtail (respond) electrical usage during peak periods. Of the various methods proposed for enabling demand-response, this paper will focus on the communication requirements for creating an energy market using transactional controls. More specifically, the paper will focus on the communication requirements needed to send the peak period notices and receive the response back from the consumers.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Comparison of Routable Control System Security Approaches

This document is an supplement to the 'Secure and Efficient Routable Control Systems.' It addressed security in routable control system communication. The control system environment that monitors and manages the power grid historically has utilized serial communication mechanisms. Leased-line serial communication environments operating at 1200 to 9600 baud rates are common. However, recent trends show that communication media such as fiber, optical carrier 3 (OC-3) speeds, mesh-based high-speed wireless, and the Internet are becoming the media of choice. In addition, a dichotomy has developed between the electrical transmission and distribution environments, with more modern communication infrastructures deployed by transmission utilities. The preceding diagram represents a typical control system. The Communication Links cloud supports all of the communication mechanisms a utility might deploy between the control center and devices in the field. Current methodologies used for security implementations are primarily led by single vendors or standards bodies. However, these entities tend to focus on individual protocols. The result is an environment that contains a mixture of security solutions that may only address some communication protocols at an increasing operational burden for the utility. A single approach is needed that meets operational requirements, is simple to operate, and provides the necessary level of security for all control system communication. The solution should be application independent (e.g., Distributed Network Protocol/Internet Protocol [DNP/IP], International Electrotechnical Commission [IEC] C37.118, Object Linking and Embedding for Process Control [OPC], etc.) and focus on the transport layer. In an ideal setting, a well-designed suite of standards for control system communication will be used for vendor implementation and compliance testing. An expected outcome of this effort is an international standard.

99 GENERAL AND MISCELLANEOUS↗