<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.1d1 20130915//EN" "JATS-journalpublishing1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:mml="http://www.w3.org/1998/Math/MathML" article-type="research-article" xml:lang="en"><front><journal-meta><journal-id journal-id-type="publisher-id">SDQ</journal-id><journal-title-group><journal-title>Security &amp; Defence Quarterly</journal-title><abbrev-journal-title>SDQ</abbrev-journal-title></journal-title-group><issn pub-type="epub">2544-994X</issn><issn pub-type="ppub">2300-8741</issn><publisher><publisher-name>Akademia Sztuki Wojennej</publisher-name></publisher></journal-meta><article-meta><article-id pub-id-type="publisher-id">SDQ-48-00311</article-id><article-id pub-id-type="doi">10.35467/sdq/177655</article-id><article-categories><subj-group subj-group-type="heading"><subject>RESEARCH PAPER</subject></subj-group></article-categories><title-group><article-title>SCADvanceXP—an intelligent Polish system for threat detection and monitoring of industrial networks</article-title></title-group><contrib-group content-type="authors"><contrib contrib-type="author"><contrib-id contrib-id-type="orcid">https://orcid.org/0000-0003-0661-0128</contrib-id><name><surname>Twardawa</surname><given-names>Mateusz Grzegorz</given-names></name><xref ref-type="aff" rid="aff1">1</xref><email>mtwardawa@man.poznan.pl</email></contrib><contrib contrib-type="author"><name><surname>Smolik</surname><given-names>Marek</given-names></name><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><contrib-id contrib-id-type="orcid">https://orcid.org/0000-0001-6133-8900</contrib-id><name><surname>Rakowski</surname><given-names>Franciszek</given-names></name><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><contrib-id contrib-id-type="orcid">https://orcid.org/0000-0001-7000-3862</contrib-id><name><surname>Kwiatkowski</surname><given-names>Jakub</given-names></name><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><contrib-id contrib-id-type="orcid">https://orcid.org/0000-0003-4020-5329</contrib-id><name><surname>Meyer</surname><given-names>Norbert</given-names></name><xref ref-type="aff" rid="aff4">4</xref></contrib><aff id="aff1"><label>1</label>ICT Security Department, Poznań Supercomputing and Networking Center (PSNC), affiliated to the Institute of Bioorganic Chemistry of the Polish Academy of Sciences, Jana Pawła II10, 61-139, Poznań, Poland; Institute of Computing Science, Poznań University of Technology, Piotrowo 2, 60-965, Poznań, Poland</aff><aff id="aff2"><label>2</label>CTO, ICsec S.A., Wichrowa 1A, 60-449, Poznań, Poland</aff><aff id="aff3"><label>3</label>R&amp;D Department, ICsec S.A., Wichrowa 1A, 60-449, Poznań, Poland</aff><aff id="aff4"><label>4</label>Data Processing Technologies Division, Poznań Supercomputing and Networking Center (PSNC), affiliated to the Institute of Bioorganic Chemistry of the Polish Academy of Sciences, Z. Noskowskiego 12/14, 61-704, Poznań, Poland</aff></contrib-group><pub-date pub-type="epub"><day>03</day><month>03</month><year>2024</year></pub-date><volume>48</volume><issue>1</issue><fpage>1</fpage><lpage>21</lpage><history><date date-type="received"><day>14</day><month>09</month><year>2023</year></date><date date-type="rev-recd"><day>11</day><month>12</month><year>2023</year></date><date date-type="accepted"><day>27</day><month>12</month><year>2023</year></date></history><permissions><copyright-statement>© 2024 M.G. Twardawa, M. Smolik, F. Rakowski, J. Kwiatkowki, N. Meyer published by War Studies University, Poland.</copyright-statement><copyright-year>2024</copyright-year><license license-type="open-access" xlink:href="http://creativecommons.org/licenses/by/4.0"><license-p>This article is an open access article distributed under the terms and conditions of the Creative Commons Attribution (CC BY) license (<ext-link ext-link-type="uri" xlink:href="http://creativecommons.org/licenses/by/4.0/">http://creativecommons.org/licenses/by/4.0/</ext-link>).</license-p></license></permissions><abstract><p>SCADvanceXP is an industrial network intrusion detection system that scans and monitors data exchange between engineering stations, field divides, controllers, supervisory control and data acquisition (SCADA), and other elements of the operational technology network in detail. SCADvanceXP has the potential to detect advanced attacks on industrial infrastructures with the use of rule-based, signature-based, and behavioural detection methods, which are supported by sophisticated machine and deep learning models. As a system developed in Poland, it addresses the needs of industry in that region of Europe. The goal of this work was to assess SCADvanceXP’s potential to detect common industrial threats. In order to check SCADvanceXP’s potential, an effort was undertaken to evaluate its functionality on major industrial threats. For that purpose, twelve malware strains interfering with industrial systems were described. Later, the SCADvanceXP functionality was overlapped on malware behavioural and detection markers, pointing out exact mechanisms in SCADvanceXP that would detect analysed threats. The results show that SCADvanceXP is able to detect a wide range of attacks on industrial networks. SCADvanceXP’s rich functionality is able to provide a high standard of security. However, if a threat is affecting systems not directly connected with industrial networks, SCADvanceXP will not be able to detect it. SCADvanceXP only monitors industrial systems; hence, corporate networks must be protected by a different solution to provide the required level of security. Nonetheless, SCADvanceXP is dedicated to operating within industrial networks and does not have access to regular IT networks. It can be concluded that SCADvanceXP is a specialist tool providing desired security for industrial networks.</p></abstract><kwd-group><kwd>malware</kwd><kwd>anomaly detection</kwd><kwd>cybersecurity</kwd><kwd>intrusion detection systems</kwd><kwd>industrial networks</kwd></kwd-group></article-meta></front><body><sec id="S1" sec-type="intro"><title>Introduction</title><p>According to the in-depth principle of defence, ensuring IT enterprise-level protection is not enough if an industrial operational technology (OT) network remains without security supervision. Constant asset monitoring, vulnerability checking, and traffic analysis are essential to detect industrial network intrusions and weak spots. For this reason, SCADvanceXP was developed. SCADvanceXP is an advanced and dedicated system for intrusion detection in diverse industrial network environments. It encompasses many complementary functions, including traffic monitoring, deep packet inspection, independent process value monitoring, tools for asset management in an industrial network, a vulnerability scanner, and many other things. SCADvanceXP’s intrusion detection methods incorporate advanced and tested machine-learning (ML) models that are able to provide robust and mature network monitoring mechanisms.</p><p>In this work, analysis was focused on overlapping SCADvanceXP functionality on the detection capacity of the most advanced current threats. For this purpose, twelve commonly occurring malware strains affecting (directly or indirectly) industrial systems were selected and SCADvanceXP’s detection mechanisms were analysed for them.</p></sec><sec id="S2"><title>Industrial network security in a nutshell</title><p>Efficient and reliable communication between devices is essential for modern industrial process automation. Thanks to fast data exchange between elements of the industrial network like programmable logic controllers (PLCs) and terminal devices (e.g. valves, sensors, and mechanical arms), it is possible to continuously control even deeply complex processes. Industrial systems incorporate many dispersed elements that have to be orchestrated, monitored, and protected. The whole system is usually encapsulated under an integrated network called the industrial control system (ICS). A popular example of such system is Supervisory Control and Data Acquisition (SCADA). <xref ref-type="fig" rid="F1">Figure 1</xref> is a diagram of an internal network and shows the structure of zones typically defined for industrial networks, highlighting their overall location and difference from other networks (the Purdue model [<xref ref-type="bibr" rid="ref53">Williams, 1994</xref>]). Almost all industrial systems demand speed, precision, and coordination to operate reliably and provide the required level of automation.</p><fig id="F1" orientation="portrait" position="float"><label>Figure 1</label><caption><p>An internal network divided into two distinct parts, that is, corporate and industrial. The visuals highlight the differences between an industrial OT network and a more regular IT network on specific network levels marked with a number. Level 5 consists of servers and other equipment that have contact with the external network (the Internet), and this fragment should be treated as a demilitarised zone (DMZ). A typical corporate network is considered as 4th level. Office computers and equipment are meant to be localised in this network segment. Level 3 is called the production zone; it stores and processes crucial data that should be protected. Therefore, it might be necessary to distinguish additional DMZ between production and corporate zones. Levels 2, 1, and 0 represent the industrial network that should be desirably disconnected from any other network, although this is not always possible or convenient. Level 2 contains human machine interfaces, monitors, and SCADA operational centres, providing necessary orchestration and supervision over industrial processes. Level 1 is meant for controllers that oversee and send direct commands to sensors and other acting devices located on Level 0 that execute and maintain industrial processes.</p></caption><graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://securityanddefence.pl/f/fulltexts/177655/SDQ-48-00311-g001_min.jpg" xlink:fullhref="https://securityanddefence.pl/f/fulltexts/177655/SDQ-48-00311-g001.jpg"/></fig><p>There are three main industrial communication architectures that will be briefly described, that is, the RS-485 (<xref ref-type="bibr" rid="ref47">Soltero <italic>et al</italic>., 2002</xref>, pp. 3–12), the Controller Area Network (CAN) (<xref ref-type="bibr" rid="ref10">De Andrade <italic>et al</italic>., 2018</xref>), and the Ethernet (<xref ref-type="bibr" rid="ref48">Spurgeon, 2000</xref>, pp. 23–38). Each of these interfaces was developed assuming different limitations and was meant to operate under well-defined but distinct conditions. RS-485 provides serial, fast, and robust communication over a fieldbus, allowing devices to communicate even at longer distances (<xref ref-type="bibr" rid="ref47">Soltero <italic>et al</italic>., 2002</xref>, pp. 3–12). Popular protocols operating in RS-485 include MODBUS remote terminal unit (RTU) (<xref ref-type="bibr" rid="ref38">Modbus Organization Inc., 2012</xref>) and PROFIBUS DP (<xref ref-type="bibr" rid="ref37">Mitchell, 2003</xref>, pp. 1–20). In contrast to RS-485, CAN was designed to work over short distances, and was developed especially for vehicles (cars, trains, planes, etc.). There is one protocol designed for this interface called CANopen (<xref ref-type="bibr" rid="ref6">CAN in Automation [CiA], 2011</xref>). The Ethernet (IEEE 802.3) is the most common interface. The Ethernet allows large amounts of data to be transferred in a relatively short time. Although there are many regular protocols operating on the Ethernet within industrial networks, the basis for the communication relies on dedicated ones, for instance, MODBUS TCP/IP, DNP3, PROFINET IO, and EtherCAT (<xref ref-type="bibr" rid="ref35">Lin and Pearson, 2018</xref>).</p><p>Industrial systems are common and extremely important for everyday life. Examples of industrial networks can be found in critical infrastructure, including power, water, or sewage treatment plants and across many factories. Moreover, industrial communication is essential for building management systems and modern vehicles. Work interruptions within industrial networks may have a wide range of consequences. In some scenarios, outcomes can have some impact on infrastructure functioning, such as wasting an employee's time. However, the real attack scenarios (as any other causes of major failures) can have extreme consequences, including long-lasting blackouts, infrastructure collapse, and loss of life (<xref ref-type="bibr" rid="ref18">Hemsley and Fisher, 2018</xref>). <xref ref-type="table" rid="T1">Table 1</xref> shows selected and well-known examples of attacks on industrial networks.</p><table-wrap id="T1" orientation="portrait" position="float"><label>Table 1</label><caption><p>Examples of successful attacks on industrial infrastructure.</p></caption><table frame="border" rules="groups"><thead valign="top"><tr><th align="left">Incident name</th><th align="center">Short description</th><th align="center">Consequences</th><th align="center">Attack type (threat type)</th></tr></thead><tbody valign="top"><tr><td align="left">PLC password change (Canada, 1988)</td><td align="left">Frustrated employee of Allen-Bradley DH+changed PLC password in different department. This situation led to loss of maintenance access (<xref ref-type="bibr" rid="ref5">Byres <italic>et al</italic>., 2002</xref>).</td><td align="left">Time spent on restoring previous configuration and minor pause in industrial operations (<xref ref-type="bibr" rid="ref5">Byres <italic>et al</italic>., 2002</xref>).</td><td align="left">Sabotage (insider)</td></tr><tr><td align="left">Maroochy Water Incidents (Australia, 2000)</td><td align="left">Ex-worker used stolen equipment (wireless radio, SCADA controller and control software) to control unprotected pumping station (<xref ref-type="bibr" rid="ref45">Slay and Miller, 2008</xref>, pp. 73–82).</td><td align="left">Contamination of river and coastal waters with more than 1,200 m3of untreated sewage that resulted in environmental harm, killing local marine life (<xref ref-type="bibr" rid="ref45">Slay and Miller, 2008</xref>, pp. 73–82).</td><td align="left">Sabotage (insider)</td></tr><tr><td align="left">Tram accidents in ódź (Poland, 2008)</td><td align="left">Teenager constructed a device for remote control of tram line junctions (<xref ref-type="bibr" rid="ref42">Policja.pl, 2008</xref>).</td><td align="left">Four trams were derailed and ten people were injured (<xref ref-type="bibr" rid="ref42">Policja.pl, 2008</xref>).</td><td align="left">Sabotage (external)</td></tr><tr><td align="left">Nuclear programme sabotage* (Iran, 2010)</td><td align="left">Advanced malware (Stuxnet) infecting computers and PLCs developed to sabotage Iranian nuclear programme (<xref ref-type="bibr" rid="ref32">Langner, 2013</xref>).</td><td align="left">Destruction of 20% of Iranian nuclear centrifuges (<xref ref-type="bibr" rid="ref32">Langner, 2013</xref>).</td><td align="left">Sabotage (external)</td></tr><tr><td align="left">German steel mill (Germany, 2014)</td><td align="left">Perpetrators used social engineering to obtain access to internal network and later leveraged the access to industrial network. The attack made it impossible to shut down the furnace (<xref ref-type="bibr" rid="ref33">Lee <italic>et al</italic>., 2014</xref>).</td><td align="left">Whole industrial infrastructure at steel mill suffered major damage (<xref ref-type="bibr" rid="ref33">Lee <italic>et al</italic>., 2014</xref>).</td><td align="left">Sabotage (external)</td></tr><tr><td align="left">Ukrainian power grid*(Ukraine, 2015)</td><td align="left">Multistage attack on three power stations executed by Sandworm team. The attackers got access to network by spear phishing, and learned industrial processes and software. During the attack, power was remotely shut down, telephone lines suffered a DDoS attack, and data was destroyed (<xref ref-type="bibr" rid="ref34">Lee <italic>et al</italic>., 2016</xref>).</td><td align="left">Blackout for up to 6 h, ∼230,000 affected consumers (<xref ref-type="bibr" rid="ref34">Lee <italic>et al</italic>., 2016</xref>).</td><td align="left">Cyberwar (external)</td></tr><tr><td align="left">Colonial Pipeline (USA, 2021)</td><td align="left">Using stolen passwords found on Darknet, perpetrators got access to internal network and downloaded 100 GB of sensitive data. One day later, adversaries deployed ransomware targeting company financial IT system used for billing customers (<xref ref-type="bibr" rid="ref22">Josephs, 2021</xref>).</td><td align="left">The company paid a ransom ($4.4 million) and halted pipeline operation as a precaution. Pipeline recovered after 5 days. Attack resulted in buying panic, altered flight schedules, gas and jet fuel shortages across five states, and even declaration of emergency (<xref ref-type="bibr" rid="ref14">Eaton and Volz, 2021</xref>).</td><td align="left">Cybercrime (external)</td></tr><tr><td align="left">Viasat satellite network*(Ukraine, 2022)</td><td align="left">KA-SAT satellite network was attacked on the day of Russian invasion. Initial access to internal network was gained through exploitation of VPN misconfiguration. Attackers executed legitimate commands that overwrote crucial data in modem memory and made them unable to reconnect with the network (<xref ref-type="bibr" rid="ref52">Viasat Inc., 2022</xref>).</td><td align="left">More than 10,000 modems in Ukraine were disconnected from satellite network. Since KA-SAT is used in the European Union (EU; mainly in Germany), collateral damage was done to 5,800 wind turbines that could not operate temporarily due to lack of network connection (<xref ref-type="bibr" rid="ref3">Burgess, 2022</xref>).</td><td align="left">Cyberwar (external)</td></tr></tbody></table><table-wrap-foot><fn id="TF1-1"><p>Note: *Incidents sponsored or executed by a foreign country’s forces.</p></fn></table-wrap-foot></table-wrap><p>Although attacks on an industrial network may cause enormous damage, these networks are often much less protected than corporate ones. The reasons behind this unintuitive situation are complicated and require some historical context to be understood.</p><p>Before the Internet became widespread, the security setup of industrial infrastructures was based on two falsely assumed premises. The first assumption was that physical access protection is one of the most important lines of defence from external threats. As might be historically true for manual elements of industrial infrastructure (e.g. hand valves andmanual switches) and fully isolated networks, modern infrastructure security cannot be limited to physical access control. Moreover, industrial networks are no longer fully isolated (<xref ref-type="bibr" rid="ref28">Knapp and Langill, 2015</xref>, pp. 41–57). For example, engineering stations have access to both internal corporate network and industrial one. Computers with such configuration might be protected but, in principle, are capable of connecting (e.g. via proxy) to the Internet. Even if the network does not have any external connections, it must still be updated. Therefore, hackers may infect industrial machines using corrupted removal drives or compromised vendors. It is hard not to mention concerns about using new Internet of things (IoT) devices within the industrial networks that may be connected to the Internet and, at the same time, supervise the industrial process (<xref ref-type="bibr" rid="ref20">Jayalaxmi <italic>et al</italic>., 2021</xref>). The second false assumption was that industrial systems are difficult to comprehend, since information about them is very hard to obtain (security by obscurity; <xref ref-type="bibr" rid="ref1">Alcaraz <italic>et al</italic>., 2012</xref>, pp. 120–149). This is no longer true, since it is possible to download for free, buy from legitimate vendors, or obtain from illegal sources industrial documentation and the specifications of almost any used industrial technology. Being in possession of large financial assets or sponsored by government, groups of hackers may even build entire industrial test laboratories. The number of industrial cybersecurity incidents was hard to notice in the last century. For example, the <xref ref-type="bibr" rid="ref44">Repository of Industrial Security Incidents (RISI, 2015)</xref> includes only thirty-two attacks or occurrences of sabotage in automated industrial systems for the whole 20th century. This resulted in a false perception of threats, bad security practices, lack of attention, and investment in industrial control systems protection (<xref ref-type="bibr" rid="ref28">Knapp and Langill, 2015</xref>, pp. 41–57).</p><p>There are other reasons behind security holes in industrial control systems. Industrial networks often have to optimise speed and efficiency of communication by design, leaving limited options for security solutions (<xref ref-type="bibr" rid="ref41">Pei <italic>et al</italic>., 2018</xref>). For example, it is common to switch off encryption and additional confirmations, since such options slow down repose time. Moreover, older devices have limited or obsolete security functions. Some devices may not allow the creation of strong passwords, since they do not possess the required memory capacity to store enough information (<xref ref-type="bibr" rid="ref28">Knapp and Langill, 2015</xref>, pp. 41–57).</p><p>Usage of technical standards is unavoidable in industrial systems. They are used to facilitate integration, enforce compatibility, and quality of equipment as well as unification of communication technology offered by multiple vendors. It is not uncommon for standards to have some minor misfits with the exact needs of specific industrial infrastructure. This can make custom standard extensions seem viable, but also lead to security issues as a consequence. Furthermore, implementation of industrial standards can be flawed and adopt protective solutions poorly or insufficiently. If a standard is oblivious to certain existing threats, it may lead to much more dangerous situations in which standard vulnerabilities are exploited (<xref ref-type="bibr" rid="ref16">Hajda <italic>et al</italic>., 2021</xref>).</p><p>The high cost of halting industrial processes is a serious issue. Unscheduled operational pauses are able to seriously affect industrial safety. In fact, there are critical infrastructures that cannot be easily stopped from operating, and maintenance breaks must be carefully planned to preserve work continuity. This situation makes software and equipment security updates problematic, since planning and coordination are needed (<xref ref-type="bibr" rid="ref31">Kumar <italic>et al</italic>., 2022</xref>). Due to such constraints, security updates tend to be neglected or postponed. Furthermore, expensive investments in industrial machines and devices often assume long exploitation time (e.g. 20 years for controllers; <xref ref-type="bibr" rid="ref4">Byres, 2013</xref>). On the one hand, industrial devices are able to operate for a considerable number of years, but on the other, progress in technology is so fast that new devices become obsolete within years. Many industries are not able to afford to replace all vulnerable devices and must rely on them, trying to strengthen the security in other places. This creates a dangerous situation in which there are many devices that are potential targets for hackers within the industrial network and none of them can be replaced for financial reasons (<xref ref-type="bibr" rid="ref4">Byres, 2013</xref>).</p><p>Security incidents in industrial networks may affect vital processes and infrastructure, which may lead to severe consequences. Therefore, it is important to prevent unwanted events and counteract them, if possible. The majority of problems and blind spots in security within industrial infrastructure can be eliminated by careful management and deploying recommended security policies (<xref ref-type="bibr" rid="ref50">Taherdoost, 2022</xref>).</p></sec><sec id="S3"><title>SCADvanceXP—An innovative system specifically for industrial network protection</title><p>SCADvanceXP is a new real-time intrusion detection system developed in Poland to ensure the safety of industrial networks (<xref ref-type="bibr" rid="ref19">ICsec S.A., n.d.</xref>). The system was designed to fit a wide range of industrial designs, including many different networks operating in energy, manufacturing, production, or water treatment as long as there is an industrial control system to protect. The core role of SCADvanceXP is to monitor industrial network traffic and detect undesired or unusual events. There are many methods for anomaly detection embedded within SCADvanceXP analytics, including event processing, rule and signature detectors, statistical and machine-learning models, and physical process monitoring. As a fully functional and mature system, it can adapt to specific industrial network infrastructures in order to strengthen the ability to detect unwanted events. SCADvanceXP’s main goal is to detect cyber threats (including Zero-Day threats) before they cause irreversible damage.</p><p>The origins of the SCADvanceXP system come from the research project SCADvance (SCADA Advance) (<xref ref-type="bibr" rid="ref12">Dobski <italic>et al</italic>., 2018</xref>). The aim of the SCADvance R&amp;D project was to develop methods and solutions increasing the security of industrial networks, especially for companies in the electric power industry. The R&amp;D project was conducted by ALMA S.A. (a beneficiary of the co-financed EU programme) and several renowned partners, including the Poznan Supercomputing and Networking Centre and Poznan University of Technology. The R&amp;D project ended with a fully functional prototype (VI TRL level). Based on the promising results of the R&amp;D project, the ICsec S.A. company designed the market-ready product, marketed it, and further developed and supported it afterwards.</p><p>ICsec S.A. conducted two R&amp;D projects co-financed from EU funds within Smart Growth Operational Programme 2014–2020 that were aimed at further development of SCADvanceXP functionalities. First one, the SMUAP project (pl.: System monitoringu urządzeń automatyki przemysłowej - Industrial Automation Equipment Monitoring System) was focused on AI/ML module development, vulnerability checking, universal network sniffer (hardware and software). The second project - IDS Utilities (Development of the IDS system for OT in terms of the requirements of the public utility sector) was focused on managing the security of third-party communication protocols, which are used in SCADA drivers and programs. The project was especially focused on tracking physical values through Deep Packet Inspection (DPI) sent by industrial protocols and the use of the SBOM (software bill of materials) standard to extend the vulnerability checker module. The IDS Utilities project also introduced proxy servers as part of SCADvanceXP system that are allow for distributed computing on selected parts of the network.</p><p>SCADvanceXP processes raw traffic collected by X1 probes installed in an industrial network. Probes were carefully designed to efficiently and reliably transfer data over the Ethernet (SPAN port and pass through), RS232/422/485 and CAN interfaces. These devices are also able to calculate fundamental traffic statistics based on embedded software. The important security feature of probes is a galvanic separation of sniffing listening that in practice makes bidirectional transmission impossible as well as any electromagnetic interference between the IT and OT sides related to the device. Therefore, the SCADvanceXP system is fully passive and unable to interfere with industrial processes and communication within the existing infrastructure of the OT network. In addition to that, thanks to its ability to work in a “transparent” or “SPAN port” mode, it is possible to install the X1 probe in all of the most complex configurations of industrial network topologies.</p><p>Time is the most important asset in industrial process automation, since rapid reaction to sudden changes may prevent irreversible losses and system failures. SCADvanceXP addresses this requirement by putting all the effort in making continuous monitoring and analysis as fast as possible and it qualifies as a real-time system. SCADvanceXP has many innovative functionalities that include asset management and inventory monitoring, industrial traffic analysis, and anomaly detection with a focus on cyber threats, vulnerability scanning, physical process monitoring, and incident management. To provide more details, each enumerated functionality is briefly described below.</p><p>Inventory awareness is essential for efficient network protection. The SCADvanceXP system detects devices connected to the protected network based on the observed traffic and creates a map of connections between devices in the network. Hence, any changes in communication architecture or device inventory can be easily spotted. With an automatically created OT network topological map, a user may study details about devices and data exchange to safely correct the configuration of industrial devices and ensure a network’s operational integrity. To give more concrete examples, the SCADvanceXP system reacts if a new device appears in the network, an existing device vanishes, or in the case of packet exchange between devices that should not communicate. However, the SCADvanceXP system was designed to be passive; therefore, it cannot exclude or block devices within an industrial network.</p><p>SCADvanceXP is focused simultaneously on many details and dimensions of industrial communication. The key advantage of this system is its analytical engine. The analytical capabilities of SCADvanceXP are supported by multiple mechanisms, including rule-based methods, signature-based methods, and <italic>Artificial Intelligence</italic> (AI)/ML methods for anomaly-based detection.</p><p>SCADvanceXP uses complex mechanisms to adapt and adjust anomaly detection models. There are three major types of AI-based anomaly detection techniques operating in the system: statistical modelling, prognostic machine-learning, and deep neural networks. These techniques are complementary to each other, and furthermore, the system does have methods to integrate all the results and present coherent information. The system has automated mechanisms based on advanced optimisation to increase anomaly detection efficiency for users with limited hardware resources.</p><p>Along with machine-learning models, SCADvanceXP employs standard and well-established methods for threat detection, namely rule and signature matching. Such methods are obligatory and allow known dangers to be detected. It is possible to define threats and search for malicious activity traces that have been found and defined in other industrial networks. These methods may also be used to notify the user of suspicious packets (e.g. execution of rare commands on industrial devices) or simply any event of interest, not necessarily related to security issues. As can be seen, SCADvanceXP has enormous potential in event and anomaly detection, since it is able to encompass information about patterns of communication and learn details about network behaviour.</p><p>The SCADvanceXP system is integrated with <xref ref-type="bibr" rid="ref9">Common Vulnerabilities and Exposures (CVE Program, n.d.)</xref> and Common Platform Enumeration (CPE) databases; therefore, it is able to detect known vulnerabilities. Thanks to this functionality, it is possible to prevent security incidents by making necessary security updates and hardening or replacing all outdated devices that could easily become a target for hackers. This feature is very important, since incident prevention is much less costly than restoring damaged infrastructure.</p><p>Another feature of SCADvanceXP is its ability to monitor physical process values. This trait is unique, since only the SCADA system and industrial devices are able to send and read requests. However, based on industrial standards, the SCADvanceXP system is able to decode user-defined variables with a dedicated module. Since the behaviour of industrial variables can be monitored, changes and unwanted variable values can be quickly reported to the users. Thanks to the fact that SCADvanceXP operates passively, it cannot interfere with industrial processes. Moreover, detection of SCADA failures is also possible. It is worth mentioning that many attacks on industrial networks are stealthy, meaning they use many means to hide their traces from SCADA systems, for example, by deploying replay attacks, disabling alerts, or misconfiguring SCADA to deceive an operator (<xref ref-type="bibr" rid="ref27">Kleinmann <italic>et al</italic>., 2018</xref>, pp. 93–109; <xref ref-type="bibr" rid="ref30">Krotofil <italic>et al</italic>., 2015</xref>, pp. 133–144; <xref ref-type="bibr" rid="ref36">Liu <italic>et al</italic>., 2011</xref>).</p><p>In addition to process value monitoring, SCADvanceXP is capable of deep packet inspection. Thanks to deep learning models, the system can learn packet features to detect distortions, unusual transmission patterns, or massage content changes without the necessity of decoding message payload.</p><p>SCADvanceXP is not only capable of security incident detection but can also help coping with it. First of all, SCADvanceXP possesses forensic tools to help study timeline of events related to the incident. Moreover, SCADvanceXP is able to present network elements involved in attack and point to associated anomalies. All of this information may help in managing the incident, showing all exploited system elements that need to be handled as well as elements within the network that may not operate correctly.</p></sec><sec id="S4"><title>Assessment of SCADvanceXP threat detection capability potential</title><p>Industrial networks are exposed to many dangerous threats. It is difficult to assess how currently known threats may be detected by any system. The following analysis is based on assumptions and available knowledge. The goal of this analysis was to evaluate detection potential for twelve commonly occurring malware strains and variants. Since well-documented malware samples are taken into evaluation, it is possible to connect SCADvanceXP detection potential with infection indicators of malware samples.</p><p>The malware picked for the analysis is summarised briefly in <xref ref-type="table" rid="T2">Table 2</xref>. All analysed samples were described in more detail, pointing to specific markers of malicious activity that could be potentially detected by the current version of the SCADvanceXP system. In order to provide more concrete and specific analysis, Industroyer malware was chosen as a representative example and its detection potential was described extensively. Based on this example, a better explanation of SCADvanceXP detection power could be presented in the context of other threats.</p><table-wrap id="T2" orientation="portrait" position="float"><label>Table 2</label><caption><p>Malicious software that are known to interfere with industrial control systems reported in Central and Eastern Europe.</p></caption><table frame="border" rules="groups"><thead valign="top"><tr><th align="left">Malware strain</th><th align="center">Short description</th><th align="center">Attacked countries</th><th align="center">SCADvanceXP detection potential</th></tr></thead><tbody valign="top"><tr><td align="left">BlackEnergy</td><td align="left">Malicious software toolkit known from Russian conflicts. Originally DDoS tool, upgraded over time to inflict damage and spy (<xref ref-type="bibr" rid="ref25">Khan <italic>et al</italic>., 2016</xref>, pp. 1–11).</td><td align="left">Ukraine and Georgia</td><td align="left">Yes</td></tr><tr><td align="left">GreyEnergy</td><td align="left">Successor of BlackEnergy malware with ability to exploit more backdoors (<xref ref-type="bibr" rid="ref11">Di Pinto [Nozomi Networks], 2019</xref>).</td><td align="left">Poland and Ukraine</td><td align="left">Yes</td></tr><tr><td align="left">Industroyer</td><td align="left">Malware dedicated to inflict damage in industrial systems, especially electrical substations (<xref ref-type="bibr" rid="ref24">Kapellmann-Zafra <italic>et al</italic>., 2022</xref>).</td><td align="left">Ukraine</td><td align="left">Yes</td></tr><tr><td align="left">PipeDream</td><td align="left">Sophisticated malware toolkit able to attack various industrial infrastructures (<xref ref-type="bibr" rid="ref17">HeadMind Partners, 2022</xref>).</td><td align="left">Unknown (Ukraine?)</td><td align="left">Yes</td></tr><tr><td align="left">Conflicker</td><td align="left">Worm that was responsible for shutting down a German nuclear power plant in 2016 (<xref ref-type="bibr" rid="ref51">Trend Micro Inc., 2016</xref>).</td><td align="left">Germany, Global</td><td align="left">Non-applicable</td></tr><tr><td align="left">NotPetya</td><td align="left">Wiper created to destroy IT infrastructure in Ukraine (<xref ref-type="bibr" rid="ref15">Greenberg, 2018</xref>).</td><td align="left">Ukraine, Poland, and Europe</td><td align="left">Non-applicable</td></tr><tr><td align="left">Conti</td><td align="left">Ransomware attacking different targets around the world (<xref ref-type="bibr" rid="ref8">Cimpanu, 2020</xref>).</td><td align="left">Ukraine, EU, and USA</td><td align="left">Non-applicable</td></tr><tr><td align="left">EKANS</td><td align="left">Ransomware targeting popular ICS software frameworks (e.g. Honeywell HMIWeb or GE PROFICY) (<xref ref-type="bibr" rid="ref2">Belding, 2020</xref>).</td><td align="left">EU and USA</td><td align="left">Non-applicable</td></tr><tr><td align="left">STUXnet</td><td align="left">Worm designed to sabotage industrial processes and exploiting Siemens Step7 PLCs (<xref ref-type="bibr" rid="ref32">Langner, 2013</xref>).</td><td align="left">Iran, Global</td><td align="left">Yes</td></tr><tr><td align="left">Duqu</td><td align="left">Closely related to STUXnet malicious espionage worm used to prepare future attacks (<xref ref-type="bibr" rid="ref40">Paganini, 2019</xref>).</td><td align="left">Austria, Russia, and Switzerland</td><td align="left">Yes</td></tr><tr><td align="left">Havex</td><td align="left">Espionage tool that affected thousands of victims in whole energy sector, including solution providers (<xref ref-type="bibr" rid="ref46">Slowik, 2021</xref>).</td><td align="left">Europe, Canada, and USA</td><td align="left">Yes</td></tr><tr><td align="left">Triton</td><td align="left">Malicious framework for exploitation of Triconex Safety Instrumented System controllers (<xref ref-type="bibr" rid="ref21">Johnson <italic>et al</italic>., 2017</xref>).</td><td align="left">Europe, Canada, and USA</td><td align="left">Yes</td></tr></tbody></table><table-wrap-foot><fn id="TF2-1"><p>Note: Only the most common and dangerous malware strains were picked for evaluation of the SCADvanceXP detection potential. The caption “Non-applicable” was used to mark examples of malware that do not interfere directly with industrial networks.</p></fn></table-wrap-foot></table-wrap><p>In order to evaluate the detectability potential of SCADvanceXP modules, twenty defined malicious actions were picked and associated with selected malware strains. <xref ref-type="table" rid="T3">Table 3</xref> shows the connections and how different malware strains can interfere with industrial networks. For each malicious action, the detectability potential by SCADvanceXP was also determined. The detection potential of every SCADvanceXP module was evaluated for each malicious capability defined in <xref ref-type="table" rid="T4">Table 4</xref>. Additionally, the same information was added for the IT security solution for corporate networks that are not able to analyse industrial networks and devices.</p><table-wrap id="T3" orientation="portrait" position="float"><label>Table 3</label><caption><p>Selected capabilities of malware strains chosen in this study.</p></caption><table frame="border" rules="groups"><thead valign="top"><tr><th align="left">Malicious action</th><th align="center">Black<break/>Energy</th><th align="center">Grey<break/>Energy</th><th align="center">Industroyer</th><th align="center">Pipe<break/>Dream</th><th align="center">Conflicker</th><th align="center">Not<break/>Petya</th><th align="center">Conti</th><th align="center">EKANS</th><th align="center">STUXnet</th><th align="center">Duqu</th><th align="center">Havex</th><th align="center">Triton</th></tr></thead><tbody valign="top"><tr><td align="left">Disruptions to ICS operations</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center"/><td align="center">X</td><td align="center">X</td></tr><tr><td align="left">Windows workstation corruption</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td></tr><tr><td align="left">Industrial network scanning</td><td align="center">X</td><td align="center"/><td align="center">X</td><td align="center">X</td><td align="center"/><td align="center">X</td><td align="center"/><td align="center"/><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td></tr><tr><td align="left">Propagation within industrial networks</td><td align="center"/><td align="center"/><td align="center"/><td align="center">X</td><td align="center"/><td align="center">X</td><td align="center"/><td align="center"/><td align="center">X</td><td align="center"/><td align="center">X</td><td align="center"/></tr><tr><td align="left">Vulnerable device profiling</td><td align="center"/><td align="center"/><td align="center">X</td><td align="center">X</td><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center">X</td><td align="center">X</td><td align="center"/><td align="center">X</td></tr><tr><td align="left">Manipulation of industrial devices (including register values and commands)</td><td align="center">X</td><td align="center"/><td align="center">X</td><td align="center">X</td><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center">X</td><td align="center"/><td align="center"/><td align="center">X</td></tr><tr><td align="left">Industrial traffic and payload manipulation</td><td align="center"/><td align="center"/><td align="center">X</td><td align="center">X</td><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center">X</td><td align="center"/><td align="center"/><td align="center">X</td></tr><tr><td align="left">Industrial DoS attacks</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center"/></tr><tr><td align="left">Password brute force on PLC</td><td align="center"/><td align="center"/><td align="center">X</td><td align="center">X</td><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center"/></tr><tr><td align="left">Industrial network traffic recording</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center">X</td><td align="center"/><td align="center"/><td align="center"/></tr><tr><td align="left">Destruction of data on industrial devices</td><td align="center"/><td align="center"/><td align="center">X</td><td align="center">X</td><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center"/></tr><tr><td align="left">Modification of project and configuration files</td><td align="center"/><td align="center"/><td align="center">X</td><td align="center">X</td><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center">X</td><td align="center"/><td align="center"/><td align="center">X</td></tr><tr><td align="left">Manipulation of view</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center">X</td><td align="center"/><td align="center"/><td align="center">X</td></tr><tr><td align="left">Loss of view</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center"/><td align="center"/><td align="center"/></tr><tr><td align="left">ICS-related processes killing</td><td align="center"/><td align="center"/><td align="center">X</td><td align="center">X</td><td align="center"/><td align="center">X</td><td align="center"/><td align="center">X</td><td align="center">X</td><td align="center"/><td align="center"/><td align="center">X</td></tr><tr><td align="left">Remote connection to C&amp;C</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center"/><td align="center">X</td><td align="center"/><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center"/></tr><tr><td align="left">Local network scanning</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td></tr><tr><td align="left">Data exfiltration</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center"/><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td></tr><tr><td align="left">Propagation within network</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td></tr><tr><td align="left">System process modification and injection</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center"/></tr></tbody></table><table-wrap-foot><fn id="TF3-1"><p>Note: The list of 20 capabilities is not exhaustive, but it provides a general overview on malicious actions performed by different malware strains evaluated in this work. Each malware strain that is able to exhibit defined malicious behaviour is marked with “X” in the respective row.</p></fn></table-wrap-foot></table-wrap><table-wrap id="T4" orientation="portrait" position="float"><label>Table 4</label><caption><p>Detectability of selected malicious capabilities by SCADvanceXP and regular IT security solutions.</p></caption><table frame="border" rules="groups"><thead valign="top"><tr><th align="left">Malicious action</th><th align="center">Asset management and inventory monitoring</th><th align="center">Industrial traffic monitoring and anomaly detection (AI)</th><th align="center">Process value monitoring</th><th align="center">Vulnerability scanning</th><th align="center">Deep packet inspection</th><th align="center">Signature matching</th><th align="center">Modern IT security solutions</th></tr></thead><tbody valign="top"><tr><td align="left">Disruptions to ICS operations</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center"/></tr><tr><td align="left">Windows workstation corruption</td><td align="center">X</td><td align="center"/><td align="center"/><td align="center">X</td><td align="center"/><td align="center">X</td><td align="center">X</td></tr><tr><td align="left">Industrial network scanning</td><td align="center">X</td><td align="center">X</td><td align="center"/><td align="center"/><td align="center"/><td align="center">X</td><td align="center"/></tr><tr><td align="left">Propagation within industrial networks</td><td align="center">X</td><td align="center">X</td><td align="center"/><td align="center">X</td><td align="center"/><td align="center">X</td><td align="center"/></tr><tr><td align="left">Vulnerable device profiling</td><td align="center">X</td><td align="center">X</td><td align="center"/><td align="center">X</td><td align="center"/><td align="center">X</td><td align="center"/></tr><tr><td align="left">Manipulation of industrial devices (including register values and commands)</td><td align="center"/><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center"/></tr><tr><td align="left">Industrial traffic and payload manipulation</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center"/></tr><tr><td align="left">Industrial DoS attacks</td><td align="center">X</td><td align="center">X</td><td align="center"/><td align="center"/><td align="center"/><td align="center">X</td><td align="center"/></tr><tr><td align="left">Password brute force on PLC</td><td align="center"/><td align="center">X</td><td align="center"/><td align="center">X</td><td align="center"/><td align="center">X</td><td align="center"/></tr><tr><td align="left">Industrial network traffic recording</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center"/><td align="center">X</td><td align="center">X</td><td align="center"/></tr><tr><td align="left">Destruction of data on industrial devices</td><td align="center"/><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center">X</td><td align="center"/></tr><tr><td align="left">Modification of project and configuration files</td><td align="center">X</td><td align="center"/><td align="center">X</td><td align="center">X</td><td align="center"/><td align="center">X</td><td align="center"/></tr><tr><td align="left">Manipulation of view</td><td align="center"/><td align="center">X</td><td align="center">X</td><td align="center"/><td align="center">X</td><td align="center">X</td><td align="center"/></tr><tr><td align="left">Loss of view</td><td align="center"/><td align="center">X</td><td align="center">X</td><td align="center"/><td align="center">X</td><td align="center">X</td><td align="center"/></tr><tr><td align="left">ICS-related processes killing</td><td align="center">X</td><td align="center">X</td><td align="center"/><td align="center"/><td align="center"/><td align="center">X</td><td align="center"/></tr><tr><td align="left">Remote connection to C&amp;C</td><td align="center">X</td><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center">X</td></tr><tr><td align="left">Local network scanning</td><td align="center">X</td><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center">X</td></tr><tr><td align="left">Data exfiltration</td><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center">X</td></tr><tr><td align="left">Propagation within network</td><td align="center">X</td><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center"/><td align="center">X</td></tr><tr><td align="left">System process modification and injection</td><td align="center"/><td align="center"/><td align="center"/><td align="center">X</td><td align="center"/><td align="center"/><td align="center">X</td></tr></tbody></table><table-wrap-foot><fn id="TF4-1"><p>Note: For each distinguished SCADvanceXP module (in columns), the letter “X” appeared for every malicious action (in rows) it can detect. The last column contained general modern IT solutions (e.g. firewalls and antiviral software) that operate in corporate networks.</p></fn></table-wrap-foot></table-wrap><p>Industroyer (or CRASHOVERRIDE) is a malicious framework that is known from one of the most infamous cyber attacks affecting power grid systems, which took place in Ukraine on 17 December 2016 (<xref ref-type="bibr" rid="ref7">Cherepanov and Lipovsky, 2018</xref>). The attack was thoroughly prepared, with extensive knowledge of the industrial-type communication network. Effectively carried out attacks and malware development is attributed to the notorious Sandworm team (<xref ref-type="bibr" rid="ref13">Dragos Inc., n.d.</xref>). Industroyer was an attempt to automate attacks on power grids, executed manually by the same team a year before (<xref ref-type="bibr" rid="ref34">Lee <italic>et al</italic>., 2016</xref>). An updated version of this malware still exists, namely Industroyer 2, which has been used to execute attacks in 2022 on Ukrainian power grid systems (<xref ref-type="bibr" rid="ref24">Kapellmann-Zafra <italic>et al</italic>., 2022</xref>).</p><p>The Industroyer attack vector, which might also be considered as an exemplary case for the methods used in other OT attacks, consists of several components. The first, allowing for general intrusion, was an installation of the malware on the main SCADA server, breaking through by spear phishing. The main backdoor was then supported by installation of an additional backdoor—letting the attackers keep control over the SCADA server while the main backdoor was out of order. These pair of backdoors enabled an obscure connection with the attackers’ Control &amp; Command system and execution of the next attack steps. However, the proper monitoring of the system topology, as is done by the SCADvanceXP EWL module, discovers the appearance of new Internet protocols (IPs) for which new regular connections have been established by means of passive packet monitoring. It raises one of the first security alerts generated by the intrusion detection system (IDS).</p><p>Secondly, the attacker scans for the presence of other supervisory computers (master stations for RTUs or PLCs), and when they are discovered installs the launcher malware and protocol-specific libraries. Industroyer toolbox had a specialised network mapping tool for scanning network topology. The act of scanning leaves a trace in the network activity log in the form of sent packets and can be detected by IDS tools, such as SCADvanceXP.</p><p>Once the launcher is installed on one or many supervisory computers, which gather data and sent control commands to RTUs or PLCs, execution of malicious commands becomes possible, including scanning and modifying the register values and functions sent to terminal devices.</p><p>The Industroyer was designed to modify the payloads of the packets transmitted within four industrial protocols: (1) IEC 60870-5-101, (2) IEC 60870-5-104, (3) IEC 61850, and (4) OLE for process control data access (<xref ref-type="bibr" rid="ref24">Kapellmann-Zafra <italic>et al</italic>., 2022</xref>). This is an important and advanced feature making it possible for this malware to directly interfere with industrial network communication. Physical value monitoring (PVM) is part of the SCADvanceXP system for monitoring the variable values defined by the user specification of register addresses and values format on RTU. In the family of IEC protocols for power system automation, the RTU registers are called Application Service Data Unit (ASDU) and referring pointers are called Information Object Addresses (OAs). The dedicated malware installed by the main door launcher altered the values in ASDU (<xref ref-type="bibr" rid="ref24">Kapellmann-Zafra <italic>et al</italic>., 2022</xref>). The SCADvanceXP system allows the constant monitoring of these values. PVM raises alerts when user-defined limits are exceeded. It might be a powerful tool for securing OT infrastructures, although it requires the active participation of human beings (security officers) in defining the registers to be monitored. The step forward is the automatic detection of anomalous behaviour applied in AI modules.</p><fig id="F2" orientation="portrait" position="float"><label>Figure 2</label><caption><p>Photo of the SCADvanceXP desktop screen and the X1 probe (provided by <xref ref-type="bibr" rid="ref19">ICsec S.A. [n.d.]</xref>).</p></caption><graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://securityanddefence.pl/f/fulltexts/177655/SDQ-48-00311-g002_min.jpg" xlink:fullhref="https://securityanddefence.pl/f/fulltexts/177655/SDQ-48-00311-g002.jpg"/></fig><fig id="F3" orientation="portrait" position="float"><label>Figure 3</label><caption><p>Graphic showing SCADvanceXP deployment within industrial network.</p></caption><graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://securityanddefence.pl/f/fulltexts/177655/SDQ-48-00311-g003_min.jpg" xlink:fullhref="https://securityanddefence.pl/f/fulltexts/177655/SDQ-48-00311-g003.jpg"/></fig><p>One of the most advanced and novel techniques for OT network monitoring is the usage of machine learning for detecting the anomalous behaviour of the systems. This might be manifested by rapid and significant change of patterns in data exchange dynamics given by network traffic. The starting point is a definition of the typical behaviour of a network or its components—sub-networks and individual connections. The claim is that each installation, composed of configured, node devices (servers and RTUs) of closed set manufactures running in operation, exhibits typical patterns that can be monitored and characterised by passive systems, such as SCADvanceXP. On the one hand, the choice of features which describe those patterns is a subject of expert research and is based on the packet content, all of which is readable, might be a constituent of the feature. On the other hand, the passiveness of the cybersecurity system limits the number of detection methods for threats. The packet content can be read out in explicit mode for depicting basic information defined in protocol specification (such as the MAC addresses, protocols of existing layers, IP addresses, and many others). Simultaneously, the packet or series of packets might be treated as an encapsulated portion of information and described by its external or non-encoded parameters. The ones which are often reliable are frequency of packets, time interval between packets, packet (or payload) length, and payload entropy. SCADvanceXP uses this information (and more) to learn network behaviour and report anomalies based on machine-learning models.</p><p>In the event of an Industroyer attack, the RTUs were affected with the usage of four low-level malicious codes (DLLs) executed by the launcher installed directly by the main backdoor malware: (1) 101 payload, (2) 104 payload, (3) 61850 payload, and (4) OPC DA payload (<xref ref-type="bibr" rid="ref24">Kapellmann-Zafra <italic>et al</italic>., 2022</xref>). The goal of the first one, 101 payload (named after IEC 60870-5-101 protocol) was to interact with all discovered IOAs (information data object) on a given RTU, and switch their state between off and on. Such an abnormal way of functioning clearly manifested in the modification of the interaction frequency of controlling and controlled stations and, to some extent, in packet payload contact, thus in its entropy and length. The alteration of those features can be detected by the AI models employed in the SCADvanceXP system, even though they are subtle and dispersed in the entire phase space of features. The system is capable of precisely defining and configuring the volume (the subspace) for the proper detection of anomalies while keeping control over the number of false positives cases.</p><p>The SCADvanceXP cybersecurity system is also equipped with a vulnerability checker module. The principal functionality of the module is directed towards detection, identification, and information about the devices and services present in the network, which might be vulnerable for malicious software installations. The module is combined with a large CVE Program (n.d.) database and CPE database issued by the <xref ref-type="bibr" rid="ref39">National Institute of Standards and Technology (n.d.)</xref> organisation and updated continuously. These databases contain the list of all platforms (i.e. the operating systems, software, services, devices) in which vulnerability has been identified. The CVE lists those vulnerabilities and refers to the recommended actions which have to be taken to secure the system. The list of platforms existing in the network and assigned to the network nodes is created automatically by the SCADvanceXP system and aligned with CPE and CVE datasets.</p><p>It is known that the Industroyer toolbox also contains malware exploiting a vulnerability tagged as CVE-2015-5374, already known at the time of the attack, and part of the Siemens SIPROTEC device. It calls up the Denial of Service function, after which a manual reboot of the device is required.</p><p>Industroyer was able to cause a blackout for less than 2 hours in 2016 (<xref ref-type="bibr" rid="ref7">Cherepanov and Lipovsky, 2018</xref>). Since then, it has been upgraded and in April 2022, a new malware toolkit was discovered related to Industroyer, namely Pipedream (also known as Chernovite and Incontroller) (<xref ref-type="bibr" rid="ref17">HeadMind Partners, 2022</xref>). Both of them are designed to attack a wide range of industrial networks, spy on them, and sabotage or directly damage them by sending crafted messages created to resemble valid commands. Pipedream tools are able to modify payloads of the packets transmitted within many industrial protocols and probably many more malicious actions. In this case, vulnerable devices include Schneider Electric PLCs, OMRON Sysmac NEX PLCs, and Open Platform Communications Unified Architecture (OPC UA) servers (<xref ref-type="bibr" rid="ref17">HeadMind Partners, 2022</xref>). The SCADvanceXP system was designed to detect unique and advanced threats similar to this. Both Industroyer and Pipedream perform malicious actions that by their very nature must interfere with industrial network communication and devices. The methods employed by SCADvanceXP quickly track and report such interference as suspicious behaviour or directly disclose it as a confirmed incident.</p><p>Since Industroyer was described in such detail, the rest of the threats are summarised briefly, especially in the case of regular malware attacking industrial infrastructure. Ransomware and wipers (Conflicker, NotPetya, Conti, and EKANS) affecting operator computer stations are beyond the detection capabilities of SCADvanceXP. Since only attack consequences can be detected (such as loss of the command centre), SCADvanceXP does not detect these forms of malware.</p><p>Conflicker is a computer worm affecting computers running on Windows OS. Although this malware is not designed to interfere with industrial control systems, it can halt whole industrial infrastructure. This happened in 2016, when a German nuclear power plant was shut down due to the Conflicker virus being found in the engineering station, which could be under the control of remote malefactors (<xref ref-type="bibr" rid="ref51">Trend Micro Inc., 2016</xref>).</p><p>NotPetya is a wiper specially designed to attack Ukrainian facilities, including companies, factories, and critical infrastructure. NotPetya spreads quickly and pretends to encrypt the memory of infected computers; however, in reality, data is also modified, making recovery impossible. The activity of this piece of malware can lead to the shutting down of large industrial infrastructures (e.g. the MAERSK incident), since ICS stations, servers, business, and other crucial items for computer operation are completely neutralised (<xref ref-type="bibr" rid="ref15">Greenberg, 2018</xref>).</p><p>Conti is a widespread malware strain that operates in the form of Ransomware-as-a-Service (RaaS). Conti steals and encrypts sensitive or information crucial for business. As in the case of NotPetya, attacks on crucial IT equipment can in consequence affect industrial processes (<xref ref-type="bibr" rid="ref8">Cimpanu, 2020</xref>).</p><p>EKANS is the ransomware strain that hides and encrypts infected computers. It can masquerade as a proper update file and is designed to target computers connected to industrial networks. EKANS has a hardcoded list of processes to kill that enumerates GE Proficy and Honeywell HMIWeb services. This malware strain was detected in the Honda manufacturing plant, causing production losses (<xref ref-type="bibr" rid="ref2">Belding, 2020</xref>).</p><p>BlackEnergy is another malicious toolkit, known since the Georgian conflict (<xref ref-type="bibr" rid="ref49">Stewart, 2010</xref>). It is suspected that the infamous Sandworm team created it to interfere with energy grids (<xref ref-type="bibr" rid="ref25">Khan <italic>et al</italic>., 2016</xref>, pp. 1–11). Upgraded versions of BlackEnergy were deployed in Ukraine during power grid attacks in 2015 (<xref ref-type="bibr" rid="ref25">Khan <italic>et al</italic>., 2016</xref>, pp. 1–11). A new updated successor version of this malware strain is called GreyEnergy (<xref ref-type="bibr" rid="ref11">Di Pinto [Nozomi Networks], 2019</xref>). These malware toolkits serve to facilitate unauthorised access to the operator station, steal data, and take control via a remote desktop client. Since SCADvanceXP operates inside the industrial network, it is not possible to detect BlackEnergy and GreyEnergy on regular Windows computers. However, SCADvanceXP does detect any action executed from an infected operator workstation. This type of threat is similar to insider attacks and the SCADvanceXP system is programmed to report malicious and untypical actions performed by privileged users, including data acquisition as well as changes made in industrial process control (even ineffective ones).</p><p>One of the most notorious examples of malware used to compromise and inflict damage to industrial control systems is STUXNET. Designed to slow down and sabotage the Iranian nuclear programme, STUXNET was successfully planted at Natanz nuclear facility (<xref ref-type="bibr" rid="ref32">Langner, 2013</xref>). At the time, some considered this malware to be state-of-the-art within the industrial sector. Along with many capabilities, STUXNET was able to self-replicate, check the type of machine it was working on, and adjust its behaviour. STUXNET could download updates for itself from a remote server and attack specific industrial devices (PLC). Interfering with industrial processes, STUXNET was able to change control commands to uranium centrifuges and, at the same time, replay previously recorded data to SCADA in order to hide the malicious act of sabotage (<xref ref-type="bibr" rid="ref32">Langner, 2013</xref>).</p><p>Duqu is a version of STUXNET that was upgraded mainly for espionage purposes (<xref ref-type="bibr" rid="ref40">Paganini, 2019</xref>). In contrast to Stuxnet, Duqu does not possess modules to directly interfere with the industrial process, since it serves only for sensitive data theft and collection of material that helps in preparation of future attacks. Duqu is also programmed to self-delete after 36 days (<xref ref-type="bibr" rid="ref40">Paganini, 2019</xref>). Since STUXNET is able to interfere with the industrial network, it can be detected by SCADvanceXP machine-learning modules; this, however, cannot be said for Duqu, which operates on a higher level. Nonetheless, Duqu can be recognised by rule-based mechanisms embedded in SCADvanceXP’s functionality.</p><p>Havex or Backdooroldrea is a Remote Access Trojan (RAT) able to conduct espionage of industrial infrastructure (<xref ref-type="bibr" rid="ref46">Slowik, 2021</xref>). This malware tool scans industrial networks, targets industrial devices, and maps the network. This scanning activity is easily detected by SCADvanceXP modules and can be quickly reported as it happens to network operators.</p><p>Triton was specifically developed to exploit Schneider Electric Triconex Safety Instrumented System (SIS) controllers (<xref ref-type="bibr" rid="ref29">Kovacs, 2018</xref>). This complex malware reprograms safety procedures of vulnerable devices. It can either make them ignore an unsafe state to allow potentially dangerous conditions to persist and lead to damage (or, in addition, interfere with the industrial process to induce real hazard) or force them to turn off full alerts and safety protocols. This may lead to the shutting down of all industrial operations, even if there are no threats to the industrial process and infrastructure at the time (<xref ref-type="bibr" rid="ref21">Johnson <italic>et al</italic>., 2017</xref>). SCADvanceXP is able to detect such reconfiguration, changes in protocol, physical values, and vulnerable devices. Triton malware and similar attacks should therefore be detected by SCADvanceXP.</p></sec><sec id="S5" sec-type="conclusions"><title>Conclusions</title><p>In summary, SCADvanceXP is an advanced and specialised system for protecting industrial networks. Among many threats currently present in Europe, SCADvanceXP is able to detect all those that interfere with industrial/OT wired networks (according to the authors’ knowledge). Thanks to machine-learning techniques and advanced detection and scanning modules, SCADvanceXP is a powerful system that is able to significantly improve the protection level of industrial infrastructure. On the other side, there are many attacks on industrial systems affecting IT systems that SCADvanceXP will not detect. Attacks on enterprise-level servers or elements of an IT network that do not affect industrial control systems are not in the scope of current SCADvanceXP detection capability. SCADvanceXP is a specialised system dedicated to analysing data from industrial communication systems and devices by design. Although SCADvanceXP is not a universal solution, its detection capabilities are unique and there are few similar solutions available (see: <xref ref-type="bibr" rid="ref23">Kaouk <italic>et al</italic>., 2019</xref>, pp. 1699–1704; <xref ref-type="bibr" rid="ref26">Kim <italic>et al</italic>., 2023</xref>; <xref ref-type="bibr" rid="ref54">Yask and Kumar, 2019</xref>). Therefore, SCADvanceXP fills a security gap and provides safety for industrial infrastructure in a way that covers all aspects of industrial communication. All the arguments mentioned and its functionalities show that SCADvanceXP can be viewed as a holistic system for protecting industrial control systems.</p><p>Current conflicts, economic interests, and complex dependencies create a unique threat and vulnerability landscape. Many attacks on critical infrastructure are prepared by groups sponsored by states. Moreover, industrial networks can become military targets. Since the escalation of the Russo-Ukrainian war, attacks on critical and industrial systems have intensified. It has been shown that hackers often analyse and study industrial networks after they are initially compromised. The initial reconnaissance period, as well as other attack stages, may be detected by SCADvanceXP. Being able to detect even advanced attacks in the early stages, SCADvanceXP may truly protect industrial infrastructure before any damage is done. As military and economic tensions escalate in Central and Eastern Europe, systems like SCADvanceXP may prevent major incidents within the industry, and manufacturing and critical infrastructure sectors. It is worth remembering that industrial systems’ security is important for electro-energetic sector stability in Europe, which remains one of the primary targets of Russian forces in Ukraine (<xref ref-type="bibr" rid="ref43">Przetacznik and Tarpova, 2022</xref>).</p><p>The paradigm of defence in depth states that successful infrastructure protection requires deployment of all available means, rather than selected assets and actions. It is common for industrial systems to rely on IT security tools and programs, but these are not enough, especially if the threat is located within the industrial network. In such cases, solutions for the IT sector appear powerless. Therefore, the SCADvanceXP system seems to answer the current needs of the industrial cybersecurity landscape.</p></sec></body><back><sec id="S6" sec-type="financial-disclosure"><title>Funding</title><p>This research received no external funding.</p></sec><sec id="S7"><title>Author Contributions</title><p>Conceptualization, M.G.T, M.S., F.R., and N.M.; methodology, M.G.T., M.S., and F.R.; software, M.G.T., M.S., and J.K.; validation, M.G.T., M.S., F.R., J.K., and N.M.; formal analysis, M.S., F.R., and J.K; investigation, M.G.T., M.S., F.R., and J.K.; resources, F.R.; data curation, F.R., and J.K.; writing—preparation of original draft, M.G.T., M.S., and F.R.; writing—review and editing, M.G.T., F.R., and J.K.; visualization, M.G.T., and J.K.; supervision, M.S., and N.M.; project administration, M.S., and N.M.; funding acquisition, M.S., and N.M.</p></sec><sec id="S8"><title>Data Availability Statement</title><p>Data sharing not applicable. No new data was created or analysed in this study.</p></sec><sec id="S9" sec-type="COI-statement"><title>Disclosure statement</title><p>Marek Smolik reports a relationship with ICsec S.A. that includes board membership and employment. Franciszek Rakowski reports a relationship with ICsec S.A. that includes B2B cooperation. SCADvanceXP system was developed, thanks to the SCADvance R&amp;D project, conducted by ALMA S.A. (beneficiary of EU co-financed programme, project ID: RPWP.01.02.00-30-0055/16-00) and several renowned partners, including Poznan Supercomputing and Networking Centre and Poznan University of Technology. The R&amp;D project ended with a fully functional prototype (VI TRL level). Based on the promising results of the R&amp;D project, ICsec S.A. designed the market-ready product, marketed it, and by ICsec S.A., continues to further develop and support it.</p></sec><ref-list><ref id="ref1"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Alcaraz</surname>, <given-names>C</given-names></string-name>., <string-name><surname>Fernandez</surname>, <given-names>G</given-names></string-name>. and <string-name><surname>Carvajal</surname>, <given-names>F</given-names></string-name></person-group>. (<year>2012</year>) <chapter-title>‘Security aspects of SCADA and DCS environments’</chapter-title>, in <person-group person-group-type="editor"><string-name><surname>Lopez</surname>, <given-names>J</given-names></string-name>., <string-name><surname>Setola</surname>, <given-names>R</given-names></string-name>. and <string-name><surname>Wolthusen</surname>, <given-names>S</given-names></string-name></person-group>. (eds.) <source>Critical infrastructure protection: Information infrastructure models, analysis, and defense</source>. <publisher-loc>Berlin</publisher-loc>: <publisher-name>Springer</publisher-name>, pp. <fpage>120</fpage>–<lpage>149</lpage>. doi: <pub-id pub-id-type="doi">10.1007/978-3-642-28920-0</pub-id>.</mixed-citation></ref><ref id="ref2"><mixed-citation publication-type="web"><person-group person-group-type="author"><string-name><surname>Belding</surname>, <given-names>G</given-names></string-name></person-group>. (<year>2020</year>) <article-title><italic>Malware spotlight: Ekans, infosec: Malware analysis</italic></article-title>. Available at: <ext-link ext-link-type="uri" xlink:href="https://resources.-infosecinstitute.com/topic/malware-spotlight-ekans/">https://resources.-infosecinstitute.com/topic/malware-spotlight-ekans/</ext-link> (Accessed: 24 March 2023).</mixed-citation></ref><ref id="ref3"><mixed-citation publication-type="web"><person-group person-group-type="author"><string-name><surname>Burgess</surname>, <given-names>M</given-names></string-name></person-group>. (<year>2022</year>) <article-title>‘A mysterious satellite hack has victims far beyond Ukraine’</article-title>, <source>Wired</source>, 23 March. Available at: <ext-link ext-link-type="uri" xlink:href="https://www.wired.co.uk/article/viasat-internet-hack-ukraine-russia">https://www.wired.co.uk/article/viasat-internet-hack-ukraine-russia</ext-link> (Accessed: 20 October 2022).</mixed-citation></ref><ref id="ref4"><mixed-citation publication-type="web"><person-group person-group-type="author"><string-name><surname>Byres</surname>, <given-names>E</given-names></string-name></person-group>. (<year>2013</year>) <article-title>‘"Rip and replace” approach to SCADA security is unrealistic’</article-title>, <source>TOFINO security blog</source>, 30 January. Available at: <ext-link ext-link-type="uri" xlink:href="https://www.tofinosecurity.com/blog/%E2%80%9Crip-and-replace%E2%80%9D--approach-scada-security-unrealistic">https://www.tofinosecurity.com/blog/%E2%80%9Crip-and-replace%E2%80%9D--approach-scada-security-unrealistic</ext-link> (Accessed: 17 October 2022).</mixed-citation></ref><ref id="ref5"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Byres</surname>, <given-names>E</given-names></string-name>., <string-name><surname>Carter</surname>, <given-names>J</given-names></string-name>., <string-name><surname>Elramly</surname>, <given-names>A</given-names></string-name>. and <string-name><surname>Hoffman</surname>, <given-names>D</given-names></string-name></person-group>. (<year>2002</year>) <chapter-title>‘Worlds in collision-ethernet and the factory floor’</chapter-title>, in <source>ISA emerging technologies conference</source>, <publisher-name>Instrumentation Systems and Automation Society</publisher-name>, <publisher-loc>Chicago, IL</publisher-loc>.</mixed-citation></ref><ref id="ref6"><mixed-citation publication-type="book"><person-group person-group-type="author"><collab>CAN in Automation (CiA)</collab></person-group> (<year>2011</year>) <chapter-title><italic>CANopen application layer and communication profile, DS-301, version 4.02</italic>, technical documentation</chapter-title>. <publisher-name>Erlangen</publisher-name>: <publisher-loc>CiA</publisher-loc>.</mixed-citation></ref><ref id="ref7"><mixed-citation publication-type="web"><person-group person-group-type="author"><string-name><surname>Cherepanov</surname>, <given-names>A</given-names></string-name>. and <string-name><surname>Lipovsky</surname>, <given-names>R</given-names></string-name></person-group>. (<year>2018</year>) <article-title>‘New telebots backdoor: First evidence linking industroyer to NotPetya’</article-title>, <source>WeLiveSecurity (ESET Research)</source>, 11 October. Available at: <ext-link ext-link-type="uri" xlink:href="https://www.welivesecurity.com/2018/10/11/new-telebots-backdoor-linking-industroyer-notpetya/">https://www.welivesecurity.com/2018/10/11/new-telebots-backdoor-linking-industroyer-notpetya/</ext-link> (Accessed: 2 March 2023).</mixed-citation></ref><ref id="ref8"><mixed-citation publication-type="web"><person-group person-group-type="author"><string-name><surname>Cimpanu</surname>, <given-names>C</given-names></string-name></person-group>. (<year>2020</year>) <article-title>‘Conti ransomware uses 32 simultaneous CPU threads for blazing-fast encryption’</article-title>, <source>ZD NET Tech</source>., 8 July. Available at: <ext-link ext-link-type="uri" xlink:href="https://www.zdnet.com/article/conti-ransomware-uses-32--simultaneous-cpu-threads-for-blazing-fast-encryption/">https://www.zdnet.com/article/conti-ransomware-uses-32--simultaneous-cpu-threads-for-blazing-fast-encryption/</ext-link> (Accessed: 24 March 2023).</mixed-citation></ref><ref id="ref9"><mixed-citation publication-type="web"><article-title>Common Vulnerabilities and Exposures (CVE) Program (n.d.) Common vulnerabilities and exposures -database</article-title>. Available at: <ext-link ext-link-type="uri" xlink:href="https://www.cve.org">https://www.cve.org</ext-link> (Accessed: 26 March 2023).</mixed-citation></ref><ref id="ref10"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>De Andrade</surname>, <given-names>R</given-names></string-name>., <string-name><surname>Hodel</surname>, <given-names>K.N</given-names></string-name>., <string-name><surname>Justo</surname>, <given-names>J.F</given-names></string-name>., <string-name><surname>Lagana</surname>, <given-names>A.M</given-names></string-name>., <string-name><surname>Santos</surname>, <given-names>M.M</given-names></string-name>., and <string-name><surname>Gu</surname>, <given-names>Z</given-names></string-name></person-group>. (<year>2018</year>) <article-title>‘Analytical and experimental performance evaluations of CAN-FD BUS’</article-title>, <source>IEEE Access</source>, <volume>6</volume>, pp. <fpage>21287</fpage>–<lpage>21295</lpage>. doi: <pub-id pub-id-type="doi">10.1109/ACCESS.2018.2826522</pub-id>.</mixed-citation></ref><ref id="ref11"><mixed-citation publication-type="web"><person-group person-group-type="author"><string-name><surname>Di Pinto</surname>, <given-names>A. (Nozomi Networks)</given-names></string-name></person-group> (<year>2019</year>) <article-title><italic>GreyEnergy: Dissecting the malware from maldoc to backdoor</italic>, research paper</article-title>. Available at: <ext-link ext-link-type="uri" xlink:href="https://uploads-ssl.webflow.com/645a4534705010e2cb244f50/649131e3441ad51e4b0da155_Nozomi-Networks-GreyEnergy-Dissecting-the-Malware.pdf">https://uploads-ssl.webflow.com/645a4534705010e2cb244f50/649131e3441ad51e4b0da155_Nozomi-Networks-GreyEnergy-Dissecting-the-Malware.pdf</ext-link> (Accessed: 6 September 2023).</mixed-citation></ref><ref id="ref12"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Dobski</surname>, <given-names>M</given-names></string-name>., <string-name><surname>Frankowski</surname>, <given-names>G</given-names></string-name>., <string-name><surname>Meyer</surname>, <given-names>N</given-names></string-name>., <string-name><surname>Pilc</surname>, <given-names>M</given-names></string-name>. and <string-name><surname>Twardawa</surname>, <given-names>M</given-names></string-name></person-group>. (<year>2018</year>) <article-title>‘Zastosowanie metod uczenia maszynowego i zaawansowanego przetwarzania zdarzeń dla ochrony przemysłowych sieci infrastruktury krytycznej’</article-title>, <source>Przegląd Policyjny</source>, <volume>4</volume>(<issue>132</issue>), pp. <fpage>79</fpage>–<lpage>93</lpage>. doi: <pub-id pub-id-type="doi">10.5604/01.3001.0013.668</pub-id>.</mixed-citation></ref><ref id="ref13"><mixed-citation publication-type="web"><person-group person-group-type="author"><collab>Dragos Inc. (n.d.)</collab></person-group><article-title><italic>ELECTRUM threat group operations</italic></article-title>. Available at: <ext-link ext-link-type="uri" xlink:href="https://www.dragos.com/threat/electrum/">https://www.dragos.com/threat/electrum/</ext-link> (Accessed: 2 March 2023).</mixed-citation></ref><ref id="ref14"><mixed-citation publication-type="web"><person-group person-group-type="author"><string-name><surname>Eaton</surname>, <given-names>C</given-names></string-name>. and <string-name><surname>Volz</surname>, <given-names>D</given-names></string-name></person-group>. (<year>2021</year>) <article-title>‘Colonial pipeline CEO tells whyhe paid hackers a $4.4 million ransom’</article-title>, <source>The Wall Street Journal</source>, 19 May. Available at: <ext-link ext-link-type="uri" xlink:href="https://www.wsj.com/articles/colonial-pipeline-ceo-tells-why-he-paid-hackers-a-4-4-million-ransom-11621435636">https://www.wsj.com/articles/colonial-pipeline-ceo-tells-why-he-paid-hackers-a-4-4-million-ransom-11621435636</ext-link> (Accessed: 20 October 2022).</mixed-citation></ref><ref id="ref15"><mixed-citation publication-type="web"><person-group person-group-type="author"><string-name><surname>Greenberg</surname>, <given-names>A</given-names></string-name></person-group>. (<year>2018</year>) <article-title>‘The untold story of NotPetya, the most devastating cyber attack in history’</article-title>, <source>Wired</source>, 22 August. Available at: <ext-link ext-link-type="uri" xlink:href="https://www.wired.com/story/notpetya-cyberattack-ukraine-russia-code-crashed-the-world/">https://www.wired.com/story/notpetya-cyberattack-ukraine-russia-code-crashed-the-world/</ext-link> (Accessed: 11 November 2022).</mixed-citation></ref><ref id="ref16"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Hajda</surname>, <given-names>J</given-names></string-name>., <string-name><surname>Jakuszewski</surname>, <given-names>R</given-names></string-name>. and <string-name><surname>Ogonowski</surname>, <given-names>S</given-names></string-name></person-group>. (<year>2021</year>) <article-title>‘Security challenges in industry 4.0 PLC systems’</article-title>, <source>Applied Sciences</source>, <volume>11</volume>(<issue>21</issue>), <fpage>9785</fpage>. doi: <pub-id pub-id-type="doi">10.3390/app11219785</pub-id>.</mixed-citation></ref><ref id="ref17"><mixed-citation publication-type="web"><person-group person-group-type="author"><collab>HeadMind Partners</collab></person-group> (<year>2022</year>) <article-title>Pipedream/Incontroller: ICS-specific malware attacks</article-title>. Available at: <ext-link ext-link-type="uri" xlink:href="https://www.headmind.com/fr/pipedream-incontroller-ics-specific-malware-attacks/">https://www.headmind.com/fr/pipedream-incontroller-ics-specific-malware-attacks/</ext-link> (Accessed: 23 March 2023).</mixed-citation></ref><ref id="ref18"><mixed-citation publication-type="web"><person-group person-group-type="author"><string-name><surname>Hemsley</surname>, <given-names>K.E</given-names></string-name>. and <string-name><surname>Fisher</surname>, <given-names>R.E</given-names></string-name></person-group>. (<year>2018</year>) <article-title><italic>History of industrial control system cyber incidents</italic></article-title>. <publisher-loc>Idaho Falls, ID</publisher-loc>: <publisher-name>Idaho National Laboratory</publisher-name>. Available at: <ext-link ext-link-type="uri" xlink:href="https://www.osti.gov/servlets/purl/1505628">https://www.osti.gov/servlets/purl/1505628</ext-link> (Accessed: 22 March 2023).</mixed-citation></ref><ref id="ref19"><mixed-citation publication-type="web"><person-group person-group-type="author"><collab>ICsec S.A. (n.d.)</collab></person-group><article-title><italic>SCADvanceXP</italic> (website)</article-title>. Available at: <ext-link ext-link-type="uri" xlink:href="https://icsec.pl/en/scadvance/">https://icsec.pl/en/scadvance/</ext-link> (Accessed: 31 March 202).</mixed-citation></ref><ref id="ref20"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Jayalaxmi</surname>, <given-names>P</given-names></string-name>., <string-name><surname>Saha</surname>, <given-names>R</given-names></string-name>., <string-name><surname>Kumar</surname>, <given-names>G</given-names></string-name>., <string-name><surname>Kumar</surname>, <given-names>N</given-names></string-name>. and <string-name><surname>Kim</surname>, <given-names>T.-H</given-names></string-name></person-group>. (<year>2021</year>) <article-title>‘A taxonomy of security issues in industrial internet-of-things: Scoping review for existing solutions, future implications, and research challenges’</article-title>, <source>IEEE Access</source>, <volume>9</volume>, pp. <fpage>25344</fpage>–<lpage>25359</lpage>. doi: <pub-id pub-id-type="doi">10.1109/ACCESS.2021.3057766</pub-id>.</mixed-citation></ref><ref id="ref21"><mixed-citation publication-type="web"><person-group person-group-type="author"><string-name><surname>Johnson</surname>, <given-names>B</given-names></string-name>., <string-name><surname>Caban</surname>, <given-names>D</given-names></string-name>., <string-name><surname>Krotofil</surname>, <given-names>M</given-names></string-name>., <string-name><surname>Scali</surname>, <given-names>D</given-names></string-name>., <string-name><surname>Brubaker</surname>, <given-names>N</given-names></string-name>. and <string-name><surname>Glyer</surname>, <given-names>C</given-names></string-name></person-group>. (<year>2017</year>) <article-title>‘Attackers deploy new ICS attack framework “TRITON” and cause operational disruption to critical infrastructure’</article-title>, <source>MANDIANT Blog</source>, 14 December. Available at: <ext-link ext-link-type="uri" xlink:href="https://www.mandiant.com/resources/blog/attackers-deploy-new-ics-attack-framework-triton">https://www.mandiant.com/resources/blog/attackers-deploy-new-ics-attack-framework-triton</ext-link> (Accessed: 31 March 2023).</mixed-citation></ref><ref id="ref22"><mixed-citation publication-type="web"><person-group person-group-type="author"><string-name><surname>Josephs</surname>, <given-names>L</given-names></string-name></person-group>. (<year>2021</year>) <article-title>‘Pipeline outage forces American airlines to add stopsto some long-haul flights, southwest flies in fuel’</article-title>, <source>CNBC</source>, 10 May. Available at: <ext-link ext-link-type="uri" xlink:href="https://www.cnbc.com/2021/05/10/colonial-pipeline-shutdown-forces-airlines-to-consider-other-ways-to-get-fuel.html">https://www.cnbc.com/2021/05/10/colonial-pipeline-shutdown-forces-airlines-to-consider-other-ways-to-get-fuel.html</ext-link> (Accessed: 20 October 2022).</mixed-citation></ref><ref id="ref23"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Kaouk</surname>, <given-names>M</given-names></string-name>., <string-name><surname>Flaus</surname>, <given-names>J.-M</given-names></string-name>., <string-name><surname>Potet</surname>, <given-names>M.-L</given-names></string-name>. and <string-name><surname>Groz</surname>, <given-names>R</given-names></string-name></person-group>. (<year>2019</year>) <chapter-title>‘A review of intrusion detection systems for industrial control systems’</chapter-title>, in <source>2019 6th International conference on control, decision and information technologies (CoDIT)</source>, <publisher-loc>Le Cnam, Paris, France</publisher-loc>, <publisher-name>IEEE</publisher-name>, pp. <fpage>1699</fpage>–<lpage>1704</lpage>. doi: <pub-id pub-id-type="doi">10.1109/CoDIT.2019.8820602</pub-id>.</mixed-citation></ref><ref id="ref24"><mixed-citation publication-type="web"><person-group person-group-type="author"><string-name><surname>Kapellmann-Zafra</surname>, <given-names>D</given-names></string-name>., <string-name><surname>Leong</surname>, <given-names>R</given-names></string-name>., <string-name><surname>Sistrunk</surname>, <given-names>C</given-names></string-name>., <string-name><surname>Proska</surname>, <given-names>K</given-names></string-name>., <string-name><surname>Hildebrandt</surname>, <given-names>C</given-names></string-name>., <string-name><surname>Lunden</surname>, <given-names>K</given-names></string-name>. and <string-name><surname>Brubaker</surname>, <given-names>N</given-names></string-name></person-group>. (<year>2022</year>) <article-title>‘INDUSTROYER.V2: Old malware learns new tricks’</article-title>, <source>MANDIANT Blog</source>, 25 April. Available at: <ext-link ext-link-type="uri" xlink:href="https://www.mandiant.com/resources/blog/industroyer-v2-old-malware-new-tricks">https://www.mandiant.com/resources/blog/industroyer-v2-old-malware-new-tricks</ext-link> (Accessed: 31 March 2023).</mixed-citation></ref><ref id="ref25"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Khan</surname>, <given-names>R</given-names></string-name>., <string-name><surname>Maynard</surname>, <given-names>P</given-names></string-name>., <string-name><surname>McLaughlin</surname>, <given-names>K</given-names></string-name>., <string-name><surname>Laverty</surname>, <given-names>D</given-names></string-name>. and <string-name><surname>Sezer</surname>, <given-names>S</given-names></string-name></person-group>. (<year>2016</year>) ‘<article-title>Threat analysis of BlackEnergy malware for synchrophasor based real-time control and monitoring in smart grid’</article-title>, in <source>Proceedings of the 4th international symposium for ICS &amp; SCADA cyber security research 2016</source>, pp. <fpage>53</fpage>–<lpage>63</lpage>. doi: <pub-id pub-id-type="doi">10.14236/ewic/ICS2016.7</pub-id>.</mixed-citation></ref><ref id="ref26"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Kim</surname>, <given-names>B</given-names></string-name>., <string-name><surname>Alawami</surname>, <given-names>M.A</given-names></string-name>., <string-name><surname>Kim</surname>, <given-names>E</given-names></string-name>., <string-name><surname>Oh</surname>, <given-names>S</given-names></string-name>., <string-name><surname>Park</surname>, <given-names>J</given-names></string-name>. and <string-name><surname>Kim</surname>, <given-names>H</given-names></string-name></person-group>. (<year>2023</year>) <article-title>‘A comparative study of time series anomaly detection models for industrial control systems’</article-title>, <source>Sensors</source>, <volume>23</volume>(<issue>3</issue>), <fpage>1310</fpage>. doi: <pub-id pub-id-type="doi">10.3390/s23031310</pub-id>.</mixed-citation></ref><ref id="ref27"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Kleinmann</surname>, <given-names>A</given-names></string-name>., <string-name><surname>Amichay</surname>, <given-names>O</given-names></string-name>., <string-name><surname>Wool</surname>, <given-names>A</given-names></string-name>., <string-name><surname>Tenenbaum</surname>, <given-names>D</given-names></string-name>., <string-name><surname>Bar</surname>, <given-names>O</given-names></string-name>. and <string-name><surname>Lev</surname>, <given-names>L</given-names></string-name></person-group>. (<year>2018</year>) <chapter-title>‘Stealthy deception attacks against SCADA systems’</chapter-title>, in <person-group person-group-type="editor"><string-name><surname>Katsikas</surname>, <given-names>S.K</given-names></string-name>., <string-name><surname>Cuppens</surname>, <given-names>F</given-names></string-name>., <string-name><surname>Cuppens</surname>, <given-names>N</given-names></string-name>., <string-name><surname>Lambrinoudakis</surname>, <given-names>C</given-names></string-name>., <string-name><surname>Kalloniatis</surname>, <given-names>C</given-names></string-name>., <string-name><surname>Mylopoulos</surname>, <given-names>J</given-names></string-name>., <string-name><surname>Anton</surname>, <given-names>A</given-names></string-name>. and <string-name><surname>Gritzalis</surname>, <given-names>S</given-names></string-name></person-group>. (eds.), <source>Computer security. SECPRE CyberICPS 2017, lecture notes in computer science, 10683</source>. <publisher-loc>Cham</publisher-loc>: <publisher-name>Springer</publisher-name>, pp. <fpage>93</fpage>–<lpage>109</lpage>. doi: <pub-id pub-id-type="doi">10.1007/978-3-319-72817-9_7</pub-id>.</mixed-citation></ref><ref id="ref28"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Knapp</surname>, <given-names>E.D</given-names></string-name>. and <string-name><surname>Langill</surname>, <given-names>J.T</given-names></string-name></person-group>. (<year>2015</year>) <chapter-title>‘Industrial cyber security history and trends’</chapter-title>, in <person-group person-group-type="editor"><string-name><surname>Knapp</surname>, <given-names>E.D</given-names></string-name>. and <string-name><surname>Langill</surname>, <given-names>J.T</given-names></string-name></person-group>. (eds.), <source>Industrial network security</source>, <edition>2nd edn</edition>. <publisher-loc>Boston, MA</publisher-loc>: <publisher-name>Syngress</publisher-name>, Chap. 3, pp. <fpage>41</fpage>–<lpage>57</lpage>.</mixed-citation></ref><ref id="ref29"><mixed-citation publication-type="web"><person-group person-group-type="author"><string-name><surname>Kovacs</surname>, <given-names>E</given-names></string-name></person-group>. (<year>2018</year>) <article-title>‘Triton malware linked to Russian government research institute’</article-title>, <source>SecurityWeek</source>, 23 October. Available at: <ext-link ext-link-type="uri" xlink:href="https://www.securityweek.com/triton-malware-linked-russian-government-research-institute">https://www.securityweek.com/triton-malware-linked-russian-government-research-institute</ext-link> (Accessed: 24 October 2022).</mixed-citation></ref><ref id="ref30"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Krotofil</surname>, <given-names>M</given-names></string-name>., <string-name><surname>Larsen</surname>, <given-names>J</given-names></string-name>. and <string-name><surname>Gollmann</surname>, <given-names>D</given-names></string-name></person-group>. (<year>2015</year>) <chapter-title>‘The process matters: Ensuring data veracity in cyber-physical systems’</chapter-title>, in <source>ASIA CCS '15: Proceedings of the 10th ACM symposium on information, computer and communications security</source>, <publisher-name>Association for Computing Machinery</publisher-name>, <publisher-loc>New York, NY</publisher-loc>, pp. <fpage>133</fpage>–<lpage>144</lpage>. doi: <pub-id pub-id-type="doi">10.1145/2714576.271459</pub-id>.</mixed-citation></ref><ref id="ref31"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Kumar</surname>, <given-names>R</given-names></string-name>., <string-name><surname>Narra</surname>, <given-names>B</given-names></string-name>., <string-name><surname>Kela</surname>, <given-names>R</given-names></string-name>. and <string-name><surname>Singh</surname>, <given-names>S</given-names></string-name></person-group>. (<year>2022</year>) <article-title>‘AFMT: Maintaining the safety-security of industrial control systems’</article-title>, <source>Computers in Industry</source>, <volume>136</volume>, <fpage>103584</fpage>. doi: <pub-id pub-id-type="doi">10.1016/j.compind.2021.103584</pub-id>.</mixed-citation></ref><ref id="ref32"><mixed-citation publication-type="web"><person-group person-group-type="author"><string-name><surname>Langner</surname>, <given-names>R</given-names></string-name></person-group>. (<year>2013</year>) <article-title><italic>To kill a centrifuge—A technical analysis of what Stuxnet’s creators tried to achieve</italic></article-title>. <source>The Langner Group</source>, <publisher-name>Hamburg</publisher-name>. Available at: <ext-link ext-link-type="uri" xlink:href="https://www.langner.com/wp-content/uploads/2017/03/to-kill-a-centrifuge.pdf">https://www.langner.com/wp-content/uploads/2017/03/to-kill-a-centrifuge.pdf</ext-link> (Accessed: 2 December 2022).</mixed-citation></ref><ref id="ref33"><mixed-citation publication-type="web"><person-group person-group-type="author"><string-name><surname>Lee</surname>, <given-names>R.M</given-names></string-name>., <string-name><surname>Assante</surname>, <given-names>M.J</given-names></string-name>. and <string-name><surname>Conway</surname>, <given-names>T</given-names></string-name></person-group>. (<year>2014</year>) <article-title><italic>German steel mill cyber attack, ICS: Defense use case</italic></article-title>. <source>SANS Industrial Control Systems</source>, <publisher-loc>Rockville, MD</publisher-loc>. Available at: <ext-link ext-link-type="uri" xlink:href="https://assets.contentstack.io/v3/assets/-blt36c2e63521272fdc/bltc79a41dbf7d1441e/607f235775873e466bcc539c/ICS-CPPE-case-Study-2-German-Steelworks_Facility.pdf">https://assets.contentstack.io/v3/assets/-blt36c2e63521272fdc/bltc79a41dbf7d1441e/607f235775873e466bcc539c/ICS-CPPE-case-Study-2-German-Steelworks_Facility.pdf</ext-link> (Accessed: 2 December 2022).</mixed-citation></ref><ref id="ref34"><mixed-citation publication-type="web"><person-group person-group-type="author"><string-name><surname>Lee</surname>, <given-names>R.M</given-names></string-name>., <string-name><surname>Assante</surname>, <given-names>M.J</given-names></string-name>. and <string-name><surname>Conway</surname>, <given-names>T</given-names></string-name></person-group>. (<year>2016</year>) <article-title><italic>Analysis of the cyber attack on the Ukrainian power grid: Defense use case</italic></article-title>. <source>SANS Industrial Control Systems</source>. Available at: <ext-link ext-link-type="uri" xlink:href="https://media.kasperskycontenthub.com/wp-content/uploads/sites/43/2016/05/20081514/E-ISAC_SANS_Ukraine_DUC_5.pdf">https://media.kasperskycontenthub.com/wp-content/uploads/sites/43/2016/05/20081514/E-ISAC_SANS_Ukraine_DUC_5.pdf</ext-link> (Accessed: 2 December 2022).</mixed-citation></ref><ref id="ref35"><mixed-citation publication-type="web"><person-group person-group-type="author"><string-name><surname>Lin</surname>, <given-names>Z</given-names></string-name>. and <string-name><surname>Pearson</surname>, <given-names>S</given-names></string-name></person-group>. (<year>2018</year>) <article-title><italic>An inside look at industrial ethernet communication protocols</italic></article-title>. <source>Texas Instruments</source>. Available at: <ext-link ext-link-type="uri" xlink:href="https://www.ti.com/lit/wp/spry254b/spry254b.pdf?ts=1693988436464">https://www.ti.com/lit/wp/spry254b/spry254b.pdf?ts=1693988436464</ext-link> (Accessed: 12 December 2022)</mixed-citation></ref><ref id="ref36"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Liu</surname>, <given-names>Y</given-names></string-name>., <string-name><surname>Ning</surname>, <given-names>P</given-names></string-name>. and <string-name><surname>Reiter</surname>, <given-names>M.K</given-names></string-name></person-group>. (<year>2011</year>) <article-title>‘False data injection attacks against state estimation in electric power grids’</article-title>, <source>ACM Transactions on Information and System Security</source><volume>14</volume>(<issue>1</issue>), pp. <fpage>1</fpage>–<lpage>33</lpage>. doi: <pub-id pub-id-type="doi">10.1145/1952982.1952995/</pub-id>.</mixed-citation></ref><ref id="ref37"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Mitchell</surname>, <given-names>R.W</given-names></string-name></person-group>. (<year>2003</year>) <article-title><italic>PROFIBUS: A pocket guide</italic></article-title>. <publisher-loc>Pittsburgh, PA</publisher-loc>: <publisher-name>International Society of Automation</publisher-name>, pp. <fpage>1</fpage>–<lpage>20</lpage>.</mixed-citation></ref><ref id="ref38"><mixed-citation publication-type="web"><person-group person-group-type="author"><collab>Modbus Organization Inc</collab></person-group>. (<year>2012</year>) <article-title><italic>MODBUS application protocol specification V1.1b3</italic></article-title>. Available at: <ext-link ext-link-type="uri" xlink:href="https://modbus.org/docs/Modbus_Application_Protocol_V1_1b.pdf">https://modbus.org/docs/Modbus_Application_Protocol_V1_1b.pdf</ext-link> (Accessed: 11 December 2022).</mixed-citation></ref><ref id="ref39"><mixed-citation publication-type="web"><article-title>National Institute of Standards and Technology (n.d.) Official common platform enumeration (CPE) dictionary, national vulnerability database</article-title>. Available at: <ext-link ext-link-type="uri" xlink:href="https://nvd.nist.gov/products/cpe">https://nvd.nist.gov/products/cpe</ext-link> (Accessed: 23 January 2023).</mixed-citation></ref><ref id="ref40"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Paganini</surname>, <given-names>P</given-names></string-name></person-group>. (<year>2019</year>) <chapter-title><italic>Duqu 2.0: The most sophisticated malware ever seen</italic></chapter-title>. <source>Malware analysis</source>. <publisher-name>Infosec Resources</publisher-name>, <publisher-loc>Madison, WI</publisher-loc>. Available at <ext-link ext-link-type="uri" xlink:href="https://resources.infosecinstitute.com/topic/duqu-2-0-the-most-sophisticated--malware-ever-seen/">https://resources.infosecinstitute.com/topic/duqu-2-0-the-most-sophisticated--malware-ever-seen/</ext-link> (Accessed: 31 March 2023).</mixed-citation></ref><ref id="ref41"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Pei</surname>, <given-names>C</given-names></string-name>., <string-name><surname>Xiao</surname>, <given-names>Y</given-names></string-name>., <string-name><surname>Liang</surname>, <given-names>W</given-names></string-name>. and <string-name><surname>Han</surname>, <given-names>X</given-names></string-name></person-group>. (<year>2018</year>) <article-title>‘Trade-off of security and performance of lightweight block ciphers in industrial wireless sensor networks’</article-title>, <source>EURASIP Journal on Wireless Communications and Networking</source>, <volume>117</volume>(<issue>2018</issue>), pp. <fpage>1</fpage>–<lpage>18</lpage>. doi: <pub-id pub-id-type="doi">10.1186/s13638-018-1121-6</pub-id>.</mixed-citation></ref><ref id="ref42"><mixed-citation publication-type="journal"><person-group person-group-type="author"><collab>Policja.pl</collab></person-group> (<year>2008</year>) <article-title>‘14-latek przestawiał zwrotnice’</article-title>, 09 January. Available at: <ext-link ext-link-type="uri" xlink:href="https://policja.pl/pol/-aktualnosci/13278,14-latek-przestawial-zwrotnice.html">https://policja.pl/pol/-aktualnosci/13278,14-latek-przestawial-zwrotnice.html</ext-link> (Accessed: 20 February 2023).</mixed-citation></ref><ref id="ref43"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Przetacznik</surname>, <given-names>J</given-names></string-name>. and <string-name><surname>Tarpova</surname>, <given-names>S</given-names></string-name></person-group>. (<year>2022</year>) <chapter-title><italic>Russia’s war on Ukraine: Timeline of cyber-attacks</italic></chapter-title>. <source>Briefing PE 733.549</source>. <publisher-loc>Brussels</publisher-loc>: <publisher-name>European Parliamentary Research Service</publisher-name>.</mixed-citation></ref><ref id="ref44"><mixed-citation publication-type="web"><person-group person-group-type="author"><collab>Repository of Industrial Security Incidents (RISI)</collab></person-group> (<year>2015</year>) <article-title><italic>The repository of industrial security incidents</italic></article-title>. Available at: <ext-link ext-link-type="uri" xlink:href="https://www.risidata.com/">https://www.risidata.com/</ext-link> (Accessed: 13 October 2022).</mixed-citation></ref><ref id="ref45"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Slay</surname>, <given-names>J</given-names></string-name>. and <string-name><surname>Miller</surname>, <given-names>M</given-names></string-name></person-group>. (<year>2008</year>) <chapter-title>‘Lessons learned from the Maroochy water breach’</chapter-title>, in <person-group person-group-type="editor"><string-name><surname>Goetz</surname>, <given-names>E</given-names></string-name>. and <string-name><surname>Shenoi</surname>, <given-names>S</given-names></string-name></person-group>. (eds.), <source>Critical infrastructure protection</source>. <publisher-loc>Boston, MA</publisher-loc>: <publisher-name>Springer</publisher-name>, pp. <fpage>73</fpage>–<lpage>82</lpage>. doi: <pub-id pub-id-type="doi">10.1007/978-0-387-75462-8_6</pub-id>.</mixed-citation></ref><ref id="ref46"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Slowik</surname>, <given-names>J</given-names></string-name></person-group>. (<year>2021</year>) <article-title>‘The baffling berserk bear: A decade’s activity targeting critical infrastructure, report’</article-title>, <source>Virus Bulletin Conference</source> October 2021. Available at: <ext-link ext-link-type="uri" xlink:href="https://vblocalhost.com/uploads/VB2021-Slowik.pdf">https://vblocalhost.com/uploads/VB2021-Slowik.pdf</ext-link> (Accessed: 14 December 2022).</mixed-citation></ref><ref id="ref47"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Soltero</surname>, <given-names>M</given-names></string-name>., <string-name><surname>Zhang</surname>, <given-names>J</given-names></string-name>., <string-name><surname>Cockril</surname>, <given-names>C</given-names></string-name>., <string-name><surname>Zhang</surname>, <given-names>K</given-names></string-name>., <string-name><surname>Kinnaird</surname>, <given-names>C</given-names></string-name>. and <string-name><surname>Kugelstadt</surname>, <given-names>T</given-names></string-name></person-group>. (<year>2002</year>) <article-title><italic>RS-422 and RS-485 standards overview and system configurations</italic></article-title>. <source>Texas Instruments</source>, pp. <fpage>3</fpage>–<lpage>12</lpage>. Available at: <ext-link ext-link-type="uri" xlink:href="https://www.ti.com/lit/an/slla070d/slla070d.pdf?ts=1693930089541">https://www.ti.com/lit/an/slla070d/slla070d.pdf?ts=1693930089541</ext-link> (Accessed: 6 September 2023).</mixed-citation></ref><ref id="ref48"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Spurgeon</surname>, <given-names>C.E</given-names></string-name></person-group>. (<year>2000</year>) <chapter-title>‘The evolution of ethernet’</chapter-title>, in <person-group person-group-type="editor"><string-name><surname>Stone</surname>, <given-names>M</given-names></string-name>. and <string-name><surname>Toporek</surname>, <given-names>C</given-names></string-name></person-group>. (eds.) <source>Ethernet: the definitive guide</source>. <publisher-loc>Sebastopol, CA</publisher-loc>: <publisher-name>O’Reilly&amp; Associates</publisher-name>, pp. <fpage>3</fpage>–<lpage>22</lpage>.</mixed-citation></ref><ref id="ref49"><mixed-citation publication-type="web"><person-group person-group-type="author"><string-name><surname>Stewart</surname>, <given-names>J</given-names></string-name></person-group>. (<year>2010</year>) <article-title>‘BlackEnergy version 2 threat analysis’</article-title>, <source>Secure works: Threat intelligence research</source>, 3 March. Available at: <ext-link ext-link-type="uri" xlink:href="https://www.secureworks.com/research/blackenergy2">https://www.secureworks.com/research/blackenergy2</ext-link> (Accessed: 24 March 2023).</mixed-citation></ref><ref id="ref50"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Taherdoost</surname>, <given-names>H</given-names></string-name></person-group>. (<year>2022</year>) <article-title>‘Understanding cybersecurity frameworks and information security standards—A review and comprehensive overview’</article-title>, <source>Electronics</source><volume>11</volume>(<issue>14</issue>), pp. <fpage>1</fpage>–<lpage>20</lpage>. doi: <pub-id pub-id-type="doi">10.3390/electronics11142181</pub-id>.</mixed-citation></ref><ref id="ref51"><mixed-citation publication-type="web"><person-group person-group-type="author"><collab>Trend Micro Inc.</collab></person-group>. (<year>2016</year>) <article-title><italic>Malware discovered in German nuclear power plant</italic></article-title>. Available at: <ext-link ext-link-type="uri" xlink:href="https://www.trendmicro.-com/vinfo/pl/security/news/cyber-attacks/malware-discovered-in-german--nuclear-power-plant%20">https://www.trendmicro.-com/vinfo/pl/security/news/cyber-attacks/malware-discovered-in-german--nuclear-power-plant</ext-link> (Accessed: 8 March 2023).</mixed-citation></ref><ref id="ref52"><mixed-citation publication-type="web"><person-group person-group-type="author"><collab>Viasat Inc.</collab></person-group> (<year>2022</year>) <article-title>‘KA-SAT network cyber attack overview’</article-title>, <source>Viasat Corporate News</source>, 30 March. Available at: <ext-link ext-link-type="uri" xlink:href="https://news.viasat.com/blog/corporate/ka-sat-network-cyber-attack-overview">https://news.viasat.com/blog/corporate/ka-sat-network-cyber-attack-overview</ext-link> (Accessed: 20 October 2022).</mixed-citation></ref><ref id="ref53"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Williams</surname><given-names>T.J</given-names></string-name></person-group>. (<year>1994</year>) <article-title>‘The Purdue enterprise reference architecture’</article-title>, <source>Computers in Industry</source>, <volume>24</volume>(<issue>2</issue>), pp. <fpage>141</fpage>–<lpage>158</lpage>. doi: <pub-id pub-id-type="doi">10.1016/0166-3615(94)90017-5</pub-id>.</mixed-citation></ref><ref id="ref54"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Yask</surname></string-name> and <string-name><surname>Kumar</surname>, <given-names>B.S</given-names></string-name></person-group>. (<year>2019</year>) <article-title>‘A review of model on malware detectionand protection for the distributed control systems (industrial control systems) in oil &amp; gas sectors’</article-title>, <source>Journal of Discrete Mathematical Sciences and Cryptography</source><volume>22</volume>(<issue>4</issue>), pp. <fpage>531</fpage>–<lpage>540</lpage>. doi: <pub-id pub-id-type="doi">10.1080/09720529.2019.1642623</pub-id>.</mixed-citation></ref></ref-list></back></article>
