<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Cyber Security strategies for the protection of Electrical Substations</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Roberto</forename><surname>Setola</surname></persName>
							<affiliation key="aff0">
								<orgName type="laboratory">Complex System &amp; Security Lab</orgName>
								<orgName type="institution">University Campus Bio-Medico of Rome</orgName>
								<address>
									<settlement>Rome</settlement>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Francesco</forename><surname>Morelli</surname></persName>
							<affiliation key="aff1">
								<orgName type="institution">ISACA Certified Information Security Manager (CISM)</orgName>
								<address>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Cyber Security strategies for the protection of Electrical Substations</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">DEA44217AEEAD362CF92D66523F01046</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-19T15:50+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Cyber-security</term>
					<term>Operational Technology</term>
					<term>Cyber-Threat, Electric infrastructure, critical infrastructures</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>The shift to widely distributed forms of energy generation and storage, requiring increased interconnectivity to geographically balance supply with distributed demand for electricity, creates a more complex electrical network. This complex network is generally labelled as the 'Internet of Energy' to stress the relevance that the digital components acquired in the electrical grid. But this introduces in the national electrical system new vulnerabilities related to the cyber risk. This paper illustrates the optimal approach that a TSO (Transmission System Operator) can adopt to manage such a risk in the electrical substations. Such an approach is based on the Zero Trust paradigm and is composed of technological, procedural and cultural elements in order to adequately manage cyber security issue all along the life cycle of any component..</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Introduction</head><p>The shift to widely distributed forms of energy generation and storage, requiring increased interconnectivity to geographically balance supply with distributed demand for electricity, creates a more complex electrical network. This complex network is generally labelled as the 'Internet of Energy' to stress the relevance that the digital components acquired in the electric grid. But this introduces in the electric grid new vulnerabilities related to the cyber risk. As noted by the World Energy Council <ref type="bibr" target="#b0">[1]</ref> the resilience of the energy sector is greatly increased by digitalization as it enables the use of a complex and widening array of decentralized resources, improved efficiency, and enhanced abilities to detect threats, thereby increasing operational accessibility, productivity, sustainability, and safety. Unfortunately, at the same time, digitalization presents new challenges because a cyber events can affect operations producing severe degradation or even induce black-out.</p><p>The World Energy Council stressed that there are five factors that increase the vulnerability of the internet of energy, and specifically:</p><p>1) The rapid pace of innovation;</p><p>2) Technological complexity;</p><p>3) Data sharing and interconnectivity; 4) Rising cyberattack sophistication; and, The sector's attractiveness as a cyber target. In this paper we focalize specifically on the last two points due to their increased relevance because a wide range of malicious external actors target power grids motivated by financial goals, such as ITASEC <ref type="bibr">'22:</ref> Italian Conference on Cybersecurity, <ref type="bibr">June 20-23, 2022</ref>, Rome, Italy EMAIL: r.setola@unicampus.it ORCID: 0000-0002-8792-2520 (A. 1); 0000-0001-7798-2936 (A. 2); ransomware or intellectual property theft, or sometimes they aim to cause broader economic and social harm. In addition, like all organizations, energy companies can be collateral damage from an attack not directed at a specific company, such as fast-spreading malware like NotPetya attacks in 2017 and recently emphasized also by the Italian government CSIRT <ref type="bibr" target="#b1">[2]</ref> in the framework of the consequences of the Russia-Ukraine war.</p><p>This fragility depends also by recent business-driven trends such as the standardization of protocols, the employment of off-the-shelves solutions and the augmented connectivity which significantly increased the vulnerable surface of industrial processes making them susceptible to be compromised via cyber-space as illustrated by the Aurora Project <ref type="bibr" target="#b2">[3]</ref>.</p><p>Episodes like Blackenergy 3 and CrashOverride which induced in 2015 and 2016 black-out in Ukraine <ref type="bibr" target="#b3">[4,</ref><ref type="bibr" target="#b4">5]</ref> have shown that attacks of this fashion are possible but require the work of highly skilled and resourceful hackers. Even if impact of cyber-attacks remained far below the threshold of catastrophic events, cyber threat remains a crucial factor that jeopardizes the electric grid security.</p><p>However, they showed that targeting OT via cyber-space can lead to mechanical damage and that cyber-attacks involving kinetic consequences have become 'possible, available, significant and liable to disrupt the functioning of developed societies' <ref type="bibr" target="#b5">[6]</ref>.</p><p>The episode happened at Colonia Pipeline in 2022 showed that in the absence of an effective segregation between IT and OT system, malware can propagate also to operational system inducing also the showdown of the system. This article will provide an overview of the approach that a TSO should adopt to improve the cyber resilience of a national High Voltage electrical grid.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">National transmission grids</head><p>Electricity is not a storable commodity. It is therefore necessary to produce in each time instant the required quantity and distribute it through the system in such a way as to ensure that the demand and supply of electricity are always balanced, thus guaranteeing the continuity of service provision. This is a very complex task because electricity production and consumption are geographically located in different areas of the country, the consumption profile of users can only be partially estimated in advance, production (especially from renewable sources) may depend to a large extent on (unpredictable) weather conditions, and finally the state of the electricity grid must be taken into account to avoid overload conditions and to manage out-of-service events.</p><p>The management of electricity flows is known as dispatching and this activity is carried out by national Transmission System Operators (TSOs). These companies, which generally operate as national monopoly operators, manage the national transmission networks, i.e. those portions of the electricity grid that operate at high (36 kV -150 kV) and extra-high voltage (220 kV -380 kV) and are used to transfer significant amounts of electricity from generation plants and acquisition points from abroad to make it available to large users (generally connected to the medium-voltage network known as the distribution network to which domestic users are in turn connected on low-voltage networks). To this end, TSOs must constantly monitor electricity flows in order to ensure the instantaneous balance between available and used electricity at every point in the network. To do this, they have both the possibility of requesting a modulation in production capacity (limited to those power plants capable of dynamically modifying their production profile, such as hydroelectric and thermal power plants) or the disconnection of interruptible users, but above all to dynamically direct the flow of electric power in a manner consistent with instantaneous demand.</p><p>In Europe, all transmission grids are galvanically interconnected in order to ensure greater stability of the electric system and more effective management of electric power. This implies, however, that the actions taken by individual TSOs can have repercussions at the level of the European electricity system, with the consequence that any inappropriate actions can create even more or less extensive blackout events in other nations, as occurred in 2003 and 2006, hence TSOs have to cooperate exchanging information on electric status. To manage the power grid in the best possible way TSOs have equipped themselves with high-tech control systems, known as National Control Centers (NCCs). These centers represent the technological heart of the power grid overseeing all its operation and managing any anomality and critical situations. Specifically, NCCs, in addition to operating on the modulation of electricity supply and demand (generation and consumption side), intervene on the grid's layout by dynamically changing its configuration through commands sent to the electrical sub-stations. Modern substation architecture can be structured roughly in three-levels: process, bay and station <ref type="bibr" target="#b41">[42,</ref><ref type="bibr" target="#b42">43]</ref>, as shown in Figure <ref type="figure">.</ref> 2.</p><p>The station level gathers information from the bay level devices for real-time supervision, monitoring and intervention by human experts. At this level are connected the computers dedicated to the supervision and management of the substation. It collects substation data like voltage, current, power factor etc. from the bay level devices and submit the control commands for the primary equipment (Circuit breakers) and collect the. Generally at Station Level there is one or more workstation used as HMI and for engineering purpose.</p><p>The bay level embedded devices control and interact with the process level equipment's. It acquires the data from the bay and then mainly act on the primary (power circuit) equipment of the bay. Generally a transformer with its related switchgear between the two busbars representing the two voltage levels forms one bay.</p><p>Process level extracts the information from sensors/transducers in the substation and to send them to upper level device. The other major task of process level function is to receive the control command from bay level device and execute it at the appropriate switch level. At process level there are different power devices like transformers, current/voltage transformers (CT/VT), circuit-breakers (CB), switchgears, surge arresters, etc., which are essentially analog devices. Therefore, merging units (MU) are required to convert the analog signals, acquired/generated by the process level equipment, into digital signals. These information are transferred to the bay level, which comprises of the protection and control devices, which are embedded devices like DFRs, DPRs, IEDs, etc.. Modern substations are aimed to be more interconnected, leveraging communication standards like IEC 61850-9-2, and associated abstract data models and communication services like GOOSE, MMS, SMV. Such interconnection would enable fast and secure data transfer, sharing of the analytics information for various purposes like wide area monitoring, faster outage recovery, blackout prevention, distributed state estimation, etc. Such communication is mainly managed at station level. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Operational Technology are inherently insecure</head><p>The acronym OT (Operational Technologies) refers to a set of interconnected systems that use physical elements, networks and communication protocols to perform industrial operations such as manufacturing, transportation and processing of goods <ref type="bibr" target="#b6">[7]</ref>. Typical examples of OT are industrial control systems (ICS), control and data acquisition (SCADA) systems, and distributed control systems (DCS). These, despite being different and highly customized, are based on similar key components that enable them to perform three essential tasks: data acquisition, control and supervision, and command execution <ref type="bibr" target="#b7">[8,</ref><ref type="bibr" target="#b8">9,</ref><ref type="bibr" target="#b9">10]</ref>. Such systems are generally designed to guarantee the safety of supervised processes, and to this end they have to be compliant with the time dynamic of the underline physical process this induces specific constraints on the maximum reaction time and the need to have high availability requirements.</p><p>OTs are generally characterized by the exchange of huge amounts of small information (limitedsized packets from a plethora of different sources) and high levels of determinism and very low latency. Thus, including elements such as encryptions, antivirus and firewalls means incorporating control routines that could affect the smooth running of activities by generating delays that, while quantitatively insignificant, make the control system less ready, preventing it from meeting the "hard real-time" requirements for which it was designed.</p><p>Another factor that undermines the implementation of security measures is the fact that the OT must operate continuously 24x365, which makes maintenance work extremely costly and problematic. Maintaining a system through the introduction of patches and updates requires infrastructure downtime <ref type="bibr" target="#b10">[11]</ref>, which implies that updating must be planned well in advance and cannot immediately follow path realise. In addition, patching is considered a risky task, as any change could produce unexpected effects. Preventing these effects would mean specific and targeted testing, the cost of which is often prohibitive <ref type="bibr" target="#b11">[12]</ref>.</p><p>Therefore, once installed and certified for safety, OTs remain in operation for up to 20 years with limited modifications, leading the operator to work with out-of-date software and inadequate assets with inherent instability, critical failure points, and security holes. Similarly, as reported in <ref type="bibr" target="#b12">[13]</ref>, only 10 percent of customers install patches and updates for programmable logic controllers (PLCs), leaving existing software with innate vulnerabilities susceptible to attacks <ref type="bibr" target="#b13">[14]</ref>.</p><p>As mentioned earlier, one of the primary needs for OT are the hard real time and high availability requirements which leaves little room for cybersecurity measures. In OT context, for a long time the only protective barrier has been the so-called "security through obscurity" Previously, control systems were based on legacy systems running on networks that were physically isolated from company IT environment and without any connection with Internet and external networks <ref type="bibr" target="#b14">[15,</ref><ref type="bibr" target="#b15">16]</ref>. In addition, OT systems employed proprietary protocols unique to the industrial environment and tailored to the supervised industrial process. This isolation allows to promote a security by obscurity approach were the integrity of a system were "guaranteed" by the impossibility to physical access to the industrial network and by the difficulties to acquire in-depth knowledge of the proprietary software in use. As a result, industrial systems were considered reasonably immune to external cyber attacks and the main threat was perceived as insider <ref type="bibr" target="#b16">[17]</ref>, e.g. a "disgruntled worker" seeking revenge <ref type="bibr" target="#b14">[15]</ref>. In fact, until 2010, the only cyber attack targeting control systems occurred in Maroochy Shire (Australia), where a former employer hacked the city's water control system and caused 800,000 liters of raw sewage to spill, resulting in significant environmental and economic damage <ref type="bibr" target="#b17">[18]</ref>.</p><p>Nowadays, OT-based sites can no longer rely on security by obscurity paradigm. In fact, modern processes, to improve efficiency, are largely based on off-the-shelf software and component and it is mandatory that OT networks can exchange data with company IT network or even be connected to internet to allow remote maintenance, monitoring and control. This imply that the OT devices used to control physical processes, which previously communicated through closed networks, are now connected not only to the corporate network but also to the Internet <ref type="bibr" target="#b18">[19]</ref>. These developments are business-oriented and aim to meet growing operational needs. While they have dramatically reduced the cost of purchasing, installing, and maintaining OTs, as well as optimized the performance and maximized the availability of systems, the general trend to "connect the unconnected" <ref type="bibr" target="#b18">[19,</ref><ref type="bibr" target="#b19">20]</ref> has exponentially increased the vulnerable surface of OTs <ref type="bibr" target="#b20">[21]</ref>, with significant implications for cybersecurity <ref type="bibr" target="#b21">[22]</ref>.</p><p>This business-driven trends have led to a change in the nature of cyber-threats. In fact, if between 1982 and 2000 70% of attacks were internal, from 2000 to 2003 the number of attacks originated externally increased to 70% <ref type="bibr" target="#b22">[23]</ref>. This progressive trend reversal is a direct consequence of the use for OT of off-the-shelf IT hardware and software included the use of commercial operative systema (e.g. Windows NT) and network protocol (e.g. TCP/IP) and it is unlikely to decrease in the future.</p><p>This elements, together with a significant increase in the frequency of cyber-attacks <ref type="bibr" target="#b23">[24]</ref>, have raised a great concern about the threats stemming from cyberspace. In 2009, a survey involving six hundred IT and security executives showed that most respondents held that a major cyber-operation involving as target the OT components of Critical Infrastructures was imminent <ref type="bibr" target="#b24">[25]</ref>.</p><p>Cyber-attacks might pursuit several goals. They could have a criminal nature, for example inflicting reputational damages <ref type="bibr" target="#b25">[26]</ref> or locking data/system and ask for a ransom <ref type="bibr" target="#b26">[27]</ref>. They could be business driven, thus with the aim of stealing valuable data or confidential information on production statistics, market strategies, drilling plans and pricing sheets <ref type="bibr" target="#b27">[28,</ref><ref type="bibr" target="#b28">29]</ref>. However, the most critical aspect of OT vulnerability is that cyber-attacks could have not only an economic impact, but also a kinetic one. Indeed, by modifying the normal functioning of a process, attackers are able to induce failures and mechanical break points. This was proved in 2007 with the Aurora Project, in which a cyber-attack targeting an industrial power generator was simulated <ref type="bibr" target="#b29">[30]</ref>. As asserted in 2012 by the former U.S. Defense Secretary Leon E. Panetta, a successful operation could result in a 'cyber-Pearl Harbour' if a group gained 'control of critical switches' <ref type="bibr" target="#b30">[31]</ref>.</p><p>As concrete examples of such scenario, BlackEnergy 3 and CRASHOVERRIDE are considered to have originated power outages in Ukraine. The first attack manifested itself on the 23rd of December 2015 and caused a loss of power for six hours that affected around 225,000 customers. The adversaries used BlackEnergy 3 malware to pivot into the SCADA environment and take control of the operation. Once intruded, they leveraged the system to disconnect substations from the grid, which caused the blackout <ref type="bibr" target="#b31">[32,</ref><ref type="bibr" target="#b32">33]</ref>. Approximatively one year later, CRASHOVERRIDE, known also as Industroyer, deprived power to a part of Kiev and its surroundings for over an hour <ref type="bibr" target="#b33">[34]</ref>. CRASHOVERRIDE allowed the attackers to take direct control of the substation breakers that were then opened, which provoked a temporary loss of power <ref type="bibr" target="#b31">[32,</ref><ref type="bibr" target="#b33">34]</ref>.</p><p>An interesting peculiarity of these attacks is that it was not the malware which directly caused the loss of power. Both BlackEnergy 3 and CRASHOVERRIDE allowed the attackers to take control of the industrial operations and sent legitimate command to the substation, and such commands where able to induce anomalous behavior in the electric grid. In other terms the malwares were able to generate a sophisticated sequences of legitimate commands which malicious interaction with the physical system provoked the outages <ref type="bibr" target="#b31">[32,</ref><ref type="bibr">45,</ref><ref type="bibr" target="#b35">36]</ref>. This means that the main focus of the attack was not con the payloads themselves, but rather on the adversary's knowledge and ability to interact with the system <ref type="bibr" target="#b34">[35]</ref>. In other words, if attackers find another entry-point into the industrial network, they would be capable of successfully repeating the attack regardless of the patches put in place by the defender.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Strategy for cyber-security of OT systems</head><p>In this paper we focalize on the cyber security of the electric substation. Such a motivation is based on the relevance that elements play for the stability of the electric grid. Indeed, as shown by the attacks in Ukrainian, a successful cyber attack is able to induce a blackout in large portion of population. Moreover being unattended and geographically dispersed sites generically located in rural areas with very low population density, their protection also from the physical point of view is a complex task. Finally the tight hard real time constraints which characterize the control schema, with maximum latency in the order of milliseconds, makes very challenging their cyber-protection.</p><p>However substations are, by their nature, comparable to distributed IT systems and, for this reason, they must be protected by implementing adequate organizational, process and technological countermeasures throughout their entire life cycle. Hence an adequate strategy to improve their cyber security involving all the components of the electric substation needs to be developed to guarantee the "construction" of a secure Cyber posture and the maintenance, until decommissioning, of the required level of protection.</p><p>This consideration should inspire any TSOs to create cyber resilient strategies which involve both technical and no-technical aspects and must be able to permeate all company divisions so that the departments dealing with substation procurement, operation, maintenance and decommissioning are fully involved and aware of the implications that failure to comply with cyber-security procedures could have in terms of negative effects on the electricity grid.</p><p>Such a strategy must include both cultural, procedural and technological elements. Even if in this paper we mainly focalize on the technological aspects, we consider mandatory to provide before a short description of the best practice that should be adopted to increase the cyber security culture in TSOs and about the procedure to manage the cyber security element along all the life cycle of any component of the electrical substations.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.1.">Cultural initiative and Cyber Security organization</head><p>To be able to implement an effective cyber protection strategy, it is mandatory that TSOs should have a dedicated structure to manage all the aspects related with the management of OT cyber security. Such a structure should have adequate decision-making autonomy and sufficient capacity to influence the various business processes in order to impose appropriate attention to cyber security issues in all decision-making and operational processes. Moreover, such a structure facilitates the development of a dedicated team with high skilled and specialization personnel with in-depth knowledge of both cyber and process issues.</p><p>Th e presence of a such a dedicated structure will ensure adequate governance and constant innovation of the cyber security architecture. This structure should supervision all the aspects related to the OT cyber issues and, among others, should:</p><p>• support the definition of security requirements in all the phases of the "life cycle" (design, acquisition, implementation, operation and decommissioning) of OT systems, components and services used to manage the high-voltage electric grid;</p><p>• ensure the constant development of defense and protection systems for the digital perimeter;</p><p>• carry out with adequate frequency cyber security assessment activities;</p><p>• guaranteeing centralized monitoring in real time of the cyber perimeters and ICT platforms (including those in the industrial sector);</p><p>• manage and coordinate security incidents in all their phases (detection, reaction, manage, forensic and post-event low up) included the management of relationship with law-enforcement and national cyber agencies;</p><p>• ensure the operation and ordinary and extraordinary maintenance of IT systems and applications in support of cyber security management activities;</p><p>• coordinate and promote corporate awareness &amp; training initiatives in the cyber security area.</p><p>The last point should be one of the cornerstones of any cyber security strategy <ref type="bibr" target="#b36">[37]</ref>, this because human incorrect operation is at the base of almost 80% of Cyber Attacks successes <ref type="bibr" target="#b37">[38]</ref>. In this regard, TSOs should develop campaigns to increase the digital culture and cyber security posture of the employers not only within the company, but also outside the company perimeter with suppliers and customers, thus increasing the awareness of all the actors involved, especially in the face of an exponential interconnection and sharing of digital data. Such initiatives should include, but not limited, specific training courses on cyber security issues for the personnel involving in the operation of OT and substation systems <ref type="bibr" target="#b38">[39]</ref>. Moreover specific campaigns should be constantly carrying out to test the effective level of awareness of the personnel for cyber security issue <ref type="bibr" target="#b39">[40]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.2.">Cyber Security procedure</head><p>How to manage cyber security issue in Electrical Substation must be codified within a specific standard in which a guideline is provided for the entire life cycle of digital station systems, consistently with the cyber security strategy. This to avoid to have multiple and potentially clashing requirements documents and also to have a repository where such information are collected and easily available. Such requirements have been inspired by the NIST 800-82 <ref type="bibr" target="#b7">[8]</ref>, but it is important to extended and customized the requirements on the base of the peculiarities of each environment in order to be immediately applicable to the specific TSOs' scenario. A factor that significantly affects this aspect is the different obsolescence level of the various technologies used within the substation, this because IT components, so as the OT components, have times of obsolescence much shorter than those of the electromechanical components.</p><p>An overview of the macro-areas that should be included in the standard is reported in the Table <ref type="table">1</ref> Table <ref type="table">1</ref> Standard for the Cyber Security of Digital Electric Substation Systems Rule for Description System acquisition policy regarding security check and constraints for software and hardware acquisition, development, integration, implementation and configuration. Elements that are not fully compliant with such criteria should not be installed in the OT environment Configuration management and system integrity set of activities focused on creating and maintaining the integrity of IT products and information systems, through the control of processes for initialization, modification and monitoring of configurations during the life of the element System maintenance checks regarding system maintenance, in particular regarding the presence of documentation and the regularity of maintenance interventions</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Compliance and accreditation</head><p>continuous assessment procedures for the effectiveness of security controls and the implementation of privacy controls Physical and environmental protection measures to be taken to protect systems, buildings and related support infrastructures from accidental and malicious threats related with physical dimension and environment Identification and authentication guideline of the process that establishes the identity of an entity that interacts with the system. This element includes also the specification for access control, i.e. the process of granting or refusing specific requests for:</p><p> obtain and use information and related IT services;</p><p>• access specific physical facilities Traceability set of activities to ensure the traceability of system operations and the availability of logs for legislation issue and for forensic activities System and communications protection rules for the implementation of security controls for any communication and data transfer</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Contingency planning</head><p>provisional measures to restore services following an emergency or a system outage Risk assessment guideline of the process of identifying risks for operations, resources and individuals resulting from the operation of an IT system Supply chain risk management prescription for managing exposure to risks, threats and vulnerabilities in the supply chain and for developing strategies in response to the risks presented by third parties, by the products and services provided As stressed by the last issue of the standard, it is mandatory that all the actors involved in the supply chain be actively involved in the risk analysis phase and for the management of the cyber security. Suppliers need to be compliant with cyber security technical specifications and to they have to guarantee an adequate level of cyber awareness. Moreover, in the supply contract should be explicitly included specific service level agreement (SLA) on the procedure to manage any situation when vulnerability are discovered/realized, specific procedures and time schedule to release and implement security patch, and also the procedure to manage specific contingency plan and to be involved in the risk assessment process.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.3.">Cyber Security architecture for Station</head><p>In line with the evolution of the Substation Automation Systems which have enabled various new functions (e.g. remote control), TSOs have to adapted their technologies and processes to ensure high protection and monitoring capacity of industrial systems.</p><p>Such approach should be inspired by the well-know principles of the Security by Design, i.e.:</p><p>• Defense in Depth: the cybersecurity strategy should be arranged as a series of different layered defense mechanisms each one characterize by peculiar mechanism and solution. In this scenario, if one mechanism fails, another immediately takes its place to counter an attack. This multi-layered redundant approach is able to increase the security of the entire system and addresses many different attack vectors;</p><p>• Least-Privilege: any user, person or software agent, is granted with the minimum levels of permissions that he/she needs to carry out his duties;</p><p>• Deny-by-Default: grants permission only what is explicitly authorized, while the rest is prohibited by default.</p><p>But it is important to implement the more innovative and recent approaches generally labelled as Zero Trust in compliance with the guidelines dictated by international industry standards such as, for example, NIST SP 800-82 <ref type="bibr" target="#b7">[8]</ref> and ISO 27001: 2013. Inside a Zero Trust schema nothing, both internal and external to the network perimeter of an organization, is considered trusted by default, A cornerstone element of this strategy is an effective segregation between IT and OT infrastructure (suggested also recently by Italian CISRT in response to the cyber risk related with Ukraine-Russia war). Such a segregation actually operates at two level from one side the IT network is segregated with respect to central OT network but also the central OT network is segregated from the OT networks distributed in the substations. This means that any malicious packed even if gained the access to the IT environment had to overcome two different type of firewalls before to be able to reach any single substation.</p><p>However, it must be considered that an attack can be carried out either by gaining physical access to the substation, which is generally unprotected, or by intercepting communications to/from the control center and the communications exchanged between substations. Hence the physical protection of a substation is the very first barrier to prevent a dangerous cyber attack and it should be carefully designed and continuously checked.</p><p>On the other side protecting communications is a challenge because only in some cases the substations are connected via proprietary fiber optics cable, while in general they use commercial or LTE links. However, the presence of a firewall is a useful tool to mitigate such a risk.</p><p>More complex is the protection of communication between substations, due to very stringent requirements on latency (generally less than 1 ms) that make unfeasible the presence of any on-line filtering component, i.e. this flow cannot generally be monitored by the firewall.</p><p>To partially overcome these difficulties, it is strongly recommended that each substation be equipped with an Anomaly Detection System (ADS) with signatures for industrial environments that, operating in parallel with the flow, is able to discover anomalous situations without interfering with the process.</p><p>The presence of the ADS, possibly integrated with the firewall in an Intrusion Prevention Systems (IPS), is also a protection mechanism for possible cyber attacks launched from the in-field devices by exploiting the connection with the 'bay' area.</p><p>In addition, it is useful to equip substation with control tools able to prevent unauthorized users or codes from accessing the station's computer. To this end, such a tools should:</p><p>-deny permission to execute any application or process not specifically approved (e.g. whitelisting); -management of asset access policies based on the user's profile; TSOs must be equipped with specific centralised asset management tools that guarantee the visibility of the network and technological elements of industrial systems.</p><p>The presence of a specific Cyber Threat Intelligence services for the industrial domain, is useful to promptly identify any external threats that put the company's information assets and critical services at risk. This allow to adopt pro-active measurements in order to prevent cyber attack.</p><p>Finally it is very useful to equip any substation with specific tools for carrying out vulnerability assessment campaigns (passive scanning on production environments, active scanning on test and experimental environments) in order to support the delivery of this instrumentation without create degradation in the operational environment.</p><p>In order to be more effective, it is strongly recommended to set up one or more test environments able to reproduce with high fidelity the architecture of the substations <ref type="bibr" target="#b39">[40]</ref>. This test environment dedicated may be used to:</p><p>• check the effectiveness of patch and the absence of any side effect;</p><p>• analyze potential impact of malware or virus on the operation capabilities of the substation;</p><p>• experiment innovative technological security solutions;</p><p>• recreate real conditions of use suitable for experimenting with cyber security solutions to be used for the protection of assets;</p><p>• develop and experiment innovative communication procedures to support Cyber Security Awareness program</p><p>• create a Digital Twin of some portions of the industrial systems infrastructure, replicating the current operating ecosystem in order to carry out vulnerability analyzes and penetration tests.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Conclusion</head><p>In the framework of energy transition and network digitalization, the introduction of new technologies in the OT, IoT and Edge Computing fields brings great benefits and great opportunities for the evolution of the electricity system, but also inevitable new correlated cyber risks <ref type="bibr" target="#b38">[39]</ref>.</p><p>Cyber Security in TSOs is now an enabling factor for advanced planning, in the face of an everincreasing complexity and unpredictability of threats, which require strengthening risk mitigation tools and reducing reaction times to attacks. These objectives can be effectively pursued through an organization equipped with adequate technologies, processes and human resources.</p><p>The experience made by several TSOs confirms that an effective response to cyber threats can be given by a structure that manages the process end-to-end in an agile manner by using an operational strategy in which the mix of insourcing and outsourcing is dynamically modified in the safety principles and contributing to the achievement of the company's strategic objectives.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: Schematic representation of TSO gridElectric sub-stations are junction points where two or more branches of the electric grid, generally with different voltage, converge with the possibility of defining different configurations of the electric circuits in order to be able to direct the electric flow to instantaneously satisfy electrical constraints.Modern substation architecture can be structured roughly in three-levels: process, bay and station<ref type="bibr" target="#b41">[42,</ref><ref type="bibr" target="#b42">43]</ref>, as shown in Figure.2.The station level gathers information from the bay level devices for real-time supervision, monitoring and intervention by human experts. At this level are connected the computers dedicated to the supervision and management of the substation. It collects substation data like voltage, current, power factor etc. from the bay level devices and submit the control commands for the primary equipment (Circuit breakers) and collect the. Generally at Station Level there is one or more workstation used as HMI and for engineering purpose.The bay level embedded devices control and interact with the process level equipment's. It acquires the data from the bay and then mainly act on the primary (power circuit) equipment of the bay. Generally a transformer with its related switchgear between the two busbars representing the two voltage levels forms one bay.Process level extracts the information from sensors/transducers in the substation and to send them to upper level device. The other major task of process level function is to receive the control command from bay level device and execute it at the appropriate switch level. At process level there are different power devices like transformers, current/voltage transformers (CT/VT), circuit-breakers (CB), switchgears, surge arresters, etc., which are essentially analog devices. Therefore, merging units (MU) are required to convert the analog signals, acquired/generated by the process level equipment, into digital signals. These information are transferred to the bay level, which comprises of the protection and control devices, which are embedded devices like DFRs, DPRs, IEDs, etc.. Modern substations are aimed to be more interconnected, leveraging communication standards like IEC 61850-9-2, and associated abstract data models and communication services like GOOSE, MMS, SMV. Such interconnection would enable fast and secure data transfer, sharing of the analytics information for various purposes like wide area monitoring, faster outage recovery, blackout prevention, distributed state estimation, etc. Such communication is mainly managed at station level.</figDesc><graphic coords="3,165.60,109.68,277.92,168.24" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 2 :</head><label>2</label><figDesc>Figure2: System architecture of the substation automation system in the 220 kV-132 kV transmission substation<ref type="bibr" target="#b40">[41]</ref> </figDesc><graphic coords="4,144.72,71.76,320.16,229.44" type="vector_box" /></figure>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<ptr target="https://www.worldenergy.org/assets/downloads/Cyber_Challenges_to_the_Energy_Transition_WEC_MMC_2019.pdf" />
		<title level="m">World Energy Council &quot;Cyber challenges to the energy transition</title>
				<imprint/>
	</monogr>
	<note>Report 2019</note>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<title/>
		<author>
			<persName><surname>Csirt</surname></persName>
		</author>
		<ptr target="https://www.csirt.gov.it/crisi-ucraina-analisi-del-rischio-tecnologico-e-diversificazione" />
		<imprint>
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Cyber threats for operational technologies</title>
		<author>
			<persName><forename type="first">Giacomo</forename><surname>Assenza</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">International Journal of System of Systems Engineering</title>
		<imprint>
			<biblScope unit="volume">10</biblScope>
			<biblScope unit="issue">2</biblScope>
			<biblScope unit="page" from="128" to="142" />
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">German steel mill cyber-attack</title>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">M</forename><surname>Lee</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">J</forename><surname>Assante</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Conway</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Industrial Control Systems</title>
		<imprint>
			<biblScope unit="volume">30</biblScope>
			<biblScope unit="page">62</biblScope>
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Triton/TriSIS -In Search of its Twin</title>
		<author>
			<persName><forename type="first">M</forename><surname>Assante</surname></persName>
		</author>
		<ptr target="https://ics.sans.org/blog/2018/01/29/tritontrisis-in-search-of-its-twin" />
	</analytic>
	<monogr>
		<title level="j">SANS Industrial Control Systems</title>
		<imprint>
			<date type="published" when="2018-01-29">2018. 29 January</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Critical Infrastructure Protection against cyber threats</title>
		<author>
			<persName><forename type="first">L</forename><surname>Tabansky</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Military and Strategic Affairs</title>
		<imprint>
			<biblScope unit="volume">3</biblScope>
			<biblScope unit="issue">2</biblScope>
			<biblScope unit="page" from="61" to="68" />
			<date type="published" when="2011">2011</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">An overview of Cyber Attack to Industrial Control System</title>
		<author>
			<persName><forename type="first">R</forename><surname>Setola</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Faramondi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Salzano</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Cozzani</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Chemical Engineering Transactions</title>
		<imprint>
			<biblScope unit="volume">77</biblScope>
			<biblScope unit="page" from="907" to="912" />
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Guide to Industrial Control Systems (ICS) Security</title>
		<author>
			<persName><forename type="first">K</forename><surname>Stouffer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Lightman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Pillitteri</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Abrams</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Hahn</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="s">NIST special publication</title>
		<imprint>
			<biblScope unit="page" from="800" to="882" />
			<date type="published" when="2015">2015</date>
		</imprint>
		<respStmt>
			<orgName>National Institute of Standards and Technology</orgName>
		</respStmt>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Cyber-physical systems in manufacturing</title>
		<author>
			<persName><forename type="first">L</forename><surname>Monostori</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Kádár</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Bauernhansl</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Kondoh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Kumara</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Reinhart</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Ueda</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Cirp Annals</title>
		<imprint>
			<biblScope unit="volume">65</biblScope>
			<biblScope unit="issue">2</biblScope>
			<biblScope unit="page" from="621" to="641" />
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<monogr>
		<title level="m" type="main">Distributed Computer Control Systems in Industrial Automation</title>
		<author>
			<persName><forename type="first">V</forename><surname>Bhatkar</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2017">2017</date>
			<publisher>Routledge</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">The industrial control system cyber defence triage process</title>
		<author>
			<persName><forename type="first">A</forename><surname>Cook</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Janicke</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Smith</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Maglaras</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Computers &amp; Security</title>
		<imprint>
			<biblScope unit="volume">70</biblScope>
			<biblScope unit="page" from="467" to="481" />
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">The cybersecurity landscape in industrial control systems</title>
		<author>
			<persName><forename type="first">S</forename><surname>Mclaughlin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Konstantinou</surname></persName>
		</author>
		<author>
			<persName><forename type="first">X</forename><surname>Wang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Davi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">R</forename><surname>Sadeghi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Maniatakos</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Karri</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the IEEE</title>
				<meeting>the IEEE<address><addrLine>Bodenheim</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2014">2016. 2014</date>
			<biblScope unit="volume">104</biblScope>
			<biblScope unit="page" from="1039" to="1057" />
		</imprint>
	</monogr>
	<note>13</note>
</biblStruct>

<biblStruct xml:id="b12">
	<monogr>
		<title level="m" type="main">Key Concepts for Critical Infrastructure Research</title>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">I</forename><surname>Engels</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2018">2018</date>
			<publisher>Springer</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Introduction to industrial control networks</title>
		<author>
			<persName><forename type="first">B</forename><surname>Galloway</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><forename type="middle">P</forename><surname>Hancke</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">IEEE Communications surveys &amp; tutorials</title>
		<imprint>
			<biblScope unit="volume">15</biblScope>
			<biblScope unit="issue">2</biblScope>
			<biblScope unit="page" from="860" to="880" />
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">The state of operational technology security</title>
		<author>
			<persName><forename type="first">S</forename><surname>Mansfield-Devine</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Network Security</title>
		<imprint>
			<biblScope unit="issue">10</biblScope>
			<biblScope unit="page" from="9" to="13" />
			<date type="published" when="2019">2019. 2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">The myths and facts behind cyber security risks for industrial control systems</title>
		<author>
			<persName><forename type="first">E</forename><surname>Byres</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Lowe</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the VDE Kongress</title>
				<meeting>the VDE Kongress</meeting>
		<imprint>
			<date type="published" when="2004-10">2004. October</date>
			<biblScope unit="volume">116</biblScope>
			<biblScope unit="page" from="213" to="218" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title level="a" type="main">A History of Cyber Incidents and Threats Involving Industrial Control Systems</title>
		<author>
			<persName><forename type="first">K</forename><surname>Hemsley</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Fisher</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">International Conference on Critical Infrastructure Protection</title>
				<meeting><address><addrLine>Cham</addrLine></address></meeting>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2018">2018</date>
			<biblScope unit="page" from="215" to="242" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title level="a" type="main">Security and privacy challenges in industrial internet of things</title>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">R</forename><surname>Sadeghi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Wachsmann</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Waidner</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Design Automation Conference (DAC)</title>
				<imprint>
			<publisher>Knowles &amp; al</publisher>
			<date type="published" when="2015">2015. 2015. 2015</date>
			<biblScope unit="page" from="1" to="6" />
		</imprint>
	</monogr>
	<note>ACM/EDAC/IEEE</note>
</biblStruct>

<biblStruct xml:id="b18">
	<analytic>
		<title level="a" type="main">Analysis of cyber security for industrial control systems</title>
		<author>
			<persName><forename type="first">Z</forename><surname>Drias</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Serhrouchni</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Vogel</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Cyber Security of Smart Cities, Industrial Control System and Communications (SSIC), 2015 International Conference on</title>
				<imprint>
			<publisher>Ani, He &amp; Tiwari</publisher>
			<date type="published" when="2015">2015. 2017</date>
			<biblScope unit="page" from="1" to="8" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b19">
	<analytic>
		<title level="a" type="main">A survey of cyber security management in industrial control systems</title>
		<author>
			<persName><forename type="first">W</forename><surname>Knowles</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Prince</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Hutchison</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">F P</forename><surname>Disso</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Jones</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">International Journal of Critical Infrastructure Protection</title>
		<imprint>
			<biblScope unit="volume">9</biblScope>
			<biblScope unit="page" from="52" to="80" />
			<date type="published" when="2015">2015</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b20">
	<monogr>
		<title level="m" type="main">Threat Landscape for Industrial Automation Systems In The Second Half Of</title>
		<ptr target="https://ics-cert.kaspersky.com/reports/2017/03/28/threat-landscape-for-industrial-automation-systems-in-the-second-half-of-2016/" />
		<imprint>
			<date type="published" when="2016">2017. 2016</date>
		</imprint>
		<respStmt>
			<orgName>Kaspersky lab ICS-CERT ; Kaspersky Lab</orgName>
		</respStmt>
	</monogr>
</biblStruct>

<biblStruct xml:id="b21">
	<monogr>
		<author>
			<persName><surname>Mcafee</surname></persName>
		</author>
		<ptr target="https://img.en25.com/Web/McAfee/CIP_report_final_uk_fnl_lores.pdf" />
		<title level="m">the Crossfire: Critical Infrastructure in the Age of Cyber War</title>
				<imprint>
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
	<note type="report_type">McAfee report</note>
</biblStruct>

<biblStruct xml:id="b22">
	<analytic>
		<title level="a" type="main">A multi-level approach to understanding the impact of cyber crime on the financial sector</title>
		<author>
			<persName><forename type="first">M</forename><surname>Lagazio</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Sherif</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Cushman</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Computers &amp; Security</title>
		<imprint>
			<biblScope unit="volume">45</biblScope>
			<biblScope unit="page" from="58" to="74" />
			<date type="published" when="2014">2014</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b23">
	<analytic>
		<title level="a" type="main">SCADA security in the light of Cyber-Warfare</title>
		<author>
			<persName><forename type="first">A</forename><surname>Nicholson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Webber</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Dyer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Patel</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Janicke</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Computers &amp; Security</title>
		<imprint>
			<biblScope unit="volume">31</biblScope>
			<biblScope unit="issue">4</biblScope>
			<biblScope unit="page" from="418" to="436" />
			<date type="published" when="2012">2012</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b24">
	<monogr>
		<ptr target="https://scholar.google.com/scholar_case?case=5478245559776905776&amp;hl=en&amp;as_sdt=0,5" />
		<title level="m">Discussing the Role of Cyber Security in OilAns Gas Pipelines</title>
				<imprint>
			<publisher>North America Oli &amp; Gas Pipelines</publisher>
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b25">
	<analytic>
		<title level="a" type="main">Economic Espionage and Business Intelligence</title>
		<author>
			<persName><forename type="first">L</forename><surname>Wright</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">People, Risk, and Security</title>
				<meeting><address><addrLine>London</addrLine></address></meeting>
		<imprint>
			<publisher>Palgrave Macmillan</publisher>
			<date type="published" when="2017">2017</date>
			<biblScope unit="page" from="91" to="105" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b26">
	<analytic>
		<title level="a" type="main">Research Challenges for the Security of Control Systems</title>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">A</forename><surname>Cárdenas</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Amin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Sastry</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">HotSec</title>
				<imprint>
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b27">
	<analytic>
		<title level="a" type="main">Panetta Warns of Dire Threat of Cyberattack on U.S</title>
		<author>
			<persName><forename type="first">E</forename><surname>Bumiller</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Shanker</surname></persName>
		</author>
		<ptr target="http://www.nytimes.com/2012/10/12/world/panetta-warns-of-dire-threat-of-cyberattack.html" />
	</analytic>
	<monogr>
		<title level="j">The New York Times</title>
		<imprint>
			<date type="published" when="2012-10-11">2012. 11 October 2012</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b28">
	<monogr>
		<title level="m" type="main">CRASHOVERRIDE: Analysis of the threat to electric grid operations</title>
		<author>
			<persName><forename type="first">R</forename><surname>Lee</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2017-03">2017. March</date>
			<publisher>Dragos Inc</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b29">
	<analytic>
		<title level="a" type="main">Analysis of the cyber attack on the Ukrainian power grid</title>
		<author>
			<persName><forename type="first">E-Isac</forename></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Electricity Information Sharing and Analysis Center</title>
				<imprint>
			<publisher>E-ISAC</publisher>
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b30">
	<analytic>
		<title level="a" type="main">ESET discovers dangerous malware designed to disrupt industrial control systems</title>
		<author>
			<persName><surname>Eset</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Enjoy Safer Technology</title>
		<imprint>
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
	<note type="report_type">ESET -</note>
</biblStruct>

<biblStruct xml:id="b31">
	<analytic>
		<title level="a" type="main">Analysis of the Cyber Attack on the Ukrainian Power Grid</title>
		<author>
			<persName><forename type="first">T</forename><surname>Conway</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">M</forename><surname>Lee</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">J</forename><surname>Assante</surname></persName>
		</author>
		<ptr target="https://ics.sans.org/media/E-ISAC_SANS_Ukraine_DUC_5.pdf" />
	</analytic>
	<monogr>
		<title level="m">Electricity Information Sharing and Analysis Center</title>
				<imprint>
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b32">
	<monogr>
		<title level="m" type="main">WIN32/INDUSTROYER, A new threat for industrial control systems</title>
		<author>
			<persName><forename type="first">A</forename><surname>Cherepanov</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2017-06">2017. June 2017</date>
			<publisher>ESET</publisher>
		</imprint>
	</monogr>
	<note type="report_type">White paper</note>
</biblStruct>

<biblStruct xml:id="b33">
	<analytic>
		<title level="a" type="main">A review of methods for evaluating security awareness initiatives</title>
		<author>
			<persName><forename type="first">G</forename><surname>Assenza</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Chittaro</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">C</forename><surname>De Maggio</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Mastrapasqua</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Setola</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">European Journal for Security Research</title>
		<imprint>
			<biblScope unit="volume">5</biblScope>
			<biblScope unit="issue">2</biblScope>
			<biblScope unit="page" from="259" to="287" />
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b34">
	<monogr>
		<title level="m" type="main">Building a cybersecurity culture in organizations</title>
		<author>
			<persName><forename type="first">I</forename><surname>Corradini</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2020">2020</date>
			<publisher>Springer International Publishing</publisher>
			<biblScope unit="volume">284</biblScope>
			<pubPlace>Berlin/Heidelberg, Germany</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b35">
	<analytic>
		<title level="a" type="main">Extending the cyber-attack landscape for SCADAbased critical infrastructure</title>
		<author>
			<persName><forename type="first">N</forename><forename type="middle">R</forename><surname>Rodofile</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Radke</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Foo</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">International Journal of Critical Infrastructure Protection</title>
		<imprint>
			<biblScope unit="volume">25</biblScope>
			<biblScope unit="page" from="14" to="35" />
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b36">
	<analytic>
		<title level="a" type="main">How to improve the security awareness in complex organizations</title>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">C</forename><surname>De Maggio</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Mastrapasqua</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Tesei</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Chittaro</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Setola</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">European Journal for Security Research</title>
		<imprint>
			<biblScope unit="volume">4</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="33" to="49" />
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b37">
	<analytic>
		<title level="a" type="main">Review of cybersecurity issues in industrial critical infrastructure: manufacturing in perspective</title>
		<author>
			<persName><forename type="first">U</forename><forename type="middle">P D</forename><surname>Ani</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>He</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Tiwari</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Journal of Cyber Security Technology</title>
		<imprint>
			<biblScope unit="volume">1</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="32" to="74" />
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b38">
	<analytic>
		<title level="a" type="main">Critical infrastructure protection: Requirements and challenges for the 21st century</title>
		<author>
			<persName><forename type="first">C</forename><surname>Alcaraz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Zeadally</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">International journal of critical infrastructure protection</title>
		<imprint>
			<biblScope unit="volume">8</biblScope>
			<biblScope unit="page" from="53" to="66" />
			<date type="published" when="2015">2015</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b39">
	<analytic>
		<title level="a" type="main">A control system testbed to validate critical infrastructure protection concepts</title>
		<author>
			<persName><forename type="first">T</forename><surname>Morris</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Srivastava</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Reaves</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><surname>Gao</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Pavurapu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Reddi</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">International Journal of Critical Infrastructure Protection</title>
		<imprint>
			<biblScope unit="volume">4</biblScope>
			<biblScope unit="issue">2</biblScope>
			<biblScope unit="page" from="88" to="103" />
			<date type="published" when="2011">2011</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b40">
	<analytic>
		<title level="a" type="main">Authentication and integrity in the smart grid: An empirical study in substation automation systems</title>
		<author>
			<persName><forename type="first">X</forename><surname>Lu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><surname>Wang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Ma</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">International Journal of Distributed Sensor Networks</title>
		<imprint>
			<biblScope unit="volume">8</biblScope>
			<biblScope unit="issue">6</biblScope>
			<biblScope unit="page">175262</biblScope>
			<date type="published" when="2012">2012</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b41">
	<analytic>
		<title level="a" type="main">Toward threat of implementation attacks on substation security: Case study on fault detection and isolation</title>
		<author>
			<persName><forename type="first">A</forename><surname>Chattopadhyay</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Ukil</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Jap</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Bhasin</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">IEEE Transactions on Industrial Informatics</title>
		<imprint>
			<biblScope unit="volume">14</biblScope>
			<biblScope unit="issue">6</biblScope>
			<biblScope unit="page" from="2442" to="2451" />
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b42">
	<analytic>
		<title level="a" type="main">Substation automation using IEC61850 standard</title>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">P</forename><surname>Gupta</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Fifteenth National Power Systems Conference (NPSC), IIT Bombay</title>
				<imprint>
			<date type="published" when="2008-12">2008. December</date>
			<biblScope unit="page" from="462" to="466" />
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
