<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR</journal-id>
      <journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
      <journal-title>Journal of Medical Internet Research</journal-title>
      <issn pub-type="epub">1438-8871</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v25i1e41748</article-id>
      <article-id pub-id-type="pmid">37097723</article-id>
      <article-id pub-id-type="doi">10.2196/41748</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Artificial Intelligence–Based Ethical Hacking for Health Information Systems: Simulation Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Mavragani</surname>
            <given-names>Amaryllis</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Angelopoulos</surname>
            <given-names>Spyros</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Vasilakopoulou</surname>
            <given-names>Polyxeni</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author">
          <name name-style="western">
            <surname>He</surname>
            <given-names>Ying</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-2023-5547</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Zamani</surname>
            <given-names>Efpraxia</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-3110-7495</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Yevseyeva</surname>
            <given-names>Iryna</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-1627-7624</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Luo</surname>
            <given-names>Cunjin</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff4" ref-type="aff">4</xref>
          <address>
            <institution>School of Computer Science and Electronic Engineering</institution>
            <institution>University of Essex</institution>
            <addr-line>Wivenhoe Park</addr-line>
            <addr-line>Colchester, CO4 3SQ</addr-line>
            <country>United Kingdom</country>
            <phone>44 7493622995</phone>
            <email>cunjin.luo@essex.ac.uk</email>
          </address>
          <xref rid="aff5" ref-type="aff">5</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-3946-1093</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>School of Computer Science</institution>
        <institution>University of Nottingham</institution>
        <addr-line>Nottingham</addr-line>
        <country>United Kingdom</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Information School</institution>
        <institution>University of Sheffield</institution>
        <addr-line>Sheffield</addr-line>
        <country>United Kingdom</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>School of Computer Science and Informatics</institution>
        <institution>De Montfort University</institution>
        <addr-line>Leicester</addr-line>
        <country>United Kingdom</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>School of Computer Science and Electronic Engineering</institution>
        <institution>University of Essex</institution>
        <addr-line>Colchester</addr-line>
        <country>United Kingdom</country>
      </aff>
      <aff id="aff5">
        <label>5</label>
        <institution>Key Laboratory of Medical Electrophysiology, Ministry of Education &#38; Medical Electrophysiological Key Laboratory of Sichuan Province, Collaborative Innovation Center for Prevention of Cardiovascular Diseases, Institute of Cardiovascular Research</institution>
        <institution>Southwest Medical University</institution>
        <addr-line>Luzhou</addr-line>
        <country>China</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Cunjin Luo <email>cunjin.luo@essex.ac.uk</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2023</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>25</day>
        <month>4</month>
        <year>2023</year>
      </pub-date>
      <volume>25</volume>
      <elocation-id>e41748</elocation-id>
      <history>
        <date date-type="received">
          <day>7</day>
          <month>8</month>
          <year>2022</year>
        </date>
        <date date-type="rev-request">
          <day>23</day>
          <month>11</month>
          <year>2022</year>
        </date>
        <date date-type="rev-recd">
          <day>11</day>
          <month>12</month>
          <year>2022</year>
        </date>
        <date date-type="accepted">
          <day>19</day>
          <month>1</month>
          <year>2023</year>
        </date>
      </history>
      <copyright-statement>©Ying He, Efpraxia Zamani, Iryna Yevseyeva, Cunjin Luo. Originally published in the Journal of Medical Internet Research (https://www.jmir.org), 25.04.2023.</copyright-statement>
      <copyright-year>2023</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in the Journal of Medical Internet Research, is properly cited. The complete bibliographic information, a link to the original publication on https://www.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://www.jmir.org/2023/1/e41748" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Health information systems (HISs) are continuously targeted by hackers, who aim to bring down critical health infrastructure. This study was motivated by recent attacks on health care organizations that have resulted in the compromise of sensitive data held in HISs. Existing research on cybersecurity in the health care domain places an imbalanced focus on protecting medical devices and data. There is a lack of a systematic way to investigate how attackers may breach an HIS and access health care records.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study aimed to provide new insights into HIS cybersecurity protection. We propose a systematic, novel, and optimized (artificial intelligence–based) ethical hacking method tailored specifically for HISs, and we compared it with the traditional unoptimized ethical hacking method. This allows researchers and practitioners to identify the points and attack pathways of possible penetration attacks on the HIS more efficiently.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>In this study, we propose a novel methodological approach to ethical hacking in HISs. We implemented ethical hacking using both optimized and unoptimized methods in an experimental setting. Specifically, we set up an HIS simulation environment by implementing the open-source electronic medical record (OpenEMR) system and followed the National Institute of Standards and Technology’s ethical hacking framework to launch the attacks. In the experiment, we launched 50 rounds of attacks using both unoptimized and optimized ethical hacking methods.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>Ethical hacking was successfully conducted using both optimized and unoptimized methods. The results show that the optimized ethical hacking method outperforms the unoptimized method in terms of average time used, the average success rate of exploit, the number of exploits launched, and the number of successful exploits. We were able to identify the successful attack paths and exploits that are related to remote code execution, cross-site request forgery, improper authentication, vulnerability in the Oracle Business Intelligence Publisher, an elevation of privilege vulnerability (in MediaTek), and remote access backdoor (in the web graphical user interface for the Linux Virtual Server).</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>This research demonstrates systematic ethical hacking against an HIS using optimized and unoptimized methods, together with a set of penetration testing tools to identify exploits and combining them to perform ethical hacking. The findings contribute to the HIS literature, ethical hacking methodology, and mainstream artificial intelligence–based ethical hacking methods because they address some key weaknesses of these research fields. These findings also have great significance for the health care sector, as OpenEMR is widely adopted by health care organizations. Our findings offer novel insights for the protection of HISs and allow researchers to conduct further research in the HIS cybersecurity domain.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>health information system</kwd>
        <kwd>HIS</kwd>
        <kwd>ethical hacking</kwd>
        <kwd>open-source electronic medical record</kwd>
        <kwd>OpenEMR</kwd>
        <kwd>artificial intelligence</kwd>
        <kwd>AI-based hacking</kwd>
        <kwd>cyber defense solutions</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Context</title>
        <p>The health care sector is continuously targeted by cyberattackers, who seek to exploit undetected vulnerabilities in critical health infrastructure. Such attacks can cause service disruptions, financial losses, and harm to patients. In the 2017 WannaCry attack on the United Kingdom’s National Health Service (NHS), there was a substantial decrease in patients’ attendances and admissions numbers, which caused a £5.9 million (US $7.1 million) lost in terms of hospital activity [<xref ref-type="bibr" rid="ref1">1</xref>]. This study is motivated by recent security incidents that have increased during the COVID-19 pandemic, affecting health care organizations, such as the US Department of Health and Human Services, the World Health Organization (WHO), and pharmaceutical companies [<xref ref-type="bibr" rid="ref2">2</xref>]. Specifically, the United States Public Health Service reported that approximately 100 million pieces of patient information were stolen monthly by 2020 [<xref ref-type="bibr" rid="ref3">3</xref>]. Fortified Health Security, a leading organization in health care cybersecurity, reported that more than 400 health information system (HIS) providers had been breached, affecting approximately 13.5 million patients [<xref ref-type="bibr" rid="ref4">4</xref>]. In such cases, cyberattackers not only destroy the HIS but also gain access to and can modify sensitive health records that may mislead medical diagnosis [<xref ref-type="bibr" rid="ref5">5</xref>].</p>
        <p>The research community and health care industry have long realized the urgency to protect HISs [<xref ref-type="bibr" rid="ref6">6</xref>-<xref ref-type="bibr" rid="ref12">12</xref>]. However, existing cybersecurity research in the health care domain places an imbalanced focus on protecting medical devices [<xref ref-type="bibr" rid="ref13">13</xref>-<xref ref-type="bibr" rid="ref17">17</xref>] and medical data [<xref ref-type="bibr" rid="ref18">18</xref>], whereas previous studies do not offer a systematic approach for the investigation of HIS breaches or for improving cybersecurity more broadly. In this study, we propose a systematic approach to address this shortcoming based on ethical hacking. Typically, ethical hacking entails analyzing a system to identify potential weak points and then executing attacks to test the robustness of the system. Such approaches often entail using artificial intelligence (AI) and, most typically, reinforcement learning, for example [<xref ref-type="bibr" rid="ref19">19</xref>]. However, reinforcement learning has important shortcomings when it comes to the ethical hacking of HISs, namely, reinforcement learning requires large data sets for training purposes, which most often are unavailable. Therefore, as an approach, it can be unreliable [<xref ref-type="bibr" rid="ref20">20</xref>]; can cause severe issues for the HIS network [<xref ref-type="bibr" rid="ref21">21</xref>]; and requires skills and expertise, neither of which are widely available [<xref ref-type="bibr" rid="ref22">22</xref>].</p>
      </sec>
      <sec>
        <title>Objectives</title>
        <p>In our study, we address the above limitations by proposing a new optimization module for ethical hacking that uses the ant colony optimization (ACO) algorithm. The algorithm is characterized by positive feedback, distributed computation, and constructive greedy heuristics [<xref ref-type="bibr" rid="ref23">23</xref>]. ACO has been previously implemented in the cybersecurity domain, focusing on network intrusion detection, and has recently been proposed for vulnerability analysis and detection [<xref ref-type="bibr" rid="ref24">24</xref>].</p>
        <p>In this study, we built an HIS simulation platform by implementing an open-source electronic medical record (OpenEMR) system and drew from the ethical hacking framework from the National Institute of Standards and Technology (NIST), which we enriched by integrating ACO within its optimization module as part of our ethical hacking method to examine the exploitation of potential vulnerabilities of HISs. We then demonstrated ethical hacking for the HIS simulation environment using both optimized and unoptimized hacking methods and compared the results.</p>
        <p>Our study makes important contributions to the health care industry from a cybersecurity perspective. First, our methodological approach to ethical hacking provides important insights into the protection of HISs. It allows practitioners to identify potential vulnerabilities in their systems and offers researchers several avenues for future research. Second, our optimized ethical hacking approach addresses the weaknesses of preexisting frameworks by proposing an intelligent and maintainable ethical hacking solution. To the best of our knowledge, there is no systematic AI-based ethical hacking method that is tailored for health care organizations. Our research makes a major theoretical and practical contribution to the field of digital health by addressing the security aspects of digital medicine infrastructure, which will ultimately improve the quality of security practices of large health care organizations. In doing so, our findings indirectly inform cognate disciplines, namely information systems literature and cybersecurity, by being centered on a core information system element [<xref ref-type="bibr" rid="ref25">25</xref>].</p>
      </sec>
      <sec>
        <title>Background</title>
        <sec>
          <title>HIS Security</title>
          <p>New technologies have been advancing the field of HISs and improving the quality of services in the health care sector [<xref ref-type="bibr" rid="ref26">26</xref>-<xref ref-type="bibr" rid="ref28">28</xref>]. Some advanced HISs support medical diagnoses based on existing health records and data gathered from intelligent medical devices. Such systems significantly reduce the workload of health care professionals and enable early detection, diagnosis, and intervention, thereby increasing the success rate of treatment [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref30">30</xref>]. However, new technologies introduce new security risks for HISs, and the lack of sufficient security control is a concern [<xref ref-type="bibr" rid="ref31">31</xref>]. According to recent studies, HISs have major security vulnerabilities [<xref ref-type="bibr" rid="ref32">32</xref>-<xref ref-type="bibr" rid="ref34">34</xref>] and privacy concerns [<xref ref-type="bibr" rid="ref35">35</xref>]. For example, access to insecure web pages and default coded passwords are common vulnerabilities introduced by medical devices [<xref ref-type="bibr" rid="ref36">36</xref>]. Similarly, insecure communications on unauthorized and unencrypted web services are also common vulnerabilities because they allow cyberattackers to gain remote access to HISs [<xref ref-type="bibr" rid="ref37">37</xref>].</p>
          <p>As a result, to date, most studies in the health care cybersecurity domain have focused primarily on increasing the security of medical devices [<xref ref-type="bibr" rid="ref13">13</xref>-<xref ref-type="bibr" rid="ref17">17</xref>] and the protection of medical data [<xref ref-type="bibr" rid="ref18">18</xref>]. For example, a common approach is to implement data encryption mechanisms [<xref ref-type="bibr" rid="ref13">13</xref>], often in combination with scrambling techniques [<xref ref-type="bibr" rid="ref18">18</xref>], to protect wavelet-based electrocardiogram (ECG) data both in transit and storage. Other popular solutions involve the design and use of access control schemes to further increase the protection of shared health data [<xref ref-type="bibr" rid="ref14">14</xref>], implementation of authentication protocols for wearable devices [<xref ref-type="bibr" rid="ref15">15</xref>], and adoption of privacy-aware profile management approaches that help manage the privacy of patient electronic profiles [<xref ref-type="bibr" rid="ref14">14</xref>]. In other cases, the proposed solutions involve mechanisms that enhance heartbeat-based security [<xref ref-type="bibr" rid="ref17">17</xref>]. However, existing research has not yet offered a systematic approach or methods to investigate and understand how attackers can breach HISs and access health care records. To address this, we discuss the ethical hacking methods that have been proposed by cybersecurity research, which can provide a systematic approach.</p>
        </sec>
        <sec>
          <title>Ethical Hacking Methods</title>
          <p>Some of the most widely adopted ethical hacking methods are the NIST framework [<xref ref-type="bibr" rid="ref38">38</xref>], Penetration Testing Execution Standard (PTES), and framework proposed by the Open Web Application Security Project (OWASP). In addition, different organizations often develop their own organization-specific methods that correspond to their particular organizational needs [<xref ref-type="bibr" rid="ref22">22</xref>].</p>
          <p>Both ethical hacking and penetration testing are authorized attempts to gain unauthorized access to computer systems or data. Penetration testing is a subset of the ethical hacking methods. Penetration testing assesses a specific aspect of a system that is usually restricted by an outlined scope, whereas ethical hacking has more flexibility without being restricted [<xref ref-type="bibr" rid="ref39">39</xref>]. However, systematic ethical hacking or penetration testing typically includes 4 main modules: information gathering, discovery, attacking, and reporting. The tester performs a reconnaissance at the information-gathering stage and collects information about the target HIS. At the discovery stage, the tester attempts to understand the system’s structure of the system and analyze its paths and directories. Next, the tester identifies the vector to attack at the attack stage, which is typically based on the vulnerability scanner results. Finally, at the reporting stage, the tester uses all evidence gathered during the previous stages to prepare a report documenting major findings.</p>
          <p>The extent to which such ethical hacking methods will be successful largely depends on the skills and expertise of professional testers involved in penetration testing. However, the number of skilled programmers in cybersecurity, particularly in the health care domain, is limited [<xref ref-type="bibr" rid="ref22">22</xref>]. This means that on the one hand, it is difficult to identify the necessary talent for ethical hacking within such complex environments, whereas on the other hand, there is a risk of poorer performance when the required skills are not available.</p>
        </sec>
        <sec>
          <title>Ethical Hacking Tools and Solutions</title>
          <p>Nettacker, a solution developed by OWASP, contains an optimization module, but it is not as mature, not fully published, and lacks an exploit module. This means that a given user will have to select the exploit tools and payload on their own, which can be challenging for nonexperts in cybersecurity. APT2, the solution offered by the Massachusetts Institute of Technology, uses Network Mapper (Nmap) to scan information. An exploit can be launched from its library, depending on the scanning information, and it has a knowledge base that can record the information of the targeted host. Nevertheless, it lacks an optimization module. This finding suggests that the accuracy and efficiency of ethical hacking risks are inferior. Similar to APT2, Autosploit [<xref ref-type="bibr" rid="ref40">40</xref>], a solution that combines Shodan, Censys, Zoomeye, and Metasploit, does not have an optimization module. It is easy to conduct ethical hacking using this solution because it requires only logging into a Shodan account and provides details regarding the targeted host. After performing a search, Shodan will provide the open port, the vulnerabilities that exist, and tools for the exploit, which will then be able to input this information to Metasploit, specifying the local host and the local port [<xref ref-type="bibr" rid="ref41">41</xref>]. Metasploit can then run the exploit automatically. However, similar to APT2, Autosploit risks have less accuracy and efficacy because it cannot be optimized. Currently, it is unfeasible to test all possible system configurations. An earlier study attempted to address this problem and proposed the use of generalized binary splitting and the Barinel method to optimize the efficiency of Autosploit [<xref ref-type="bibr" rid="ref40">40</xref>]. Although this approach positively influenced Autosploit’s performance, the tool library and database of vulnerabilities stopped being updated in 2019 and are now outdated.</p>
        </sec>
        <sec>
          <title>AI-Based Ethical Hacking in HISs</title>
          <p>Ethical hacking methods often use AI techniques. Among those most often used is reinforcement learning, which helps identify and analyze vulnerabilities in information systems. To date, reinforcement learning has been successfully applied in simulated environments to analyze vulnerabilities using the Partially Observed Markov Decision Process [<xref ref-type="bibr" rid="ref42">42</xref>] and within the context of applied Q-learning with a deep neural network architecture [<xref ref-type="bibr" rid="ref19">19</xref>]. However, these approaches tend to offer mostly theoretical insights and are being implemented in MATLAB; to date, they have not been systematically integrated into any ethical hacking method. Another major shortcoming is that reinforcement <italic>learning</italic> requires a vast amount of data and ample time to train the model. In reality, it is unlikely that a single targeted host will exhibit sufficient vulnerabilities to train the algorithm. Additionally, reinforced learning can be unreliable for ethical hacking. For example, it has been used in the past for learning control policies in Atari games, whereby an agent triggers several bugs to achieve a high score; however, such behavior does not form part of the ethical hacking plan [<xref ref-type="bibr" rid="ref21">21</xref>] and causes severe problems for the whole network, which is undesirable. Finally, most importantly, reinforcement learning is characterized by low reproducibility because of its data requirements and because its results can be negatively affected by even small environmental changes such as machine upgrades [<xref ref-type="bibr" rid="ref20">20</xref>].</p>
        </sec>
        <sec>
          <title>ACO Approach</title>
          <p>In this paper, we propose the use of the ACO approach as an optimization algorithm to enhance the optimization module for ethical hacking. This algorithm is characterized by positive feedback, distributed computation, and constructive greedy heuristics [<xref ref-type="bibr" rid="ref23">23</xref>] and can be particularly beneficial during attack path analysis, which is the core part of ethical hacking optimization.</p>
          <p>ACO is an evolutionary algorithm often used to solve various optimization problems, for example, the traveling salesman problem (TSP). Optimization problems such as the TSP are particularly relevant to identifying and analyzing attack paths as part of ethical hacking, as in both cases, the objective is to construct the shortest path between the point of origin and the target point. In more detail, the goal of the TSP is to identify the shortest or quickest path for a salesman to arrive at their destination while covering all nodes between the point of origin and the target point and visiting them only once. Similarly, in ethical hacking, the goal is to attack the targeted machine by investigating some already known vulnerabilities and their exploitation (exploits) that can be combined to complete the attack successfully.</p>
          <p>To date, the ACO approach has been implemented in the cybersecurity domain, focusing on network intrusion detection, which is a passive form of defense. More recently, it was proposed to be efficient for vulnerability analysis and detection, informed by bioinspired cybersecurity research [<xref ref-type="bibr" rid="ref24">24</xref>]. On the basis of these earlier findings, our study integrated ACO within the optimization module of ethical hacking to examine its performance regarding the exploitation of potential vulnerabilities of HISs.</p>
        </sec>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Simulation Platform</title>
        <p>For the purposes of our study, we set up a virtual environment to avoid acting directly in a real-world setting, thus causing potential damage to the HIS. Specifically, we designed an experiment to simulate an HIS.</p>
        <sec>
          <title>Targeted Host and Attack Host</title>
          <p>In ethical hacking, the targeted host machine is attacked by the host machine. We installed the Kali Linus System 2021.1 on a virtual machine workstation in our simulation environment, which acts as the attack host. In addition, we installed Ubuntu 20.04.2.0 on another virtual machine workstation, which acted as the targeted host. <xref ref-type="table" rid="table1">Table 1</xref> summarizes the hardware details of the target and attack hosts. Information on the software and services of the targeted host that simulates a medical worker is presented in <xref ref-type="table" rid="table2">Table 2</xref>.</p>
          <p>As part of our experiment, we adapted the NIST ethical hacking framework [<xref ref-type="bibr" rid="ref38">38</xref>] and follow the core planning, discovery, attack, and reporting modules. We first set up a simulation environment by implementing an OpenEMR system and then launched ethical hacking to exploit the vulnerabilities of the simulated HIS.</p>
          <table-wrap position="float" id="table1">
            <label>Table 1</label>
            <caption>
              <p>Hardware details for the targeted machine and attack machine.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="300"/>
              <col width="300"/>
              <col width="400"/>
              <thead>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Target host</td>
                  <td>Attack host</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Location</td>
                  <td>VM<sup>a</sup> workstation</td>
                  <td>VM workstation</td>
                </tr>
                <tr valign="top">
                  <td>System</td>
                  <td>Ubuntu 20.04.2.0</td>
                  <td>Kali Linux system 2021.1</td>
                </tr>
                <tr valign="top">
                  <td>Kernel</td>
                  <td>Linux version 5.8.0-59-generic</td>
                  <td>Linux version 5.8.0-59-generic</td>
                </tr>
                <tr valign="top">
                  <td>Memory</td>
                  <td>4 GB</td>
                  <td>4 GB</td>
                </tr>
                <tr valign="top">
                  <td>Bandwidth</td>
                  <td>100 Mbps<sup>b</sup></td>
                  <td>100 Mbps</td>
                </tr>
                <tr valign="top">
                  <td>Hard disk space</td>
                  <td>2 GB</td>
                  <td>20 GB</td>
                </tr>
                <tr valign="top">
                  <td>Core of CPU<sup>c</sup></td>
                  <td>8</td>
                  <td>4</td>
                </tr>
                <tr valign="top">
                  <td>Kind of CPU</td>
                  <td>Intel core i7-9750 CPU 2.6 GHz</td>
                  <td>Intel core i7-9750 CPU 2.6 GHz</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table1fn1">
                <p><sup>a</sup>VM: virtual machine.</p>
              </fn>
              <fn id="table1fn2">
                <p><sup>b</sup>Mbps: megabits per second.</p>
              </fn>
              <fn id="table1fn3">
                <p><sup>c</sup>CPU: central processing unit.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
          <table-wrap position="float" id="table2">
            <label>Table 2</label>
            <caption>
              <p>Software and services used on the targeted machine.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="180"/>
              <col width="240"/>
              <col width="580"/>
              <thead>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Version</td>
                  <td>Description</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>PHP</td>
                  <td>PHP v8.1.0</td>
                  <td>PHP is a hypertext preprocessor, ie, a scripting language on a server, which is used by OpenEMR<sup>a</sup>.</td>
                </tr>
                <tr valign="top">
                  <td>Apache2</td>
                  <td>Apache v2.0</td>
                  <td>Apache is the most popular web server software for building a website. In the targeted host, it is used by OpenEMR.</td>
                </tr>
                <tr valign="top">
                  <td>MySQL</td>
                  <td>MySQL v5.7.17</td>
                  <td>MySQL is one of the most popular relational database management systems. It has a small volume, high speed, and low maintainable cost, which is used by OpenEMR.</td>
                </tr>
                <tr valign="top">
                  <td>MySQL</td>
                  <td>MySQL v5.7.17</td>
                  <td>MySQL is one of the most popular relational database management systems. It has a small volume, high speed, and low maintainable cost, which is used by OpenEMR.</td>
                </tr>
                <tr valign="top">
                  <td>OpenEMR</td>
                  <td>OpenEMR v6.0.0</td>
                  <td>OpenEMR is an open-source electronic medical record system. In the targeted host, it is used to simulate a medical worker’s machine.</td>
                </tr>
                <tr valign="top">
                  <td>Vsftp</td>
                  <td>Vsftp v3.0.3</td>
                  <td>Vsftp provides a designedly open port installed for the experiment environment. It has many dangerous vulnerabilities.</td>
                </tr>
                <tr valign="top">
                  <td>OpenSSH-server</td>
                  <td>OpenSSH-server v1.8.2</td>
                  <td>OpenSSH-server provides a designedly open port installed in the experiment environment. It has many dangerous vulnerabilities.</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table2fn1">
                <p><sup>a</sup>OpenEMR: open-source electronic medical record.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
        </sec>
        <sec>
          <title>OpenEMR Implementation</title>
          <p>In our HIS simulation platform, we implemented OpenEMR. Overall, OpenEMR is a complex system with key functionalities, including practice management, EMR management, scheduling, electronic billing, prescribing, a patient portal, and a clinical decision support system, and has a complex database of more than 100 tables. We purposefully chose to implement this HIS because it supports a comprehensive security risk-management scheme based on the Health Insurance Portability and Accountability Act and NIST standards [<xref ref-type="bibr" rid="ref43">43</xref>]. In addition, it is certified by the Office of the National Coordinator for Health Information Technology, which can run on different platforms such as Windows, Linux, and Mac OS X, and it is the most widely adopted HIS [<xref ref-type="bibr" rid="ref44">44</xref>].</p>
        </sec>
      </sec>
      <sec>
        <title>AI-Based Ethical Hacking Method</title>
        <sec>
          <title>Overview</title>
          <p>Our adaptation of the NIST ethical hacking framework [<xref ref-type="bibr" rid="ref38">38</xref>] consisted of following 6 modules: scanning, discovery, exploitation, optimization, reporting, and control. In other words, we used the original NIST modules, but further enhanced them with 2 additional modules: optimization and control. <xref ref-type="table" rid="table3">Table 3</xref> summarizes the key activities of each stage.</p>
          <p>We conducted a comparative experiment between AI-based and non–AI-based ethical hacking methods. Although the AI-based experiment followed the 6 stages of the ethical hacking method as indicated above, the non–AI-based experiment followed the same method without executing the optimization module. Optimized and unoptimized penetration tests were performed 50 times to reduce the uncertainty caused by the simulation environment. In each run, information on the time, the number of exploits, and the number of successful exploits were recorded and compared.</p>
          <p>Generally, the results from each module were first recorded and then used in each subsequent module. <xref rid="figure1" ref-type="fig">Figure 1</xref> shows the interactions between different modules and the results from each module.</p>
          <table-wrap position="float" id="table3">
            <label>Table 3</label>
            <caption>
              <p>Key activities and the National Institute of Standards and Technology (NIST) method coverage of the (artificial intelligence [AI]–based) ethical hacking method.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="260"/>
              <col width="540"/>
              <col width="200"/>
              <thead>
                <tr valign="top">
                  <td>(AI-based) ethical hacking stages</td>
                  <td>Key activities</td>
                  <td>NIST method stages</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Scanning</td>
                  <td>Use the Nmap<sup>a</sup> scanning tool to identify the number of ports, port status, protocol, and operating system</td>
                  <td>Planning discovery</td>
                </tr>
                <tr valign="top">
                  <td>Discovery</td>
                  <td>Use the Xray scanning tool to identify vulnerabilities</td>
                  <td>Planning discovery</td>
                </tr>
                <tr valign="top">
                  <td>Exploiting</td>
                  <td>Use attacking tools (eg, SQLMap and Metasploit) to probe networks, applications, and database-related flaws and vulnerabilities</td>
                  <td>Attack</td>
                </tr>
                <tr valign="top">
                  <td>Optimizing (optional)</td>
                  <td>Optimize attack paths using AI (eg, ACO<sup>b</sup>)</td>
                  <td>Discovery attack</td>
                </tr>
                <tr valign="top">
                  <td>Controlling</td>
                  <td>Coordinate the modules to launch attacks and set ethical hacking preferences</td>
                  <td>Planning discovery attack</td>
                </tr>
                <tr valign="top">
                  <td>Reporting</td>
                  <td>Collect and report results on the exploit</td>
                  <td>Reporting</td>
                </tr>
              </tbody>
            </table>
            <table-wrap-foot>
              <fn id="table3fn1">
                <p><sup>a</sup>Nmap: Network Mapper.</p>
              </fn>
              <fn id="table3fn2">
                <p><sup>b</sup>ACO: ant colony optimization.</p>
              </fn>
            </table-wrap-foot>
          </table-wrap>
          <fig id="figure1" position="float">
            <label>Figure 1</label>
            <caption>
              <p>Interactions between different modules.</p>
            </caption>
            <graphic xlink:href="jmir_v25i1e41748_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Scanning Module</title>
          <p>As part of the scanning module, we scanned the host information of the targeted machine, including the port, operating system, and installed service of the targeted machine. Nmap was used as a scanning tool to collect this information. Other similar tools included ZMap and Masscan. ZMap has an accuracy rate similar to that of NMap, but its computational time is higher [<xref ref-type="bibr" rid="ref40">40</xref>]. Masscan is faster, but its accuracy rate is lower, particularly when the scanning area increases [<xref ref-type="bibr" rid="ref40">40</xref>]. Therefore, we selected Nmap because of its accuracy and efficiency (computational time) and because it has more than 200 extension scripts for scanning.</p>
          <p>We developed the following 2 versions of Nmap scanning scripts: the first was used for a single IP address and the other was used for an IP address segment. For a single IP address, Nmap scanning imports the IP from the control modules, checks whether the host is alive, and then scans and reports the results. For an IP address segment, the tool adopts multithreading to support multiple IP addresses in an IP address segment, and, as in the previous case, it then scans and reports the results.</p>
        </sec>
        <sec>
          <title>Discovery Module</title>
          <p>This module focuses on obtaining vulnerability-related information of the target host. Existing vulnerability scanning tools include Nessus, NexSpose, and Xray. Although Nessus and Nexpose have a Metasploit application programming interface, and their vulnerability data set is one of the largest for vulnerability scanning, they are costly, and the education version has a limited number of vulnerabilities and ports.</p>
          <p>In this study, Xray was selected for vulnerability scanning using the basic crawler method. Xray is a free vulnerability scanning tool, and their performance is comparable to that of Nessus and Nexpose. Xray supports diverse operating systems such as Windows, Linux, and Mac. As a passive scanning tool, it is much faster than active scanning because the latter requires sending requests to the targeted host and waiting for a response. Passive scanning is also challenging to detect using a targeted host. Xray also supports the use of web scanning. The Xray output is a JSON file that contains the type, payload, and target of the vulnerability. Because the targeted machine is an HIS using OpenEMR, the web scanning module can help detect vulnerabilities in OpenEMR.</p>
        </sec>
        <sec>
          <title>Exploiting Module</title>
          <p>This module launches attacks on the targeted host by leveraging the information gathered in the previous modules. This module applies ethical hacking tools, namely, SQLMap and Metasploit. Many exploiting tools provide similar performance and functionalities; however, we selected Metasploit as the primary attack tool because it is the most powerful and widely used tool in the field. This tool integrates several application programming interfaces that can be used for manual and automated exploitation using predefined settings. When conducting a manual penetration test, the tester must set up the targeted information and tools used for exploitation. The exploitation procedure is replaced by a resource scripts file that configures the Metasploit when using automated scripts. In our study, we imported output files from Nmap and Xray, ran automated exploits, and extracted the exploitation results.</p>
          <p>In addition, as the database is an essential component of the HIS, attacks should be launched as part of ethical hacking, and the vulnerabilities of the database should be exploited. For this purpose, we used SQLMap to conduct attacks on a database that launches attacks by executing malicious SQL commands in the web input. It supports 5 types of SQL injections and can launch other types of exploits, such as XSS (cross-site scripting) injection [<xref ref-type="bibr" rid="ref45">45</xref>]. By exploiting database vulnerabilities using SQLMap, the attacker can tamper with or steal digital data and information, remotely control the database, crash the hard disk, and control the system using Trojan viruses [<xref ref-type="bibr" rid="ref46">46</xref>]. However, this behavior does not damage the targeted host, which is essential because the penetration test aims to enhance security rather than destroy the system. In our experiment, SQLMap imported the JSON output file from Xray and retrieved the URL for SQL injection. It then launched the attack automatically and exported a file using exploitation results.</p>
        </sec>
        <sec>
          <title>Optimizing Module</title>
          <p>For the optimizing module, we used ACO as the optimization algorithm for the optimization module. ACO simulates the behavior of ants to identify the shortest path(s) and pheromone-based communication within the colony. Attack path analysis is a core aspect of ethical hacking optimization. In ethical hacking, the goal is to attack the targeted machine using known paths, and the objective is to identify the shortest or fastest path to achieve this. The most common example of using ACO is to solve the TSP, where the shortest or fastest path is searched for by a salesman to deliver goods in all cities by exploring various paths and visiting each city exactly once. Ethical hacking has a similar goal, whereby the objective is to attack the targeted machine by exploiting as few known vulnerabilities as possible to successfully and swiftly complete the attack. Various paths between the origin and target machines can be built by combining exploits and finding the shortest or fastest way to do so. <xref ref-type="boxed-text" rid="box1">Textbox 1</xref> demonstrates the optimization procedure for ACO.</p>
          <p>The optimization module reads the file (“ant_cve.json”) as the input, which contains the history information of the exploits of the targeted host. Common vulnerabilities and exposures were allocated to different nodes of the vulnerability matrix. The path represents the set of successful exploits selected out of all the launched exploits, the ant represents a potential solution, and a path composed of a set of exploits is described as the payload. The concentration at each node depends on the severity level of the identified vulnerability. Here, each ant probes for building a path by combining nodes of the path into a successful trial and informs other ants on the results of such an attempt by sharing certain information, such as the intensity of the trail between 2 nodes <italic>i</italic> and <italic>j</italic> at some moment of time <italic>t</italic>, denoted as <inline-graphic xlink:href="jmir_v25i1e41748_fig4.png" xlink:type="simple" mimetype="image"/>
 and visibility <inline-graphic xlink:href="jmir_v25i1e41748_fig5.png" xlink:type="simple" mimetype="image"/></p>
          <p>ACO starts with initialization, where the number of ants (m=40) is selected, and the number of iterations is set to 50. Initially, all the ants were positioned in different nodes of the vulnerability matrix. The intensity of the trail between each pair of nodes <italic>i</italic> and <italic>j</italic> at the initial moment of time <italic>0</italic> was set to a small constant <inline-graphic xlink:href="jmir_v25i1e41748_fig6.png" xlink:type="simple" mimetype="image"/>. The pheromone concentration <inline-graphic xlink:href="jmir_v25i1e41748_fig7.png" xlink:type="simple" mimetype="image"/> is updated after each iteration of each path as follows:</p>
          <disp-formula>
            <graphic xlink:href="jmir_v25i1e41748_fig8.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </disp-formula>
          <p>where <italic>ρ</italic> is the volatilization of pheromone, and it refers to reductions in the pheromone after each run, which is set to <italic>ρ</italic>=0.3, according to Axinte [<xref ref-type="bibr" rid="ref46">46</xref>], and <inline-graphic xlink:href="jmir_v25i1e41748_fig9.png" xlink:type="simple" mimetype="image"/> is computed as follows:</p>
          <disp-formula>
            <graphic xlink:href="jmir_v25i1e41748_fig10.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </disp-formula>
          <p>where <italic>Q</italic> is a constant and <italic>L<sub>k</sub></italic> is the length of the <italic>k</italic>th ant tour.</p>
          <p>The visibility for a pair of 2 node is computed as <inline-graphic xlink:href="jmir_v25i1e41748_fig11.png" xlink:type="simple" mimetype="image"/> and is an inverse of the Euclidian distance between them. The global best and shortest path value was computed as the distance between the origin and target. It was initially set to 9999, and the evolution process was started by updating it to any real distance value after the computation of the first path at the end of the first iteration.</p>
          <p>The transition probability for each pair of nodes <italic>i</italic> and <italic>j</italic> for the <italic>k</italic>th ant can then be computed as follows:</p>
          <disp-formula>
            <graphic xlink:href="jmir_v25i1e41748_fig12.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </disp-formula>
          <p>where <italic>allowed</italic> is the set of not yet visited nodes, α is the weight of the pheromone, and β is the weight of the heuristic value [<xref ref-type="bibr" rid="ref23">23</xref>]; here, they are set to α=.7 and β=.7, as suggested in Liu et al [<xref ref-type="bibr" rid="ref47">47</xref>].</p>
          <p>Each successful use of an exploit increases the concentration of pheromones for a pair of exploits that are connected successfully.</p>
          <p>An ant explores a set of nodes vulnerabilities presented in a matrix in an attempt to construct a successful exploitation path. Whenever a successful exploitation is recorded, the current successful path is compared with the global best path found in all runs thus far and updated every time a shorter path is found.</p>
          <p>The end condition for each literation was whether all the ants visited all the nodes in the vulnerability matrix. When all iterations have finished, ACO ends and provides results on the global best path.</p>
          <p>After the final iteration, the optimization module reports the list of attack paths and prioritizes the paths with the highest pheromone concentration. The output was then stored as a *.csv file, titled “ant_output.csv,” which contains information on the common vulnerabilities and exposures, exploit, and used payload.</p>
          <boxed-text id="box1" position="float">
            <title>Algorithm 1 (the ant colony optimization [ACO] algorithm: ACO(Num_Iters, Num_Ants, VulnerList).</title>
            <p>Require: </p>
            <p>NumIters (NumIters &#62;0) # the maximum number of iterations,</p>
            <p>NumAnts (NumAnts &#62;0) # the maximum number of ants,</p>
            <p>VulnerList # the vulnerability exploits list.</p>
            <p>Ensure</p>
            <p>The best path (BestPath) is exported.</p>
            <p>1: BestPath ← 0; BestPathDist ← 99999999;</p>
            <p>2: For k← 1: NumIters do</p>
            <p>3: LocalBestPath ← 0; LocalBestPathDist ← 99999999; # local best path for a single iteration</p>
            <p>4: PheromCons ← zeros([][]); # matrix of pheromone concentrations for all pairs of ants.</p>
            <p>5: For i← 1: NumAnts do</p>
            <p>6: Vulner_i = VulnerList[i];</p>
            <p>7: For j← 1: NumAnts do</p>
            <p>8: Vulner_j = VulnerList[j];</p>
            <p>9: p_ij=compute_Pij(Vulner_i, Vulner_j); # transition probability for pair (i,j).</p>
            <p>10: CurrentPath_ij=computeProbablePath(p_ij, Vulner_i, Vulner_j); # path for pair (i,j)</p>
            <p>11: CurrentPathDist=computerPathDist(CurrentPath_ij); # distance for path (i,j).</p>
            <p>12: PheromCons(i,j) = updatePheromCons(CurrentPath_ij); # update of pheromon matrix</p>
            <p>13: If (CurrentPathDist&#60;LocalBestPathDist)</p>
            <p>14: LocalBestPath=CurrentPath; # update of the shortest local path</p>
            <p>15: LocalPathDist=CurrentPathDist; # update of the shortest local path distance</p>
            <p>16: End if</p>
            <p>17: End for #NumAnts with j index</p>
            <p>18: End for #NumAnts with i index</p>
            <p>19: If (LocalBestPathDist&#60;BestPathDist)</p>
            <p>20: BestPath=LocalBestPath; # update of the shortest global path</p>
            <p>21: BestPathDist=LocalBestPathDist; # update of the shortest global path distance</p>
            <p>22: End if</p>
            <p>23: End for #NumIters</p>
            <p>24: return BestPath</p>
          </boxed-text>
        </sec>
        <sec>
          <title>Controlling Module</title>
          <p>The controlling module imports the results produced from the previous modules, and it is necessary to conduct ethical hacking and launch attacks. Users can control the penetration test via an interactive user interface and set the targeted machine’s IP address or IP address segment of the targeted machine. The module then transmits this information to the information and vulnerability scanning modules. Once the scanning module is completed, users have to decide whether optimization is needed, and based on their decision, the optimization module will be triggered. This, in turn, calls the exploiting module to launch the attack on the targeted host. At the end of the procedure, this module sends its results to the reporting module, recording the time required to carry out ethical hacking for each module.</p>
        </sec>
        <sec>
          <title>Reporting Module</title>
          <p>The reporting module collected the results of ethical hacking. Two sets of results (.csv files) were generated. The first set reports the time used for each module and the number and success rate of the launched exploits. This information can also be used to evaluate the performance of the algorithm in the optimization module. The second set of results contains information regarding the vulnerabilities themselves and can help users understand the targeted host’s security status and, therefore, act accordingly. <xref rid="figure2" ref-type="fig">Figure 2</xref> summarizes the execution of the ethical hacking framework.</p>
          <fig id="figure2" position="float">
            <label>Figure 2</label>
            <caption>
              <p>Flowchart of the ethical hacking framework. ACO: ant colony optimization.</p>
            </caption>
            <graphic xlink:href="jmir_v25i1e41748_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
      </sec>
      <sec>
        <title>Ethical Considerations</title>
        <p>As our research does not involve human participants directly or indirectly (eg, observations of public behaviors or secondary analyses of research data), ethics approval, informed consent, and compensation for human participants research were not required. In addition, the design of our study was based on simulations conducted within an experimental setting; as such, it did not raise any privacy or confidentiality concerns.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <p>We performed AI-based (optimized) and non–AI-based (unoptimized) ethical hacking on the target machine (host IP 192.168.1.44). The AI-based experiment followed the novel ethical hacking framework (see the <italic>Methods</italic> section). The non–AI-based experiment followed the same method but omitted the optimization module. <xref ref-type="table" rid="table4">Table 4</xref> shows the key activities across the different modules according to the proposed 6-stage ethical hacking method.</p>
      <p>Both the optimized and the unoptimized ethical hacking were run 50 times (50 runs) each to account for the stochastic nature of ACO and to reduce the uncertainty owing to the simulation environment. The information regarding execution time, the number of exploits investigated, and the number of successful exploits used to construct the attack path was recorded for each run.</p>
      <p><xref ref-type="table" rid="table5">Table 5</xref> presents the results of 50 runs of comparison of unoptimized and optimized ethical hacking methods, where the average time used to perform the penetration test, the success rate of all penetration tests, and the highest and average rates of exploits with regard to all exploits were used as comparison metrics. The highest numbers of exploits were 11 and 20, the average numbers of launched exploits were 8 and 14, the numbers of successful penetration tests were 32 and 42, the numbers the highest number of successful exploits were 9 and 18, and the average numbers of successful exploits were 5 and 11 for the unoptimized and optimized ethical hacking methods, respectively.</p>
      <p><xref rid="figure3" ref-type="fig">Figure 3</xref> depicts in a box plot (each box composed by quartiles 1-3) the total number of launched exploits (<xref rid="figure3" ref-type="fig">Figure 3</xref>A) and successful exploits (<xref rid="figure3" ref-type="fig">Figure 3</xref>B) for both optimized and unoptimized ethical hacking methods with the average (indicated by X), median (indicated by straight line across the box), and SD (indicated by whiskers, which might go outside of the box plot or overlap with it). <xref rid="figure3" ref-type="fig">Figure 3</xref>C depicts the box plots of the rate of successful exploits with respect to the total number of exploits, and <xref rid="figure3" ref-type="fig">Figure 3</xref>D shows the average execution time for both optimized and unoptimized ethical hacking methods.</p>
      <p>To show an example of the results in a single run, the last run out of 50 runs for the unoptimized and optimized ethical hacking methods were compared for the penetration test for 192.168.1.44. The results of the unoptimized method show that the method ran for 177 seconds; out of 9 exploits, 7 were successful; and these exploits were related to improper input validation, cross-site request forgery, remote code execution (in Windows Remote Desktop Gateway), denial of service attacks, improper authentication, remote access backdoors, and the deserialization of untrusted data. In the case of the optimized method, the method ran for 153 seconds, and only 6 exploits were investigated, all of which were used to build a successful attack path.</p>
      <p>The details of the exploits used for building a successful path are presented in <xref ref-type="table" rid="table6">Table 6</xref>, which are related to remote code execution, cross-site request forgery, improper authentication, vulnerability in the Oracle Business Intelligence Publisher, an elevation of privilege vulnerability (in MediaTek), and remote access backdoor (in the web graphical user interface for the Linux Virtual Server).</p>
      <table-wrap position="float" id="table4">
        <label>Table 4</label>
        <caption>
          <p>Key activities for the experiment setting for each of the 2 ethical hacking the methods section.</p>
        </caption>
        <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
          <col width="160"/>
          <col width="590"/>
          <col width="110"/>
          <col width="140"/>
          <thead>
            <tr valign="top">
              <td>Module</td>
              <td>Key activities</td>
              <td>Optimized</td>
              <td>Unoptimized</td>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td>Scanning</td>
              <td>
                <list list-type="bullet">
                  <list-item>
                    <p>Use the Nmap<sup>a</sup> scanning tool to identify the number of ports, the port status, protocol, and operating system</p>
                  </list-item>
                </list>
              </td>
              <td>Yes</td>
              <td>Yes</td>
            </tr>
            <tr valign="top">
              <td>Discovery</td>
              <td>
                <list list-type="bullet">
                  <list-item>
                    <p>Use the Xray scanning tool to identify vulnerabilities</p>
                  </list-item>
                </list>
              </td>
              <td>Yes</td>
              <td>Yes</td>
            </tr>
            <tr valign="top">
              <td>Exploiting</td>
              <td>
                <list list-type="bullet">
                  <list-item>
                    <p>Use the SQLMap tool to exploit SQL injection related vulnerabilities</p>
                  </list-item>
                  <list-item>
                    <p>Use the Metasploit tool to probe networks and applications related flaws and vulnerabilities</p>
                  </list-item>
                </list>
              </td>
              <td>Yes</td>
              <td>Yes</td>
            </tr>
            <tr valign="top">
              <td>Optimizing (optional)</td>
              <td>
                <list list-type="bullet">
                  <list-item>
                    <p>Optimize the attack path using ACO<sup>b</sup></p>
                  </list-item>
                </list>
              </td>
              <td>Yes</td>
              <td>No</td>
            </tr>
            <tr valign="top">
              <td>Controlling</td>
              <td>
                <list list-type="bullet">
                  <list-item>
                    <p>Use results from the modules above to launch attacks</p>
                  </list-item>
                  <list-item>
                    <p>Provide an interactive interface that allows users to specify the IP of the targeted machine</p>
                  </list-item>
                </list>
              </td>
              <td>Yes</td>
              <td>Yes</td>
            </tr>
            <tr valign="top">
              <td>Reporting</td>
              <td>
                <list list-type="bullet">
                  <list-item>
                    <p>Collect and report results on vulnerabilities, time used, and the success rate of the launched exploits</p>
                  </list-item>
                </list>
              </td>
              <td>Yes</td>
              <td>Yes</td>
            </tr>
          </tbody>
        </table>
        <table-wrap-foot>
          <fn id="table4fn1">
            <p><sup>a</sup>Nmap: Network Mapper.</p>
          </fn>
          <fn id="table4fn2">
            <p><sup>b</sup>ACO: ant colony optimization.</p>
          </fn>
        </table-wrap-foot>
      </table-wrap>
      <table-wrap position="float" id="table5">
        <label>Table 5</label>
        <caption>
          <p>Comparison of the results of optimized and unoptimized ethical hacking after 50 runs.</p>
        </caption>
        <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
          <col width="660"/>
          <col width="190"/>
          <col width="150"/>
          <thead>
            <tr valign="top">
              <td>Metrics</td>
              <td>Unoptimized</td>
              <td>Optimized</td>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td>Average used time (in seconds)</td>
              <td>178</td>
              <td>160</td>
            </tr>
            <tr valign="top">
              <td>Success rate of all penetration tests (%)</td>
              <td>64</td>
              <td>98</td>
            </tr>
            <tr valign="top">
              <td>Highest success rate of exploit or exploits (%)</td>
              <td>88.9</td>
              <td>100</td>
            </tr>
            <tr valign="top">
              <td>Average success rate of exploit or exploits (%)</td>
              <td>50.3</td>
              <td>73.5</td>
            </tr>
          </tbody>
        </table>
      </table-wrap>
      <fig id="figure3" position="float">
        <label>Figure 3</label>
        <caption>
          <p>Results of the computational experiments for both unoptimized and optimized ethical hacking methods. (A) Total number of exploits; (B) Number of successful exploits; (C) Success rate results; (D) Average execution time.</p>
        </caption>
        <graphic xlink:href="jmir_v25i1e41748_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
      </fig>
      <table-wrap position="float" id="table6">
        <label>Table 6</label>
        <caption>
          <p>Exploits used in the successful attack path found by optimized ethical hacking.</p>
        </caption>
        <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
          <col width="100"/>
          <col width="100"/>
          <col width="200"/>
          <col width="600"/>
          <thead>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>Exploit</td>
              <td>CVE<sup>a</sup> number</td>
              <td>Details</td>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td>0</td>
              <td>V7</td>
              <td>CVE-2020-0610</td>
              <td>/exploit/windows/browser/adobe_flash_otf_font</td>
            </tr>
            <tr valign="top">
              <td>1</td>
              <td>V8</td>
              <td>CVE-2012-0714</td>
              <td>/exploit/windows/browser/adobe_flash_regex_value</td>
            </tr>
            <tr valign="top">
              <td>2</td>
              <td>V9</td>
              <td>CVE-2012-5975</td>
              <td>/exploit/linux/http/piranha_passwd_exec</td>
            </tr>
            <tr valign="top">
              <td>3</td>
              <td>V17</td>
              <td>CVE-2021-23919</td>
              <td>/exploit/unix/webapp/openemr_upload_exec</td>
            </tr>
            <tr valign="top">
              <td>4</td>
              <td>V4</td>
              <td>CVE-2017-0503</td>
              <td>/exploit/windows/browser/adobe_flash_otf_font</td>
            </tr>
            <tr valign="top">
              <td>5</td>
              <td>V2</td>
              <td>CVE-2000-0248</td>
              <td>/exploit/linux/http/symantec_web_gateway_lfi</td>
            </tr>
          </tbody>
        </table>
        <table-wrap-foot>
          <fn id="table6fn1">
            <p><sup>a</sup>CVE: common vulnerabilities and exposures</p>
          </fn>
        </table-wrap-foot>
      </table-wrap>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Brief Summary of Findings</title>
        <p>In this study, we propose a novel methodological approach to ethical hacking in HISs. We conducted a comparable experiment by launching ethical hacking using both the optimized and unoptimized methods. In particular, we set up an HIS simulation environment by implementing the OpenEMR system and followed the NIST ethical hacking framework to perform ethical hacking. We launched 50 rounds of attacks using both the unoptimized and optimized methods. The results show that the optimized ethical hacking method outperforms the unoptimized method in terms of average time used, the average success rate of exploitation, the number of exploits launched, and the number of successful exploits. We were able to identify the successful attack paths and exploits that are related to remote code execution, cross-site request forgery, improper authentication, vulnerability in the Oracle Business Intelligence Publisher, an elevation of privilege vulnerability (in MediaTek), and remote access backdoor (in the web graphical user interface for the Linux Virtual Server). Theoretically, these findings contribute to HISs, ethical hacking methodology, and mainstream AI-based ethical hacking methods. Practically, the findings have great significance for the health care sector, specifically because OpenEMR is widely adopted by health care organizations.</p>
      </sec>
      <sec>
        <title>Implications</title>
        <p>Our work contributes to the HIS security domain by proposing an AI-based method for ethical hacking that helps identify vulnerabilities in HISs. In particular, we set up a simulation environment by implementing OpenEMR and performed systematic ethical hacking on this virtual platform. Existing cybersecurity research in health care places emphasis on the protection of medical devices [<xref ref-type="bibr" rid="ref13">13</xref>-<xref ref-type="bibr" rid="ref17">17</xref>] and medical data [<xref ref-type="bibr" rid="ref18">18</xref>], such as data encryption mechanisms [<xref ref-type="bibr" rid="ref13">13</xref>], combined or not with scrambling techniques [<xref ref-type="bibr" rid="ref18">18</xref>], managing shared health data [<xref ref-type="bibr" rid="ref14">14</xref>], securing digital patient profiles [<xref ref-type="bibr" rid="ref14">14</xref>], and authentication protocols for wearable devices [<xref ref-type="bibr" rid="ref15">15</xref>]. However, this focus disregards the HIS as a holistic system, which can potentially exhibit vulnerabilities in other functions. In addition, such studies typically do not examine how potential attackers can breach the security of HISs and access, for example, ECG records, that is, other records besides those that are strictly patient focused. In this study, we address this shortcoming by providing an approach that considers and approaches an HIS as a holistic system, whereby the novelty of the AI-driven ethical hacking approach is combined with the familiar NIST framework [<xref ref-type="bibr" rid="ref38">38</xref>], which we adapted to perform ethical hacking systematically.</p>
        <p>Our study further contributes to the ethical hacking methods section by proposing and validating a novel AI-based ethical hacking method that incorporates optimizing and controlling modules. Several ethical hacking methods exist today, including the NIST ethical hacking framework [<xref ref-type="bibr" rid="ref38">38</xref>], PTES, and OWASP. However, they all have limitations. For example, Nettacker, a solution developed by OWASP, contains an optimizing module, but it is not as mature, not fully published, and lacks the exploiting and controlling module. The NIST ethical hacking framework and PTES do not have optimized and controlled modules.</p>
        <p>Our study also addressed some of the shortcomings of mainstream AI-based ethical hacking methods. Mainstream methods typically adopt reinforcement learning. Reinforcement learning is an area of machine learning concerned with how intelligent agents ought to take action in an environment to maximize the notion of cumulative rewards. This approach differs from supervised and unsupervised learning because reinforcement learning aims to learn the algorithm to obtain the best results in highly complex and uncertain situations [<xref ref-type="bibr" rid="ref48">48</xref>]. However, as previously explained, these methods have not yet been integrated into any ethical hacking methods, and reinforcement learning itself has considerable disadvantages when applied to ethical hacking, owing to its requirement for large data sets, the lack of reliability and predictability (which could cause severe problems for the whole system), low reproducibility, and sensitivity to environmental changes [<xref ref-type="bibr" rid="ref20">20</xref>]. The use of ACO in our optimizing module addresses these shortcomings. Our implementation of the ACO algorithm as part of the optimization module shows that it can support the conduct of an efficient vulnerability analysis and detection and offers superior results.</p>
        <p>Our proposed AI-based ethical hacking method has practical implications, as it addresses the weaknesses of ethical hacking tools such as Nettacker, APT2, and Autosploit [<xref ref-type="bibr" rid="ref40">40</xref>], which are used by cybersecurity practitioners. For example, Nettacker lacks an exploit module. This means that a given user will have to select the exploit tools and payload on their own, which can be challenging for nonexperts in cybersecurity. APT2, the solution offered by the Massachusetts Institute of Technology, uses Nmap to scan information; however, it lacks an optimization module. This finding suggests that the accuracy and efficiency of ethical hacking risks are inferior. Similar to APT2, Autosploit [<xref ref-type="bibr" rid="ref40">40</xref>] is a solution that combines Shodan, Censys, Zoomeye, and Metasploit, but it does not have an optimization module. The Metasploit can then run the exploit automatically. However, similar to APT2, Autosploit risks having less accuracy and efficacy because it cannot be optimized. Currently, it is unfeasible to test all possible system configurations.</p>
        <p>Our proposed approach addresses these limitations. The combined effect of the 2 new modules is that our approach proposes an intelligent and maintainable ethical hacking solution. First, the incorporation of the optimization module supports the identification of the shortest path for the attack, which improves the efficiency of ethical hacking. Second, incorporating the control module provides a user interface and coordinates the other modules so that ethical hacking can be carried out by nonexperts, addressing the challenge of the shortage of security experts in the health care domain.</p>
      </sec>
      <sec>
        <title>Limitations and Future Work</title>
        <p>One limitation is that the simulation environment is set up in a virtual environment; although it is portable, it can potentially affect the performance of ethical hacking. As we are running the optimized and unoptimized ethical hacking methods in the same simulation environment, we would assume that this will have a limited impact on the comparable experimental results. Another limitation is that ethical hacking is set up in a network with one system or machine in the simulation environment. In real-world practice, it would be ideal to set up a network with multiple connected machines, so that ethical hacking can target multiple systems or machines.</p>
        <p>From a cybersecurity defense perspective, future work should consider applying advanced AI techniques in HISs and explore security defense strategies to counteract cyberattacks. For example, future work could consider exploring other AI algorithms that have been used to resolve the TSP problem (eg, genetic algorithms) in the context of optimizing attack paths in ethical hacking. Future studies could also consider integrating advanced security defense strategies, such as Security Information and Event Management, Orchestration Automation and Response [<xref ref-type="bibr" rid="ref49">49</xref>], and security operations centers. From an HIS perspective, future research could focus on building a more mature HIS that integrates diagnostic components such as arrhythmia detection and classification in ambulatory ECGs [<xref ref-type="bibr" rid="ref50">50</xref>]. Finally, future research could expand the data set to include data from different medical devices, such as magnetocardiogram and magnetic resonance imaging.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>In this study, we proposed a novel AI-based ethical hacking method, which we validated using an HIS simulation platform using OpenEMR as the focal HIS. We incorporated 2 new modules into the NIST ethical hacking framework, namely the optimization and control modules, and demonstrated the ethical hacking of the HIS simulation environment using optimized (AI-based) and unoptimized methods. The results show that the optimized ethical hacking method outperforms the unoptimized method in terms of average time used, the average success rate of exploitation, the number of exploits launched, and the number of successful exploits. We were able to identify the successful attack paths and exploits. Theoretically, the findings contribute to HIS literature, ethical hacking methodology and mainstream AI-based ethical hacking method as they address some key weaknesses of these research fields. Practically, these findings have great significance for the health care sector, as OpenEMR is widely adopted by health care organizations. It also addresses some of the key weaknesses of ethical testing tools used by practitioners.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group/>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">ACO</term>
          <def>
            <p>ant colony optimization</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">AI</term>
          <def>
            <p>artificial intelligence</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">ECG</term>
          <def>
            <p>electrocardiogram</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">HIS</term>
          <def>
            <p>health information system</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">NHS</term>
          <def>
            <p>National Health Service</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">NIST</term>
          <def>
            <p>National Institute of Standards and Technology</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">Nmap</term>
          <def>
            <p>Network Mapper</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">OpenEMR</term>
          <def>
            <p>open-source electronic medical record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">OWASP</term>
          <def>
            <p>Open Web Application Security Project</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">PTES</term>
          <def>
            <p>Penetration Testing Execution Standard</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb11">TSP</term>
          <def>
            <p>traveling salesman problem</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb12">WHO</term>
          <def>
            <p>World Health Organization</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>CL was supported by the National Natural Science Foundation of China (grant 61803318) and the Scientific-Technological Collaboration Project (grant 2018LZXNYD-FP02).</p>
      <p>We would like to thank Kun Ni for his efforts and participation in the creation of the software system.</p>
    </ack>
    <notes>
      <sec>
        <title>Data Availability</title>
        <p>The data sets generated and analyzed during this study are available from the corresponding author upon reasonable request.</p>
      </sec>
    </notes>
    <fn-group>
      <fn fn-type="con">
        <p>YH is the first author. YH and CL contributed to the conception and design of the study. YH and CL contributed to data acquisition. YH, EZ, IY, and CL contributed to data modeling and analysis. YH contributed to the creation of the software system used in the study. YH drafted the manuscript. YH, CL, EZ, and IY have substantively revised it. All the authors contributed to the final work and approved the final version of the manuscript.</p>
      </fn>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ghafur</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kristensen</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Honeyford</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Martin</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Darzi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Aylin</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>A retrospective impact analysis of the WannaCry cyberattack on the NHS</article-title>
          <source>NPJ Digit Med</source>
          <year>2019</year>
          <month>10</month>
          <day>2</day>
          <volume>2</volume>
          <fpage>98</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41746-019-0161-6"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-019-0161-6</pub-id>
          <pub-id pub-id-type="medline">31602404</pub-id>
          <pub-id pub-id-type="pii">161</pub-id>
          <pub-id pub-id-type="pmcid">PMC6775064</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>He</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Aliyu</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Evans</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Luo</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Health care cybersecurity challenges and solutions under the climate of COVID-19: scoping review</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <month>04</month>
          <day>20</day>
          <volume>23</volume>
          <issue>4</issue>
          <fpage>e21747</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/4/e21747/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/21747</pub-id>
          <pub-id pub-id-type="medline">33764885</pub-id>
          <pub-id pub-id-type="pii">v23i4e21747</pub-id>
          <pub-id pub-id-type="pmcid">PMC8059789</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="web">
          <article-title>Breach portal: notice to the secretary of HHS breach of unsecured protected health information</article-title>
          <source>U.S. Department of Health and Human Services, Office for Civil Rights</source>
          <year>2018</year>
          <access-date>2023-03-05</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ocrportal.hhs.gov/ocr/smartscreen/main.jsf">https://ocrportal.hhs.gov/ocr/smartscreen/main.jsf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dodson</surname>
              <given-names>DL</given-names>
            </name>
            <name name-style="western">
              <surname>Crank</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>2021 Horizon report: the state of cybersecurity in healthcare</article-title>
          <source>Fortified Health Security</source>
          <access-date>2023-03-05</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://fortifiedhealthsecurity.com/wp-content/uploads/2020/12/Fortified-Health-Security-2021-Horizon-Report.pdf">https://fortifiedhealthsecurity.com/wp-content/uploads/2020/12/Fortified-Health-Security-2021-Horizon-Report.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Luo</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Soygazi</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Janicke</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>He</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Security defense strategy for intelligent medical diagnosis systems (IMDS)</article-title>
          <source>Annu Int Conf IEEE Eng Med Biol Soc</source>
          <year>2019</year>
          <month>07</month>
          <volume>2019</volume>
          <fpage>3454</fpage>
          <lpage>7</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://pubmed.ncbi.nlm.nih.gov/31946622/"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/EMBC.2019.8857166</pub-id>
          <pub-id pub-id-type="medline">31946622</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>McMahon</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>EI</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Samtani</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Patton</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Assessing medical device vulnerabilities on the Internet of Things</article-title>
          <source>Proceedings of the 2017 IEEE International Conference on Intelligence and Security Informatics</source>
          <year>2017</year>
          <conf-name>ISI '17</conf-name>
          <conf-date>July 22-24, 2017</conf-date>
          <conf-loc>Beijing, China</conf-loc>
          <fpage>176</fpage>
          <lpage>8</lpage>
          <pub-id pub-id-type="doi">10.1109/isi.2017.8004903</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wirth</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Cybercrimes pose growing threat to medical devices</article-title>
          <source>Biomed Instrum Technol</source>
          <year>2011</year>
          <month>01</month>
          <volume>45</volume>
          <issue>1</issue>
          <fpage>26</fpage>
          <lpage>34</lpage>
          <pub-id pub-id-type="doi">10.2345/0899-8205-45.1.26</pub-id>
          <pub-id pub-id-type="medline">21322805</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Raghunathan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Jha</surname>
              <given-names>NK</given-names>
            </name>
          </person-group>
          <article-title>Trustworthiness of medical devices and body area networks</article-title>
          <source>Proc IEEE</source>
          <year>2014</year>
          <month>8</month>
          <volume>102</volume>
          <issue>8</issue>
          <fpage>1174</fpage>
          <lpage>88</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/6827202"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/jproc.2014.2322103</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Khera</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Think like a hacker: insights on the latest attack vectors (and security controls) for medical device applications</article-title>
          <source>J Diabetes Sci Technol</source>
          <year>2017</year>
          <month>03</month>
          <volume>11</volume>
          <issue>2</issue>
          <fpage>207</fpage>
          <lpage>12</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.sagepub.com/doi/10.1177/1932296816677576"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/1932296816677576</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gordon</surname>
              <given-names>WJ</given-names>
            </name>
            <name name-style="western">
              <surname>Coravos</surname>
              <given-names>AR</given-names>
            </name>
            <name name-style="western">
              <surname>Stern</surname>
              <given-names>AD</given-names>
            </name>
          </person-group>
          <article-title>Ushering in safe, effective, secure, and ethical medicine in the digital era</article-title>
          <source>NPJ Digit Med</source>
          <year>2021</year>
          <month>03</month>
          <day>25</day>
          <volume>4</volume>
          <issue>1</issue>
          <fpage>56</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nature.com/articles/s41746-021-00424-5#citeas"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-021-00424-5</pub-id>
          <pub-id pub-id-type="medline">33767377</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>CM</given-names>
            </name>
            <name name-style="western">
              <surname>Chaturvedi</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Chakravarthy</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Cybersecurity risks in a pandemic</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>09</month>
          <day>17</day>
          <volume>22</volume>
          <issue>9</issue>
          <fpage>e23692</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/9/e23692/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/23692</pub-id>
          <pub-id pub-id-type="medline">32897869</pub-id>
          <pub-id pub-id-type="pii">v22i9e23692</pub-id>
          <pub-id pub-id-type="pmcid">PMC7528623</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jalali</surname>
              <given-names>MS</given-names>
            </name>
            <name name-style="western">
              <surname>Kaiser</surname>
              <given-names>JP</given-names>
            </name>
          </person-group>
          <article-title>Cybersecurity in hospitals: a systematic, organizational perspective</article-title>
          <source>J Med Internet Res</source>
          <year>2018</year>
          <month>05</month>
          <day>28</day>
          <volume>20</volume>
          <issue>5</issue>
          <fpage>e10059</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2018/5/e10059/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/10059</pub-id>
          <pub-id pub-id-type="medline">29807882</pub-id>
          <pub-id pub-id-type="pii">v20i5e10059</pub-id>
          <pub-id pub-id-type="pmcid">PMC5996174</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ma</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Shrestha</surname>
              <given-names>PL</given-names>
            </name>
            <name name-style="western">
              <surname>Hempel</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Peng</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Sharif</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>HH</given-names>
            </name>
          </person-group>
          <article-title>Assurance of energy efficiency and data security for ECG transmission in BASNs</article-title>
          <source>IEEE Trans Biomed Eng</source>
          <year>2012</year>
          <month>04</month>
          <volume>59</volume>
          <issue>4</issue>
          <fpage>1041</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/6122058"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/tbme.2011.2182196</pub-id>
          <pub-id pub-id-type="medline">22231147</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Edemacu</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Jang</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>JW</given-names>
            </name>
          </person-group>
          <article-title>Collaborative eHealth privacy and security: an access control with attribute revocation based on OBDD access structure</article-title>
          <source>IEEE J Biomed Health Inform</source>
          <year>2020</year>
          <month>10</month>
          <volume>24</volume>
          <issue>10</issue>
          <fpage>2960</fpage>
          <lpage>72</lpage>
          <pub-id pub-id-type="doi">10.1109/JBHI.2020.2973713</pub-id>
          <pub-id pub-id-type="medline">32071017</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Das</surname>
              <given-names>AK</given-names>
            </name>
            <name name-style="western">
              <surname>Wazid</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Kumar</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Khan</surname>
              <given-names>MK</given-names>
            </name>
            <name name-style="western">
              <surname>Choo</surname>
              <given-names>KK</given-names>
            </name>
            <name name-style="western">
              <surname>Park</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Design of secure and lightweight authentication protocol for wearable devices environment</article-title>
          <source>IEEE J Biomed Health Inform</source>
          <year>2018</year>
          <month>7</month>
          <volume>22</volume>
          <issue>4</issue>
          <fpage>1310</fpage>
          <lpage>22</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/8039175"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/jbhi.2017.2753464</pub-id>
          <pub-id pub-id-type="medline">28922132</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Seepers</surname>
              <given-names>RM</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>de Haan</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Sourdis</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Strydis</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Attacks on heartbeat-based security using remote photoplethysmography</article-title>
          <source>IEEE J Biomed Health Inform</source>
          <year>2018</year>
          <month>5</month>
          <volume>22</volume>
          <issue>3</issue>
          <fpage>714</fpage>
          <lpage>21</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/7892894"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/jbhi.2017.2691282</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Seepers</surname>
              <given-names>RM</given-names>
            </name>
            <name name-style="western">
              <surname>Strydis</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Sourdis</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>De Zeeuw</surname>
              <given-names>CI</given-names>
            </name>
          </person-group>
          <article-title>Enhancing heart-beat-based security for mHealth applications</article-title>
          <source>IEEE J Biomed Health Inform</source>
          <year>2017</year>
          <month>01</month>
          <volume>21</volume>
          <issue>1</issue>
          <fpage>254</fpage>
          <lpage>62</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://pubmed.ncbi.nlm.nih.gov/26540720/"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/JBHI.2015.2496151</pub-id>
          <pub-id pub-id-type="medline">26540720</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ibaida</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Khalil</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Wavelet-based ECG steganography for protecting patient confidential information in point-of-care systems</article-title>
          <source>IEEE Trans Biomed Eng</source>
          <year>2013</year>
          <month>12</month>
          <volume>60</volume>
          <issue>12</issue>
          <fpage>3322</fpage>
          <lpage>30</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/abstract/document/6517870"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/tbme.2013.2264539</pub-id>
          <pub-id pub-id-type="medline">23708767</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chaudhary</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>O’Brien</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Automated post-breach penetration testing through reinforcement learning</article-title>
          <source>Proceedings of the 2020 IEEE Conference on Communications and Network Security</source>
          <year>2020</year>
          <conf-name>CNS '20</conf-name>
          <conf-date>June 29-July 1, 2020</conf-date>
          <conf-loc>Avignon, France</conf-loc>
          <fpage>1</fpage>
          <lpage>2</lpage>
          <pub-id pub-id-type="doi">10.1109/cns48642.2020.9162301</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Raghu</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Irpan</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Andreas</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kleinberg</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Le</surname>
              <given-names>QV</given-names>
            </name>
            <name name-style="western">
              <surname>Kleinberg</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Can deep reinforcement learning solve erdos-selfridge-spencer games?</article-title>
          <source>Proceedings of the 35th International Conference on Machine Learning</source>
          <year>2018</year>
          <conf-name>PMLR '18</conf-name>
          <conf-date>July 10-15, 2018</conf-date>
          <conf-loc>Stockholm, Sweden</conf-loc>
          <fpage>4238</fpage>
          <lpage>46</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Berendt</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>AI for the common good?! Pitfalls, challenges, and ethics pen-testing</article-title>
          <source>Paladyn J Behav Med</source>
          <year>2019</year>
          <month>01</month>
          <day>11</day>
          <volume>10</volume>
          <issue>1</issue>
          <fpage>44</fpage>
          <lpage>65</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.degruyter.com/document/doi/10.1515/pjbr-2019-0004/html?lang=en"/>
          </comment>
          <pub-id pub-id-type="doi">10.1515/pjbr-2019-0004</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Baloch</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <source>Ethical Hacking and Penetration Testing Guide</source>
          <year>2017</year>
          <publisher-loc>Boca Raton, FL, USA</publisher-loc>
          <publisher-name>Auerbach Publications</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Dorigo</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Maniezzo</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Colorni</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Ant system: optimization by a colony of cooperating agents</article-title>
          <source>IEEE Trans Syst Man Cybern</source>
          <year>1996</year>
          <month>2</month>
          <volume>26</volume>
          <issue>1</issue>
          <fpage>29</fpage>
          <lpage>41</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/484436"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/3477.484436</pub-id>
          <pub-id pub-id-type="medline">18263004</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Lv</surname>
              <given-names>LT</given-names>
            </name>
          </person-group>
          <article-title>Network intrusion detection method based on combination of improved ant colony optimization and genetic algorithm</article-title>
          <source>J Chongqing Univ Posts Telecommun</source>
          <year>2019</year>
          <month>01</month>
          <volume>29</volume>
          <issue>1</issue>
          <fpage>85</fpage>
          <lpage>9</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Struijk</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ou</surname>
              <given-names>CX</given-names>
            </name>
            <name name-style="western">
              <surname>Davison</surname>
              <given-names>RM</given-names>
            </name>
            <name name-style="western">
              <surname>Angelopoulos</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Putting the IS back into IS research</article-title>
          <source>Inf Syst J</source>
          <year>2022</year>
          <month>5</month>
          <volume>32</volume>
          <issue>3</issue>
          <fpage>469</fpage>
          <lpage>72</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://onlinelibrary.wiley.com/doi/full/10.1111/isj.12368"/>
          </comment>
          <pub-id pub-id-type="doi">10.1111/isj.12368</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Guo</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>The application of medical artificial intelligence technology in rural areas of developing countries</article-title>
          <source>Health Equity</source>
          <year>2018</year>
          <month>08</month>
          <volume>2</volume>
          <issue>1</issue>
          <fpage>174</fpage>
          <lpage>81</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/30283865"/>
          </comment>
          <pub-id pub-id-type="doi">10.1089/heq.2018.0037</pub-id>
          <pub-id pub-id-type="medline">30283865</pub-id>
          <pub-id pub-id-type="pii">10.1089/heq.2018.0037</pub-id>
          <pub-id pub-id-type="pmcid">PMC6110188</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tully</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Coravos</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Doerr</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Dameff</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Connected medical technology and cybersecurity informed consent: a new paradigm</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>03</month>
          <day>30</day>
          <volume>22</volume>
          <issue>3</issue>
          <fpage>e17612</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/3/e17612/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/17612</pub-id>
          <pub-id pub-id-type="medline">32224492</pub-id>
          <pub-id pub-id-type="pii">v22i3e17612</pub-id>
          <pub-id pub-id-type="pmcid">PMC7154933</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kelly</surname>
              <given-names>JT</given-names>
            </name>
            <name name-style="western">
              <surname>Campbell</surname>
              <given-names>KL</given-names>
            </name>
            <name name-style="western">
              <surname>Gong</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Scuffham</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>The internet of things: impact and implications for health care delivery</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>11</month>
          <day>10</day>
          <volume>22</volume>
          <issue>11</issue>
          <fpage>e20135</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/11/e20135/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/20135</pub-id>
          <pub-id pub-id-type="medline">33170132</pub-id>
          <pub-id pub-id-type="pii">v22i11e20135</pub-id>
          <pub-id pub-id-type="pmcid">PMC7685921</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kala</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Shukla</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Tiwari</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Shukla</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Tiwari</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Hybrid intelligent systems for medical diagnosis</article-title>
          <source>Intelligent Medical Technologies and Biomedical Engineering: Tools and Applications</source>
          <year>2010</year>
          <publisher-loc>Hershey, PA, USA</publisher-loc>
          <publisher-name>IGI Global</publisher-name>
          <fpage>187</fpage>
          <lpage>202</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kjoelen</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Thompson</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Umbaugh</surname>
              <given-names>SE</given-names>
            </name>
            <name name-style="western">
              <surname>Moss</surname>
              <given-names>RH</given-names>
            </name>
            <name name-style="western">
              <surname>Stoecker</surname>
              <given-names>WV</given-names>
            </name>
          </person-group>
          <article-title>Performance of AI methods in detecting melanoma</article-title>
          <source>IEEE Eng Med Biol Mag</source>
          <year>1995</year>
          <volume>14</volume>
          <issue>4</issue>
          <fpage>411</fpage>
          <lpage>6</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/395323"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/51.395323</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Jalali</surname>
              <given-names>MS</given-names>
            </name>
            <name name-style="western">
              <surname>Razak</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Gordon</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Perakslis</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Madnick</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Health care and cybersecurity: bibliometric analysis of the literature</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>02</month>
          <day>15</day>
          <volume>21</volume>
          <issue>2</issue>
          <fpage>e12644</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/2/e12644/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/12644</pub-id>
          <pub-id pub-id-type="medline">30767908</pub-id>
          <pub-id pub-id-type="pii">v21i2e12644</pub-id>
          <pub-id pub-id-type="pmcid">PMC6396074</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Xiao</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Ma</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>A privacy-preserving intelligent medical diagnosis system based on oblivious keyword search</article-title>
          <source>Math Probl Eng</source>
          <year>2017</year>
          <month>08</month>
          <day>30</day>
          <volume>2017</volume>
          <fpage>8632183</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.hindawi.com/journals/mpe/2017/8632183/"/>
          </comment>
          <pub-id pub-id-type="doi">10.1155/2017/8632183</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kruse</surname>
              <given-names>CS</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Vanderlinden</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Nealand</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Security techniques for the electronic health records</article-title>
          <source>J Med Syst</source>
          <year>2017</year>
          <month>08</month>
          <volume>41</volume>
          <issue>8</issue>
          <fpage>127</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/28733949"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s10916-017-0778-4</pub-id>
          <pub-id pub-id-type="medline">28733949</pub-id>
          <pub-id pub-id-type="pii">10.1007/s10916-017-0778-4</pub-id>
          <pub-id pub-id-type="pmcid">PMC5522514</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Budimir</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Fontaine</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Huijts</surname>
              <given-names>NM</given-names>
            </name>
            <name name-style="western">
              <surname>Haans</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Loukas</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Roesch</surname>
              <given-names>EB</given-names>
            </name>
          </person-group>
          <article-title>Emotional reactions to cybersecurity breach situations: scenario-based survey study</article-title>
          <source>J Med Internet Res</source>
          <year>2021</year>
          <month>05</month>
          <day>12</day>
          <volume>23</volume>
          <issue>5</issue>
          <fpage>e24879</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2021/5/e24879/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/24879</pub-id>
          <pub-id pub-id-type="medline">33978591</pub-id>
          <pub-id pub-id-type="pii">v23i5e24879</pub-id>
          <pub-id pub-id-type="pmcid">PMC8156130</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Iwaya</surname>
              <given-names>LH</given-names>
            </name>
            <name name-style="western">
              <surname>Fischer-Hübner</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Åhlfeldt</surname>
              <given-names>RM</given-names>
            </name>
            <name name-style="western">
              <surname>Martucci</surname>
              <given-names>LA</given-names>
            </name>
          </person-group>
          <article-title>Mobile health systems for community-based primary care: identifying controls and mitigating privacy threats</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2019</year>
          <month>03</month>
          <day>20</day>
          <volume>7</volume>
          <issue>3</issue>
          <fpage>e11642</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2019/3/e11642/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/11642</pub-id>
          <pub-id pub-id-type="medline">30892275</pub-id>
          <pub-id pub-id-type="pii">v7i3e11642</pub-id>
          <pub-id pub-id-type="pmcid">PMC6446152</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yaqoob</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Abbas</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Atiquzzaman</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Security vulnerabilities, attacks, countermeasures, and regulations of networked medical devices—a review</article-title>
          <source>IEEE Commun Surv Tutor</source>
          <year>2019</year>
          <volume>21</volume>
          <issue>4</issue>
          <fpage>3723</fpage>
          <lpage>68</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ieeexplore.ieee.org/document/8703068"/>
          </comment>
          <pub-id pub-id-type="doi">10.1109/comst.2019.2914094</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>PA</given-names>
            </name>
            <name name-style="western">
              <surname>Woodward</surname>
              <given-names>AJ</given-names>
            </name>
          </person-group>
          <article-title>Cybersecurity vulnerabilities in medical devices: a complex environment and multifaceted problem</article-title>
          <source>Med Devices (Auckl)</source>
          <year>2015</year>
          <month>7</month>
          <day>20</day>
          <volume>8</volume>
          <fpage>305</fpage>
          <lpage>16</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/26229513"/>
          </comment>
          <pub-id pub-id-type="doi">10.2147/MDER.S50048</pub-id>
          <pub-id pub-id-type="medline">26229513</pub-id>
          <pub-id pub-id-type="pii">mder-8-305</pub-id>
          <pub-id pub-id-type="pmcid">PMC4516335</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Souppaya</surname>
              <given-names>MP</given-names>
            </name>
            <name name-style="western">
              <surname>Scarfone</surname>
              <given-names>KA</given-names>
            </name>
          </person-group>
          <article-title>Technical guide to information security testing and assessment</article-title>
          <source>National Institute of Standards and Technology</source>
          <year>2008</year>
          <month>09</month>
          <day>30</day>
          <access-date>2023-03-05</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nist.gov/publications/technical-guide-information-security-testing-and-assessment">https://www.nist.gov/publications/technical-guide-information-security-testing-and- assessment</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Najera-Gutierrez</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Ansari</surname>
              <given-names>JA</given-names>
            </name>
          </person-group>
          <source>Web Penetration Testing with Kali Linux: Explore the Methods and Tools of Ethical Hacking with Kali Linux. 3rd edition</source>
          <year>2018</year>
          <month>01</month>
          <publisher-loc>Birmingham, UK</publisher-loc>
          <publisher-name>Packt Publishing</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Moscovich</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Bitton</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Mallah</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Inokuchi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Yagyu</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Kalech</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Elovici</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Shabtai</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Autosploit: a fully automated framework for evaluating the exploitability of security vulnerabilities</article-title>
          <source>arXiv</source>
          <year>2020</year>
          <month>06</month>
          <day>30</day>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://arxiv.org/abs/2007.00059"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rahalkar</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Jaswal</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <source>The Complete Metasploit Guide: Explore Effective Penetration Testing Techniques with Metasploit</source>
          <year>2019</year>
          <publisher-loc>Birmingham, UK</publisher-loc>
          <publisher-name>Packt Publishing</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ghanem</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>TM</given-names>
            </name>
          </person-group>
          <article-title>Reinforcement learning for intelligent penetration testing</article-title>
          <source>Proceedings of the 2nd World Conference on Smart Trends in Systems, Security and Sustainability</source>
          <year>2018</year>
          <conf-name>WorldS4 '18</conf-name>
          <conf-date>October 30-31, 2018</conf-date>
          <conf-loc>London, UK</conf-loc>
          <fpage>185</fpage>
          <lpage>92</lpage>
          <pub-id pub-id-type="doi">10.1109/worlds4.2018.8611595</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Farhadi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Haddad</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Shahriar</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Compliance checking of open source EHR applications for HIPAA and ONC security and privacy requirements</article-title>
          <source>Proceedings of the IEEE 43rd Annual Computer Software and Applications Conference</source>
          <year>2019</year>
          <conf-name>COMPSAC '19</conf-name>
          <conf-date>July 15-19, 2019</conf-date>
          <conf-loc>Milwaukee, WI, USA</conf-loc>
          <fpage>704</fpage>
          <lpage>13</lpage>
          <pub-id pub-id-type="doi">10.1109/compsac.2019.00106</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>de Abajo</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ballestero</surname>
              <given-names>AL</given-names>
            </name>
          </person-group>
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Rodrigues</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>de la Torre Diez</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>de Abajo</surname>
              <given-names>BS</given-names>
            </name>
          </person-group>
          <article-title>Overview of the most important open source software: analysis of the benefits of OpenMRS, OpenEMR, and VistA</article-title>
          <source>Telemedicine and E-Health Services, Policies, and Applications: Advancements and Developments</source>
          <year>2012</year>
          <publisher-loc>Hershey, PA, USA</publisher-loc>
          <publisher-name>IGI Global</publisher-name>
          <fpage>315</fpage>
          <lpage>46</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Martin</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>Lam</surname>
              <given-names>MS</given-names>
            </name>
          </person-group>
          <article-title>Automatic generation of XSS and SQL injection attacks with goal-directed model checking</article-title>
          <source>Proceedings of the 17th USENIX Security Symposium</source>
          <year>2008</year>
          <conf-name>USENIX Security '08</conf-name>
          <conf-date>July 28- August 1, 2008</conf-date>
          <conf-loc>San Jose, CA, USA</conf-loc>
          <fpage>31</fpage>
          <lpage>43</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Axinte</surname>
              <given-names>SD</given-names>
            </name>
          </person-group>
          <article-title>SQL injection testing in web applications using SQLmap</article-title>
          <source>Int J Inf Secur Cybercrime</source>
          <year>2014</year>
          <month>12</month>
          <day>29</day>
          <volume>3</volume>
          <issue>2</issue>
          <fpage>61</fpage>
          <lpage>8</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ijisc.com/year-2014-issue-2-article-7/"/>
          </comment>
          <pub-id pub-id-type="doi">10.19107/ijisc.2014.02.07</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Dai</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Gao</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Ant colony optimization algorithm for continuous domains based on position distribution model of ant colony foraging</article-title>
          <source>ScientificWorldJournal</source>
          <year>2014</year>
          <volume>2014</volume>
          <fpage>428539</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1155/2014/428539"/>
          </comment>
          <pub-id pub-id-type="doi">10.1155/2014/428539</pub-id>
          <pub-id pub-id-type="medline">24955402</pub-id>
          <pub-id pub-id-type="pmcid">PMC4037618</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref48">
        <label>48</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sutton</surname>
              <given-names>RS</given-names>
            </name>
            <name name-style="western">
              <surname>Barto</surname>
              <given-names>AG</given-names>
            </name>
          </person-group>
          <source>Reinforcement Learning: An Introduction</source>
          <year>2018</year>
          <publisher-loc>Cambridge, MA, USA</publisher-loc>
          <publisher-name>MIT Press</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref49">
        <label>49</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Islam</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Babar</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Nepal</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>A multi-vocal review of security orchestration</article-title>
          <source>ACM Comput Surv</source>
          <year>2019</year>
          <month>04</month>
          <day>30</day>
          <volume>52</volume>
          <issue>2</issue>
          <fpage>37</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dl.acm.org/doi/10.1145/3305268"/>
          </comment>
          <pub-id pub-id-type="doi">10.1145/3305268</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref50">
        <label>50</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hannun</surname>
              <given-names>AY</given-names>
            </name>
            <name name-style="western">
              <surname>Rajpurkar</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Haghpanahi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Tison</surname>
              <given-names>GH</given-names>
            </name>
            <name name-style="western">
              <surname>Bourn</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Turakhia</surname>
              <given-names>MP</given-names>
            </name>
            <name name-style="western">
              <surname>Ng</surname>
              <given-names>AY</given-names>
            </name>
          </person-group>
          <article-title>Cardiologist-level arrhythmia detection and classification in ambulatory electrocardiograms using a deep neural network</article-title>
          <source>Nat Med</source>
          <year>2019</year>
          <month>01</month>
          <volume>25</volume>
          <issue>1</issue>
          <fpage>65</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/30617320"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41591-018-0268-3</pub-id>
          <pub-id pub-id-type="medline">30617320</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41591-018-0268-3</pub-id>
          <pub-id pub-id-type="pmcid">PMC6784839</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
