<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-title-group>
        <journal-title>S. Seilkhanova);</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Analysis and Prospects for Ensuring the Cybersecurity of Industrial Robots</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Sabyrzhan K. Atanov</string-name>
          <email>atanov5@mail.ru</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Kymbat Z. Seilkhanova</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Yerzhan N. Seitkulov</string-name>
          <email>yerzhan.seitkulov@gmail.com</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Shadi A. Aljawarneh</string-name>
          <email>saaljawarneh@just.edu.jo</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Jordan University of Science and Technology</institution>
          ,
          <addr-line>Irbid, 22110</addr-line>
          ,
          <country country="JO">Jordan</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>L.N. Gumilyov Eurasian National University</institution>
          ,
          <addr-line>2 Satpayev St., Astana, 010008</addr-line>
          ,
          <country country="KZ">Kazakhstan</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2020</year>
      </pub-date>
      <volume>000</volume>
      <fpage>0</fpage>
      <lpage>0002</lpage>
      <abstract>
        <p>Ensuring a high level of cybersecurity for industrial robots is of fundamental importance given their key role in automating industrial processes. Vulnerabilities in robotic systems can lead to serious consequences, including production downtime, data loss, and even threats to workers and the environment. Cybersecurity problems for industrial robots are caused not only by insufficient software protection but also by their physical integration into industrial networks. In this article, we will look at real-life examples of vulnerabilities in robotic systems that can have serious consequences, including the possibility of unauthorized access, potential impact on physical processes in a production environment, and so on. The authors propose several ways to strengthen the cybersecurity of industrial robots in the future.</p>
      </abstract>
      <kwd-group>
        <kwd>1 Cybersecurity</kwd>
        <kwd>industrial robots</kwd>
        <kwd>industrial automation</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Cybersecurity for industrial robots is an extremely important aspect of the field of industrial
automation. It plays a key role in ensuring the safety of the work environment and equipment, as
well as protecting the enterprise's confidential data and intellectual property [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Maintaining
strong cybersecurity helps prevent potential threats to production and ensures business
continuity. In addition, compliance with safety standards and legal requirements is important
both from a legal liability perspective and to maintaining a good company reputation.
      </p>
      <p>
        According to [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], robotics is rapidly developing using the Internet of Things (IoT), increasingly
applying the concept of the Internet of Everything (IoE). This development combines robotic
systems with wireless networks, sensors, cloud platforms, open-source software, other devices
and artificial intelligence. This process increases the complexity of robot development and
emphasizes the importance of ensuring robot safety.
      </p>
      <p>Therefore, in this article, we will consider industrial robots as IoT devices, which allows us to
assume that these devices can be attacked by “traditional” hacking methods.</p>
      <p>
        In addition, over the past decades, industrial automation has been developed without, in fact,
paying due attention to safety aspects as we can see in Figure 1. This has led to the fact that there
is now a significant amount of equipment in industrial plants that have structural flaws that can
be exploited by hackers and cybercriminals [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. In this article, we will analyze the vulnerabilities
characteristic of industrial automation systems and provide recommendations for improving the
current situation in this area.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. Vulnerabilities in industrial robots</title>
      <p>In modern conditions, most robots and automated systems are controlled either by human
operators directly or using hardware and software systems operating in remote control mode.</p>
      <p>
        Robot security covers two important aspects: information security and control security.
Information security focuses primarily on areas related to data encryption, transmission, and
subsequent decryption. Device management security focuses on possible attacks aimed at
changing the dynamic characteristics of a given system [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ].
      </p>
      <p>
        The [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] study examined the technical details and weaknesses of eight of the most popular
industrial programming environments and confirmed that without proper data validation,
industrial automation programs can express common vulnerabilities found in applications
written in general-purpose languages.
      </p>
      <p>
        Another issue with legacy industrial automation programming languages, such as the
Industrial Robots Programming Language (IRPL), is the lack of tools to identify unsafe patterns
in the code. Unlike modern programming languages, legacy IRPL languages do not have tools
available to automatically check code for potential vulnerabilities [
        <xref ref-type="bibr" rid="ref10 ref6">6, 10</xref>
        ].
      </p>
      <p>Let's look at some examples and possible consequences of these applications, taking into
account today's cybersecurity threats.</p>
      <sec id="sec-2-1">
        <title>2.1. Data theft</title>
        <p>Engineers use a computer-based development environment, often known as "offline
programming" (OLP), to customize how robots behave offline. However, when using OLP with
remote services enabled, engineers' computers become susceptible to remote attacks. These
computers are sometimes located outside the enterprise's internal network, creating the risk of
attacks on their computer equipment without access to the enterprise's main network.</p>
        <p>
          Those types of vulnerabilities were discovered in the ROBOGUIDE-HandlingPRO simulator,
which is true for version 9 Rev.ZD FANUC ROBOGUIDE-HandlingPRO and earlier versions [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ].
        </p>
        <p>
          Attackers can relatively easily gain access to the simulator on an engineer's computer through
the web interface (Figure 2). Moreover, OLP was found to not provide adequate access control to
computer resources, allowing remote attackers to exploit vulnerabilities such as security
bypasses to gain unauthorized access to system resources [
          <xref ref-type="bibr" rid="ref12 ref3">3,12</xref>
          ]. It should also be noted that
integrators who need to maintain robots in different plants often move potentially compromised
computers from one location to another, which can increase the risk of negative consequences
from attacks.
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2. Substitution of commands at the network level</title>
        <p>Spoofing industrial robot commands over a network is the process of changing or forging
commands sent to the remote control of a robot via a network. The vulnerability occurs when the
authentication and security mechanisms used to access the robot over the network are not
sufficiently secure. If an attacker can bypass or replace authentication, he will gain access to
control the robot. An attacker can intercept or modify commands sent to the robot. This may be
done to change its behavior or cause unwanted behavior that may be hazardous to operators or
the environment.</p>
        <p>
          For example, according to [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ], a study conducted on seven industrial robots from six different
OEMs revealed the ability of malware known as CORMAND2 to bypass existing anomaly detection
systems. These systems are typically designed to verify the authenticity of traffic data received
through a SCADA system. SCADA (Supervisory Control and Data Acquisition) system is a
comprehensive system used in industry and critical infrastructure to monitor, control and collect
data about work processes.
        </p>
        <p>
          The CORMAND2 attack is based on a Man-in-the-Middle (MITM) technique that establishes a
new TCP connection between two victims using proxy solutions such as Mitmproxy and Burp
Suite. However, these solutions do not apply to industrial robots, since the connection between
the robot and SCADA is established and maintained throughout the entire system operation [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ].
CORMAND2 overcomes this limitation by introducing the MITM attack and modifying the existing
connection between the robot and SCADA without causing anomalies in the robot's movement
that would be seen by the SCADA system, in the transmitted data packets, or in the TCP
connection itself. This highlights the threat posed by data tampering in industrial systems and
requires additional security measures to protect against such attacks.
        </p>
        <p>
          A similar vulnerability was discovered in 2022 in KUKA.SystemSoftware (KSS), which is the
robot controller operating system for most KUKA robot models. KUKA SystemSoftware V/KSS
versions prior to 8.6.5 did not provide access controls for the specified interface. If access control
is absent or disabled, reading and changing the robot's configuration can be performed without
the need for authentication, solely based on access to TCP port 49003 at the network level
(CVE2022-2242l) [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ].
        </p>
      </sec>
      <sec id="sec-2-3">
        <title>2.3. Remote Code Execution vulnerability</title>
        <p>RCE (Remote Code Execution) vulnerability is a serious vulnerability in a computer system or
software that allows an attacker to execute remote code (often malicious) on the target system
(Figure 3).</p>
        <p>
          CISA [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ] has reported this type of vulnerability that affects motion servers in robots and allows
an attacker to execute arbitrary code. Motion servers are programs that run on robot controllers
and are used to set up and control the motion of robots. The vulnerability is present in many OEM
robots and is not associated with any specific vendor.
        </p>
        <p>
          For example, ABB [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ] reported in 2020 that the OPC server for the AC 800M contained a
remote code execution vulnerability, CVE-2021-22284. An authenticated, low-privilege remote
user who successfully exploited this vulnerability could insert and execute arbitrary code on a
host running the AC800M OPC Server.
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Discussion</title>
      <p>
        As can be seen from the examples above, the sources of vulnerabilities in industrial robots
represent a variety of threats that can compromise the safety and efficiency of robotic systems.
These sources include network attacks, software bugs, insufficient security of network protocols,
authentication problems, physical threats, and even social engineering [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]. All of these factors
can contribute to vulnerabilities that attackers can use to gain access to and control robots,
creating potential production and security risks.
      </p>
      <p>To protect against such vulnerabilities, it is important to pay due attention to the cybersecurity
of industrial robots.</p>
      <p>
        To help protect against vulnerabilities and reduce risks, future projects should consider the
following scientific principles and methods:
• Engineer safety from the start: Safety must be built into the robot design process from the
very beginning. Consider potential threats and risks during the design and selection of
components [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ].
• Secure standards and protocols: Apply standards and protocols to ensure the safety of
robots and their network interactions. This includes the use of encryption and authentication
tools.
• Regular software updates: Implement mechanisms to regularly update robot software to
fix vulnerabilities and improve security.
• Integration of monitoring and incident detection systems: Include monitoring and
anomaly detection mechanisms in the robot system to quickly respond to possible attacks and
incidents.
• Proactive testing and security analysis: Conduct regular testing of robots for
vulnerabilities and weaknesses. This will help identify potential problems before they are
used.
• Collaborate with Cybersecurity Experts: Involve cybersecurity experts in robot
development and maintenance who can evaluate and improve system security.
• Physical Security: Ensure robots and their components are physically protected from
unauthorized access.
      </p>
      <p>
        Industrial automation remains insecure while traditional software developers have been
grappling with the consequences of insecure programming for decades. With the accelerating
convergence of information technology (IT) and operational technology (OT), the adoption of
secure code development methodologies in industrial automation has become important [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ].
Otherwise, serious industrial cyber incidents are possible in the coming years, with impacts in
both the digital and physical worlds.
      </p>
      <p>There is currently no globally standardized and mandatory cybersecurity certification for
industrial robots. However, such certification may become relevant and necessary in the future,
especially if the industry and customers begin to require it as a prerequisite for contracts and the
implementation of robotic systems. It is important to note that not all industrial robots are
equally vulnerable, and the need for mandatory certification may vary depending on the type of
robot and the specific threats.</p>
      <p>We propose for future research to implement security for manufacturing robots using
lightweight cryptography and granite computing, which represents a promising research
direction that could greatly impact the future of industrial automation.</p>
      <p>Lightweight cryptography will enable secure communication and data storage in robots'
limited computing resources. Granite computing involves performing calculations in a
distributed environment with maximum security. Granite computing allows robots to
collaboratively process data and perform tasks while minimizing the risk of leaking sensitive
information.</p>
    </sec>
    <sec id="sec-4">
      <title>4. Conclusion</title>
      <p>We concluded that cybersecurity systems in industrial robots often lag behind in development
compared to modern methods and threats. One of the reasons is that many robotic systems run
on outdated operating systems and software that are not regularly updated or adequately
monitored for vulnerabilities. This leaves the door open to potential attacks.</p>
      <p>In light of these factors, industrial robot developers should attach great importance to
updating and strengthening cybersecurity systems. This includes regular software updates,
implementation of modern authentication and authorization methods, and so on. Without such
measures, industrial automation systems may remain vulnerable to the ever-changing cyber
threat landscape. In addition, we believe that the creation of mandatory cybersecurity
certification for industrial robots has the potential to be a significant step in ensuring security in
industrial sectors.</p>
      <p>Our future research will focus on using lightweight cryptography and granite computing to
secure manufacturing robots, a promising direction in industrial automation. We envision that
this will enable secure communication and data storage with limited computing resources.</p>
    </sec>
    <sec id="sec-5">
      <title>5. Acknowledgements</title>
      <p>This research is funded by the Science Committee of the Ministry of Science and Higher Education
of the Republic of Kazakhstan (Project No. АP19677508).</p>
    </sec>
    <sec id="sec-6">
      <title>6. References</title>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>F.</given-names>
            <surname>Botta</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Rotbei</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Zinno</surname>
          </string-name>
          and
          <string-name>
            <given-names>G.</given-names>
            <surname>Ventre</surname>
          </string-name>
          (
          <year>2023</year>
          ).
          <article-title>Cyber security of robots: A comprehensive survey</article-title>
          ,
          <source>Intell. Syst. with Applic</source>
          . https://doi.org/10.1016/j.iswa.
          <year>2023</year>
          .
          <volume>200237</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>D.</given-names>
            <surname>Vibekananda</surname>
          </string-name>
          and
          <string-name>
            <given-names>T.</given-names>
            <surname>Zielińska</surname>
          </string-name>
          (
          <year>2021</year>
          ).
          <source>Cybersecurity of Robotic Systems: Leading Challenges and Robotic System Design Methodology, Electronics</source>
          <volume>10</volume>
          , no.
          <volume>22</volume>
          : 2850. https://doi.org/10.3390/electronics10222850.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>TXOne</surname>
          </string-name>
          <article-title>Networks blog</article-title>
          , “FANUC Robot
          <string-name>
            <surname>Off-Line Programming Path Traversal Vulnerability (CVE-2023-1864</surname>
          </string-name>
          <article-title>)”</article-title>
          ,
          <year>April 2023</year>
          . URL: https://www.txone.com/blog/fanuc
          <article-title>-robot-off-lineprogramming-path-traversal-vulnerability-cve20231864/.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>A.</given-names>
            <surname>Petrosyan</surname>
          </string-name>
          , “
          <article-title>Anticipated results of successful cyber attack against automation and/or robotics systems worldwide</article-title>
          as of
          <year>2017</year>
          .”,
          <year>August 2023</year>
          . URL: https://www.statista.com/statistics/780375/worldwide-anticipated
          <article-title>-result-of-cyberattacks-against-automation-and-or-robotics-systems/.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <surname>Kuka</surname>
          </string-name>
          , “
          <article-title>Security Advisory for the KUKA V/KSS WorkVisual Service Host access control vulnerability (CVE-</article-title>
          <year>2022</year>
          -2242)”,
          <year>2022</year>
          . URL: https://www.kuka.com/-/media/kukadownloads/manual-upload/services/kuka_psirt_advisory_kss_
          <source>wov_sh_2022-08- 04.pdf?rev=8ec87e743f5c43b8b7a3da93bb409b02.</source>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>F.</given-names>
            <surname>Maggi</surname>
          </string-name>
          and
          <string-name>
            <given-names>M.</given-names>
            <surname>Pogliani</surname>
          </string-name>
          (
          <year>2020</year>
          ).
          <article-title>Rogue Automation: Vulnerable and Malicious Code in Industrial Programming</article-title>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          <article-title>[7] ABB, “ CYBER SECURITY ADVISORY</article-title>
          .
          <article-title>SECURITY - OPC Server for AC 800M - Remote Code Execution Vulnerability</article-title>
          .
          <source>CVE ID: CVE-2021-22284.”</source>
          ,
          <year>2022</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          <article-title>[8] Cybersecurity and Infrastructure Security Agency, “ ICS Alert. Robot Motion Servers</article-title>
          .ICSALERT-
          <volume>20</volume>
          -217-01.”,
          <year>2020</year>
          . URL: https://www.cisa.gov/news-events/ics-alerts/ics-alert-
          <volume>20</volume>
          - 217-01.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>A.</given-names>
            <surname>Bhardwaj</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Avasthi</surname>
          </string-name>
          and
          <string-name>
            <given-names>S.</given-names>
            <surname>Goundar</surname>
          </string-name>
          (
          <year>2019</year>
          ).
          <article-title>Cyber security attacks on robotic platforms, Netw</article-title>
          . Sec.,
          <fpage>13</fpage>
          -
          <lpage>19</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>S.</given-names>
            <surname>Rivera</surname>
          </string-name>
          and
          <string-name>
            <given-names>R.</given-names>
            <surname>State</surname>
          </string-name>
          (
          <year>2021</year>
          ).
          <article-title>Securing robots: An integrated approach for security challenges and monitoring for the robotic operating system (ros)”, 2021 IFIP/IEEE Intern</article-title>
          .
          <source>Symp. on Integr. Netw. Managem. (IM)</source>
          , pp.
          <fpage>754</fpage>
          -
          <lpage>759</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>H.</given-names>
            <surname>Pu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>He</surname>
          </string-name>
          , P. Cheng, J. Chen and
          <string-name>
            <given-names>Y.</given-names>
            <surname>Sun</surname>
          </string-name>
          (
          <year>2023</year>
          ).
          <article-title>CORMAND2: A Deception Attack Against Industrial Robots”</article-title>
          , Engineering,
          <string-name>
            <surname>ISSN</surname>
          </string-name>
          <year>2095</year>
          -
          <volume>8099</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>J. P. A.</given-names>
            <surname>Yaacoub</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H. N.</given-names>
            <surname>Noura</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Salman</surname>
          </string-name>
          and
          <string-name>
            <given-names>A</given-names>
            .
            <surname>Chehab</surname>
          </string-name>
          (
          <year>2021</year>
          ).
          <article-title>Robotics cyber security: Vulnerabilities, attacks, countermeasures, and recommendations</article-title>
          .
          <source>Int. Jour. of Inf</source>
          . Sec. https://doi.org/10.1007/s10207-021-00545-8.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>B.</given-names>
            <surname>Dieber</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Breiling</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Taurer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Kacianka</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Rass</surname>
          </string-name>
          , and
          <string-name>
            <given-names>P.</given-names>
            <surname>Schartner</surname>
          </string-name>
          (
          <year>2017</year>
          ).
          <article-title>Security for the robot operating system</article-title>
          .
          <source>Rob. and Auton</source>
          . Syst.,
          <volume>98</volume>
          ,
          <fpage>192</fpage>
          -
          <lpage>203</lpage>
          . https://doi.org/10.1016/j.robot.
          <year>2017</year>
          .
          <volume>09</volume>
          .017.
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>A.</given-names>
            <surname>Khalid</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Kirisci</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z. H.</given-names>
            <surname>Khan.</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Ghrairi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K. D.</given-names>
            <surname>Thoben</surname>
          </string-name>
          and J.
          <string-name>
            <surname>Pannek</surname>
          </string-name>
          (
          <year>2018</year>
          ).
          <article-title>Security framework for industrial collaborative robotic cyber-physical systems</article-title>
          . Comp. in Indust.,
          <volume>97</volume>
          ,
          <fpage>132</fpage>
          -
          <lpage>145</lpage>
          . https://doi.org/10.1016/j.compind.
          <year>2018</year>
          .
          <volume>02</volume>
          .009.
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>M.</given-names>
            <surname>Pogliani</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Quarta</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Polino</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Vittone</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Maggi</surname>
          </string-name>
          and
          <string-name>
            <given-names>S.</given-names>
            <surname>Zanero</surname>
          </string-name>
          (
          <year>2019</year>
          ).
          <article-title>Security of controlled manufacturing systems in the connected factory: The case of industrial robots</article-title>
          .
          <source>Jour. of Comp. Virol. and Hack</source>
          . Tech.,
          <volume>15</volume>
          ,
          <fpage>161</fpage>
          -
          <lpage>175</lpage>
          . https:// doi.org/10.1007/s11416-019- 00329-8.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>