<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <issn pub-type="ppub">1613-0073</issn>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>of Smart Peripheral Devices - Mobiles / IoT / Edge (Preface)</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Gurvan Le Guernic</string-name>
          <email>gurvan.le_guernic@inria.fr</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Cybersecurity</institution>
          ,
          <addr-line>Mobile, IoT, Android, C&amp;ESAR, Conference, Preface</addr-line>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>DGA Maîtrise de l'Information</institution>
          ,
          <addr-line>Rennes</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Univ Rennes</institution>
          ,
          <addr-line>Inria, CNRS, IRISA, Rennes</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2023</year>
      </pub-date>
      <abstract>
        <p>C&amp;ESAR is an educational, professional and scientific conference on cybersecurity whose specific topic changes every year. This year C&amp;ESAR is focused the cybersecurity of “Smart Peripheral Devices”, i.e. mobiles, IoT and Edge devices. The scope covers all issues related to the cybersecurity of semi-autonomous connected devices deployed at the periphery of an information system close to its data sources and sinks. Those devices include mobiles, smartphones, IoT devices, and lightweight Edge devices. computation power than devices in the core of an IT or OT network, and are more exposed to external threats. Hence, attacking or securing them may require diferent means that for attacking r securing the core of an IT or OT network. C&amp;ESAR 2023 received 18 submissions for peer-review. Out of these, 9 papers were accepted for presentation at the conference. After the conference, 4 were short listed for inclusion in this volume. connectés semi-autonomes déployés en périphérie d'un système d'information à proximité des C&amp;ESAR'23: Computer &amp; Electronics Security Application Rendezvous, Nov. 21-22, 2023, Rennes, Workshop Proceedings Workshop Proceedings (CEUR-WS.org) Workshop Proceedings</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Résumé
C&amp;ESAR est une conférence pédagogique, professionnelle et scientifique sur la cybersécurité
dont le thème spécifique change chaque année. Cette année, C&amp;ESAR se concentre sur la
cybersécurité des « appareils périphériques intelligents », c’est-à-dire les appareils mobiles,
IoT et Edge. Le périmètre couvre toutes les problématiques liées à la cybersécurité des objets
producteurs et consommateurs de données. Ces équipements incluent les appareils mobiles,
les smartphones, les appareils IoT et les appareils Edge légers. Ces équipements ont souvent
moins de puissance de calcul que les appareils situés dans le coeur d’un réseau informatique
ou OT, et sont plus exposés aux menaces externes. Ainsi, les attaquer ou les sécuriser peut
nécessiter des moyens diférents de ceux pour attaquer ou sécuriser le coeur d’un réseau IT ou
OT. C&amp;ESAR 2023 a reçu 18 soumissions pour examen par les pairs. Parmi ceux-ci, 9 articles
ont été acceptés pour présentation à la conférence, dont 4 pour inclusion dans les actes.
France
CEUR</p>
      <p>CEUR</p>
      <p>ceur-ws.org
Every year since 1997, the French Ministry of Defense organizes a cybersecurity conference,
called C&amp;ESAR. This conference is now one of the main events of the European Cyber
Week (ECW) organized every fall in Rennes, Brittany, France.</p>
      <p>The goal of C&amp;ESAR is to bring together governmental, industrial, and academic
stakeholders interested in cybersecurity. This event, both educational and scientific,
gathers experts, researchers, practitioners and decision-makers. This inter-disciplinary
approach allows operational practitioners to learn about and anticipate future
technological inflection points, and for industry and academia to confront research and product
development to operational realities. Every year, C&amp;ESAR explores a diferent topic
within the field of cybersecurity.</p>
      <p>This year’s topic is: Cybersecurity of Smart Peripheral Devices (Mobiles /
IoT / Edge). This topic is subtitled: Cybersecurity of semi-autonomous connected
devices deployed at the periphery of an information system, close to its data sources and
sinks.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Cybersecurity of Smart Peripheral Devices (Mobiles / IoT /</title>
    </sec>
    <sec id="sec-3">
      <title>Edge)</title>
      <p>
        There is a trend to move more and more information processing towards the edges of
information systems, close to the data sources and sinks, and to the end-users [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. In
2018, Gartner evaluated that 10% of “enterprise-generated data is created and processed
outside a traditional centralized data center or cloud” [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], and predicted in 2021 that this
number would increase to 50% in 2025 [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] (which it originally predicted at 75% in its 2018
report [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]) while the number of IoT devices will triple [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] or quadruple [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] between 2020
and 2030 reaching “more than 15 billion IoT devices [that] will connect to the enterprise
infrastructure by 2029” [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] (IoT analytics even forecasts 27 billions connected IoT devices
by 2025 [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]). There are varying reasons for this trend, among which: improving latency,
relieving the network bandwidth from part of the huge amount of data generated, and
bringing some autonomy to the end-users interacting at the periphery of the information
system. This trend exists in the civil world, and in particular in industry with the
specific concept of Industrial IoT (IIoT) [
        <xref ref-type="bibr" rid="ref6 ref7 ref8 ref9">6, 7, 8, 9</xref>
        ], but also in the military one with
the concepts of the Internet of Battle Things (IoBT) [
        <xref ref-type="bibr" rid="ref10 ref11 ref12">10, 11, 12</xref>
        ] or Internet of Military
Things (IoMT) [
        <xref ref-type="bibr" rid="ref13 ref14">13, 14</xref>
        ], which aim in part to increase local information exploitation
[
        <xref ref-type="bibr" rid="ref15 ref16 ref17">15, 16, 17</xref>
        ]. To develop those concepts in the military domain, among other initiatives, the
Internet of Battlefield Things Collaborative Research Alliance (IoBT-CRA) [
        <xref ref-type="bibr" rid="ref18 ref19 ref20">18, 19, 20</xref>
        ]
was established in 2017 for a 10 years period.
      </p>
      <p>
        In this call, devices handling those peripheral computations are called Smart
Peripheral Devices (SPDs). Those SPDs are quiet diferent from, and have more variability,
than devices found in the “core” of information systems (servers, desktops and laptops).
They range: from somewhat expensive and powerful devices, such as smartphones or
communication equipment of military vehicles [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ]; to low cost low power devices, such as
disposable wearable devices or disposable vessels [
        <xref ref-type="bibr" rid="ref21">21, 22</xref>
        ]; through Internet of Things
(IoT) devices [23], and some lightweight Edge Computing devices [24]. While quite
diferent, SPDs share some characteristics: they reside at the periphery of the system
and are more susceptible to loss and theft; they have to comply with specific constraints
limiting the resources they can use; they run on specific hardware usually not found
in “core” devices; they use connection technologies not found in the core of the system
to communicate with the core and between themselves; they handle some information
processing directly, independently from the core of the system; they have to allow for
“temporary” disconnections from the core, while still being able to function properly; and
they are not continuously visible and monitored by the core of the information system.
      </p>
      <p>
        Those specifics raise some concerns over their resilience to cybersecurity attacks
[25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36], and even the faithfulness of their supply
chain [
        <xref ref-type="bibr" rid="ref22">37</xref>
        ]. As stated by Verizon for IoT [
        <xref ref-type="bibr" rid="ref23">38</xref>
        ], but applying to all SPD, “an [SPD] can be
an attack vector (a weak point that can be exploited to mount an attack), a vehicle for
attacks (like a part of a botnet used to carry out a distributed denial-of-service (DDoS)
attack) or a target in its own right”. For example, the Mirai botnet [
        <xref ref-type="bibr" rid="ref24">39</xref>
        ] infected many IoT
devices and has been used to attack many other systems. Mobiles are also an interesting
target for attackers [
        <xref ref-type="bibr" rid="ref25 ref26 ref27 ref28">40, 41, 42, 43</xref>
        ]. Over a one year period, half of companies recently
surveyed by Verizon sufered a compromise involving a mobile device [
        <xref ref-type="bibr" rid="ref23">38</xref>
        ]; for half of the
companies concerned, applications were involved (in 2021, the percentage of organizations
experiencing the installation of a malware on a remote device doubled [
        <xref ref-type="bibr" rid="ref29">44</xref>
        ]); and half of
SMBs that sufered a mobile-related hack said that it had a major impact. Attackers do
design applications and phishing campaigns specifically for mobiles [
        <xref ref-type="bibr" rid="ref23">38</xref>
        ], and if they do
its because there is a benefit in doing so. As a consequence, more than 8 companies out
of 10 have a specific budget for mobile security [
        <xref ref-type="bibr" rid="ref23">38</xref>
        ]. Last year C&amp;ESAR addressed the
concept of Zero Trust, among others. From the point of view of the security of the core
of the information system, an SPD can be disconnected if the core has lost trust in it.
However, the features carried by this SPD will also be lost. It is therefore important to
be able to secure those SPDs.
      </p>
      <p>
        However, cybersecurity technologies and methodologies applied to the core of
information systems are not necessarily directly applicable to SPDs. Adapting standard Endpoint
Detection and Response (EDR) solutions to the vast variety of SPD and integrating
them to the core IT system SIEM is not a simple task. The specific technologies used
for SPDs may contain weaknesses and vulnerabilities diferent from those of core system
technologies [
        <xref ref-type="bibr" rid="ref30 ref31">45, 46</xref>
        ]. Ensuring the cybersecurity of SPDs may also require specific
methodologies [
        <xref ref-type="bibr" rid="ref32">47</xref>
        ].
      </p>
      <p>
        For example, SPDs use specific technologies in their processing stack (hardware and
software). Among the various hardware used, they rely more commonly on ARM
platforms and technologies. Those hardwares and deployment environment have specific
characteristics impacting their cybersecurity [
        <xref ref-type="bibr" rid="ref33 ref34">48, 49</xref>
        ]. Among the various hardware
support for securing SPDs [
        <xref ref-type="bibr" rid="ref35">50</xref>
        ], we can cite Secure Elements (SE) [
        <xref ref-type="bibr" rid="ref36">51</xref>
        ] or Tusted Execution
Element (TEE). SPDs also use specific operating systems, such as Android and iOS
for smartphones [
        <xref ref-type="bibr" rid="ref37 ref38">52, 53</xref>
        ]. And, for some of them, they allow end-users (hopefully the
device administrator) to pull computing payloads from application stores populated
by softwares coming from various, sometimes obscure, sources. The low confidence in
the cybersecurity level of those application stores has pushed some institutions such as
Google to launch initiatives to improve the state of afairs [
        <xref ref-type="bibr" rid="ref39">54</xref>
        ] or to launch projects
aiming at standardizing the cybersecurity requirements for those applications [
        <xref ref-type="bibr" rid="ref40 ref41">55, 56</xref>
        ].
This state of afairs with regard to the low cybersecurity level of mobile applications
pushes for much need improvements [
        <xref ref-type="bibr" rid="ref42">57</xref>
        ].
      </p>
      <p>
        SPDs also use diferent technologies to connect to the core of the information system and
to connect between themselves. One promising technology is the 5G one [
        <xref ref-type="bibr" rid="ref43 ref44 ref45 ref46 ref5">58, 59, 60, 5, 61</xref>
        ],
and 6G in the future [
        <xref ref-type="bibr" rid="ref47 ref48">62, 63</xref>
        ]. However, this technology, as well as the others, have
raised cybersecurity concerns among researchers [
        <xref ref-type="bibr" rid="ref49">64</xref>
        ], institutions [
        <xref ref-type="bibr" rid="ref50 ref51 ref52 ref53 ref54 ref55 ref56 ref57">65, 66, 67, 68, 69, 70,
71, 72</xref>
        ] and industry [
        <xref ref-type="bibr" rid="ref58 ref59">73, 74</xref>
        ]. For example, even the specification of Bluetooth contains
vulnerabilities [
        <xref ref-type="bibr" rid="ref60 ref61 ref62">75, 76, 77</xref>
        ]. The deployment environment and ability of SPDs to create
device-to-device connections result in networks, such as ad hoc or mesh ones, having
diferent shapes and behaving diferently than core information system networks, and
having specific cybersecurity concerns.
      </p>
      <p>
        To secure communications in those networks, SPDs can rely on cryptography. However,
the low level of infrastructure support some of them receive and low computation power
some of them have may require some specific cryptographic solutions, such as lightweight
cryptography [
        <xref ref-type="bibr" rid="ref63">78</xref>
        ] or specific key agreement protocols [
        <xref ref-type="bibr" rid="ref64">79</xref>
        ].
      </p>
      <p>Another challenge that comes with SPDs is their deployment “far away” from the core of
the information system, and with an intermittent connection to it. This setting prevents
the implementation of security policies centered around the core of the information
system. SPDs require sepcific security policies that require specific means for deployment,
management and enforcement. Those means need to be secured in their own right in
order to prevent attackers from exploiting them to take control of the managed SPDs.</p>
      <p>
        Finally, the peripheral deployment of SPDs, their proximity to information sources, and
their common reliance on information collection imply concerns over privacy and data
protection issues [
        <xref ref-type="bibr" rid="ref65 ref66 ref67 ref68">80, 81, 82, 83</xref>
        ]. As a consequence, policymakers have published specific
and generic laws and regulations that apply to SPDs [
        <xref ref-type="bibr" rid="ref69 ref70 ref71 ref72 ref73 ref74 ref75 ref76">84, 85, 86, 87, 88, 89, 90, 91</xref>
        ].
      </p>
    </sec>
    <sec id="sec-4">
      <title>3. Solicited Papers</title>
      <p>In this context, C&amp;ESAR solicited submissions presenting didactic surveys, innovative
solutions, or insightful experience reports on the subject “Cybersecurity of Smart
Peripheral Devices (Mobiles / IoT / Edge)”.</p>
      <p>The scope covered:
• all steps of cybersecurity, from system design to operational cyberdefense or
pentesting, including DevSecOps loops and disposal/retirement of equipment and
systems;
• all types of systems and devices related to Smart Peripheral Devices (SPDs): mobiles
(including smartphones), IoT and lightweight semi-autonomous Edge computing.</p>
      <p>The topics included (without being limited to them, and in relation to cybersecurity
and SPDs) those mentioned above and below:
• Wireless connectivity technologies (5G/6G, Bluetooth, Zigbee, Z-Wave, LoRa,</p>
      <p>NB-IoT, Cat M1, Starlink, …)
• Peripheral network protocols (ad hoc networks, mesh routing protocols, 5G network
protocols, …)
• Cryptography (lightweight cryptography, multi-party key agreement with little
infrastructure support, 5G cryptography, …)
• Hardware support (ARM, Trusted Execution Environment, Secure Element, …)
• Lightweight security mechanisms
• Smartphones OS (iOS/Android) and other lightweight OS
• Supply chain, including application stores
• Attack surface of SPDs (Mobiles, IoT, Edge)
• Forensic of SPDs (Mobiles, IoT, Edge)
• Malware and phishing specifics relating to SPDs (Mobiles, IoT, Edge)
• Security policies and their management
• Privacy and data protection
• Laws and regulations
• Domain specific issues (Industrial IoT, UAV, health devices, autonomous vehicules,
…)</p>
      <p>The topic also covered all the following keywords applied in the context of peripheral
devices: Cybersecurity, Mobiles, Smartphone, Internet of Things (IoT), Edge Computing,
Internet of Battle Things (IoBT), Internet of Military Things (IoMT), Android, iOS, 5G,
6G, LoRa, StarLink, (Lightweight) Cryptography, Mobile Ad Hoc Network (MANET),
Device to Device (D2D) Connections, Malwares, AppStore, Forensic, Trusted Execution
Environment (TEE), Secure Element (SE), Security Policies, Law, Regulation.</p>
    </sec>
    <sec id="sec-5">
      <title>4. Review Process</title>
      <p>C&amp;ESAR received 18 submissions. Among those, 12 proposals have been selected for
the final round of reviews (67% pre-selection rate). Out of those pre-selected proposals,
12 final versions were submitted; out of which, 9 have been selected for presentation at
the conference (a 75% acceptation rate for the final round of reviews, and a 50% overall
acceptation rate for the conference). Finally, 4 of the presented papers have been selected
for inclusion in the proceedings (an overall acceptation rate of 22% for the proceedings).</p>
    </sec>
    <sec id="sec-6">
      <title>5. Program Committee</title>
      <p>This peer review has been made possible thanks to the dedication of the members of the
following program committee:
• Erwan Abgrall
• José Araujo, Orange Cyberdéfense
• Christophe Bidan, CentraleSupélec
• Frédéric Cuppens, Polytechnique Montréal
• Herve Debar, Télécom SudParis
• Ivan Fontarensky, Thales
• Jacques Fournier, CEA
• Julien Francq, Naval Group
• Brittia Guiriec, DGA MI
• Gurvan Le Guernic, DGA MI &amp; Université de Rennes
• Frédéric Majorczyk, DGA MI &amp; CentraleSupélec
• Guillaume Meier, Airbus R&amp;D
• Laurence Ogor, DGA MI
• Marc-Oliver Pahl, IMT Atlantique &amp; Chaire Cyber CNI
• Yves-Alexis Perez, ANSSI
• Ludovic Pietre-Cambacedes, EDF
• Louis Rilling, DGA MI
• Eric Wiatrowski
• Olivier Zendra, Inria
[22] DARPA Staf, Ocean of Things Aims to Expand Maritime Awareness across Open
Seas, Technical Report, DARPA, 2017. URL: https://www.darpa.mil/news-events/
2017-12-06.
[23] Wikipedia contributors, Internet of things — Wikipedia, The Free
Encyclopedia, https://en.wikipedia.org/w/index.php?title=Internet_of_things&amp;oldid=
1128546461, 2022. [Online; accessed 6-January-2023].
[24] Wikipedia contributors, Edge computing — Wikipedia, The Free Encyclopedia, https:
//en.wikipedia.org/w/index.php?title=Edge_computing&amp;oldid=1127185952, 2022.
[Online; accessed 6-January-2023].
[25] Check Point, Mobile Security Report 2021, Technical Report, Check Point
Software Technologies Ltd., 2021. URL: https://resources.checkpoint.com/
cyber-security-resources/mobile-security-report-2021.
[26] Check Point, Mobile Security Trends in 2022, Blog Post, Check Point
Software Technologies Ltd., 2022. URL: https://www.checkpoint.com/cyber-hub/
threat-prevention/what-is-mobile-security/mobile-security-trends-in-2022/.
[27] M. b. Mohamad Noor, W. H. Hassan, Current research on Internet of Things
(IoT) security: A survey, Computer Networks 148 (2019) 283–294. URL: https:
//www.sciencedirect.com/science/article/pii/S1389128618307035. doi:10.1016/j.
comnet.2018.11.025.
[28] H. Awan, Mobile Security Threats Prediction for 2023, Technical Report, efani, 2022.</p>
      <p>URL: https://www.efani.com/blog/mobile-threats-prediction-2023.
[29] G. Rowlands, The Internet of Military Things &amp; Machine Intelligence: A Winning</p>
      <p>Edge or Security Nightmare?, Technical Report, III, 2017.
[30] P. S. Bangare, K. P. Patil, Security Issues and Challenges in Internet of Things (IOT)
System, in: Proc. Advance Computing and Innovative Technologies in Engineering
(ICACITE), 2022, pp. 91–94. doi:10.1109/ICACITE53722.2022.9823709.
[31] Y. Harbi, Z. Aliouat, S. Harous, A. Bentaleb, A. Refoufi, A Review of Security in
Internet of Things, Wireless Personal Communications 108 (2019) 325–344. URL:
https://doi.org/10.1007/s11277-019-06405-y. doi:10.1007/s11277-019-06405-y.
[32] B. Liao, Y. Ali, S. Nazir, L. He, H. U. Khan, Security Analysis of IoT Devices by
Using Mobile Computing: A Systematic Literature Review, IEEE Access 8 (2020)
120331–120350. doi:10.1109/ACCESS.2020.3006358.
[33] P. Delgado-Santos, G. Stragapede, R. Tolosana, R. Guest, F. Deravi, R.
VeraRodriguez, A Survey of Privacy Vulnerabilities of Mobile Device Sensors, ACM
Computing Surveys 54 (2022) 1–30. doi:10.1145/3510579.
[34] Y. Mekdad, A. Aris, L. Babun, A. E. Fergougui, M. Conti, R. Lazzeretti, A. S.</p>
      <p>Uluagac, A Survey on Security and Privacy Issues of UAVs, 2021. URL: https:
//arxiv.org/abs/2109.14442. doi:10.48550/ARXIV.2109.14442.
[35] M. Aqeel, F. Ali, M. w. Iqbal, T. Rana, M. Arif, M. Auwul, A Review of Security
and Privacy Concerns in the Internet of Things (IoT), Journal of Sensors 2022
(2022) 1–20. doi:10.1155/2022/5724168.
[36] S. Sendhil, The security impact of IoT on business transformation, Insights,
ManageEngine, 2023. URL: https://insights.manageengine.com/digital-transformation/
the-security-impact-of-iot-on-business-transformation/.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>European</given-names>
            <surname>Commission</surname>
          </string-name>
          ,
          <article-title>Europe's Internet of Things Policy</article-title>
          , Webpage, European Commission,
          <year>2022</year>
          . URL: https://digital-strategy.ec.europa.eu/en/policies/ internet-things-policy.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>R. van der Meulen</surname>
          </string-name>
          ,
          <article-title>What Edge Computing Means for Infrastructure and Operations Leaders</article-title>
          , Article, Gartner, Inc.,
          <year>2018</year>
          . URL: https://www.gartner.com/smarterwithgartner/ what
          <article-title>-edge-computing-means-for-infrastructure-and-operations-leaders.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>A.</given-names>
            <surname>Nef</surname>
          </string-name>
          ,
          <year>Predicts 2022</year>
          :
          <article-title>The Distributed Enterprise Drives Computing to the Edge</article-title>
          ,
          <source>Technical Report</source>
          , Gartner, Inc.,
          <year>2021</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>K.</given-names>
            <surname>Costello</surname>
          </string-name>
          ,
          <article-title>Gartner Predicts the Future of Cloud and Edge Infrastructure</article-title>
          , Article, Gartner, Inc.,
          <year>2021</year>
          . URL: https://www.gartner.com/smarterwithgartner/ gartner
          <article-title>-predicts-the-future-of-cloud-and-edge-infrastructure.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>M.</given-names>
            <surname>Hasan</surname>
          </string-name>
          , State of IoT 2022:
          <article-title>Number of connected IoT devices growing 18% to 14.4 billion globally, Blog post</article-title>
          ,
          <source>IoT Analytics GmbH</source>
          ,
          <year>2022</year>
          . URL: https://iot-analytics.
          <article-title>com/number-connected-iot-devices/.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Wikipedia</surname>
            <given-names>contributors</given-names>
          </string-name>
          ,
          <source>Industrial internet of things - Wikipedia</source>
          , The Free Encyclopedia, https://en.wikipedia.org/wiki/Industrial_internet_of_things,
          <year>2023</year>
          . [Online; accessed 6-January-2023].
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>E.</given-names>
            <surname>Sisinni</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Saifullah</surname>
          </string-name>
          , S. Han,
          <string-name>
            <surname>U</surname>
          </string-name>
          . Jennehag,
          <string-name>
            <given-names>M.</given-names>
            <surname>Gidlund</surname>
          </string-name>
          , Industrial Internet of Things: Challenges, Opportunities, and Directions,
          <source>IEEE Transactions on Industrial Informatics</source>
          <volume>14</volume>
          (
          <year>2018</year>
          )
          <fpage>4724</fpage>
          -
          <lpage>4734</lpage>
          . doi:
          <volume>10</volume>
          .1109/TII.
          <year>2018</year>
          .
          <volume>2852491</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>P. K.</given-names>
            <surname>Malik</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Sharma</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Singh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Gehlot</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. C.</given-names>
            <surname>Satapathy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W. S.</given-names>
            <surname>Alnumay</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Pelusi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>U.</given-names>
            <surname>Ghosh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Nayak</surname>
          </string-name>
          ,
          <article-title>Industrial Internet of Things and its Applications in Industry 4.0: State of The Art</article-title>
          ,
          <source>Computer Communications</source>
          <volume>166</volume>
          (
          <year>2021</year>
          )
          <fpage>125</fpage>
          -
          <lpage>139</lpage>
          . URL: https://www.sciencedirect.com/science/article/ pii/S0140366420319964. doi:
          <volume>10</volume>
          .1016/j.comcom.
          <year>2020</year>
          .
          <volume>11</volume>
          .016.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>M.</given-names>
            <surname>Serror</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Hack</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Henze</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Schuba</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Wehrle</surname>
          </string-name>
          ,
          <article-title>Challenges and Opportunities in Securing the Industrial Internet of Things</article-title>
          ,
          <source>IEEE Transactions on Industrial Informatics</source>
          <volume>17</volume>
          (
          <year>2021</year>
          )
          <fpage>2985</fpage>
          -
          <lpage>2996</lpage>
          . doi:
          <volume>10</volume>
          .1109/TII.
          <year>2020</year>
          .
          <volume>3023507</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>A.</given-names>
            <surname>Kott</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Swami</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>West</surname>
          </string-name>
          ,
          <source>The Internet of Battle Things, Computer</source>
          <volume>49</volume>
          (
          <year>2017</year>
          )
          <fpage>70</fpage>
          -
          <lpage>75</lpage>
          . doi:
          <volume>10</volume>
          .1109/
          <string-name>
            <surname>MC</surname>
          </string-name>
          .
          <year>2018</year>
          .
          <volume>2876048</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>S.</given-names>
            <surname>Russell</surname>
          </string-name>
          , T. Abdelzaher,
          <article-title>The Internet of Battlefield Things: The Next Generation of Command, Control, Communications and Intelligence (C3I) Decision-Making</article-title>
          ,
          <source>in: Proc. IEEE Military Communications Conference (MilCom)</source>
          ,
          <year>2018</year>
          , pp.
          <fpage>737</fpage>
          -
          <lpage>742</lpage>
          . doi:
          <volume>10</volume>
          .1109/MILCOM.
          <year>2018</year>
          .
          <volume>8599853</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>T.</given-names>
            <surname>Abdelzaher</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Ayanian</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Basar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Diggavi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Diesner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Ganesan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Govindan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Jha</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Lepoint</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Marlin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Nahrstedt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Nicol</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Rajkumar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Russell</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Seshia</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Sha</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Shenoy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Srivastava</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Sukhatme</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Swami</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Tabuada</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Towsley</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Vaidya</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Veeravalli</surname>
          </string-name>
          ,
          <article-title>Toward an Internet of Battlefield Things: A Resilience Perspective</article-title>
          ,
          <source>Computer</source>
          <volume>51</volume>
          (
          <year>2018</year>
          )
          <fpage>24</fpage>
          -
          <lpage>36</lpage>
          . URL: https://doi.org/10.1109/
          <string-name>
            <surname>MC</surname>
          </string-name>
          .
          <year>2018</year>
          .
          <volume>2876048</volume>
          . doi:
          <volume>10</volume>
          .1109/
          <string-name>
            <surname>MC</surname>
          </string-name>
          .
          <year>2018</year>
          .
          <volume>2876048</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <surname>Wikipedia</surname>
            <given-names>contributors</given-names>
          </string-name>
          ,
          <source>Internet of Military Things - Wikipedia</source>
          , The Free Encyclopedia, https://en.wikipedia.org/w/index.php?title=Internet_of_Military_Things&amp; oldid=1130011550,
          <year>2022</year>
          . [Online; accessed 6-January-2023].
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>L.</given-names>
            <surname>Cameron</surname>
          </string-name>
          ,
          <article-title>Internet of Things Meets the Military and Battlefield: Connecting Gear and Biometric Wearables for an IoMT and IoBT</article-title>
          , IEEE Computer Society (
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>M.</given-names>
            <surname>Pesqueur</surname>
          </string-name>
          , L'ailier de demain :
          <article-title>le partenariat homme-machine dans l</article-title>
          'armée de Terre, Notes de l'Ifri, Ifri,
          <year>2021</year>
          . URL: https://www.ifri.org/sites/default/files/ atoms/files/pesqueur_partenariat_homme_machine_
          <year>2021</year>
          .pdf.
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <article-title>Ministère des Armées, SICS (Système d'information du combat</article-title>
          de SCORPION),
          <source>Webpage, Ministère des Armées</source>
          ,
          <year>2022</year>
          . URL: https: //www.defense.gouv.fr/eurosatory/poles-thematiques/scorpion/connectivite/ sics-systeme
          <article-title>-dinformation-du-combat-scorpion.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <article-title>Ministère des Armées, The SCORPION programme</article-title>
          , Webpage,
          <source>Ministère des Armées</source>
          ,
          <year>2022</year>
          . URL: https://www.defense.gouv.fr/eurosatory/the-scorpion-programme.
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <article-title>Ofice of Strategic Communications, Internet of Battlefield Things (IoBT) CRA</article-title>
          , Website, U.S. Army DEVCOM Army Research Laboratory,
          <year>2023</year>
          . URL: https: //www.arl.army.mil/cras/iobt-cra/.
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>T.</given-names>
            <surname>Abdelzaher</surname>
          </string-name>
          ,
          <article-title>Alliance for IoBT Research on Evolving Intelligent Goal-driven Networks (IoBT REIGN)</article-title>
          , Website, University of Illinois at Urbana-Champaign,
          <year>2022</year>
          . URL: https://iobt.illinois.edu/.
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <surname>Wikipedia</surname>
            <given-names>contributors</given-names>
          </string-name>
          ,
          <string-name>
            <surname>IoBT-CRA - Wikipedia</surname>
          </string-name>
          , The Free Encyclopedia, https: //en.wikipedia.org/wiki/IoBT-CRA,
          <year>2022</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <article-title>MeriTalk Staf, DARPA Floats a Proposal for the Ocean of Things, MeriTalk (</article-title>
          <year>2018</year>
          ). URL: https://www.meritalk.com/articles/ darpa-floats
          <article-title>-a-proposal-for-the-ocean-of-things/.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [37]
          <string-name>
            <given-names>C.</given-names>
            <surname>Parton</surname>
          </string-name>
          ,
          <article-title>Chinese Cellular IoT technology: An analysis of threats and mitigation measures, White paper</article-title>
          ,
          <source>OODA LLC</source>
          ,
          <year>2023</year>
          . URL: https://www.oodaloop.com/globalrisk/2023/01/23/ chinese-cellular
          <article-title>-iot-technology-an-analysis-of-threats-and-mitigation-measures/</article-title>
          ,
          <source>full report ”Cellular IoT</source>
          modules - Supply Chain Security” available at https://www.oodaloop.com/wp-content/uploads/2023/01/Cellular_IoT_Paper_ JAN_Master_PDF.pdf.
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [38]
          <string-name>
            <surname>Verizon</surname>
          </string-name>
          ,
          <article-title>Verizon 2022 Mobile Security Index</article-title>
          ,
          <source>Technical Report, Verizon</source>
          ,
          <year>2022</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          [39]
          <string-name>
            <given-names>M.</given-names>
            <surname>Antonakakis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>April</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Bailey</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Bernhard</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Bursztein</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Cochran</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Durumeric</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. A.</given-names>
            <surname>Halderman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Invernizzi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Kallitsis</surname>
          </string-name>
          , et al.,
          <source>Understanding the Mirai Botnet, in: Proc. USENIX security symposium</source>
          ,
          <year>2017</year>
          , pp.
          <fpage>1093</fpage>
          -
          <lpage>1110</lpage>
          . URL: https://www.usenix.org/conference/usenixsecurity17/ technical-sessions/presentation/antonakakis.
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          [40]
          <string-name>
            <surname>Pradeo</surname>
          </string-name>
          ,
          <article-title>Mobile security predictions for 2022, Blog post</article-title>
          , Pradeo,
          <year>2022</year>
          . URL: https: //blog.pradeo.com/pradeos-predictions-
          <year>2022</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          [41]
          <string-name>
            <surname>Wikipedia</surname>
            <given-names>contributors</given-names>
          </string-name>
          ,
          <source>Mobile security - Wikipedia</source>
          , The Free Encyclopedia,
          <year>2022</year>
          . URL: https://en.wikipedia.org/w/index.php?title=Mobile_security&amp;oldid= 1127644660, [Online; accessed 6-January-2023].
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          [42]
          <string-name>
            <given-names>C.</given-names>
            <surname>Brown</surname>
          </string-name>
          , S. Dog,
          <string-name>
            <given-names>J. M.</given-names>
            <surname>Franklin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>McNab</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Voss-Northrop</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Peck</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Stidham</surname>
          </string-name>
          , Assessing Threats to Mobile Devices &amp;
          <article-title>Infrastructure: The Mobile Threat Catalogue</article-title>
          ,
          <source>NIST Interagency Report 8144, National Institute of Standards and Technology (NIST)</source>
          ,
          <year>2016</year>
          . Draft.
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          [43]
          <string-name>
            <surname>NIST</surname>
            , Mobile Threat Catalogue, Website,
            <given-names>NIST</given-names>
          </string-name>
          ,
          <year>2023</year>
          . URL: https://pages.nist.gov/ mobile-threat-catalogue/.
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          [44]
          <string-name>
            <surname>Jamf</surname>
          </string-name>
          ,
          <source>Security 360 Annual Trends Report, Technical Report, Jamf</source>
          ,
          <year>2022</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          [45]
          <string-name>
            <given-names>P.</given-names>
            <surname>Weichbroth</surname>
          </string-name>
          , L. Łysik, Mobile Security: Threats and
          <string-name>
            <given-names>Best</given-names>
            <surname>Practices</surname>
          </string-name>
          ,
          <source>Mobile Information Systems</source>
          <year>2020</year>
          (
          <year>2020</year>
          ). doi:
          <volume>10</volume>
          .1155/
          <year>2020</year>
          /8828078.
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          [46]
          <string-name>
            <given-names>A.</given-names>
            <surname>Qamar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Karim</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Chang</surname>
          </string-name>
          ,
          <article-title>Mobile malware attacks: Review, taxonomy &amp; future directions</article-title>
          ,
          <source>Future Generation Computer Systems</source>
          <volume>97</volume>
          (
          <year>2019</year>
          )
          <fpage>887</fpage>
          -
          <lpage>909</lpage>
          . doi:
          <volume>10</volume>
          .1016/j.future.
          <year>2019</year>
          .
          <volume>03</volume>
          .007.
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          [47]
          <string-name>
            <given-names>B.</given-names>
            <surname>Liao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Ali</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Nazir</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>He</surname>
          </string-name>
          , H. U. Khan,
          <article-title>Security Analysis of IoT Devices by Using Mobile Computing: A Systematic Literature Review</article-title>
          ,
          <source>IEEE Access 8</source>
          (
          <year>2020</year>
          )
          <fpage>120331</fpage>
          -
          <lpage>120350</lpage>
          . doi:
          <volume>10</volume>
          .1109/ACCESS.
          <year>2020</year>
          .
          <volume>3006358</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref33">
        <mixed-citation>
          [48]
          <string-name>
            <surname>Arrow</surname>
          </string-name>
          ,
          <article-title>Hardware Security for IoT Devices and Types of Hardware Security Attacks, Technical article</article-title>
          , Arrow,
          <year>2020</year>
          . URL: https://www.arrow.com/en/ research-and
          <article-title>-events/articles/understanding-the-importance-of-hardware-security.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref34">
        <mixed-citation>
          [49]
          <string-name>
            <surname>M. K. Pratt</surname>
          </string-name>
          ,
          <article-title>Bolster physical defenses with IoT hardware security, News article</article-title>
          ,
          <source>TechTarget</source>
          ,
          <year>2021</year>
          . URL: https://www.techtarget.com/iotagenda/tip/ Bolster-physical
          <article-title>-defenses-with-IoT-hardware-security.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref35">
        <mixed-citation>
          [50]
          <string-name>
            <given-names>W.</given-names>
            <surname>Hu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.-H.</given-names>
            <surname>Chang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Sengupta</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Bhunia</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Kastner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <article-title>An Overview of Hardware Security and Trust: Threats, Countermeasures, and Design Tools</article-title>
          ,
          <source>IEEE Transactions on Computer-Aided Design of Integrated Circuits and Systems</source>
          <volume>40</volume>
          (
          <year>2021</year>
          )
          <fpage>1010</fpage>
          -
          <lpage>1038</lpage>
          . doi:
          <volume>10</volume>
          .1109/TCAD.
          <year>2020</year>
          .
          <volume>3047976</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref36">
        <mixed-citation>
          [51]
          <string-name>
            <given-names>E.</given-names>
            <surname>Bernard-Moulin</surname>
          </string-name>
          ,
          <article-title>Protect your IoT device with hardware-based Secure Elements, Blog post</article-title>
          ,
          <source>IC'ALPS</source>
          ,
          <year>2021</year>
          . URL: https://www.icalps.com/news/blog_post/ embedded-security-iot/.
        </mixed-citation>
      </ref>
      <ref id="ref37">
        <mixed-citation>
          [52]
          <string-name>
            <given-names>M.</given-names>
            <surname>Zinkus</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T. M.</given-names>
            <surname>Jois</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Green</surname>
          </string-name>
          ,
          <article-title>Data Security on Mobile Devices: Current State of the Art</article-title>
          , Open Problems, and Proposed Solutions,
          <year>2021</year>
          . URL: https: //arxiv.org/abs/2105.12613. doi:
          <volume>10</volume>
          .48550/ARXIV.2105.12613.
        </mixed-citation>
      </ref>
      <ref id="ref38">
        <mixed-citation>
          [53]
          <string-name>
            <given-names>S.</given-names>
            <surname>Garg</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Baliyan</surname>
          </string-name>
          ,
          <article-title>Comparative analysis of Android and iOS from security viewpoint</article-title>
          ,
          <source>Computer Science Review</source>
          <volume>40</volume>
          (
          <year>2021</year>
          )
          <article-title>100372</article-title>
          . doi:
          <volume>10</volume>
          .1016/j.cosrev.
          <year>2021</year>
          .
          <volume>100372</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref39">
        <mixed-citation>
          [54]
          <string-name>
            <surname>Google</surname>
          </string-name>
          , App Defense Alliance,
          <year>2023</year>
          . URL: https://appdefensealliance.dev, [Online; accessed 4-January-2023].
        </mixed-citation>
      </ref>
      <ref id="ref40">
        <mixed-citation>
          [55]
          <string-name>
            <given-names>B.</given-names>
            <surname>Mueller</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Schleier</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Willemsen</surname>
          </string-name>
          ,
          <string-name>
            <surname>C.</surname>
          </string-name>
          <article-title>Holguera, OWASP Mobile Application Security Verification Standard (MASVS)</article-title>
          ,
          <source>Technical Report, Open Web Application Security Project (OWASP)</source>
          ,
          <year>2022</year>
          . URL: https://mas.owasp.org/,
          <source>version 1.4.2.</source>
        </mixed-citation>
      </ref>
      <ref id="ref41">
        <mixed-citation>
          [56]
          <string-name>
            <surname>ioXt</surname>
            <given-names>Alliance</given-names>
          </string-name>
          ,
          <article-title>The Global Standard for IoT Security</article-title>
          , Online,
          <year>2023</year>
          . URL: https: //www.ioxtalliance.org/, [Online; accessed 4-January-2023].
        </mixed-citation>
      </ref>
      <ref id="ref42">
        <mixed-citation>
          [57]
          <fpage>Build38</fpage>
          ,
          <article-title>Mobile application security trends for 2023, Blog post</article-title>
          ,
          <source>Build38</source>
          ,
          <year>2022</year>
          . URL: https://build38.com/trends-app-protection-2023/.
        </mixed-citation>
      </ref>
      <ref id="ref43">
        <mixed-citation>
          [58]
          <string-name>
            <given-names>R.</given-names>
            <surname>Khan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Kumar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D. N. K.</given-names>
            <surname>Jayakody</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Liyanage</surname>
          </string-name>
          ,
          <string-name>
            <surname>A</surname>
          </string-name>
          <article-title>Survey on Security and Privacy of 5G Technologies: Potential Solutions, Recent Advancements, and Future Directions</article-title>
          ,
          <source>IEEE Communications Surveys &amp; Tutorials</source>
          <volume>22</volume>
          (
          <year>2020</year>
          )
          <fpage>196</fpage>
          -
          <lpage>248</lpage>
          . doi:
          <volume>10</volume>
          .1109/COMST.
          <year>2019</year>
          .
          <volume>2933899</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref44">
        <mixed-citation>
          [59]
          <string-name>
            <given-names>H.</given-names>
            <surname>Attar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Issa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Ababneh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Abbasi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. A. A.</given-names>
            <surname>Solyman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Khosravi</surname>
          </string-name>
          ,
          <string-name>
            <surname>R.</surname>
          </string-name>
          <article-title>Said Agieb, 5G System Overview for Ongoing Smart Applications: Structure, Requirements, and</article-title>
          <string-name>
            <surname>Specifications</surname>
          </string-name>
          ,
          <source>Computational Intelligence and Neuroscience</source>
          (
          <year>2022</year>
          )
          <fpage>1</fpage>
          -
          <lpage>11</lpage>
          . doi:
          <volume>10</volume>
          .1155/
          <year>2022</year>
          /2476841.
        </mixed-citation>
      </ref>
      <ref id="ref45">
        <mixed-citation>
          [60]
          <string-name>
            <given-names>X.</given-names>
            <surname>Ji</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Huang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Jin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Tang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Liu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Zhong</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>You</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Xu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Zhao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Wu</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.</surname>
          </string-name>
          <article-title>Yi, Overview of 5G security technology</article-title>
          ,
          <source>Science China: Information Sciences</source>
          <volume>61</volume>
          (
          <year>2018</year>
          ).
          <source>doi:10.1007/s11432-017-9426-4.</source>
        </mixed-citation>
      </ref>
      <ref id="ref46">
        <mixed-citation>
          [61]
          <string-name>
            <given-names>X.</given-names>
            <surname>Huang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Yoshizawa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. B. M.</given-names>
            <surname>Baskaran</surname>
          </string-name>
          ,
          <article-title>Authentication Mechanisms in the 5G System</article-title>
          ,
          <source>Journal of ICT Standardization</source>
          <volume>9</volume>
          (
          <year>2021</year>
          )
          <fpage>61</fpage>
          -
          <lpage>78</lpage>
          . doi:
          <volume>10</volume>
          .13052/ jicts2245-
          <fpage>800X</fpage>
          .
          <fpage>921</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref47">
        <mixed-citation>
          [62]
          <string-name>
            <given-names>S.</given-names>
            <surname>Dang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Amin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Shihada</surname>
          </string-name>
          , M.-S. Alouini, What should 6G be?,
          <source>Nature Electronics</source>
          <volume>3</volume>
          (
          <year>2020</year>
          )
          <fpage>20</fpage>
          -
          <lpage>29</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref48">
        <mixed-citation>
          [63]
          <string-name>
            <surname>C. D. Alwis</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Kalla</surname>
            ,
            <given-names>Q.-V.</given-names>
          </string-name>
          <string-name>
            <surname>Pham</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          <string-name>
            <surname>Kumar</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          <string-name>
            <surname>Dev</surname>
            , W.-J. Hwang,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Liyanage</surname>
          </string-name>
          ,
          <source>Survey on 6G Frontiers: Trends</source>
          , Applications, Requirements, Technologies and Future Research,
          <source>IEEE Open Journal of the Communications Society</source>
          <volume>2</volume>
          (
          <year>2021</year>
          )
          <fpage>836</fpage>
          -
          <lpage>886</lpage>
          . doi:
          <volume>10</volume>
          .1109/OJCOMS.
          <year>2021</year>
          .
          <volume>3071496</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref49">
        <mixed-citation>
          [64]
          <string-name>
            <given-names>D.</given-names>
            <surname>Basin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Dreier</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Hirschi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Radomirovic</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Sasse</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Stettler</surname>
          </string-name>
          ,
          <string-name>
            <surname>A Formal</surname>
          </string-name>
          <article-title>Analysis of 5G Authentication</article-title>
          , in
          <source>: Proc. Computer and Communications Security (CCS)</source>
          ,
          <year>2018</year>
          , pp.
          <fpage>1383</fpage>
          -
          <lpage>1396</lpage>
          . doi:
          <volume>10</volume>
          .1145/3243734.3243846.
        </mixed-citation>
      </ref>
      <ref id="ref50">
        <mixed-citation>
          <source>[65] CISA, 5G Security and Resilience</source>
          , Website,
          <source>Cybersecurity and Infrastructure Security Agency (CISA)</source>
          ,
          <year>2023</year>
          . URL: https://www.cisa.gov/5g.
        </mixed-citation>
      </ref>
      <ref id="ref51">
        <mixed-citation>
          [66]
          <string-name>
            <given-names>Enduring</given-names>
            <surname>Security</surname>
          </string-name>
          <article-title>Framework (ESF) working group</article-title>
          , Potential Threat Vectors to 5G Infrastructure,
          <source>Technical Report, National Security Agency (NSA)</source>
          ,
          <article-title>the Cybersecurity and Infrastructure Security Agency (CISA), and the Ofice of the Director of National Intelligence (ODNI</article-title>
          ),
          <year>2021</year>
          . URL: https://www.cisa.gov/5g-library.
        </mixed-citation>
      </ref>
      <ref id="ref52">
        <mixed-citation>
          [67]
          <string-name>
            <given-names>Enduring</given-names>
            <surname>Security</surname>
          </string-name>
          <article-title>Framework (ESF) working group, ESF Potential Threats to 5G Network Slicing, Guidance, National Security Agency (NSA), the Cybersecurity and Infrastructure Security Agency (CISA), and the Ofice of the Director of National Intelligence (ODNI</article-title>
          ),
          <year>2022</year>
          . URL: https://www.cisa.gov/5g-library.
        </mixed-citation>
      </ref>
      <ref id="ref53">
        <mixed-citation>
          [68]
          <article-title>MITRE, the Department of Defense (DoD), FiGHT™ (5G Hierarchy of Threats), Knowledge Base, MITRE and the Department of Defense (DoD</article-title>
          ),
          <year>2022</year>
          . URL: https://fight.mitre.org/.
        </mixed-citation>
      </ref>
      <ref id="ref54">
        <mixed-citation>
          [69]
          <article-title>MITRE, MITRE and the Ofice of the Under Secretary of Defense Announce FiGHT™ Framework to Protect 5G Ecosystem, Press Release, MITRE and the Department of Defense (DoD</article-title>
          ),
          <year>2022</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref55">
        <mixed-citation>
          [70]
          <string-name>
            <surname>European</surname>
            <given-names>Commission</given-names>
          </string-name>
          ,
          <article-title>Member States publish a report on EU coordinated risk assessment of 5G networks security</article-title>
          , Press release,
          <source>European Union (EU)</source>
          ,
          <year>2019</year>
          . URL: https://ec.europa.eu/commission/presscorner/detail/en/IP_19_
          <fpage>6049</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref56">
        <mixed-citation>
          [71] NIS Cooperation Group,
          <article-title>EU coordinated risk assessment of the cybersecurity of 5G networks</article-title>
          ,
          <source>Technical Report, European Union (EU)</source>
          ,
          <year>2019</year>
          . URL: https://ec.europa. eu/commission/presscorner/detail/en/IP_19_
          <fpage>6049</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref57">
        <mixed-citation>
          [72]
          <string-name>
            <given-names>V.</given-names>
            <surname>Oeselg</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Šalaševičius</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Ploom</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Palm</surname>
          </string-name>
          ,
          <source>Military Movement: Risks from 5G Networks, Research Report, NATO Cooperative Cyber Defence Centre of Excellence (CCDCOE)</source>
          ,
          <year>2022</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref58">
        <mixed-citation>
          [73]
          <string-name>
            <surname>NIST</surname>
          </string-name>
          , 5G Cybersecurity: Volume B:
          <string-name>
            <surname>Approach</surname>
          </string-name>
          , Architecture, and Security Characteristics,
          <source>Special Report (SP)</source>
          <year>1800</year>
          -
          <fpage>33B</fpage>
          , NIST,
          <year>2022</year>
          . URL: https://www.nccoe.nist. gov/5g-cybersecurity, preliminary Draft.
        </mixed-citation>
      </ref>
      <ref id="ref59">
        <mixed-citation>
          [74]
          <string-name>
            <given-names>D.</given-names>
            <surname>Hutchins</surname>
          </string-name>
          , Making the Move to 5G, Playbook,
          <source>Government Business Council (GBC)</source>
          ,
          <year>2022</year>
          . URL: https://www.verizon.com/business/resources/reports/ making
          <article-title>-the-move-to-5g.pdf, underwritten by Verizon Communications Inc</article-title>
          .
        </mixed-citation>
      </ref>
      <ref id="ref60">
        <mixed-citation>
          [75]
          <string-name>
            <surname>CERT-FR</surname>
          </string-name>
          ,
          <article-title>Multiples vulnérabilités dans Bluetooth Core Specification, Avis du CERT-FR CERTFR-</article-title>
          2022
          <string-name>
            <surname>-</surname>
          </string-name>
          AVI-1107, ANSSI,
          <year>2022</year>
          . URL: https://www.cert.ssi.gouv. fr/avis/CERTFR-2022
          <string-name>
            <surname>-</surname>
          </string-name>
          AVI-1107/.
        </mixed-citation>
      </ref>
      <ref id="ref61">
        <mixed-citation>
          [76]
          <string-name>
            <surname>Bluetooth</surname>
            <given-names>SIG</given-names>
          </string-name>
          , Inc.,
          <string-name>
            <surname>Bluetooth</surname>
            <given-names>SIG</given-names>
          </string-name>
          <article-title>Statement Regarding the “Pairing Mode Confusion in BR/EDR” Vulnerability</article-title>
          ,
          <source>Technical Report</source>
          ,
          <string-name>
            <surname>Bluetooth</surname>
            <given-names>SIG</given-names>
          </string-name>
          , Inc.,
          <year>2022</year>
          . URL: https://www.bluetooth.
          <article-title>com/learn-about-bluetooth/key-attributes/ bluetooth-security/confusion-in-br-edr/.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref62">
        <mixed-citation>
          [77]
          <string-name>
            <surname>Bluetooth</surname>
            <given-names>SIG</given-names>
          </string-name>
          , Inc.,
          <source>Bluetooth SIG Statement Regarding the “Pairing Mode Confusion in BLE Passkey Entry” Vulnerability, Technical Report</source>
          ,
          <string-name>
            <surname>Bluetooth</surname>
            <given-names>SIG</given-names>
          </string-name>
          , Inc.,
          <year>2022</year>
          . URL: https://www.bluetooth.
          <article-title>com/learn-about-bluetooth/key-attributes/ bluetooth-security/confusion-in-ble-passkey/.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref63">
        <mixed-citation>
          [78]
          <string-name>
            <given-names>S.</given-names>
            <surname>Ganiev</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Khudoykulov</surname>
          </string-name>
          ,
          <article-title>Lightweight Cryptography Algorithms for IoT Devices: Open issues and challenges</article-title>
          ,
          <source>in: Proc. Information Science and Communications Technologies (ICISCT)</source>
          ,
          <year>2021</year>
          , pp.
          <fpage>01</fpage>
          -
          <lpage>04</lpage>
          . doi:
          <volume>10</volume>
          .1109/ICISCT52966.
          <year>2021</year>
          .
          <volume>9670281</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref64">
        <mixed-citation>
          [79]
          <string-name>
            <given-names>M.</given-names>
            <surname>Miettinen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Asokan</surname>
          </string-name>
          ,
          <article-title>Ad-hoc key agreement: A brief history and the challenges ahead</article-title>
          ,
          <source>Computer Communications</source>
          <volume>131</volume>
          (
          <year>2018</year>
          )
          <fpage>32</fpage>
          -
          <lpage>34</lpage>
          . URL: https: //www.sciencedirect.com/science/article/pii/S0140366418302007. doi:
          <volume>10</volume>
          .1016/j. comcom.
          <year>2018</year>
          .
          <volume>07</volume>
          .030, cOMCOM 40 years.
        </mixed-citation>
      </ref>
      <ref id="ref65">
        <mixed-citation>
          [80]
          <string-name>
            <given-names>FTC</given-names>
            <surname>Staf</surname>
          </string-name>
          ,
          <article-title>FTC Report on Internet of Things Urges Companies to Adopt Best Practices to Address Consumer Privacy</article-title>
          and
          <string-name>
            <given-names>Security</given-names>
            <surname>Risks</surname>
          </string-name>
          , Press Release,
          <source>Federal Trade Commission (FTC)</source>
          ,
          <year>2015</year>
          . URL: https://www.ftc.gov/news-events/news/press-releases/
          <year>2015</year>
          /01/ ftc
          <article-title>-report-internet-things-urges-companies-adopt-best-practices-address-consumer-privacy-security.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref66">
        <mixed-citation>
          [81]
          <string-name>
            <given-names>A.</given-names>
            <surname>Karale</surname>
          </string-name>
          ,
          <article-title>The Challenges of IoT Addressing Security</article-title>
          , Ethics, Privacy, and
          <string-name>
            <surname>Laws</surname>
          </string-name>
          ,
          <source>Internet of Things</source>
          <volume>15</volume>
          (
          <year>2021</year>
          )
          <article-title>100420</article-title>
          . doi:
          <volume>10</volume>
          .1016/j.iot.
          <year>2021</year>
          .
          <volume>100420</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref67">
        <mixed-citation>
          [82]
          <string-name>
            <given-names>K.</given-names>
            <surname>Kollnig</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Binns</surname>
          </string-name>
          ,
          <string-name>
            <surname>M. Van Kleek</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          <string-name>
            <surname>Lyngs</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Zhao</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          <string-name>
            <surname>Tinsman</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          <string-name>
            <surname>Shadbolt</surname>
          </string-name>
          ,
          <article-title>Before and after GDPR: Tracking in Mobile Apps</article-title>
          ,
          <source>Internet Policy Review</source>
          <volume>10</volume>
          (
          <year>2021</year>
          ). doi:
          <volume>10</volume>
          .14763/
          <year>2021</year>
          .4.1611.
        </mixed-citation>
      </ref>
      <ref id="ref68">
        <mixed-citation>
          [83]
          <string-name>
            <given-names>T.</given-names>
            <surname>Klosowski</surname>
          </string-name>
          ,
          <article-title>How Mobile Phones Became a Privacy Battleground-</article-title>
          and
          <string-name>
            <surname>How</surname>
          </string-name>
          to Protect Yourself, The New York Times: Wirecutter (
          <year>2022</year>
          ). URL: https://www. nytimes.com/wirecutter/blog/protect-your
          <article-title>-privacy-in-mobile-phones/.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref69">
        <mixed-citation>
          [84]
          <string-name>
            <given-names>M.</given-names>
            <surname>Nelson</surname>
          </string-name>
          ,
          <string-name>
            <surname>Understanding Global IoT Security Regulations</surname>
          </string-name>
          , Blog Post, Security Boulevard,
          <year>2021</year>
          . URL: https://securityboulevard.com/
          <year>2021</year>
          /06/ understanding-global
          <article-title>-iot-security-regulations/.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref70">
        <mixed-citation>
          [85]
          <string-name>
            <surname>Thales</surname>
            ,
            <given-names>IoT</given-names>
          </string-name>
          <article-title>Cybersecurity: regulating the Internet of Things, Webpage</article-title>
          , Thales,
          <year>2021</year>
          . URL: https://www.thalesgroup.com/en/markets/digital-identity-and-security/iot/ inspired/iot-regulations.
        </mixed-citation>
      </ref>
      <ref id="ref71">
        <mixed-citation>
          [86]
          <string-name>
            <given-names>P.</given-names>
            <surname>Nolan</surname>
          </string-name>
          ,
          <article-title>The 'Internet of Things': Legal Challenges in an Ultra-connected World</article-title>
          ,
          <source>Insights: Privacy &amp; Data Security</source>
          ,
          <year>2016</year>
          . URL: http://www.mhc.ie/latest/blog/ the-internet
          <article-title>-of-things-legal-challenges-in-an-ultra-connected-world.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref72">
        <mixed-citation>
          [87]
          <string-name>
            <surname>I. Brown</surname>
          </string-name>
          ,
          <source>Regulation and the Internet of Things</source>
          , Oxford Internet Institute,
          <year>2015</year>
          . URL: https://www.itu.int/en/ITU-D/Conferences/GSR/Documents/ GSR2015/Discussion_papers_and_Presentations/GSR_DiscussionPaper_IoT.pdf.
        </mixed-citation>
      </ref>
      <ref id="ref73">
        <mixed-citation>
          [88]
          <string-name>
            <surname>California</surname>
            <given-names>Senate</given-names>
          </string-name>
          , California Senate Bill No.
          <volume>327</volume>
          ,
          <string-name>
            <surname>Technical</surname>
            <given-names>Report</given-names>
          </string-name>
          , California Senate,
          <year>2018</year>
          .
          <article-title>Référence 209 dans la page wikipedia sur IoT</article-title>
          .
        </mixed-citation>
      </ref>
      <ref id="ref74">
        <mixed-citation>
          [89]
          <article-title>Ofice of the Privacy Commissioner of Canada, Privacy guidance for manufacturers of Internet of Things devices</article-title>
          , Guidance,
          <source>Ofice of the Privacy Commissioner of Canada</source>
          ,
          <year>2020</year>
          . URL: https://www.priv.gc.ca/en/privacy-topics/technology/gd_iot_man/.
        </mixed-citation>
      </ref>
      <ref id="ref75">
        <mixed-citation>
          [90]
          <string-name>
            <surname>ETSI</surname>
          </string-name>
          ,
          <article-title>Cyber Security for Consumer Internet of Things: Baseline Requirements</article-title>
          ,
          <source>European Standard EN 303 645</source>
          , ETSI,
          <year>2020</year>
          . URL: https://www.etsi.org/deliver/etsi_ en/303600_303699/303645/02.01.01_60/en_303645v020101p.
          <source>pdf, version 2.1.1.</source>
        </mixed-citation>
      </ref>
      <ref id="ref76">
        <mixed-citation>
          [91]
          <string-name>
            <surname>ETSI</surname>
          </string-name>
          ,
          <article-title>Guide to Cyber Security for Consumer Internet of Things</article-title>
          ,
          <source>Technical Report 103 621</source>
          , ETSI,
          <year>2022</year>
          . URL: https://www.etsi.org/deliver/etsi_tr/103600_103699/ 103621/01.02.01_60/tr_103621v010201p.
          <source>pdf, version 1.2.1.</source>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>