<!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 />
    <article-meta>
      <title-group>
        <article-title>Technology of Secure Data Exchange in the IoT System</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Hassan Mohamed Muhi-Aldeen</string-name>
          <email>muhialdeen.hassan@aliraqia.edu.iq</email>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Yurii Khlaponin</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ibtehal Shakir Mahmoud</string-name>
          <email>ibtehal.shaker@aliraqia.edu.iq</email>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Volodymyr Vyshniakov</string-name>
          <email>volodymyr.vyshniakov@gmail.com</email>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Vadym Poltorak</string-name>
          <email>poltorak_vp@online.ua</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Dmytro Khlaponin</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Muwafaq Shyaa Alwan</string-name>
          <email>dr.muwafaqalwan@aliraqia.edu.iq</email>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Kyiv National University of Construction and Architecture</institution>
          ,
          <addr-line>Kyiv</addr-line>
          ,
          <country country="UA">Ukraine</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>NTUU “Igor Sikorsky Kyiv Polytechnic Institute”</institution>
          ,
          <addr-line>Kyiv</addr-line>
          ,
          <country country="UA">Ukraine</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The use of public Internet channels for managing objects in the IoT system can lead to the emergence of security threats not only for this IoT system, but also it can provide cybercriminals with resources to carry out attacks on any other objects of the global network. Therefore, you should use secure data exchange technologies that prevent unauthorized entry into the system when building IoT systems. This technology is discussed in detail in this article. The purpose of this work is to improve safety of IoT systems through the use of a perfectly secure data exchange channel.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;IoT system</kwd>
        <kwd>safety of IoT systems</kwd>
        <kwd>secure data exchange technologies</kwd>
        <kwd>secure data exchange channel</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        In 2020 the number of connected devices to the
IoT exceeded 30 billion, and their annual growth
increased from 3 billion in 2017 to 5 billion in
2020 as shown by the published data of
researchers [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
      </p>
      <p>
        Forecasts up to 2025 assume that this growth
will not decrease, but tends to increase. This
testifies to the rapidly growing need for managing
remote sites and ample opportunities for their
implementation using existing tools and
technologies. However, the rapid growth of needs
and the broad possibilities of implementing IoT in
a short time often leads to insufficiently thought
out solutions from the point of view of security,
which is described in [
        <xref ref-type="bibr" rid="ref2 ref3 ref4">2-4</xref>
        ], where security at the
network level is attributed to the most vulnerable
area. Attackers are given the opportunity to use
them to implement DDoS attacks due to
insufficient protection of IoT devices, the number
and power of which increases with the number of
IoT users. The overwhelming majority of users
believe that general security rules for the IoT
should be developed at the state or interstate level.
      </p>
      <p>However, it is difficult to develop uniform
recommendations or standards due to the
difference in security requirements depending on
the area of use of the IoT. The variety of areas of
use is shown in Table 1.</p>
      <p>Gemalto's survey of IoT users found that 90%
were unsure about security. Thus, it seems to be
relevant the analysis of IoT systems from the point
of view of ensuring the secure exchange of data
over the Internet channels, as well as the technical
solutions in this area, given in the work.
2. Analysis of data exchange options
in IoT systems</p>
      <p>To connect IoT devices to the Internet, one of
two schemes can be used, shown in Fig. 1 and Fig.
2 respectively.</p>
      <p>The scheme shown in Fig. 1 is the simplest one
and can be successfully used in internal computer
networks. But such solution has a number of
disadvantages in the conditions of the public
Internet:</p>
      <p>- Connecting the server directly to the Internet
facilitates the intervention of unpredictable
external threats into management processes.
- Cybercriminals are more likely to install their
botnets (malware) on your server to implement
DoS and DDoS attacks.</p>
      <p>- This server requires a dedicated IP address on
the Internet, which is associated with additional
material costs.</p>
      <p>- To ensure the information security of the
server, qualified service is required.</p>
      <p>Disadvantages listed above are absent in the
circuit shown in Fig. 2, where data flows between
the terminal and management objects are filtered
by the proxy server. This server can
simultaneously serve many users, protecting their
data streams from malicious attacks. Internet
service providers (ISPs) can install such servers,
providing customers with cloud-based access to
resources. However, the user can install own
separate or corporate broker server in case of high
security requirements for information about
objects managed. In cases when the broker's
server is hit by a threat, the information about the
managed objects will be kept intact. An increase
in signal latency should be noted as a
disadvantage of control through an intermediary
server in comparison with the first scheme. But
this disadvantage can be considered insignificant,
since the performance in control systems cannot
be high due to the presence of unpredictable
network access latency using Internet channels.
3. Technical solutions to secure the
IoT</p>
      <p>
        Object management via the Internet does not
require the transfer of large amounts of data and
high-speed messaging. This allows you to use the
most advanced methods of protecting data from
threats of disclosure or spoofing during
transmission over channels. The use of such
methods makes it possible to exclude the
possibility of these threats being realized, which
is mathematically provable. It should be noted that
no expensive technical solutions are needed for
absolute protection. This protection is
implemented using simple software methods. It is
mathematically proven that the absolute
protection of information is provided by the
Vernam cipher, which is called one-time pad [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
The use of this cipher requires the fulfillment of
the conditions, the list of which is presented in
Table 2.
Conditions for ensuring absolute data protection
during transmission
      </p>
      <p>Condition
Generation of random
bit sequences (not
pseudo-random)</p>
      <p>Condition fulfillment
A method for random bits
generating is implemented,
which allows you to generate</p>
      <p>
        random sequences on any
computer, as described in [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]
      </p>
      <p>Each random bit For each communication
sequence can be used session, random bit
for encryption only sequences are generated
once independently of each other</p>
      <p>For the exchange of The exchange of random bit
random bit sequences, sequences occurs according to
an absolutely secure the Diffie-Hellman algorithm
communication with such parameters for
channel should be which there is no possibility of
used data disclosure in modern
conditions</p>
      <p>
        The work [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] substantiates the choice of the
Diffie-Hellman algorithm parameters. The
parameters of the algebraic group for the
implementation of the algorithm are selected
based on two conditions. In first, it is needed to
ensure the impossibility of disclosing data. From
the other hand, it is needed that the time of
cryptographic transformations does not exceed
the allowable value. In order to prevent data
disclosure, an algebraic group in the form of a
Galois field with characteristic 2 was chosen and
a degree, which is a safe prime number from the
series 503, 563, 587, 719, was chosen too. Since
the solution to the discrete logarithm problem for
such fields is unknown today, this protection
cannot be hacked in modern conditions. All
cryptographic transformations are implemented in
the form of several dozen lines in JavaScript and
can be copied and placed both in the client and
server parts of the software of IoT systems. If the
Node.js platform is used to write the server side,
then the cryptographic transformations in the
server and client sides will be identical. All
fragments of the data protection program for a
field of (2^503) elements are presented below.
      </p>
      <p>
        The beginning of filling the array with N
random bits looks like this:
var N = [504]; // Array of 503
random bits (N [0] is not used)
var T1 = new Date (); // Take the
timestamp for transformations
var TN = T1.getTime (); // TN
the number of milliseconds from
01/01/1970
N [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] = TN% 2; // Fill the first
bit depending on the parity of TN
The rest of the random bits will be formed in
the cycle of filling the array MA with powers of
the primitive root of the Galois field.
      </p>
      <p>
        The block for filling an array MA with powers
of A looks like this:
// Elements of arrays with index 0
are not used
var A = [504]; // Sequence of 503
bits for exponentiation
var B = [504]; // A sequence of
503 bits of the exponent
// Arrays for multiplying the
elements of the Galois field GF (2
^ 503)
var M1 = [504], M2 = [504], R =
[504];
// M1 [], M2 [] - factors R []
the result of multiplication
var MA = new Array (504); // Array
MA [] [] of degrees A []
for (var i = 0; i&lt;504; i ++) MA
[i] = new Array (504);
for (var i = 1; i&lt;= 503; i ++) MA
[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] [i] = A [i];
// The first line of the array was
filled with the value A []
for (var I = 2; I &lt;= 503; I ++)
{// Loop filling the array MA []
[] with powers of A []
// In the next 3 lines, we
continue filling the array N []
T1 = new Date (); // Take the
timestamp for transformations
TN = T1.getTime (); // TN - the
number of milliseconds from
01/01/1970
N [I] = TN% 2; // Fill in the next
bit depending on the parity of TN
for (var J = 1; J &lt;= 503; J ++) M1
[J] = M2 [J] = MA [I-1] [J];
      </p>
    </sec>
    <sec id="sec-2">
      <title>MULT (); // Function for</title>
      <p>
        multiplying the elements of the
Galois field GF (2 ^ 503)
for (var j = 1; j &lt;= 503; j ++) MA
[I] [j] = R [j];
} // Put degree 2 in MA [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] , put
degree 4 in MA [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ],
// put degree 8 in MA [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], put
degree 16 in MA [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], etc.
      </p>
      <p>Our task is to get the same random bit
sequences C[] on both sides of the data exchange.
This allows to add modulo 2 (XOR operation) bits
of the C[] sequence to each bit of data being sent
on the transmitting side. With such information
coding, absolute protection against disclosure
threats in the communication channel is provided.
The recipient of the information must add modulo
2 bits of the C[] sequence to the received bits for
decryption, which is exactly the same procedure
as on the transmitting side.</p>
      <p>
        The transformation process begins by
generating a sequence of 503 random bits on each
side. This is done simultaneously with filling the
array MA[][] with powers of the primitive root of
the Galois field. The number 2 is one of primitive
roots, which should be entered into the array A[].
In our example, the least significant bits
correspond to the lower array indices. Therefore,
we get a primitive root like this:
for (var i = 1; i&lt;= 503; i ++) A
[i] = 0; A [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] = 1; // Put the
number 2 in A []
      </p>
      <p>For raising to a power, a well-known method
of simplifying calculations was used, which
consists in replacing the operation of raising to a
power by a product of powers according to the
next expression:
(1)
where</p>
      <p>Since any exponent B can be represented as a
sum of values selected from a range of weights
20, 21, 22, 23,…, 2502, to calculate AB it is
enough to multiply no more than 503 elements
from the array MA.</p>
      <p>
        The block for raising A to power B looks like
this:
for (var i=1; i&lt;=503; i++) A[i]=0;
A[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]=1; // Put a unit in A[]
for (var J=1; J&lt;=503; J++)
if (B[J]==1) // Select the bits
equal to 1 from the binary form of
exponent
{
for (var I=1; I&lt;= 503;
I++){M1[I]=MA[J][I]; M2[I]=A[I];}
{
{
{
{
}
}
}
      </p>
    </sec>
    <sec id="sec-3">
      <title>MULT(); // Function for</title>
      <p>multiplying the elements of the
Galois field GF(2^503)
for (var I=1; I&lt;= 503; I++)
A[I]=R[I];
} // The elements MA[][] was
Multiplied, where B[J]=1.</p>
      <p>The function of multiplying the elements of the
Galois field according to the rule of polynomials
looks like this:
function MULT()
{ // Multiplication using the
polynomial X^503=X^3+1
var i, j, r, r1, r2, r3;
for (i = 1; i&lt;= 503; i ++) R[i] =
0;
for (i = 1; i&lt;= 503; i ++)
if (M1[i] == 1) // Select units,
because multiplication by 0 gives
0
for (j = 1; j &lt;= 503; j ++)
if (M2[j] == 1)
r = i + j-1;
if (r&gt; 503)</p>
      <p>Let's imagine an algorithm for obtaining bit
sequences that will be the same on both sides of
the data exchange.</p>
      <p>Step 1. The client enters a random bit into the
first element of the array N, and enters the value
of the primitive root of the Galois field into array
A.</p>
      <p>Step 2. The client executes the block of filling
the array MA with powers of A with the
simultaneous completion of filling the array with
N random bits.</p>
      <p>Step 3. The client copies array N to array B and
executes the exponentiation block of A.</p>
      <p>Step 4. The client sends to the server the result
of raising A to the power of B as a sequence of
503 bits</p>
      <p>Step 5. The server stores the sequence of bits
received from the client in array C and performs
actions similar to steps 1-3 of the client.</p>
      <p>Step 6. The server sends to the client its result
of raising A to power B.</p>
      <p>Step 7. The client stores the sequence of 503
bits received from the server in array A.</p>
      <p>Step 8. The client executes the block of filling
the array MA with powers of A without filling the
array with N random bits.</p>
      <p>Step 9. The client executes the block for
raising A to the power B and enters the result into
array C.</p>
      <p>Step 10. The server copies array C to array A
and performs the steps similar to steps 8 and 9 of
the client.</p>
      <p>The result of performing the above actions is
to obtain the same random sequences of bits in the
arrays C of the same name on the client and server
sides, which was required for encryption using the
one-time pad method.
4. Full-scale model of a secure IoT
system</p>
      <p>The main element of the IoT system that needs
to be protected from false control commands and
from intrusion by attackers who can create threats
such as DDoS attacks is computer for object
management (see Fig. 2). Connecting this
computer through the Router without providing a
real IP address does not provide the ability to
control this computer other than through the
console used to install the software or an
application program that provides the protection
described in the previous section. A well-known
minicomputer of the Raspberry Pi 3 type, which
has a 40-pin GPIO interface with wide
possibilities for connecting objects for monitoring
and control, was chosen as hardware. Linux
version Ubuntu 20.10 was selected as the
operating system, and the Node.js platform
version v12.18.2 with the onoff package was used
as a programming tool, which allows objects to be
controlled via the GPIO interface.</p>
      <p>The initial snippet of the CONPIN.js program
installed on this computer in the / home / ubuntu /
directory looks like this:
const HOST = '91 .198.50.144 ';</p>
      <p>This client program regularly contacts the
server (Mediator server) (see Fig. 2) with a period
of 20 seconds to transmit information about the
state of objects and receive control signals. The
duration of the period of 20 seconds is chosen
from the condition of proportionality with the
time of entering the Internet. The operation of this
program must be protected against possible power
outages. To automatically start the program after
power-up, add the following three lines to the
/etc/rc.local file:
#! / bin / sh
echo "#################### CONPIN
######################"
/ usr / bin / node / home / ubuntu
/ CONPIN &amp;</p>
      <p>The SOCKET.js program must be running on
the Mediator server (see Fig. 2) located at the ISP
(Internet Service Provider) site that provides
services in SaaS (Software as a Service) mode.
The initial snippet of this program looks like this:
// server / SOCKET.js //</p>
      <p>
        With a single intermediary computer with a
single real IP address, the provider can serve
multiple IoT client systems. The number of
supported systems depends only on the technical
data of the computer. The operation of the
SOCKET.js program must be protected from
failures that can lead to an emergency shutdown.
To do this, use the process manager pm2
automatic program restart tool, which must be
downloaded using the npm install pm2 –g
command. After that, the SOCKET.js program
should be launched with the pm2 start
SOCKET.js command. In this case, in case of any
failures, the program will automatically restart
[
        <xref ref-type="bibr" rid="ref13 ref8">8,13</xref>
        ].
      </p>
      <p>
        The main task of the Mediator server is to
protect the resources of IoT systems from the
penetration of intruders who have as their goal the
implementation of DoS and DDoS attacks. This
requires unauthorized entry into the Mediator
server, which is unlikely, provided the provider
follows standard instructions. Usually this
situation arises due to the fault of the provider's
staff. In any case of failures on this server, the
provider always has the ability to switch to a
backup server or restore the operation of the same
server using copies, which is the norm in the work
of providers [
        <xref ref-type="bibr" rid="ref12 ref9">9,12</xref>
        ].
      </p>
      <p>The exchange of data between users of the IoT
system and their objects is carried out via a web
interface through intermediate data files. These
files are created anew at each data exchange
session. Each individual user on the Mediator
server is allocated his own directory, where, in
addition to the SOCKET.js program with a unique
value for the PORT parameter, the vybir.js
program is located, the initial fragment of which
looks like this:
// vybir.js - HTTP Server Ver. 18
February 2021
var http = require ('http');
var url = require ('url');
var fs = require ('fs');
var static = require
('nodestatic');
var querystring = require
('querystring');
var file = new static.Server
('.');
http.createServer (function (req,
res)
{</p>
      <p>In the vybir.js program, a separate TCP port
number is allocated for each user. The
CONPIN.html file with images of object state
indicators and control buttons is also located in the
user directory. The user can download this file
through the link given to him like
http://91.198.50.144:8000/CONPIN.html. All
communication processes, including the
authorization procedure, are protected using the
means described in the previous section. The
above link is unprotected as it is only intended to
demonstrate the control process using eight binary
objects as an example. Authorization data is
stored in the same directory in an encrypted file.
5. Conclusions</p>
      <p>The reasons for the emergence of security
problems in IoT systems are described. Potential
security threats have been identified, both for the
IoT itself and for the use of its resources by
intruders in the implementation of attacks on other
objects of the Internet.</p>
      <p>Variants of data exchange schemes in IoT
systems have been analyzed and the choice of the
most secure scheme has been substantiated.</p>
      <p>The technical solutions that make it possible to
secure data exchange in IoT systems by building
an ideally secure data exchange channel are
considered in detail. These solutions are presented
in the form of text programs in the JavaScript
language and can be embedded in any user
software.</p>
      <p>Using the example of the current model of the
IoT system, it is shown that it is possible to
eliminate problems with emergencies in IoT
systems that arise for various reasons, including
malfunctions of programs, temporary power
outages or attempts to unauthorized entry into the
system. A link to a resource on the Internet is
provided to demonstrate the process of managing
objects.</p>
      <p>The technical solutions proposed in this work
make it possible to fully secure IoT systems from
information threats.
6. References</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>Orlov</surname>
            <given-names>S.</given-names>
          </string-name>
          (
          <year>2020</year>
          )
          <article-title>Pochemu problem bezopasnosti interneta veshhej okazalos' tak trudno reshit'? https://safe</article-title>
          .cnews.ru/articles/2020-05- 1_pochemu_problemu_bezopasnosti_intern eta
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Frustaci</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pace</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Aloi</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Fortino</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          (
          <year>2018</year>
          ).
          <article-title>Evaluating critical security issues of the iot world: Present and future challenges</article-title>
          .
          <source>IEEE Internet of Things Journal</source>
          ,
          <volume>5</volume>
          (
          <issue>4</issue>
          ),
          <fpage>2483</fpage>
          -
          <lpage>2495</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Conti</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dehghantanha</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Franke</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Watson</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          (
          <year>2018</year>
          ).
          <article-title>Internet of Things security and forensics: Challenges and opportunities</article-title>
          .
          <source>Future Generation Computer Systems</source>
          ,
          <volume>78</volume>
          (
          <issue>2</issue>
          ),
          <fpage>544</fpage>
          -
          <lpage>546</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>Giray</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tekinerdogan</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Tüzün</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          (
          <year>2018</year>
          ).
          <article-title>IoT system development methods</article-title>
          .
          <source>In Internet of Things</source>
          (pp.
          <fpage>141</fpage>
          -
          <lpage>159</lpage>
          ). CRC Press/Taylor &amp; Francis.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <surname>Shannon</surname>
            <given-names>C</given-names>
          </string-name>
          .
          <source>Communication Theory of Secrecy Systems. Bell System Technical Journal</source>
          .
          <year>1949</year>
          .
          <volume>28</volume>
          (
          <issue>4</issue>
          ). Pp.
          <volume>656</volume>
          -
          <fpage>715</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Chupryn</surname>
            <given-names>V.M.</given-names>
          </string-name>
          <article-title>Generuvannja vypadkovyh chisel shtatnymy zasobamy hostiv merezhi Internet</article-title>
          ./ V.M.
          <string-name>
            <surname>Chupryn</surname>
            ,
            <given-names>V.M.</given-names>
          </string-name>
          <string-name>
            <surname>Vyshnjakov</surname>
          </string-name>
          , M.P. Prygara // Zahyst informacii'.
          <source>- 2016</source>
          . -
          <fpage>Т</fpage>
          .
          <volume>18</volume>
          , №
          <fpage>4</fpage>
          . -
          <lpage>С</lpage>
          .
          <fpage>323</fpage>
          -
          <lpage>335</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>Chupryn</surname>
            <given-names>V.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vyshnjakov</surname>
            <given-names>V.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Prygara</surname>
            <given-names>M.P.</given-names>
          </string-name>
          <article-title>Metod protydii' nezakonnomu vplyvu na vyborciv u systemi Internet golosuvannja</article-title>
          .
          <source>Bezpeka informacii'</source>
          .
          <source>- 2017</source>
          . - Tom
          <volume>23</volume>
          , №
          <fpage>1</fpage>
          . -
          <lpage>С</lpage>
          .
          <fpage>7</fpage>
          -
          <lpage>14</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>V.M.</given-names>
            <surname>Chupryn</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.M.</given-names>
            <surname>Vyshnjakov</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.O.</given-names>
            <surname>Komarnyc</surname>
          </string-name>
          <article-title>'kyj, Metod protydii' atakam poserednyka u transparentnij systemi internet golosuvannja</article-title>
          , Zahyst informacii',
          <source>Ukrainian Information Security Research Journal</source>
          .
          <article-title>-</article-title>
          K.: NAU,
          <year>2018</year>
          . -
          <fpage>Т</fpage>
          .
          <year>20</year>
          . -
          <fpage>№</fpage>
          3. -
          <fpage>С</fpage>
          .
          <fpage>180</fpage>
          -
          <lpage>187</lpage>
          . http://jrnl.nau.edu.ua/index.php/ZI/article/vi ew/13079
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>Valentyn</given-names>
            <surname>Sobchuk</surname>
          </string-name>
          , Volodymyr Pichkur, Oleg Barabash, Oleksandr Laptiev, Kovalchuk Igor,
          <string-name>
            <given-names>Amina</given-names>
            <surname>Zidan</surname>
          </string-name>
          .
          <article-title>Algorithm of control of functionally stable manufacturing processes of enterprises</article-title>
          .
          <source>2020 IEEE 2nd International Conference on Advanced Trends in Information Theory (IEEE ATIT 2020) Conference Proceedings Kyiv, Ukraine, November 25-27</source>
          . pp.
          <fpage>206</fpage>
          -
          <lpage>211</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>Oleksandr</surname>
            <given-names>Laptiev</given-names>
          </string-name>
          , Savchenko Vitalii, Serhii Yevseiev, Halyna Haidur, Sergii Gakhov,
          <string-name>
            <given-names>Spartak</given-names>
            <surname>Hohoniants</surname>
          </string-name>
          .
          <article-title>The new method for detecting signals of means of covert obtaining information</article-title>
          .
          <source>2020 IEEE 2nd International Conference on Advanced Trends in Information Theory (IEEE ATIT 2020) Conference Proceedings Kyiv, Ukraine, November 25-27</source>
          . pp.
          <fpage>176</fpage>
          -
          <lpage>181</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>O.</given-names>
            <surname>Svynchuk</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Barabash</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Nikodem</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Kochan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Laptiev</surname>
          </string-name>
          .
          <article-title>Image compression using fractal functions</article-title>
          .
          <source>Fractal and Fractional</source>
          ,
          <year>2021</year>
          ,
          <volume>5</volume>
          (
          <issue>2</issue>
          ), 31.pp.
          <fpage>1</fpage>
          -
          <lpage>14</lpage>
          . DOI:
          <volume>10</volume>
          .3390/fractalfract5020031 - 14
          <source>Apr</source>
          <year>2021</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <surname>Androshchuk</surname>
            ,
            <given-names>А.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yevseiev</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Melenchuk</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lemeshko</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lemeshko</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          <article-title>Improvement of project risk assessment methods of implementation of automated information components of non-commercial organizational and technical systems</article-title>
          . EUREKA, Physics and Engineeringthis link is disabled,
          <year>2020</year>
          ,
          <year>2020</year>
          (1), pp.
          <fpage>48</fpage>
          -
          <lpage>55</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>V.</given-names>
            <surname>Khoroshko</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Khokhlacheva</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Khlaponin</surname>
          </string-name>
          ,
          <string-name>
            <surname>E. Gavrilko.</surname>
          </string-name>
          <article-title>Parametric monitoring of computing processes in information and computing systems</article-title>
          .
          <source>Workshop Proceedings</source>
          (http://ceurws.org) Vol-
          <volume>2067</volume>
          urn:nbn:de:
          <fpage>0074</fpage>
          -
          <lpage>2067</lpage>
          -8-0 P.
          <fpage>45</fpage>
          -
          <lpage>53</lpage>
          . - ISSN 1613-
          <fpage>0073</fpage>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>