<!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>Practical Aspects of Using Fully Homomorphic Encryption Systems to Protect Cloud Computing</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Anna Ilyenko</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sergii Ilyenko</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Olena Prokopenko</string-name>
          <email>bortnik.olena.v@nau.edu.ua</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Hennadii Hulak</string-name>
          <email>h.hulak@kubg.edu.ua</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Iryna Melnyk</string-name>
          <email>iy.melnyk@kubg.edu.ua</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Borys Grinchenko Kyiv University</institution>
          ,
          <addr-line>18/2 Bulvarno-Kudriavska str., Kyiv, 04053</addr-line>
          ,
          <country country="UA">Ukraine</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>National Academy of the Security Service of Ukraine</institution>
          ,
          <addr-line>22 Mykhaila Maksymovycha str., Kyiv, 03022</addr-line>
          ,
          <country country="UA">Ukraine</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>National Aviation University</institution>
          ,
          <addr-line>1 Liubomyra Huzara ave., Kyiv, 03058</addr-line>
          ,
          <country country="UA">Ukraine</country>
        </aff>
      </contrib-group>
      <fpage>226</fpage>
      <lpage>233</lpage>
      <abstract>
        <p>Fully homomorphic encryption schemes are the most promising area of cryptographic information security, particularly in cloud computing. Over the last ten years, Fully Homomorphic Encryption (FHE) has moved from a theoretical idea to practical implementation in real-world cryptographic applications. The concept of homomorphic encryption is ideal for providing secure cloud computing, where user data will never be in plaintext at any stage of its processing. However, there are still many problems related to the performance and complexity of computing that need to be overcome. To confirm the effectiveness of homomorphic encryption in the cloud, a cryptographic cloud computing protection application based on homomorphic encryption was developed. Based on a detailed analysis of existing FHEs, studying their mathematical apparatus, and classifying them according to various criteria, two schemes were selected for implementation in the application-CKKS and BFV, which allow to performance of homomorphic processing of encrypted data. The proposed solution demonstrates a new approach to the design of FHE applications, where the user independently chooses the parameters for implementing the FHE scheme, according to his requirements. The proposed test local server allows to testing of selected scheme parameters by combining the execution of various homomorphic computations. Based on the tests, it is possible to customize the proposed application according to one's tasks, sacrificing performance and security for the ability to perform more complex homomorphic computations, or vice versa, or even to maintain a balance between them.</p>
      </abstract>
      <kwd-group>
        <kwd>1 Fully homomorphic encryption</kwd>
        <kwd>BFV schema</kwd>
        <kwd>CKKS schema</kwd>
        <kwd>cloud computing</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        By using cloud services, the user assigns the
task of ensuring the integrity, availability, and
confidentiality of data to the cloud provider. At
the same time, ensuring data confidentiality
using standard encryption methods is
ineffective, because the server must first
decrypt the data to perform data processing
[
        <xref ref-type="bibr" rid="ref1 ref2 ref3">1–3</xref>
        ]. This necessity creates the problem of
key distribution, as well as the problem of
possible theft of data decrypted by the server
and processed in plaintext.
      </p>
      <sec id="sec-1-1">
        <title>An effective solution to the shortcomings of</title>
        <p>standard cryptosystems is the use of
homomorphic schemes that allow the cloud
server to process encrypted client data while
obtaining the result that would be obtained by
performing the same operations on open data.</p>
        <p>Thus, the data is not in the open form at all
stages of processing.</p>
        <p>This paper aims to demonstrate how fully
homomorphic encryption can be used to
ensure data privacy in cloud computing. The
development of the author’s cryptographic
application for the protection of cloud
computing based on homomorphic encryption can
show how exactly it is possible to implement a DDoS, conflict between client procedures.
fully homomorphic encryption scheme in the Using cloud services allows users to access
model of client-server interaction, analyze the computing resources anywhere and anytime.
performance of encrypted data processing in Considering the obvious advantages of using
comparison with conventional encryption cloud services, there are also obvious
methods, and also track the correctness of the disadvantages.
results of the calculations performed on the The main disadvantage of using cloud
encrypted data when decrypting them. services is that the user provides their data to</p>
        <p>
          The work aims to study and test an the cloud provider and relies on the service
approach to cryptographic protection of cloud provider to ensure the appropriate level of
computing based on homomorphic encryption. confidentiality, integrity, and authenticity of
The practical value is the creation of an the user’s data through encryption, hashing,
author’s cryptographic application for cloud and other cryptographic mechanisms. However,
computing protection based on fully most cloud services require user data to be
homomorphic encryption using CKKS and BFV decrypted before it is processed. Therefore, if
schemes. This is an application with a the user does not trust the security
mechawindowed interface written in the Python nisms offered by the provider, he encrypts the
programming language using the capabilities data before transferring it to the cloud and
of the Microsoft SEAL cryptographic library, must transfer the private key along with the
which allows the user to independently select encrypted data to the cloud server, which in
the parameters of the homomorphic scheme turn uses this key to decrypt and further
implementation and investigate its process the decrypted data. In this scheme of
performance and the correctness of interaction between the client and the server,
homomorphic computations over encrypted the secret key can be stolen during its
data on a local cloud server. transmission. Data that has been decrypted by
the server for processing can also be stolen [
          <xref ref-type="bibr" rid="ref6 ref7 ref8">6–8</xref>
          ].
2. Theoretical Approaches to The use of homomorphic encryption
Security based on Fully eplriimvainteateensctrhyeptpioonsskibeiylistiynocefcitodmopersonmoitsninegedthtoe
Homomorphic Computing be transferred to the server, as well as the
possibility of stealing open data during
The National Institute of Standards and processing because the data is not decrypted
Technology (NIST) defines cloud computing as during processing and is never stored on the
a model for providing convenient, on-demand cloud server in plaintext. That is why this
network access to a shared pool of configurable technology is the most promising in the field of
computing resources (networks, servers, cloud computing security [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ].
storage, applications, and services) that can be Homomorphic encryption allows the cloud
quickly provisioned and released with minimal service provider to perform certain
effort by the administrator or service provider. computational functions on the data even
        </p>
        <p>
          Security risk analysis in cloud computing when it is encrypted. With traditional
should consider the risks of storing data in encryption schemes, customers must
different locations and the risks of data compromise the security of their data by
distribution between employees, and the level providing a private decryption key to the
of risk significance may depend on the cloud service provider to use cloud services, as
architecture model under consideration [
          <xref ref-type="bibr" rid="ref4 ref5">4–5</xref>
          ]. traditional schemes do not allow the provider
        </p>
        <p>
          Based on the ENISA report, the following to work with encrypted data [
          <xref ref-type="bibr" rid="ref10 ref11 ref12 ref13 ref14">10–14</xref>
          ].
categories of cloud computing security risks The use of homomorphic cryptosystems
exist organizational risks: loss of management, allows to exclude from the algorithm of
loss of business reputation, compliance issues, interaction between the user and the cloud
stoppage or failure of a cloud service, etc.; server the stages of transferring the secret key
technical risks: data protection risks, resource to the cloud provider with the subsequent
exhaustion (under- or over-utilization), decryption of data on the cloud server for
isolation failure, malicious insider (abuse of processing, so the interaction algorithm shows
high privileges), data interception, data leakage, in Fig. 1 looks like this: The user creates a
message m that must be sent and processed on
the cloud server. The user generates a key
pair—a public key Pk and a private key Sk
using some asymmetric encryption algorithm.
        </p>
        <p>The user encrypts the plaintext message m
using the public key Pk. The user sends the
received cryptogram c to a remote cloud
server. The server processes the encrypted
text с. The server sends the processed
encrypted text с to the user. The user decrypts
the processing result received from the server
with a private key.</p>
        <p>As we can see, the use of homomorphic
cryptosystems has made it possible to reduce
the algorithm of interaction between the user
and the cloud server by two stages: there is no
longer a need to send a private key to the
server, which eliminates the possibility of its
compromise, and to decrypt data on the server,
which eliminates the possibility of its theft.</p>
      </sec>
      <sec id="sec-1-2">
        <title>Modern fully homomorphic encryption</title>
        <p>
          schemes (hereinafter referred to as FHE, i.e.
Fully Homomorphic Encryption) date back to
2009, when Craig Gentry presented the first
possible FHE design. Later, Gentry developed
the idea of fully homomorphic encryption and
now there are many modern schemes [
          <xref ref-type="bibr" rid="ref15 ref16 ref17 ref18">15–18</xref>
          ].
        </p>
        <p>Any homomorphic encryption scheme
consists of four algorithms, namely:
1. Key generation algorithm (KeyGen):
accepts as input some parameters that
depend on the encryption scheme, and
as output receives a pair—a public key
(Pk) and a private key (Sk).
2. Encryption algorithm (Enc): accepts as
input the plaintext m and the public
encryption key Pk. The output is a
cryptogram (1):</p>
        <p>=Enc( ) (1)
3. Decryption algorithm (Dec): accepts a
cryptogram c and a private decryption
key Sk as input. The output is a
decrypted message (2):</p>
        <p>Dec( )= (2)
4. Evaluation algorithm (Eval): accepts a
pair of ciphers (c1, c2) as input and
evaluates the f() function over the
ciphers to get the result (3):
f(Enc( 1, 2))=f(Dec( 1, 2)=f( 1, 2) (3)</p>
        <p>
          The paper focuses on practical schemes for
complete homomorphic encryption systems,
namely: Brakerski-Fon-Vercauteren, BFV, and
Cheon-Kim-Kim-Song, CKKS. These schemes
work based on levels where there is a noise
parameter that allows only a limited number of
multiplication operations to be performed
until correct decryption is impossible. After all,
in non-binary schemes, the problem of
multiplication depth is now acute, which is
solved differently in different schemes—
linearization and modules switching in BFV,
change of scale in CKKS, etc. Despite all the
existing problems, at this stage, homomorphic
schemes can provide an appropriate level of
security and a sufficient level of computing
performance, offering to solve various
problems with binary and non-binary
schemes, integer and floating point schemes,
etc. [
          <xref ref-type="bibr" rid="ref19 ref20 ref21 ref7">7, 19–21</xref>
          ].
        </p>
        <p>To compare the homomorphic schemes, the
sizes of the public and private keys, the size of
the ciphertext, and three parameters are given
for each of them:  is security parameter, n is
grid size, and p is a power of two.</p>
        <p>The sizes of the public and private keys, as
well as the ciphertext for each of the schemes
under consideration are shown in Table 1.</p>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>3. Practical Aspects of</title>
    </sec>
    <sec id="sec-3">
      <title>Implementing Fully</title>
    </sec>
    <sec id="sec-4">
      <title>Homomorphic Systems</title>
      <p>
        For practical testing of homomorphic
cryptographic systems for cloud computing, a
cloud server was deployed, a leveled fully
homomorphic BFV and CKKS schemes were
selected, and the Microsoft SEAL library was
selected. The designed cryptographic module
uses Pyfhel, which provides a Python shell for
the Microsoft SEAL library that can be
extended with other C++ libraries and goes
beyond simply exposing the core API by adding
a carefully crafted abstraction layer that is easy
to use in Python [
        <xref ref-type="bibr" rid="ref22 ref23 ref24">22–24</xref>
        ]. The proposed
solution demonstrates a new approach to the
design of FHE applications, where the user
independently chooses the parameters for
implementing the FHE scheme, according to
their requirements.
      </p>
      <p>To evaluate the performance of the
implemented BFV and CKKS schemes,
performance tests of homomorphic addition
and multiplication for three values of n were
performed, followed by decryption, decoding,
and verification of the correctness of
homomorphic addition and multiplication.</p>
      <p>Based on the practical tests, a comparative
Table 2 was formed, which demonstrates the
performance of the BFV scheme concerning the
addition and multiplication operations.</p>
      <p>So, changing the value of n does not affect
the performance of the encoding operation,
and the encryption operation slows down by
70% for each increase in n.</p>
      <sec id="sec-4-1">
        <title>The decoding speed decreases by 50%, and all</title>
        <p>other operations by about 80% with each
increase in the value of the polynomial module.
The homomorphic calculations were performed
correctly, and the decrypted result coincides
with the manually calculated one, so the noise
level was greater than 0.</p>
        <p>As with the homomorphic addition
operation, the results of the homomorphic
multiplication performance testing for the BFV
scheme are presented in Table 3.</p>
      </sec>
      <sec id="sec-4-2">
        <title>According to the results of testing the speed of</title>
        <p>operations during homomorphic multiplication,
the decoding speed decreases by 50%, and all
other operations by about 80% with each
increase in the value of the polynomial module.
The homomorphic calculations were performed
correctly, and the decrypted result coincides
with the manually calculated one, so the noise
level was greater than 0.</p>
        <p>The percentage reduction in performance is
approximately the same for both multiplication
and addition operations in the BFV scheme.</p>
        <p>However, the absolute speed of
multiplication operations is lower than that of
addition, due to the need to perform
relinearization to reduce the polynomial degree
of the encrypted text and module switching
operations to reduce noise. Thus, the speed of
addition and multiplication operations when n
is equal to 8192 is almost the same, but if the
value of n increases, the performance of the
multiplication operation drops evenly by 70%.</p>
        <p>So, the most computationally complex
operations are homomorphic operations, which
take much longer than encryption, decryption,
encoding, and decoding operations. It is obvious
that the noise level increases much faster when
performing homomorphic multiplication, so
with several consecutive multiplication
operations or large number multiplication
operations, the noise level can drop to zero and
correct decryption will be impossible. However,
to perform the calculations required by the test,
even the minimum value of n equal to 8192 is
enough to ensure that the results of addition
and multiplication are correct.</p>
      </sec>
      <sec id="sec-4-3">
        <title>Based on the practical tests, comparative Table 4 is formed, which demonstrates the performance of the CKKS scheme concerning the addition operation.</title>
        <p>From the performed tests, it can be seen that
when moving from n equal to 8192 to n equal
to 16384, the encoding speed drops by 86%
and the encryption speed by 70%, with a
further transition to the value of n equal to
32768, both operations reduce their
performance by about 75%. At the same time,
the decryption speed steadily decreases by
50% in proportion to the increase in the value
of the polynomial module n. Decoding
operation is 80–85% slower on average.
Homomorphic addition, when changing the
value from n equal to 8192 to n equal to 16384,
reduces the efficiency of calculations by 70%,
and with further growth of n, the performance
drops by half, i.e. to 80%. All three values of n
for the CKKS scheme provide a sufficient noise
budget for the tested addition operations, so
the operations are performed correctly.</p>
        <p>As with the homomorphic addition
operation, the results of testing the
performance of homomorphic multiplication
for the CKKS scheme are presented in Table 5.
With homomorphic multiplication in the CKKS
scheme, decryption at the first two values of
the polynomial modulus n: 8192 and 16384
does not change, but performance drops
sharply by 85% when n is equal to 32768. At
the same time, with an increase in the value of
n, the speed of homomorphic multiplication
decreases by 83% on average, and decoding—
by 75%.</p>
        <p>Increasing the value of n has a more
significant effect on the decrease in
multiplication performance than addition. This
is primarily because multiplication operations
take more time than addition. After all,
homomorphic multiplication additionally
requires a linearization operation to reduce
the degree of the ciphertext polynomial, as well
as a scaling operation of the scale factor in the
CKKS scheme to reduce noise. The
linearization operation and scale switching of
the scale factor are computationally expensive,
which affects the performance of
homomorphic multiplication.</p>
        <p>However, what these two operations have
in common is that when moving from n equal
to 8192 to n equal to 16384, there is a uniform
drop in the performance of all operations, but
when n is equal to 32768, there is a sharp jump
in the speed of all operations, of course, except
for encryption and encoding operations.</p>
        <p>It is seen that, as in the BFV scheme, the
performance of multiplication and addition
operations in CKKS when n is equal to 8192 is
almost the same, but with the growth of n, the
multiplication performance gradually
decreases, first by 75%, and then by another
80%, which is more significant than in the BFV
scheme. The graphs clearly show that when
performing the cycle of homomorphic addition
operations, the BFV scheme is more productive,
where the total time for performing the
sequence of operations: encryption, encoding,
addition, decryption, and decoding is less than
that of CKKS. With n equal to 8192 and n equal
to 16384, the performance of addition in CKKS
and BFV is almost the same, but with n equal to
32768, homomorphic addition in BFV is 20%
faster.</p>
      </sec>
      <sec id="sec-4-4">
        <title>As we can see, the situation is similar to the one</title>
        <p>when comparing the performance of
homomorphic multiplication, the overall
performance of the BFV scheme is higher than
that of CKKS. With n equal to 8192 and n equal
to 16384, the multiplication performance of
CKKS and BFV is almost the same, but with n
equal to 32768, the homomorphic
multiplication in BFV is 20% faster.</p>
        <p>At the same time, the speed of the addition
operation is much faster for both schemes than
the multiplication operation. As explained
earlier, this is because the multiplication
operation is much more complex than the
addition operation. After all, there is a concept
of multiplication depth and noise level, which
grows much faster in homomorphic
multiplication than in addition. Therefore, to
perform homomorphic multiplication in both
schemes, additional operations are performed,
such as linearization, which reduces the degree
of the ciphertext polynomial, module
switching, to reduce the noise level in the BFV
scheme, and the scaling operation in CKKS, to
reduce the degree of the scale factor and noise
level.</p>
        <p>The testing proved that even with n equal to
8192, the noise level is sufficient to perform at
least one addition and multiplication
operation. That is, the larger the value of n, the
more consecutive multiplications the scheme
supports, but the lower its performance. It is
also worth taking into account the peculiarities
of the implementation of the schemes—if the
noise level reaches zero, then correct
decryption of the cryptogram using the BFV
scheme will be impossible, while at the same
time since the CKKS scheme is based on
“approximate calculations,” a high noise level
will significantly affect the accuracy of
calculations.</p>
        <p>In terms of performance, testing has shown
that the BFV scheme is faster when performing
homomorphic multiplication and addition
operations than CKKS. As for the accuracy of
calculations, the very fact that the CKKS
scheme is based on the concept of approximate
calculations makes it necessary to use the BFV
scheme to perform accurate calculations.
However, it is worth noting that CKKS is the
only option for working with floating-point
numbers.</p>
        <p>Thus, the choice of the CKKS and BFV
schemes in most cases depends on the type of
data to be processed: integers or floating point
numbers, after testing the performance of
homomorphic calculations, we can say that if
you need to ensure a small level of
multiplication depth, then for values of n below
32768, the performance of these schemes is
the same.</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>4. Conclusions</title>
      <p>The practical implementation of the designed
cryptographic application of cloud computing
protection based on homomorphic encryption
can provide a comprehensive solution for
protecting cloud infrastructure while
maintaining a balance between the required
level of security and computing performance,
as well as the number and complexity of
homomorphic computing. These capabilities
exist due to the use of the modern SEAL
cryptographic library as the basis of the
application architecture, which provides tools
for flexible implementation and customization
of CKKS and BFV schemes:
• At n = 8192 and n = 16384, the addition
performance in CKKS and BFV is the
same, at n = 32768, homomorphic
addition in BFV is 20% faster.
• At n = 8192 and n = 16384, the
multiplication performance of CKKS and
BFV is the same, at n = 32768,
homomorphic multiplication in BFV is
20% faster.
• At the same time, the speed of the
addition operation is much faster for
both schemes than the multiplication
operation. This is because to perform
homomorphic multiplication, both
schemes perform additional operations,
such as linearization, which reduces the
degree of the ciphertext polynomial,
module switching to reduce the noise
level in the BFV scheme, as well as the
CKKS scaling operation to reduce the
degree of the scale factor and noise level.</p>
      <p>The flexibility of customizing the program
module to meet the specific needs of the user is
provided by a user-friendly graphical interface,
where one can choose: the required FHE
scheme, depending on the type of data that the
user will work with; a polynomial module n,
which is chosen small if maximum performance
is required and large if there is a need to
perform complex homomorphic calculations; a
security parameter that affects the level of
security but does not affect the performance
and complexity of homomorphic computing.</p>
      <p>Along with the advantages, there are also
obvious disadvantages and unrealized
opportunities that allow the application to be
enhanced in the future. Among these, it is
possible to highlight the inability to see and
control the noise level—the user learns that
the noise level has reached the limit after
which correct decryption is impossible only
after decryption is performed and the
incorrectness of the calculations is assessed.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>A.</given-names>
            <surname>Bessalov</surname>
          </string-name>
          , et al.,
          <string-name>
            <surname>Multifunctional</surname>
            <given-names>CRS</given-names>
          </string-name>
          <article-title>Encryption Scheme on Isogenies of NonSupersingular Edwards Curves</article-title>
          , in: Workshop on Classic, Quantum, and
          <string-name>
            <surname>Post-Quantum</surname>
            <given-names>Cryptography</given-names>
          </string-name>
          , vol.
          <volume>3504</volume>
          (
          <year>2023</year>
          )
          <fpage>12</fpage>
          -
          <lpage>25</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>V.</given-names>
            <surname>Sokolov</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Skladannyi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Hulak</surname>
          </string-name>
          ,
          <article-title>Stability Verification of Self-Organized Wireless Networks with Block Encryption</article-title>
          ,
          <source>in: 5th International Workshop on Computer Modeling and Intelligent Systems</source>
          , vol.
          <volume>3137</volume>
          (
          <year>2022</year>
          )
          <fpage>227</fpage>
          -
          <lpage>237</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>A.</given-names>
            <surname>Bessalov</surname>
          </string-name>
          , et al.,
          <article-title>Implementation of the CSIDH Algorithm Model on Supersingular Twisted and Quadratic Edwards Curves</article-title>
          ,
          <source>in: Workshop on Cybersecurity Providing in Information and Telecommunication Systems</source>
          , vol.
          <volume>3187</volume>
          , no.
          <issue>1</issue>
          (
          <year>2022</year>
          )
          <fpage>302</fpage>
          -
          <lpage>309</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>N.</given-names>
            <surname>Roy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Jain</surname>
          </string-name>
          ,
          <source>Cloud Computing: Architecture and Concept of Virtualization, J. Sci. Technol</source>
          . Manag.
          <volume>4</volume>
          (
          <year>2015</year>
          )
          <fpage>2394</fpage>
          -
          <lpage>1537</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>Z.</given-names>
            <surname>Balogh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Turčáni</surname>
          </string-name>
          ,
          <article-title>Modeling of Data Security in Cloud Computing</article-title>
          , IEEE Systems Conference (
          <year>2016</year>
          )
          <fpage>1</fpage>
          -
          <lpage>6</lpage>
          . doi:
          <volume>10</volume>
          .1109/syscon.
          <year>2016</year>
          .
          <volume>7490658</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>D.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Zhao</surname>
          </string-name>
          .
          <article-title>Data Security and Privacy Protection Issues in Cloud Computing</article-title>
          ,
          <source>IEEE Int. Conf. Comput. Sci. Electron</source>
          . Eng.
          <volume>1</volume>
          (
          <year>2012</year>
          )
          <fpage>641</fpage>
          -
          <lpage>651</lpage>
          . doi:
          <volume>10</volume>
          .1109/iccsee.
          <year>2012</year>
          .
          <volume>193</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>J.</given-names>
            <surname>Cheon</surname>
          </string-name>
          , et al.
          <source>Homomorphic Encryption for Arithmetic of Approximate Numbers, 23rd Int. Conf. Theory Appl</source>
          . Cryptol. Inf. Secur. (
          <year>2017</year>
          )
          <fpage>409</fpage>
          -
          <lpage>437</lpage>
          . doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>319</fpage>
          -70694-8_
          <fpage>15</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>D.</given-names>
            <surname>Meng</surname>
          </string-name>
          , Data Security in Cloud Computing,
          <source>IEEE Int. Conf. Comput. Sci. Educ</source>
          . (
          <year>2013</year>
          )
          <fpage>810</fpage>
          -
          <lpage>813</lpage>
          . doi:
          <volume>10</volume>
          .1007/978-1-
          <fpage>4614</fpage>
          -3872-4_
          <fpage>103</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>P.</given-names>
            <surname>Anakhov</surname>
          </string-name>
          , et al.,
          <article-title>Evaluation Method of the Physical Compatibility of Equipment in a Hybrid Information Transmission Network</article-title>
          ,
          <source>Journal of Theoretical and Applied Information Technology</source>
          <volume>100</volume>
          (
          <issue>22</issue>
          ) (
          <year>2022</year>
          )
          <fpage>6635</fpage>
          -
          <lpage>6644</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>B.</given-names>
            <surname>Schneier</surname>
          </string-name>
          , Applied Cryptography: Protocols, Algorithms and Source Code in
          <string-name>
            <given-names>C</given-names>
            , 2nd
            <surname>Edition</surname>
          </string-name>
          , Wiley (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>C.</given-names>
            <surname>Gentry</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A Fully</given-names>
            <surname>Homomorphic Encryption Scheme</surname>
          </string-name>
          , Stanford University (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>A.</given-names>
            <surname>Acar</surname>
          </string-name>
          , et al.
          <source>A Survey on Homomorphic Encryption Schemes: Theory and Implementation</source>
          ,
          <source>ACM Computing Surveys</source>
          <volume>51</volume>
          (
          <issue>4</issue>
          ) (
          <year>2018</year>
          )
          <fpage>1</fpage>
          -
          <lpage>35</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>A.</given-names>
            <surname>Ilyenko</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Ilyenko</surname>
          </string-name>
          ,
          <source>Program Module of Cryptographic Protection Critically Important Information of Civil Aviation Channels, Int. Conf. Comput. Sci. Eng</source>
          . Educ. Appl. (
          <year>2022</year>
          )
          <fpage>235</fpage>
          -
          <lpage>247</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>S.</given-names>
            <surname>Kazmirchuk</surname>
          </string-name>
          , et al.,
          <article-title>Improved Gentry's Fully Homomorphic Encryption Scheme: Design, Implementation and Performance Evaluation, CybHyg (</article-title>
          <year>2019</year>
          )
          <fpage>72</fpage>
          -
          <lpage>83</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>C.</given-names>
            <surname>Gentry</surname>
          </string-name>
          ,
          <source>Fully Homomorphic Encryption Using Ideal Lattices, 41st ACM Symposium on Theory of Computing</source>
          (
          <year>2009</year>
          )
          <fpage>169</fpage>
          -
          <lpage>178</lpage>
          . doi:
          <volume>10</volume>
          .1145/1536414. 1536440.
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>C.</given-names>
            <surname>Gentry</surname>
          </string-name>
          ,
          <source>Toward Basing Fully Homomorphic Encryption on WorstCase Hardness</source>
          , Annual Cryptology Conference (
          <year>2010</year>
          )
          <fpage>116</fpage>
          -
          <lpage>137</lpage>
          . doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>642</fpage>
          -14623-
          <issue>7</issue>
          _
          <fpage>7</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <surname>[</surname>
            <given-names>C.</given-names>
          </string-name>
          <string-name>
            <surname>Gentry</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Halevi</surname>
          </string-name>
          ,
          <article-title>Implementing Gentry's Fully-Homomorphic Encryption Scheme</article-title>
          ,
          <source>Annual Int. Conf. Theory Appl</source>
          . Cryptogr.
          <string-name>
            <surname>Techniques</surname>
          </string-name>
          (
          <year>2011</year>
          )
          <fpage>129</fpage>
          -
          <lpage>148</lpage>
          . doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>642</fpage>
          -20465-
          <issue>4</issue>
          _
          <fpage>9</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>C.</given-names>
            <surname>Gentry</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Halevi</surname>
          </string-name>
          ,
          <article-title>Implementing Gentry's Fully-Homomorphic Encryption Scheme</article-title>
          ,
          <source>Cryptology ePrint Archive, Report</source>
          (
          <year>2010</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>Z.</given-names>
            <surname>Brakerski</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Gentry</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Vaikuntanathan</surname>
          </string-name>
          , (
          <article-title>Leveled) Fully Homomorphic Encryption Without Bootstrapping, ACM Transactions on Computation Theory (TOCT) 6(3) (</article-title>
          <year>2014</year>
          )
          <fpage>1</fpage>
          -
          <lpage>36</lpage>
          . doi:
          <volume>10</volume>
          .1145/2633600.
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <given-names>X.</given-names>
            <surname>Sun</surname>
          </string-name>
          , et al.,
          <source>Private Machine Learning Classification based on Fully Homomorphic Encryption, IEEE Transactions on Emerging Topics in Computing</source>
          <volume>8</volume>
          (
          <issue>2</issue>
          ) (
          <year>2018</year>
          )
          <fpage>352</fpage>
          -
          <lpage>364</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <given-names>D.</given-names>
            <surname>Stehlé</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Steinfeld</surname>
          </string-name>
          , Faster Fully Homomorphic Encryption,
          <source>Int. Conf. Theory Appl</source>
          . Cryptol. Inf. Secur. (
          <year>2010</year>
          )
          <fpage>377</fpage>
          -
          <lpage>394</lpage>
          . doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>642</fpage>
          - 17373-8_
          <fpage>22</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [22]
          <string-name>
            <given-names>A.</given-names>
            <surname>Titus</surname>
          </string-name>
          , et al.,
          <article-title>PySEAL: A Python Wrapper Implementation of the SEAL Homomorphic Encryption Library</article-title>
          , arXiv (
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [23]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Polyakov</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Rohloff</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Ryan. PALISADE Lattice Cryptography Library User Manual</surname>
          </string-name>
          ,
          <source>Tech. Rep</source>
          . (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          [24]
          <string-name>
            <given-names>S.</given-names>
            <surname>Erabelli</surname>
          </string-name>
          ,
          <article-title>pyFHE-a Python Library for Fully Homomorphic Encryption</article-title>
          ,
          <source>Ph. D. Dissertation</source>
          , Massachusetts Institute of Technology (
          <year>2020</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>