<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.1 20151215//EN" "http://jats.nlm.nih.gov/publishing/1.1/JATS-journalpublishing1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" article-type="research-article" dtd-version="1.1">
<front>
<journal-meta>
<journal-id journal-id-type="pmc">CSSE</journal-id>
<journal-id journal-id-type="nlm-ta">CSSE</journal-id>
<journal-id journal-id-type="publisher-id">CSSE</journal-id>
<journal-title-group>
<journal-title>Computer Systems Science &#x0026; Engineering</journal-title>
</journal-title-group>
<issn pub-type="ppub">0267-6192</issn>
<publisher>
<publisher-name>Tech Science Press</publisher-name>
<publisher-loc>USA</publisher-loc>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="publisher-id">22404</article-id>
<article-id pub-id-type="doi">10.32604/csse.2022.022404</article-id>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Article</subject>
</subj-group>
</article-categories>
<title-group>
<article-title>Binary Multifold Encryption Technique for Complex Cloud Systems</article-title><alt-title alt-title-type="left-running-head">Binary Multifold Encryption Technique for Complex Cloud Systems</alt-title><alt-title alt-title-type="right-running-head">Binary Multifold Encryption Technique for Complex Cloud Systems</alt-title>
</title-group>
<contrib-group content-type="authors">
<contrib id="author-1" contrib-type="author" corresp="yes">
<name name-style="western"><surname>Ansgar Mary</surname><given-names>N.</given-names></name>
<xref ref-type="aff" rid="aff-1">1</xref><email>ansgarmary123@gmail.com</email>
</contrib>
<contrib id="author-2" contrib-type="author">
<name name-style="western"><surname>Latha</surname><given-names>T.</given-names></name>
<xref ref-type="aff" rid="aff-2">2</xref>
</contrib>
<aff id="aff-1"><label>1</label><institution>Department of Information and Technology, St. Xavier&#x2019;s Catholic College of Engineering</institution>, <addr-line>Tamil Nadu, 629001</addr-line>, <country>India</country></aff>
<aff id="aff-2"><label>2</label><institution>Department of Electronics and Communication Engineering, St. Xavier&#x2019;s Catholic College of Engineering</institution>, <addr-line>Tamil Nadu, 629001</addr-line>, <country>India</country></aff>
</contrib-group><author-notes><corresp id="cor1"><label>&#x002A;</label>Corresponding Author: N. Ansgar Mary. Email: <email>ansgarmary123@gmail.com</email></corresp></author-notes>
<pub-date pub-type="epub" date-type="pub" iso-8601-date="2022-01-18"><day>18</day>
<month>01</month>
<year>2022</year></pub-date>
<volume>42</volume>
<issue>3</issue>
<fpage>1199</fpage>
<lpage>1213</lpage>
<history>
<date date-type="received"><day>06</day><month>8</month><year>2021</year></date>
<date date-type="accepted"><day>18</day><month>9</month><year>2021</year></date>
</history>
<permissions>
<copyright-statement>&#x00A9; 2022 Ansgar Mary and Latha</copyright-statement>
<copyright-year>2022</copyright-year>
<copyright-holder>Ansgar Mary and Latha</copyright-holder>
<license xlink:href="https://creativecommons.org/licenses/by/4.0/">
<license-p>This work is licensed under a <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International License</ext-link>, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
</license>
</permissions>
<self-uri content-type="pdf" xlink:href="TSP_CSSE_22404.pdf"></self-uri>
<abstract>
<p>Data security is a major cloud computing issue due to different user transactions in the system. The evolution of cryptography and cryptographic analysis are regarded domains of current research. deoxyribo nucleic acid (DNA) cryptography makes use of DNA as a sensing platform, which is then manipulated using a variety of molecular methods. Many security mechanisms including knowledge-based authentication, two-factor authentication, adaptive authentication, multifactor authentication and single password authentication have been deployed. These cryptographic techniques have been developed to ensure confidentiality, but most of them are based on complex mathematical calculations and equations. In the proposed approach, a novel and unique Hybrid helix scuttle-deoxy ribo nucleic acids (HHS-DNA) encryption algorithm has been proposed which is inspired by DNA cryptography and Helix scuttle. The proposed HHS-DNA is a type of multifold binary version of DNA (MF-BDNA). The major role of this paper is to present a multifold HHS-DNA algorithm to encrypt the cloud data assuring more security with less complexity. The experimentation is carried out and it reduces the encryption time, cipher text size, and improves throughput. When compared with previous techniques, there is a 45&#x0025; improvement in throughput, 37&#x0025; fast in encryption time, 54.67&#x0025; cipher text size. The relevant experimental results and foregoing analysis show that this method is of good robustness, stability, and security.</p>
</abstract>
<kwd-group kwd-group-type="author">
<kwd>Cryptography</kwd>
<kwd>cloud network</kwd>
<kwd>deoxy ribo nucleic acid (DNA)</kwd>
<kwd>encryption</kwd>
<kwd>security</kwd>
<kwd>cloud service provider (CSP)</kwd>
</kwd-group>
</article-meta>
</front>
<body>
<sec id="s1">
<label>1</label>
<title>Introduction</title>
<p>Data security is being the biggest roadblock to cloud computing since the data are complex and of varied mode. Many security methods have been implemented to overcome this issue. Cryptography is particularly advantageous since data may be viewed without authorization but not read. Before storing data in the cloud, data owners must encrypt it. This ensures the confidentiality of sensitive information stored on public cloud storage. There are several cryptographic approaches for ensuring secrecy. However, the majority of them rely on complicated mathematical computations and ratios. Recently big data and cloud computing have been used for secured data processing during the transmission of data to authorized persons. It can give more efficiency and more storage space to clients securely. Many investors and enterprises are willing to spend their data on a cloud network. A recent report announced 76900 accounts are signing in to the Facebook in a minute, 400360 videos are uploaded to YouTube in a minute, 7.2 million Google searches were updated in a minute, 3.4 million Instagram posts are uploaded [<xref ref-type="bibr" rid="ref-1">1</xref>]. The data owner will upload the data into the cloud network, where all the information from various services is stored. The owner has to encrypt the data and finally, the encrypted data has been given to the cloud network [<xref ref-type="bibr" rid="ref-2">2</xref>]. The data uploaded for each minute is 1.8 ZB, this storage has been provided by cloud service [<xref ref-type="bibr" rid="ref-3">3</xref>]. HHS-DNA is a symmetric key algorithm [<xref ref-type="bibr" rid="ref-4">4</xref>] i.e., the same key is used for encryption as well as for decryption. The idea of this technique is based upon DNA cryptographic technique [<xref ref-type="bibr" rid="ref-5">5</xref>]. According to the proposed scheme, if a data owner wants to upload the data onto the cloud, he has to encrypt the data. Even if the cloud service providers are forced to reveal the data, the data which has been encrypted cannot be read by unauthorized users. The traditional approaches like DES [<xref ref-type="bibr" rid="ref-6">6</xref>], AES, Blow&#xFB01;sh [<xref ref-type="bibr" rid="ref-7">7</xref>], RSA [<xref ref-type="bibr" rid="ref-8">8</xref>], DNA cryptography etc. are still in operation for the real-time systems which are consuming enormous computing resources. So, it is required to develop a new cryptographic technique [<xref ref-type="bibr" rid="ref-9">9</xref>] that generates a bridge between the existing and the new technology.</p>
<p>The Cloud computing network has a storage mechanism to store the data in a cloud platform. Cloud computing networks consist of the data owner, data user, and mainly cloud data storage which is shown in <xref ref-type="fig" rid="fig-1">Fig. 1</xref>. Once the cloud receives the request from the data user, the encrypted data from the owner is sent to the cloud for further processing.</p>
<fig id="fig-1">
<label>Figure 1</label>
<caption>
<title>Cloud computing network</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_22404-fig-1.png"/>
</fig>
<p>When the user wants to accept the data, the user must have the Re-enc key. With the help of the Re-enc key [<xref ref-type="bibr" rid="ref-10">10</xref>], the data user can decrypt the content and view the data. The recent framework demonstrates privacy information of cloud networks and amplified input is given to the multi-fold cloud system. But the major center of this paper is to examine a component of this demonstration which could be a novel Re-enc symmetric key encryption method that has been utilized to encrypt/decrypt the [<xref ref-type="bibr" rid="ref-11">11</xref>] information. Asymmetric encryption techniques employs long keys to ensure the security which is a major drawback of it. Recent encryption techniques utilize more resources such as CPU time, storage, and power. Existing techniques need two keys for encrypt and decrypt the data. Most of the existing algorithms mainly involves complex and arduous numerical expressions. To overcome the hurdles existing in the prior research, the proposed HHS-DNA is a good contender for key encryption. Since this research paper utilizes symmetric key algorithm, it is easier for encrypting and decrypting large amount of data in lesser time. Compared with asymmetric algorithms, symmetric key algorithms provide more security in cloud data over the network. The speed of DNA cryptography is unremarkably 100 times high while compared with a computer. Also DNA needs lesser storage and can be perform using low power. This paper suggests reasonable encryption, which achieves high security over many attacks with the usage of low resources for encryption with less time complexity.</p>
<p>Section 2 progress with the review of the existing methodologies, its measures, and precise problem statements present in each methodology has efficiently emphasized. system model is presented in Section 3. Section 4 explains the proposed cryptographic algorithm and Section 5 has the results and discussion obtained by simulating the algorithm. Section 6 concludes the paper along with the future research direction of this paper.</p>
</sec>
<sec id="s2">
<label>2</label>
<title>Literature Survey</title>
<p>Encrypting the data before uploading it onto the cloud prevents unauthorized users from accessing the data. A lot of encryption algorithms have been developed to secure data stored on the cloud. Hiding the messages in an organism is more reversible and scalable compared with other DNA techniques. Tacking of message is negligible using [<xref ref-type="bibr" rid="ref-12">12</xref>] technique, it is more suitable for secret military information. DNA cryptography-based encryption algorithm has been used in [<xref ref-type="bibr" rid="ref-13">13</xref>]. It generates encoding tables randomly which enables the system to become more secure. Using this special encoding technique, the plaintext is converted into a 7-bit character and finally a 5-bit character. The same plaintext provides different cipher text each time; hence it is a more flexible and reliable technique. The multi-fold symmetric DNA encryption key [<xref ref-type="bibr" rid="ref-14">14</xref>] enables the encryption process to transpire on the client side. The result was compared with the previous technique to prove the function of the symmetric key.</p>
<p>Later investigations [<xref ref-type="bibr" rid="ref-15">15</xref>,<xref ref-type="bibr" rid="ref-16">16</xref>] demonstrate that some hidden function is established for DNA. The first research on DNA hiding was achieved in 1997, in which &#x201C;June 6 night: Normandy&#x201D; was successfully hidden. It was accomplished by encoding the secret message by substituting three successive characters for one value. For example, &#x00C4; was represented as CGE&#x201D;. Hence, a hidden secret may utilize keys as groundwork&#x2019;s of PCR ampli&#xFB01;cation to crack DNA microdots. At later repetitive codes are used to hide the secret message. RNA nucleotides have four distinctive sorts of nucleotides: adenine (A), guanine (G), cytosine (C), and uracil (U). Therefore, there are 4&#x2009;&#x003D;&#x2009;64 distinctive combinations, with almost twenty essential amino acids.</p>
<p>The multi-fold symmetric-key cryptography technique is based upon DNA cryptography [<xref ref-type="bibr" rid="ref-17">17</xref>]. A consistent view about both data security concerns and privacy issues presented in the survey that are faced by clients in cloud storage environments has been carried out [<xref ref-type="bibr" rid="ref-18">18</xref>]. Further to study the security in a cloud network, Secure Hidden Layer (SHL) and Application Programming Interface (API) for data encryption explained in [<xref ref-type="bibr" rid="ref-19">19</xref>]. The SHL is consisting of two major modules (i) Key Management Server (KMS) and (ii) Share Holder Server (SHS) which is used for storing and sharing cryptographic keys. A server-side encryption algorithm, has been employed which is based on the asymmetric algorithm (RSA and CRT) for providing end-to-end security of multimedia data. A novel DNA-based data encryption scheme was introduced in [<xref ref-type="bibr" rid="ref-20">20</xref>] for the cloud computing environment. Here, a 1024-bit secret key is generated based on DNA computing, user&#x2019;s attributes and Media Access Control (MAC) address of the user, and decimal encoding rule. American Standard Code for Information Interchange (ASCII) value, DNA bases, and complementary rule are used to generate the secret key that enables the system to protect against many security attacks.</p>
<p>A data security based strategy through DNA sequence by the virtue of Steganography has been employed by Raniyah Wazirali and Zenon Chaczko (2016). A new data concealing method based on DNA characteristics has been devised in the research. The encrypted image was represented by a DNA helix. Following, that DNA matrix was transformed to a QR (Quick Response) form, which has a wide range of applications. In addition, the article offers suggestions for selecting the best QR sites in order to get the rightmost position. A novel genetic algorithm-based model has been built [<xref ref-type="bibr" rid="ref-21">21</xref>]. Suyel Namasudra et al. (2017) have established a DNA based approach to overcome the time complexity in terms of data security. A lengthy 512-bit DNA based novel sequence has successfully utilized to improve data security, and it is protected from collision attacks, internal attacks, and other types of attacks. The suggested scheme is assessed in terms of both theoretical and experimental findings, which demonstrate its superiority to current schemes. In the future, an authorization mechanism might be implemented to improve security towards cybercriminals or bad users [<xref ref-type="bibr" rid="ref-22">22</xref>]. Chirakkarottu and Mathew [<xref ref-type="bibr" rid="ref-23">23</xref>] recommended a encryption method to encrypt the medical images. This paper mainly focused on providing security without minding the storage visual aspect. The images are initially re-arranged randomly and then DNA encrypt the images. Though the method provide security, the execution time is high. Balaraju and Rao [<xref ref-type="bibr" rid="ref-24">24</xref>] implemented Secure Hadoop Cluster using DNA Cryptography (SHCDNA) for securing data as a individual security that keeps the authenticated data in encrypted form. Although, SHCDNA reduces computations encryption of metadata is still questionable which is to be enhanced. Das et al. [<xref ref-type="bibr" rid="ref-25">25</xref>] explained the cryptography algorithm DNA in diverse facets like details about input and outputs and their nature. Yet a detailed implementation results are missing.</p>
<p>Based on the above researches reviewed, it is clear that the asymmetric key encryption algorithms take larger execution time. Moreover, the keys are larger and more complex for asymmetric encryption algorithm when compared to the symmetric encryption. Furthermore, the major drawbacks of existing techniques includes more power consumption, high storage and longer execution time. Hence, this paper presented an HHS-DNA to overcome the aforementioned hurdles. The subsequent Section 3 copes with the system model and structure.</p>
</sec>
<sec id="s3">
<label>3</label>
<title>System Model</title>
<p>The system model has five components such as Third-Party Examiner (TPE), Data owner (DO), Data User (DU), Trusted Privilege (TP), Cloud Service Provider (CSP). The system model for the proposed methodology is shown in <xref ref-type="fig" rid="fig-2">Fig. 2</xref>.</p>
<fig id="fig-2">
<label>Figure 2</label>
<caption>
<title>Cloud system model</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_22404-fig-2.png"/>
</fig>
<p>The major application of the proposed methodology is to provide security for the data owner side. The data owner is responsible for making a key index and data accessing policy. Trusted privilege duty is updating, canceling and distributing the keys for the Data holder and Cloud Service Provider. The data holder is the entity that can outsource the data files. If the data holder has the key to satisfy the terms and policies, it will outsource the data files. CSP has two semi-honest entities such as Storage-CSP and decryption-CSP for storage and qualified decryption of cipher text respectively. When data outsourced requires, it updates its cipher text. The result is checked by a third party examiner either matched or not.</p>
<sec id="s3_1">
<label>3.1</label>
<title>Trusted Privilege (TP) Set Up</title>
<p>The inputs of TP are &#x2018;i&#x2019; and outputs are private R encrypt key (R<sub>pi</sub>) and master R encrypt key is (R<sub>mi</sub>), explained in this section (input k: output R<sub>pi</sub>, R<sub>mi</sub>).</p>
<sec id="s3_1_1">
<label>3.1.1</label>
<title>R-Key</title>
<p>It takes a user&#x2019;s role <inline-formula id="ieqn-1">
<mml:math id="mml-ieqn-1"><mml:mi>r</mml:mi><mml:mi>o</mml:mi><mml:mi>l</mml:mi><mml:msub><mml:mi>e</mml:mi><mml:mrow><mml:msub><mml:mi>u</mml:mi><mml:mi>i</mml:mi></mml:msub></mml:mrow></mml:msub></mml:math>
</inline-formula>as input, and returns a role key <italic>rkey<sub>j</sub></italic>, <inline-formula id="ieqn-2">
<mml:math id="mml-ieqn-2"><mml:msub><mml:mrow><mml:mi>r</mml:mi><mml:mi>k</mml:mi><mml:mi>e</mml:mi><mml:mi>y</mml:mi></mml:mrow><mml:mrow><mml:mi>j</mml:mi></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:msub><mml:mrow><mml:mi>r</mml:mi><mml:mi>o</mml:mi><mml:mi>l</mml:mi><mml:mi>e</mml:mi></mml:mrow><mml:mrow><mml:msub><mml:mrow><mml:mi>u</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="normal">i</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:msub><mml:mo>.</mml:mo><mml:mrow><mml:mi>r</mml:mi><mml:mi>o</mml:mi><mml:mi>l</mml:mi><mml:mi>e</mml:mi><mml:mi>k</mml:mi><mml:mi>e</mml:mi><mml:mi>y</mml:mi></mml:mrow></mml:math>
</inline-formula>. The specific user <italic>u</italic><sub><italic>i</italic></sub> is associated with the role key <italic>rkey<sub>j</sub></italic>. Upon receiving an authorization request with the user&#x2019;s role, it returns the role key <italic>rkey<sub>j</sub></italic>. Each role is associated with a unique role key and has the corresponding privilege.</p>
</sec>
<sec id="s3_1_2">
<label>3.1.2</label>
<title>Encryption</title>
<p>The user executes the algorithm to encrypt the data blocks with the convergent key. It takes a set of file blocks &#x007B;<italic>b<sub>i</sub></italic>&#x007D;<sub><italic>i</italic>&#x2208;[1,<italic>n</italic>]</sub> as input, and returns the cipher text Cm &#x003D; &#x007B;Pm &#x002B; KA &#x00D7; PB&#x007D;. The user runs the hash over level blocks &#x007B;<italic>b<sub>i</sub></italic>&#x007D;<sub><italic>i</italic>&#x2208;[1,<italic>n</italic>]</sub> to obtain the convergent key&#x007B;<italic>k<sub>i</sub></italic>&#x007D;<sub>i&#x2208;[1,<italic>n</italic>]</sub>, <italic>k<sub>i</sub></italic>&#x2009;&#x003D;&#x2009;<italic>h</italic>(<italic>b<sub>i</sub></italic>). Then, the user symmetrically encrypts the blocks with the convergent public key, PB &#x003D; KB &#x00D7; M to obtain the cipher text Cm &#x003D; &#x007B;Pm &#x002B; KA &#x00D7; PB&#x007D;.</p>
<p>The subsequent section deals with the comprehensive emphasize of the proposed system and functions.</p>
</sec>
</sec>
</sec>
<sec id="s4">
<label>4</label>
<title>Proposed Methodology</title>
<p>The proposed methodology is based on three levels as user level, security level, cloud storage level which are shown in <xref ref-type="fig" rid="fig-3">Fig. 3</xref>. At the user level, encryption key generation and encryption processes have been done. At the security level, encrypted data has been uploaded to the cloud and the encryption process has been done based on key level management. At the same time, the receiver receives the encrypted data along with key management. The receiver decrypts the data based on their requirement.</p>
<fig id="fig-3">
<label>Figure 3</label>
<caption>
<title>Different cloud levels</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_22404-fig-3.png"/>
</fig>
<sec id="s4_1">
<label>4.1</label>
<title>User Level</title>
<p>At the data user level, the data is transferred with the correct key for the authentication process. The key selection is processed based on node selection and Re-enc key processing. For node selection, we define three parameters as hold, children, and grade for TP. In between TP and DH, many nodes are present. So, we have to select the best node for the transmission of keys over the network. In holder stores the parameters of the nodes which is defined as V<italic>&#x003D;</italic> &#x007B;<italic>v</italic><sub>1</sub>&#x007C;<italic>v</italic><sub>2</sub>&#x007D; (left to right index). Children nodes contain child node f, corresponding nodes such as left, right, and middle nodes. The grade represents the number of elements present in the nodes. If grade &#x003D;&#x2009;2 means, it will save 2 elements, and order 3 saves 3 elements.</p>
<fig id="fig-8">
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_22404-fig-8.png"/>
</fig>
<p>Step 1: Trusted authority gets in hold and grade of current nodes between the networks.</p>
<p>Step 2: if (grade <italic>(</italic><italic>Z<sub>k</sub>)</italic> &#x003D;&#x2009;2) then trusted privilege checks the node value with <inline-formula id="ieqn-3">
<mml:math id="mml-ieqn-3"><mml:msub><mml:mrow><mml:mi>x</mml:mi></mml:mrow><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mrow><mml:mi>x</mml:mi></mml:mrow><mml:mrow><mml:mrow><mml:mi>i</mml:mi><mml:mo>+</mml:mo><mml:mn>1</mml:mn></mml:mrow></mml:mrow></mml:msub></mml:math>
</inline-formula> of node <italic>X</italic><sub><italic>i</italic></sub>.</p>
<p>Step 3: if (grade (<italic>Z<sub>k</sub>)</italic> &#x003D;&#x2009;3) then trusted privilege checks the node value with <inline-formula id="ieqn-4">
<mml:math id="mml-ieqn-4"><mml:msub><mml:mrow><mml:mi>x</mml:mi></mml:mrow><mml:mrow><mml:mi>i</mml:mi></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mrow><mml:mi>x</mml:mi></mml:mrow><mml:mrow><mml:mrow><mml:mi>i</mml:mi><mml:mo>+</mml:mo><mml:mn>1</mml:mn></mml:mrow></mml:mrow></mml:msub><mml:mo>,</mml:mo><mml:msub><mml:mrow><mml:mi>x</mml:mi></mml:mrow><mml:mrow><mml:mrow><mml:mi>i</mml:mi><mml:mo>+</mml:mo><mml:mn>2</mml:mn></mml:mrow></mml:mrow></mml:msub></mml:math>
</inline-formula> of node <italic>X</italic><sub><italic>i</italic></sub>.</p>
<p>Step 4: These steps are continued until the child node <italic>Z</italic><sub><italic>k</italic></sub> is obtained. From algorithm. 1 the Trusted privilege gets grade&#x2009;&#x003D;&#x2009;2, then, trusted privilege has two nodes such as &#x007B;<italic>z</italic><sub><italic>t</italic></sub>&#x007C;&#x007C;<italic>z</italic><sub><italic>t</italic>&#x002B;1</sub>&#x007D; and returns inhold (<italic>Z</italic><sub><italic>k</italic></sub>), grade (<italic>Z<sub>k</sub></italic>)</p>
<p>Step 5: From algorithm. 1, whether Trusted Privilege (TP) gets grade&#x2009;&#x003D;&#x2009;3, then, TP had three nodes such as &#x007B;<italic>z</italic><sub><italic>t</italic></sub>&#x007C;&#x007C;<italic>z</italic><sub><italic>t</italic>&#x002B;1</sub>&#x007C;&#x007C;<italic>z</italic><sub><italic>t</italic>&#x002B;2</sub>&#x007D; and returns inhold (<italic>Z</italic><sub><italic>k</italic></sub>), grade (<italic>Z</italic><sub><italic>k</italic></sub>).</p>
<p>Re-enc key: Keys are classified as private Re-enc key and master Re-enc keys that are generated for public parameters. R<sub>pi</sub> and R<sub>mi</sub> are the keys that are used for accessing the Data Holder (DH) from Trusted Privilege (TP). Model description algorithm for key generation is described in algorithm 2. User means token value or <italic>h</italic>(<italic>h</italic>(<italic>f</italic>)) function. In each process, a specific user token is uploaded and corresponding key is generated by <inline-formula id="ieqn-5">
<mml:math id="mml-ieqn-5"><mml:mi>r</mml:mi><mml:mi>e</mml:mi><mml:mi>k</mml:mi><mml:mi>e</mml:mi><mml:msub><mml:mi>y</mml:mi><mml:mi>j</mml:mi></mml:msub><mml:mo>=</mml:mo><mml:mi>a</mml:mi><mml:mi>s</mml:mi><mml:mi>p</mml:mi><mml:mi>e</mml:mi><mml:mi>c</mml:mi><mml:msub><mml:mi>t</mml:mi><mml:mrow><mml:msub><mml:mi>u</mml:mi><mml:mi>i</mml:mi></mml:msub></mml:mrow></mml:msub><mml:mo>.</mml:mo><mml:mi>a</mml:mi><mml:mi>s</mml:mi><mml:mi>p</mml:mi><mml:mi>e</mml:mi><mml:mi>c</mml:mi><mml:mi>t</mml:mi><mml:mi>k</mml:mi><mml:mi>e</mml:mi><mml:mi>y</mml:mi></mml:math>
</inline-formula> formula. Each user generates an authorized request. After the request is received, TP checks the node <italic>z</italic><sub><italic>k</italic></sub> for Re enc key. Each grade has unique keys for different TP. User aspect <inline-formula id="ieqn-6">
<mml:math id="mml-ieqn-6"><mml:mi>a</mml:mi><mml:mi>s</mml:mi><mml:mi>p</mml:mi><mml:mi>e</mml:mi><mml:mi>c</mml:mi><mml:msub><mml:mi>t</mml:mi><mml:mrow><mml:msub><mml:mi>u</mml:mi><mml:mi>i</mml:mi></mml:msub></mml:mrow></mml:msub></mml:math>
</inline-formula>is given to Re enc key for key generation. Initially, <inline-formula id="ieqn-7">
<mml:math id="mml-ieqn-7"><mml:mi>a</mml:mi><mml:mi>s</mml:mi><mml:mi>p</mml:mi><mml:mi>e</mml:mi><mml:mi>c</mml:mi><mml:msub><mml:mi>t</mml:mi><mml:mrow><mml:msub><mml:mi>u</mml:mi><mml:mi>i</mml:mi></mml:msub></mml:mrow></mml:msub></mml:math>
</inline-formula> is used instead of Upload or download. <italic>aspectkey</italic> is a constant key generated by each node <italic>z</italic><sub><italic>k</italic></sub>. Constant key and aspect value of user is multiplied and obtained a <italic>rekey</italic><sub><italic>j</italic></sub>.</p>
<fig id="fig-9">
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_22404-fig-9.png"/>
</fig>
</sec>
<sec id="s4_2">
<label>4.2</label>
<title>Security Level</title>
<p>The implementation of the encryption process was developed by two encoding tables, the 14-bit encryption key and number N. This encryption process is more dynamic and depends on the n value. Based on n values, the value in the tables is shifted. Even though the intermediate persons have the access to encoding tables, they can&#x0027;t access the data. First table will move the data continuously until it stops. First table will keep on moving, so it is unbreakable.</p>
<p>After shifting the table values, the data owner changes the plain text into a binary sequence. If the intruder has access, they can decrypt the sequence. It is a secured technique compared with the previous technique. After the conversion, the binary sequence is converted into encryption data using <xref ref-type="table" rid="table-1">Tab. 1</xref>. Finally, the cipher text is obtained using an encryption table, and the original cipher data is obtained using the table. On the receiver side, if the user has the key to access the data, the user can perform the decryption process based on a random number N.</p>
<table-wrap id="table-1"><label>Table 1</label>
<caption>
<title>Final cryptography code</title></caption>
<table><colgroup><col align="left"/><col align="left"/><col align="left"/><col align="left"/>
</colgroup>
<tbody>
<tr>
<td align="left">000000-F</td>
<td align="left">000010-O</td>
<td align="left">000100-c</td>
<td align="left">000110-&#x002B;</td>
</tr>
<tr>
<td align="left">001000-g</td>
<td align="left">001010-t</td>
<td align="left">001100-W</td>
<td align="left">001110-N</td>
</tr>
<tr>
<td align="left">010000-Z</td>
<td align="left">010010-X</td>
<td align="left">010100-y</td>
<td align="left">010110-v</td>
</tr>
<tr>
<td align="left">011000-I</td>
<td align="left">011010-3</td>
<td align="left">011100-6</td>
<td align="left">011110-R</td>
</tr>
<tr>
<td align="left">100000-r</td>
<td align="left">100010-V</td>
<td align="left">100100-G</td>
<td align="left">100110-8</td>
</tr>
<tr>
<td align="left">101000-l</td>
<td align="left">101010-7</td>
<td align="left">101100-0</td>
<td align="left">101110-B</td>
</tr>
<tr>
<td align="left">110000-C</td>
<td align="left">110010-J</td>
<td align="left">110100-u</td>
<td align="left">110110-4</td>
</tr>
<tr>
<td align="left">111000-j</td>
<td align="left">111010-l</td>
<td align="left">111100-z</td>
<td align="left">111110-x</td>
</tr>
<tr>
<td align="left">000001-S</td>
<td align="left">000011-a</td>
<td align="left">000101-P</td>
<td align="left">000111-U</td>
</tr>
<tr>
<td align="left">001001-b</td>
<td align="left">001011-i</td>
<td align="left">001101-k</td>
<td align="left">001111-2</td>
</tr>
<tr>
<td align="left">010001-L</td>
<td align="left">010011-M</td>
<td align="left">010101-5</td>
<td align="left">010111-/</td>
</tr>
<tr>
<td align="left">011001-w</td>
<td align="left">011011-s</td>
<td align="left">011101-T</td>
<td align="left">011111-H</td>
</tr>
<tr>
<td align="left">100001-Q</td>
<td align="left">100011-Y</td>
<td align="left">100101-e</td>
<td align="left">100111-p</td>
</tr>
<tr>
<td align="left">101001-o</td>
<td align="left">101011-h</td>
<td align="left">101101-q</td>
<td align="left">101111-E</td>
</tr>
<tr>
<td align="left">110001-A</td>
<td align="left">110011-D</td>
<td align="left">110101-K</td>
<td align="left">110111-f</td>
</tr>
<tr>
<td align="left">111001-m</td>
<td align="left">111011-n</td>
<td align="left">111101-9</td>
<td align="left">111111-d</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>The proposed methodology uses 14-bit data for encryption before using 14 bits it generates a 7-bit encryption key for data processing. It is derived from the first bit of the encryption key. Further, it improves the proposed technique; hence multi-fold cryptography methodology is accomplished.</p>
<sec id="s4_2_1">
<label>4.2.1</label>
<title>Multi-Fold Encryption</title>
<p>Proposed encryption is a client-based encryption process, hence there is no encryption process in the cloud. The encryption data will be stored in the cloud while the Input is 14 bits of data. The plain text is converted into a binary sequence. When the plaintext is entered into a table, the text values are shuffled. The shuffled 14 bits (input) are generated. If the initial bit is 1, then the odd values are extracted, otherwise even bits are extracted. If the initial bit is 0, the even values of the bits are extracted. After the extraction process, the 7-bit key is an original key, which is processed for further operation. Then XOR operation is performed between 7-bit actual key with plaintext. The XOR-operated bits are divided into several blocks and each block has 7 bits. The position of each bit is calculated. The bits are divided into two halves, left half and right half. These two halves are interchanged and the resulting bit sequence is converted into cipher text characters which are represented in <xref ref-type="table" rid="table-1">Tab. 1</xref>.</p>
<fig id="fig-10">
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_22404-fig-10.png"/>
</fig>
</sec>
<sec id="s4_2_2">
<label>4.2.2</label>
<title>Multi-Fold Decryption</title>
<p>The decryption process is performed on the user side. If the user has access only to decrypt the data, they can access the data alone. For authentication, the Re-enc key is transmitted to the data user. If the user has this key on the client-side, the decryption operation will be performed. The data from the cloud is in the encrypted format, it has to be decrypted. Hence the user must have the Re-enc key, N random number, and access rights. The values in <xref ref-type="table" rid="table-1">Tab. 1</xref> are shuffled according to cipher text, finally, a binary bit sequence is obtained. The obtained binary sequence is further processed to obtain the original text with the help of <xref ref-type="table" rid="table-1">Tab. 1</xref>. Binary sequences from First table is divided into two halves, right half and left half. The two halves are interchanged. Finally, the binary bits are divided into seven blocks. Each block is replaced with 127bits. The resultant binary sequence is XOR with an actual 7-bit key. The binary sequence is processed and the plaintext is retrieved from a binary sequence. Multi-fold Decryption algorithm is shown below,</p>
<fig id="fig-11">
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_22404-fig-11.png"/>
</fig>
</sec>
</sec>
<sec id="s4_3">
<label>4.3</label>
<title>Cloud Storage Level</title>
<p>The cloud storage level has a storage mechanism to store the data in the cloud platform. A Cloud interface is used to upload the data to a cloud storage system. When a user wants to accept the data, the user must have the Re-enc key. With the help of the Re-enc key, data requests from the cloud and encryption will be processed by the security framework. The verification and analysis has been carried out in the following section.</p>
</sec>
</sec>
<sec id="s5">
<label>5</label>
<title>Verification and Analysis</title>
<p>For searching and verification Index I<sub>n</sub>, user token (<italic>&#x03C9;</italic><sub>ui</sub>) is used, while output access rights for decrypt the data. For (1 &#x003C; i &#x003C; n), many users have the right to access, hence i is defined as 1 &#x003C; i &#x003C; n, where n is the last user. If (<inline-formula id="ieqn-11">
<mml:math id="mml-ieqn-11"><mml:msub><mml:mi>&#x03C9;</mml:mi><mml:mrow><mml:mrow><mml:mi mathvariant="normal">u</mml:mi><mml:mi mathvariant="normal">i</mml:mi></mml:mrow></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:msubsup><mml:mi>&#x03C9;</mml:mi><mml:mrow><mml:mrow><mml:mi mathvariant="normal">u</mml:mi><mml:mi mathvariant="normal">i</mml:mi></mml:mrow></mml:mrow><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msubsup></mml:math>
</inline-formula>), the user has access rights, otherwise the user has the right to decline the access request. <xref ref-type="fig" rid="fig-4">Fig. 4</xref> shows the signature-based verification scheme and search methodology.</p>
<fig id="fig-4">
<label>Figure 4</label>
<caption>
<title>Signature-based verification theme and search methodology</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_22404-fig-4.png"/>
</fig>
<p><italic>TP</italic>: The attribute authority (TP) takes input as the security algorithm &#x03B2;, and then it returns the master secret key MSK and the public parameter PK.</p>
<p><italic>Extract</italic>: The AA enters the master secret key MSK, the public parameter PK, and a signing predicate &#x0393; as input, this algorithm outputs the partial signing key p<sub>sk</sub> and the user signing key u<sub>sk</sub>.</p>
<p><italic>Server:</italic> The server takes the partial signing key psk, the public parameter PK as an attribute set S and the message m as input, and returns the partial signature <italic>&#x03B3;</italic>&#x2032; to the signer.</p>
<p><italic>Signer (Data Signer):</italic> This algorithm takes input as the user signing key usk, the partial signature <italic>&#x03B3;</italic>&#x2032;, the attribute set S, the message m and the public parameter PK, and then the signer computes and outputs the signature <inline-formula id="ieqn-12">
<mml:math id="mml-ieqn-12"><mml:mrow><mml:mrow><mml:mo>&#x20AC;</mml:mo></mml:mrow></mml:mrow></mml:math>
</inline-formula>.</p>
<p><italic>Transform:</italic> The veri&#xFB01;er randomly selects the Transferred signature key <italic>t</italic><sub><italic>k</italic></sub>, and inputs the signature &#x03C3; and the public parameter PK. This algorithm outputs the transformed signature <inline-formula id="ieqn-13">
<mml:math id="mml-ieqn-13"><mml:mrow><mml:mover><mml:mrow><mml:mo>&#x20AC;</mml:mo></mml:mrow><mml:mo stretchy="false">&#x005E;</mml:mo></mml:mover></mml:mrow></mml:math>
</inline-formula>.</p>
<p><italic>Server:</italic> This algorithm takes input as the transformed signature <inline-formula id="ieqn-14">
<mml:math id="mml-ieqn-14"><mml:mrow><mml:mrow><mml:mo>&#x20AC;</mml:mo></mml:mrow></mml:mrow></mml:math>
</inline-formula> and the public parameter PK and returns the intermediate signature <inline-formula id="ieqn-15">
<mml:math id="mml-ieqn-15"><mml:mrow><mml:mover><mml:mrow><mml:mo>&#x20AC;</mml:mo></mml:mrow><mml:mo stretchy="false">&#x005E;</mml:mo></mml:mover></mml:mrow></mml:math>
</inline-formula>.</p>
<p><italic>Verifier:</italic> The veri&#xFB01;er takes input as the intermediate signature <inline-formula id="ieqn-16">
<mml:math id="mml-ieqn-16"><mml:mrow><mml:mover><mml:mrow><mml:mo>&#x20AC;</mml:mo></mml:mrow><mml:mo stretchy="false">&#x005E;</mml:mo></mml:mover></mml:mrow></mml:math>
</inline-formula>, the transformation key <italic>t</italic><sub><italic>k</italic></sub> and the public parameter PK, then this algorithm outputs true or false.</p>
<sec id="s5_1">
<label>5.1</label>
<title>Configuration</title>
<p>TP extracts the user signing key and the public parameter (PP) for generating partial signing key and user signing key. A clipping algorithm can be performed to generate partial signing and user signing key. The server takes input as a partial signing key, attribution set, public parameter as input, and produced output as a partial signature. Data user takes partial signature, attribution set, and public parameter and message data as input and produces original signature for verification. Verifier randomly selects the transformation key <italic>t</italic><sub><italic>k</italic></sub>, attribution set and public parameter to generate the transferred signature key. The server takes a transferred signature key, attribution set and public parameter for generating intermediate signature key <inline-formula id="ieqn-17">
<mml:math id="mml-ieqn-17"><mml:mrow><mml:mover><mml:mrow><mml:mo>&#x20AC;</mml:mo></mml:mrow><mml:mo stretchy="false">&#x005E;</mml:mo></mml:mover></mml:mrow></mml:math>
</inline-formula>. Verifier takes the transferred signature key and an intermediate signature key as input and this algorithm returns true or false.</p>
</sec>
<sec id="s5_2">
<label>5.2</label>
<title>Clipping Algorithm</title>
<p>This algorithm is used to generate a partial signing key and user signing key. The algorithm is explained with LSSS structure (D,<italic>&#x03C9;</italic>)<list list-type="simple"><list-item><label>1)</label>
<p>De&#xFB01;ne an LSSS matrix M with size <italic>n</italic><sub><italic>r</italic></sub>&#x2009;&#x00D7;&#x2009;<italic>n</italic><sub><italic>c</italic></sub>. For each row k &#x2208; [1, <italic>n</italic><sub><italic>r</italic></sub>] in M, select a labeling function (k) <italic>&#x03C9;</italic>&#x2208;<italic>V</italic><sub><italic>P</italic></sub>, which corresponding to an attribute in UA.</p></list-item><list-item><label>2)</label>
<p>Vector &#x20D7;v &#x003D; &#x007B;<italic>&#x03C1;</italic><sub>1</sub>, <italic>v</italic><sub>1</sub>, &#x2026;, <italic>v</italic><sub><italic>n</italic></sub>&#x007D;. Compute<inline-formula id="ieqn-18">
<mml:math id="mml-ieqn-18"><mml:mo>,</mml:mo><mml:mspace width="thickmathspace" /><mml:msub><mml:mi>&#x03C6;</mml:mi><mml:mrow><mml:mi>&#x03C9;</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:mi>k</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mover><mml:msub><mml:mi>D</mml:mi><mml:mi>k</mml:mi></mml:msub><mml:mo>&#x2192;</mml:mo></mml:mover><mml:mover><mml:msub><mml:mi>v</mml:mi><mml:mi>t</mml:mi></mml:msub><mml:mo>&#x2192;</mml:mo></mml:mover></mml:math>
</inline-formula> . Where <inline-formula id="ieqn-19">
<mml:math id="mml-ieqn-19"><mml:mrow><mml:mover><mml:mi>D</mml:mi><mml:mo stretchy="false">&#x2192;</mml:mo></mml:mover></mml:mrow></mml:math>
</inline-formula> denotes the k-th row of the matrix D.</p></list-item><list-item><label>3)</label>
<p>TP computes <inline-formula id="ieqn-20">
<mml:math id="mml-ieqn-20"><mml:msub><mml:mi>f</mml:mi><mml:mi>k</mml:mi></mml:msub><mml:mo>=</mml:mo><mml:msup><mml:mi>m</mml:mi><mml:mrow><mml:msub><mml:mi>&#x03C6;</mml:mi><mml:mrow><mml:mi>&#x03C9;</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:mi>k</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:mrow></mml:msub></mml:mrow></mml:msup></mml:math>
</inline-formula></p></list-item></list></p>
<p>Similarly, AA calculates <inline-formula id="ieqn-21">
<mml:math id="mml-ieqn-21"><mml:msub><mml:mi>f</mml:mi><mml:mi>e</mml:mi></mml:msub><mml:mo>=</mml:mo><mml:msup><mml:mi>m</mml:mi><mml:mrow><mml:msub><mml:mi>&#x03C1;</mml:mi><mml:mn>1</mml:mn></mml:msub></mml:mrow></mml:msup><mml:mo stretchy="false">(</mml:mo><mml:mrow><mml:msub><mml:mi>r</mml:mi><mml:mn>0</mml:mn></mml:msub><mml:mo>.</mml:mo><mml:msub><mml:mi>r</mml:mi><mml:mi>e</mml:mi></mml:msub></mml:mrow><mml:msup><mml:mo stretchy="false">)</mml:mo><mml:mrow><mml:msub><mml:mi>x</mml:mi><mml:mi>e</mml:mi></mml:msub></mml:mrow></mml:msup></mml:math>
</inline-formula> and <inline-formula id="ieqn-22">
<mml:math id="mml-ieqn-22"><mml:msubsup><mml:mi>f</mml:mi><mml:mi>e</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msubsup><mml:mo>=</mml:mo><mml:msup><mml:mi>m</mml:mi><mml:mrow><mml:msub><mml:mi>x</mml:mi><mml:mi>e</mml:mi></mml:msub></mml:mrow></mml:msup></mml:math>
</inline-formula>. Hence partial signature key under the server is expressed as PK &#x003D; <inline-formula id="ieqn-23">
<mml:math id="mml-ieqn-23"><mml:mo fence="false" stretchy="false">{</mml:mo><mml:msub><mml:mrow><mml:msub><mml:mi>f</mml:mi><mml:mi>k</mml:mi></mml:msub><mml:mo>,</mml:mo><mml:mspace width="thickmathspace" /><mml:msubsup><mml:mi>f</mml:mi><mml:mi>k</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msubsup><mml:mo>,</mml:mo><mml:mspace width="thickmathspace" /><mml:msubsup><mml:mi>f</mml:mi><mml:mi>k</mml:mi><mml:mrow><mml:msup><mml:mi></mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup></mml:mrow></mml:msubsup><mml:mo fence="false" stretchy="false">}</mml:mo></mml:mrow><mml:mrow><mml:mi>k</mml:mi><mml:mo>&#x2208;</mml:mo><mml:mo stretchy="false">[</mml:mo><mml:mrow><mml:mn>1</mml:mn><mml:mo>,</mml:mo><mml:msub><mml:mi>n</mml:mi><mml:mi>r</mml:mi></mml:msub></mml:mrow><mml:mo stretchy="false">]</mml:mo></mml:mrow></mml:msub></mml:math>
</inline-formula>. For user key UK &#x003D; <inline-formula id="ieqn-24">
<mml:math id="mml-ieqn-24"><mml:mo fence="false" stretchy="false">{</mml:mo><mml:mrow><mml:msub><mml:mi>f</mml:mi><mml:mi>e</mml:mi></mml:msub><mml:mo>,</mml:mo><mml:mspace width="thickmathspace" /><mml:msubsup><mml:mi>f</mml:mi><mml:mi>e</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msubsup><mml:mo fence="false" stretchy="false">}</mml:mo></mml:mrow></mml:math>
</inline-formula>.</p>
<sec id="s5_2_1">
<label>5.2.1</label>
<title>Signing</title>
<p>Partial signature produces with the help of message d, and attribution set S which satisfies (D, <italic>&#x03C9;</italic>). Define K&#x003D;&#x007B;<italic>k</italic>&#x007D;<sub><italic>p</italic>(<italic>k</italic>)&#x2208;<italic>S</italic></sub>, select set of constant <inline-formula id="ieqn-25">
<mml:math id="mml-ieqn-25"><mml:munder><mml:mrow><mml:mo movablelimits="false">&#x2211;</mml:mo></mml:mrow><mml:mrow><mml:mi>k</mml:mi><mml:mo>&#x2208;</mml:mo><mml:mi>K</mml:mi></mml:mrow></mml:munder><mml:mo>&#x2061;</mml:mo><mml:msub><mml:mi>&#x03BC;</mml:mi><mml:mi>k</mml:mi></mml:msub><mml:msub><mml:mi>&#x03C6;</mml:mi><mml:mrow><mml:mi>&#x03C9;</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:mi>k</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mn>1.</mml:mn></mml:math>
</inline-formula></p>
<p>Partial signature after an attribution set S is expressed as<inline-formula id="ieqn-26">
<mml:math id="mml-ieqn-26"><mml:mspace width="thickmathspace" /><mml:msup><mml:mi>&#x03B3;</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msup><mml:mo>=</mml:mo><mml:mo fence="false" stretchy="false">{</mml:mo><mml:mrow><mml:msubsup><mml:mi>&#x03B3;</mml:mi><mml:mn>0</mml:mn><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msubsup><mml:mo>,</mml:mo><mml:mspace width="thickmathspace" /><mml:msubsup><mml:mi>&#x03B3;</mml:mi><mml:mn>1</mml:mn><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msubsup><mml:mo>,</mml:mo><mml:mspace width="thickmathspace" /><mml:msubsup><mml:mi>&#x03B3;</mml:mi><mml:mn>2</mml:mn><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msubsup><mml:mo>,</mml:mo><mml:mspace width="thickmathspace" /><mml:mi>d</mml:mi><mml:mo fence="false" stretchy="false">}</mml:mo></mml:mrow></mml:math>
</inline-formula>.</p>
</sec>
<sec id="s5_2_2">
<label>5.2.2</label>
<title>User Signer</title>
<p>This algorithm is performed after the reception of partial sign from the server, <italic>&#x03B3;</italic>&#x2032;. The signer calculates, <inline-formula id="ieqn-27">
<mml:math id="mml-ieqn-27"><mml:msub><mml:mi>&#x03B3;</mml:mi><mml:mn>0</mml:mn></mml:msub><mml:mo>=</mml:mo><mml:msubsup><mml:mi>&#x03B3;</mml:mi><mml:mn>0</mml:mn><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msubsup><mml:mo>.</mml:mo><mml:msub><mml:mi>f</mml:mi><mml:mi>e</mml:mi></mml:msub><mml:mo>.</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:mrow><mml:msub><mml:mi>r</mml:mi><mml:mi>e</mml:mi></mml:msub><mml:mo>,</mml:mo><mml:mspace width="thickmathspace" /><mml:msub><mml:mi>r</mml:mi><mml:mi>o</mml:mi></mml:msub></mml:mrow><mml:msup><mml:mo stretchy="false">)</mml:mo><mml:mrow><mml:msubsup><mml:mi>x</mml:mi><mml:mi>e</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msubsup></mml:mrow></mml:msup><mml:mo>.</mml:mo><mml:mi>H</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:mi>d</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:math>
</inline-formula>, <inline-formula id="ieqn-28">
<mml:math id="mml-ieqn-28"><mml:msub><mml:mi>&#x03B3;</mml:mi><mml:mn>1</mml:mn></mml:msub><mml:mo>=</mml:mo><mml:msubsup><mml:mi>&#x03B3;</mml:mi><mml:mn>1</mml:mn><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msubsup><mml:mo>.</mml:mo><mml:msup><mml:mi>g</mml:mi><mml:mrow><mml:msubsup><mml:mi>x</mml:mi><mml:mi>e</mml:mi><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msubsup></mml:mrow></mml:msup></mml:math>
</inline-formula> and <inline-formula id="ieqn-29">
<mml:math id="mml-ieqn-29"><mml:msub><mml:mi>&#x03B3;</mml:mi><mml:mn>2</mml:mn></mml:msub><mml:mo>=</mml:mo><mml:msubsup><mml:mi>&#x03B3;</mml:mi><mml:mn>2</mml:mn><mml:mrow><mml:mi mathvariant="normal">&#x2032;</mml:mi></mml:mrow></mml:msubsup><mml:mo>.</mml:mo><mml:mi>g</mml:mi></mml:math>
</inline-formula>.</p>
<p>The signer output the signature such as <italic>&#x03B3;</italic>&#x2009;&#x003D;&#x2009;&#x007B;<italic>&#x03B3;</italic><sub>0</sub>, <italic>&#x03B3;</italic><sub>1</sub>, <italic>&#x03B3;</italic><sub>2</sub>, <italic>d</italic>&#x007D; of message d, with attribution set S.</p>
<p>The signature <italic>&#x03B3;</italic> is converted into the transferred signature.</p>
<p>Randomly select transferred key <inline-formula id="ieqn-300">
<mml:math id="mml-ieqn-300"><mml:mi>t</mml:mi><mml:mi>&#x03B5;</mml:mi><mml:msub><mml:mi>V</mml:mi><mml:mi>p</mml:mi></mml:msub></mml:math>
</inline-formula></p>
<p>Compute <inline-formula id="ieqn-30">
<mml:math id="mml-ieqn-30"><mml:mrow><mml:mover><mml:mrow><mml:msub><mml:mi>&#x03B3;</mml:mi><mml:mn>0</mml:mn></mml:msub></mml:mrow><mml:mo>&#x005E;</mml:mo></mml:mover></mml:mrow><mml:mo>=</mml:mo><mml:msubsup><mml:mi>&#x03B3;</mml:mi><mml:mn>0</mml:mn><mml:mi>t</mml:mi></mml:msubsup></mml:math>
</inline-formula> and <inline-formula id="ieqn-31">
<mml:math id="mml-ieqn-31"><mml:mrow><mml:mover><mml:mrow><mml:msub><mml:mi>&#x03B3;</mml:mi><mml:mn>1</mml:mn></mml:msub></mml:mrow><mml:mo>&#x005E;</mml:mo></mml:mover></mml:mrow><mml:mo>=</mml:mo><mml:msubsup><mml:mi>&#x03B3;</mml:mi><mml:mn>1</mml:mn><mml:mi>t</mml:mi></mml:msubsup></mml:math>
</inline-formula></p>
<p>Transferred signature <inline-formula id="ieqn-32">
<mml:math id="mml-ieqn-32"><mml:mrow><mml:mover><mml:mi>&#x03B3;</mml:mi><mml:mo stretchy="false">&#x005E;</mml:mo></mml:mover></mml:mrow><mml:mo>=</mml:mo><mml:mrow><mml:mo fence="false" stretchy="false">{</mml:mo><mml:mrow><mml:mover><mml:mrow><mml:msub><mml:mi>&#x03B3;</mml:mi><mml:mn>0</mml:mn></mml:msub></mml:mrow><mml:mo>&#x005E;</mml:mo></mml:mover></mml:mrow><mml:mo>,</mml:mo><mml:mspace width="thickmathspace" /><mml:mrow><mml:mover><mml:mrow><mml:msub><mml:mi>&#x03B3;</mml:mi><mml:mn>1</mml:mn></mml:msub></mml:mrow><mml:mo>&#x005E;</mml:mo></mml:mover></mml:mrow><mml:mo>,</mml:mo><mml:mspace width="thickmathspace" /><mml:mi>d</mml:mi><mml:mo fence="false" stretchy="false">}</mml:mo></mml:mrow></mml:math>
</inline-formula></p>
</sec>
</sec>
<sec id="s5_3">
<label>5.2.3</label>
<title>Intermediate Key</title>
<p>This algorithm is designed to delegate the server for heavy computations of veri&#xFB01;cation. The server performs the following computations and obtains the intermediate key &#x02C7;<inline-formula id="ieqn-33">
<mml:math id="mml-ieqn-33"><mml:msub><mml:mi>&#x03B3;</mml:mi><mml:mn>1</mml:mn></mml:msub></mml:math>
</inline-formula><disp-formula id="eqn-1"><label>(1)</label>
<mml:math id="mml-eqn-1" display="block"><mml:mrow><mml:mover><mml:mrow><mml:msub><mml:mi>&#x03B3;</mml:mi><mml:mn>1</mml:mn></mml:msub></mml:mrow><mml:mo>&#x007E;</mml:mo></mml:mover></mml:mrow><mml:mo>=</mml:mo><mml:mstyle displaystyle="true" scriptlevel="0"><mml:mrow><mml:mfrac><mml:mrow><mml:mi>e</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:mrow><mml:mrow><mml:mover><mml:mrow><mml:msub><mml:mi>&#x03B3;</mml:mi><mml:mn>0</mml:mn></mml:msub></mml:mrow><mml:mo>&#x007E;</mml:mo></mml:mover></mml:mrow><mml:mo>,</mml:mo><mml:mspace width="thickmathspace" /><mml:mi>m</mml:mi></mml:mrow><mml:mo stretchy="false">)</mml:mo></mml:mrow><mml:mrow><mml:mi>e</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:mrow><mml:mover><mml:mrow><mml:msub><mml:mi>&#x03B3;</mml:mi><mml:mn>1</mml:mn></mml:msub></mml:mrow><mml:mo>&#x007E;</mml:mo></mml:mover></mml:mrow><mml:mo>,</mml:mo><mml:mtext>&#xA0;</mml:mtext><mml:msub><mml:mi>r</mml:mi><mml:mn>0</mml:mn></mml:msub><mml:msub><mml:mrow><mml:mo movablelimits="false">&#x220F;</mml:mo></mml:mrow><mml:mrow><mml:mi>i</mml:mi><mml:mi>&#x03F5;</mml:mi><mml:mi>S</mml:mi></mml:mrow></mml:msub><mml:mo>&#x2061;</mml:mo><mml:msub><mml:mi>r</mml:mi><mml:mi>i</mml:mi></mml:msub><mml:mo stretchy="false">)</mml:mo></mml:mrow></mml:mfrac></mml:mrow></mml:mstyle></mml:math>
</disp-formula></p>
<sec id="s5_3_1">
<label>5.2.4</label>
<title>Verification</title>
<p>After receiving an intermediate key from the server, the signature verification is processed.</p>
<p>First it checks,<disp-formula id="eqn-2"><label>(2)</label>
<mml:math id="mml-eqn-2" display="block"><mml:mrow><mml:mover><mml:mrow><mml:msub><mml:mi>&#x03B3;</mml:mi><mml:mn>2</mml:mn></mml:msub></mml:mrow><mml:mo>&#x007E;</mml:mo></mml:mover></mml:mrow><mml:mo>=</mml:mo><mml:mi>e</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:mrow><mml:msubsup><mml:mi>&#x03B3;</mml:mi><mml:mn>2</mml:mn><mml:mi>t</mml:mi></mml:msubsup><mml:mo>,</mml:mo><mml:mspace width="thickmathspace" /><mml:mi>H</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:mi>d</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:mrow><mml:mo stretchy="false">)</mml:mo><mml:mo>.</mml:mo><mml:msup><mml:mi>V</mml:mi><mml:mi>t</mml:mi></mml:msup><mml:mo stretchy="false">)</mml:mo></mml:math>
</disp-formula></p>
<p>Check whether the equation <inline-formula id="ieqn-34">
<mml:math id="mml-ieqn-34"><mml:mrow><mml:mover><mml:mrow><mml:msub><mml:mi>&#x03B3;</mml:mi><mml:mn>2</mml:mn></mml:msub></mml:mrow><mml:mo>&#x007E;</mml:mo></mml:mover></mml:mrow><mml:mo>=</mml:mo><mml:mrow><mml:mover><mml:mrow><mml:msub><mml:mi>&#x03B3;</mml:mi><mml:mn>1</mml:mn></mml:msub></mml:mrow><mml:mo>&#x007E;</mml:mo></mml:mover></mml:mrow></mml:math>
</inline-formula></p>
<p>If <inline-formula id="ieqn-35">
<mml:math id="mml-ieqn-35"><mml:mrow><mml:mover><mml:mrow><mml:msub><mml:mi>&#x03B3;</mml:mi><mml:mn>2</mml:mn></mml:msub></mml:mrow><mml:mo>&#x005E;</mml:mo></mml:mover></mml:mrow><mml:mo>=</mml:mo><mml:mrow><mml:mover><mml:mrow><mml:msub><mml:mi>&#x03B3;</mml:mi><mml:mn>1</mml:mn></mml:msub></mml:mrow><mml:mo>&#x005E;</mml:mo></mml:mover></mml:mrow></mml:math>
</inline-formula> then the signature is valid and true otherwise the signature is invalid or false. In this way, the authentication process is accomplished with the SKVS algorithm.</p>
</sec>
</sec>
<sec id="s5_4">
<label>5.3</label>
<title>Analysis of SKVS</title>
<p>For SKVS, two parameters are needed which are the public parameter and master key. The input of the first setup is security parameter &#x03B2; and multiplicative group such as <italic>M</italic>, <italic>M</italic><sub><italic>T</italic></sub> with prime number is taken as output.</p>
<sec id="s5_4_1">
<label>5.3.1</label>
<title>Set Up</title>
<p>Bilinear pairing: <italic>M</italic>&#x2009;&#x00D7;&#x2009;<italic>M</italic>&#x2009;&#x003D;&#x2009;<italic>M</italic><sub><italic>T</italic></sub>. The multiplicative group (M) of integers modulo n is the group under multiplication of the invertible elements. Where <italic>&#x03C1;</italic><sub>1</sub>, <italic>&#x03C1;</italic><sub>2</sub> are the parameter which is used for security purpose.</p>
<fig id="fig-12">
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_22404-fig-12.png"/>
</fig>
<p>Steps:</p>
<p>Step.1. Randomly choose <italic>r</italic><sub>0</sub>, <italic>uA</italic><sub>0</sub>, <italic>uA</italic><sub>1</sub>, &#x2026;, <italic>uA</italic><sub><italic>n</italic></sub> from G and collision resistance has function is defined as H(d) &#x003D; <inline-formula id="ieqn-37">
<mml:math id="mml-ieqn-37"><mml:mi>u</mml:mi><mml:msub><mml:mi>A</mml:mi><mml:mn>0</mml:mn></mml:msub><mml:munderover><mml:mrow><mml:mo movablelimits="false">&#x220F;</mml:mo></mml:mrow><mml:mrow><mml:mi>j</mml:mi><mml:mo>=</mml:mo><mml:mn>1</mml:mn></mml:mrow><mml:mi>n</mml:mi></mml:munderover><mml:mo>&#x2061;</mml:mo><mml:mi>u</mml:mi><mml:msubsup><mml:mi>A</mml:mi><mml:mi>j</mml:mi><mml:mrow><mml:mi>d</mml:mi><mml:mo stretchy="false">[</mml:mo><mml:mi>j</mml:mi><mml:mo stretchy="false">]</mml:mo></mml:mrow></mml:msubsup></mml:math>
</inline-formula>, <italic>d</italic>[<italic>j</italic>] is j th bit of data (d).</p>
<p>Step. 2. Set the attributes set as A &#x003D; &#x007B;1, 2&#x2026; t&#x007D;, for each attribute i &#x2208; A, r &#x2208; M.</p>
<p>Step. 3. Set additional attributes (&#x2126;), attribution set denoted as r &#x2208; &#x2126;.</p>
<p>Step. 4. Randomly select some parameter (<italic>&#x03C1;</italic><sub>1</sub>, <italic>&#x03C1;</italic><sub>2</sub>), M&#x2208;m, and calculate <inline-formula id="ieqn-38">
<mml:math id="mml-ieqn-38"><mml:mi>V</mml:mi><mml:mo>=</mml:mo><mml:mi>e</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:mrow><mml:mi>m</mml:mi><mml:mo>,</mml:mo><mml:mspace width="thickmathspace" /><mml:mi>m</mml:mi></mml:mrow><mml:msup><mml:mo stretchy="false">)</mml:mo><mml:mrow><mml:msub><mml:mi>&#x03C1;</mml:mi><mml:mn>1</mml:mn></mml:msub><mml:mo>+</mml:mo><mml:mspace width="thickmathspace" /><mml:msub><mml:mi>&#x03C1;</mml:mi><mml:mn>2</mml:mn></mml:msub></mml:mrow></mml:msup></mml:math>
</inline-formula></p>
<p>Public parameter &#x003D; &#x007B;<italic>m</italic>, <italic>e</italic>, <italic>M</italic>, <italic>M</italic><sub><italic>T</italic></sub>, <italic>H</italic>, <italic>V</italic>, <italic>r</italic><sub>0</sub>, <italic>u</italic><sub>0</sub>, <italic>u</italic><sub>1</sub>, &#x2026;, <italic>u</italic><sub><italic>n</italic></sub>&#x007D;, where master key is expressed as MK&#x003D;&#x007B;<italic>&#x03C1;</italic><sub>1</sub>, <italic>&#x03C1;</italic><sub>2</sub>&#x007D;.</p>
</sec>
<sec id="s5_4_2">
<label>5.3.2</label>
<title>File Corruption Check</title>
<p>Initialize &#x2013; Start Holder, and Call TPA</p>
<p>Holder &#x2013; file ids and Hash values</p>
<p>TPA &#x2013; Log in Cloud</p>
<p>File id 1: number of files File</p>
<p>Check files id and reference id</p>
<p>If (file id)</p>
<p>H &#x003D; Check file has value</p>
<p>K&#x003D;user given hash value of file</p>
<p>If (H&#x003D;&#x003D;K)</p>
<p>Send (the file is ok)</p>
<p>Else</p>
<p><bold>If (H</bold>&#x2260;K)</p>
<p>Send (File is corrupted)</p>
<p>End</p>
<p>TPA-Next File-User</p>
<p>Section 4 comprises the result and discussion of the proposed methodology.</p>
</sec>
</sec>
</sec>
<sec id="s6">
<label>6</label>
<title>Result and Discussion</title>
<p>In the result section, the proposed methodology is compared with the previous technique based on experimental and theoretical aspects. Computational cost and storage overhead are the parameters that are used to calculate the proposed methodology. We have compared and evaluated symmetric algorithms for different encryption and encoding techniques and came up with the conclusion that the recent encryption techniques utilize more resources such as CPU time, storage, and power. Also, HHS-DNA is a good contender for key encryption. The proposed encryption achieves high security over many attacks and usage of low resources for encryption.</p>
<sec id="s6_1">
<label>6.1</label>
<title>Encryption Time</title>
<p>Encryption time is defined as the time required to convert plaintext into cipher text. The efficiency of the encryption technique is evaluated based on encryption time. If the plaintext size is large, then encryption time will also increase. At the plaintext size of 5Kb, encryption time is increased by 21&#x0025;. At the plaintext size of 30&#x2005;kb, the encryption time will also increase to 56.78&#x0025;. The encryption time calculated using different algorithms is shown in <xref ref-type="fig" rid="fig-5">Fig. 5</xref>.</p>
<fig id="fig-5">
<label>Figure 5</label>
<caption>
<title>Comparison of encryption time with the <italic>vs.</italic> plaintext (Kb)</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_22404-fig-5.png"/>
</fig>
<p>Whenever the number of plaintexts increases, the cipher text will also increase linearly. When compared to the proposed method with BDNA, the cipher text is decreased to 9&#x0025; at 5Kb of plaintext while compared with AES cipher text is reduced to 15.5&#x0025;. When compared to the proposed method with DES, the cipher text is decreased to 7.45&#x0025; at 5Kb of plaintext while compared with DNA cipher text is reduced to 5.5&#x0025;. <xref ref-type="fig" rid="fig-6">Fig. 6</xref> shows the performance of plaintext <italic>vs.</italic> cipher text.</p>
<fig id="fig-6">
<label>Figure 6</label>
<caption>
<title>Cipher text (Kb) <italic>vs.</italic> plain text (Kb)</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_22404-fig-6.png"/>
</fig>
</sec>
<sec id="s6_2">
<label>6.2</label>
<title>Throughput</title>
<p>Based upon the recorded encryption time, the throughput for the proposed and the existing techniques (BDNA, AES, Bf, DES) have been calculated using the formula,<disp-formula id="eqn-3"><label>(3)</label>
<mml:math id="mml-eqn-3" display="block"><mml:mi>T</mml:mi><mml:mi>h</mml:mi><mml:mi>r</mml:mi><mml:mi>o</mml:mi><mml:mi>u</mml:mi><mml:mi>g</mml:mi><mml:mi>h</mml:mi><mml:mi>p</mml:mi><mml:mi>u</mml:mi><mml:mi>t</mml:mi><mml:mo>=</mml:mo><mml:mstyle displaystyle="true" scriptlevel="0"><mml:mrow><mml:mfrac><mml:mrow><mml:mi>P</mml:mi><mml:mi>l</mml:mi><mml:mi>a</mml:mi><mml:mi>i</mml:mi><mml:mi>n</mml:mi><mml:mi>t</mml:mi><mml:mi>e</mml:mi><mml:mi>x</mml:mi><mml:mi>t</mml:mi><mml:mspace width="thickmathspace" /><mml:mi>s</mml:mi><mml:mi>i</mml:mi><mml:mi>z</mml:mi><mml:mi>e</mml:mi></mml:mrow><mml:mrow><mml:mi>E</mml:mi><mml:mi>n</mml:mi><mml:mi>c</mml:mi><mml:mi>r</mml:mi><mml:mi>y</mml:mi><mml:mi>p</mml:mi><mml:mi>t</mml:mi><mml:mi>i</mml:mi><mml:mi>o</mml:mi><mml:mi>n</mml:mi><mml:mspace width="thickmathspace" /><mml:mi>T</mml:mi><mml:mi>i</mml:mi><mml:mi>m</mml:mi><mml:mi>e</mml:mi></mml:mrow></mml:mfrac></mml:mrow></mml:mstyle></mml:math>
</disp-formula></p>
<p>The throughput of HHS-DNA is higher than all the other techniques which are shown in <xref ref-type="fig" rid="fig-7">Fig. 7</xref>. Hence, it can be concluded that the proposed method performs better than other symmetric key algorithms. Higher throughput gives better performance.</p>
<fig id="fig-7">
<label>Figure 7</label>
<caption>
<title>Throughput</title></caption>
<graphic mimetype="image" mime-subtype="png" xlink:href="CSSE_22404-fig-7.png"/>
</fig>
<p>From the above results, it is obvious that the proposed HHS-DNA encryption algorithm outperforms other algorithms. The proposed algorithm has high throughput which indicates that the HHS-DNA has high performance efficiency than the other methods. Likewise, higher throughput symbolizes the reduction of power consumption, since throughput is inversely proportional to power consumption. Besides, the lesser encryption time determines that HHS-DNA&#x2019;s speed in encrypting the given data.</p>
</sec>
</sec>
<sec id="s7">
<label>7</label>
<title>Conclusion</title>
<p>In the proposed approach, a novel and unique Hybrid Helix Scuttle - Deoxyribo nucleic Acids (HHS-DNA) encryption algorithm have been proposed. HHS-DNA encryption reduces the encryption time, cipher text size and improves the throughput. The reduction of time complexity and improved data security is comprehended in the proposed strategy. The simulation contrasts with the proposed algorithm, DNA, and other previous techniques. When compared with previous techniques, there is a 45&#x0025; improvement in throughput, 37&#x0025; in encryption time, 54.67&#x0025; cipher text size. Simulation outputs showed that the proposed HHS-DNA technique is a proficient scheme for encrypting the data in the cloud and improving data security. The relevant experimental results and foregoing analysis show that this method is of good robustness, stability, and security. The performance measures of the proposed scheme are correlated with the prior art techniques and acquired a performance improvement of 0.9&#x0025; to 0.99&#x0025;. Future research will be focused on reducing CPU processing time and CPU workload.</p>
</sec>
</body>
<back>
<ack>
<p>The authors would like to thank Anna University and also we like to thank Anonymous reviewers for their so-called insights.</p>
</ack><fn-group>
<fn fn-type="other">
<p><bold>Funding Statement:</bold> The authors received no specific funding for this study.</p>
</fn>
<fn fn-type="conflict">
<p><bold>Conflicts of Interest:</bold> The authors declare that they have no conflicts of interest to report regarding the present study.</p>
</fn>
</fn-group>
<ref-list content-type="authoryear">
<title>References</title>
<ref id="ref-1"><label>[1]</label><mixed-citation publication-type="conf-proc"><person-group person-group-type="author"><string-name><given-names>J.</given-names> <surname>Xu</surname></string-name>, <string-name><given-names>E. C.</given-names> <surname>Chang</surname></string-name> and <string-name><given-names>J.</given-names> <surname>Zhou</surname></string-name></person-group>, &#x201C;<article-title>Weak leakage-resilient client-side deduplication of encrypted data in cloud storage</article-title>,&#x201D; in <conf-name>Proc. ACM SIGSAC</conf-name>, <publisher-name>IEEE</publisher-name>, <conf-loc>Hangzhou, China</conf-loc>, pp. <fpage>195</fpage>&#x2013;<lpage>206</lpage>, <year>2013</year>.</mixed-citation></ref>
<ref id="ref-2"><label>[2]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>J.</given-names> <surname>Xiong</surname></string-name>, <string-name><given-names>Y.</given-names> <surname>Zhang</surname></string-name>, <string-name><given-names>S.</given-names> <surname>Tang</surname></string-name>, <string-name><given-names>X.</given-names> <surname>Liu</surname></string-name> and <string-name><given-names>Z.</given-names> <surname>Yao</surname></string-name></person-group>, &#x201C;<article-title>Secure encrypted data with authorized deduplication in cloud</article-title>,&#x201D; <source>IEEE Access</source>, vol. <volume>7</volume>, no. <issue>2</issue>, pp. <fpage>75090</fpage>&#x2013;<lpage>75104</lpage>, <year>2019</year>.</mixed-citation></ref>
<ref id="ref-3"><label>[3]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>Z.</given-names> <surname>Yan</surname></string-name>, <string-name><given-names>L.</given-names> <surname>Zhang</surname></string-name>, <string-name><given-names>W.</given-names> <surname>Ding</surname></string-name> and <string-name><given-names>Q.</given-names> <surname>Zheng</surname></string-name></person-group>, &#x201C;<article-title>Heterogeneous data storage management with deduplication in cloud computing</article-title>,&#x201D; <source>IEEE Transactions on Big Data</source>, vol. <volume>5</volume>, no. <issue>3</issue>, pp. <fpage>393</fpage>&#x2013;<lpage>407</lpage>, <year>2019</year>.</mixed-citation></ref>
<ref id="ref-4"><label>[4]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>S.</given-names> <surname>Wang</surname></string-name>, <string-name><given-names>Y.</given-names> <surname>Wang</surname></string-name> and <string-name><given-names>Y.</given-names> <surname>Zhang</surname></string-name></person-group>, &#x201C;<article-title>Block chain-based fair payment protocol for deduplication cloud storage system</article-title>,&#x201D; <source>IEEE Access</source>, vol. <volume>7</volume>, pp. <fpage>127662</fpage>&#x2013;<lpage>127668</lpage>, <year>2019</year>.</mixed-citation></ref>
<ref id="ref-5"><label>[5]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>Y.</given-names> <surname>Zhao</surname></string-name>, <string-name><given-names>Y.</given-names> <surname>Li</surname></string-name>, <string-name><given-names>Q.</given-names> <surname>Mu</surname></string-name>, <string-name><given-names>B.</given-names> <surname>Yang</surname></string-name> and <string-name><given-names>Y.</given-names> <surname>Yu</surname></string-name></person-group>, &#x201C;<article-title>Block chain based fair payment with reputation for reliable cyber physical systems</article-title>,&#x201D; <source>IEEE Access</source>, vol. <volume>6</volume>, no. <issue>8</issue>, pp. <fpage>12295</fpage>&#x2013;<lpage>12303</lpage>, <year>2018</year>.</mixed-citation></ref>
<ref id="ref-6"><label>[6]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>H.</given-names> <surname>Li</surname></string-name>, <string-name><given-names>M.</given-names> <surname>Dong</surname></string-name>, <string-name><given-names>X.</given-names> <surname>Liao</surname></string-name> and <string-name><given-names>H.</given-names> <surname>Jin</surname></string-name></person-group>, &#x201C;<article-title>Deduplication-based energy ef&#xFB01;cient storage system in cloud environment</article-title>,&#x201D; <source>the Computer Journal</source>, vol. <volume>58</volume>, no. <issue>6</issue>, pp. <fpage>1373</fpage>&#x2013;<lpage>1383</lpage>, <year>2015</year>.</mixed-citation></ref>
<ref id="ref-7"><label>[7]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>J.</given-names> <surname>Li</surname></string-name>, <string-name><given-names>J.</given-names> <surname>Li</surname></string-name>, <string-name><given-names>D.</given-names> <surname>Xie</surname></string-name> and <string-name><given-names>Z.</given-names> <surname>Cai</surname></string-name></person-group>, &#x201C;<article-title>Secure auditing and deduplicating data in cloud</article-title>,&#x201D; <source>IEEE Transactions on Computers</source>, vol. <volume>65</volume>, no. <issue>8</issue>, pp. <fpage>2386</fpage>&#x2013;<lpage>2396</lpage>, <year>2015</year>.</mixed-citation></ref>
<ref id="ref-8"><label>[8]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>B.</given-names> <surname>Mao</surname></string-name>, <string-name><given-names>H.</given-names> <surname>Jiang</surname></string-name>, <string-name><given-names>S.</given-names> <surname>Wu</surname></string-name> and <string-name><given-names>L.</given-names> <surname>Tian</surname></string-name></person-group>, &#x201C;<article-title>Leveraging data deduplication to improve the performance of primary storage systems in the cloud</article-title>,&#x201D; <source>IEEE Transactions on Computers</source>, vol. <volume>65</volume>, no. <issue>6</issue>, pp. <fpage>1775</fpage>&#x2013;<lpage>1788</lpage>, <year>2016</year>.</mixed-citation></ref>
<ref id="ref-9"><label>[9]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>J.</given-names> <surname>Hur</surname></string-name>, <string-name><given-names>D.</given-names> <surname>Koo</surname></string-name>, <string-name><given-names>Y.</given-names> <surname>Shin</surname></string-name> and <string-name><given-names>K.</given-names> <surname>Kang</surname></string-name></person-group>, &#x201C;<article-title>Secure data deduplication with dynamic ownership management in cloud storage</article-title>,&#x201D; <source>IEEE Transactions on Knowledge and Data Engineering</source>, vol. <volume>8</volume>, no. <issue>11</issue>, pp. <fpage>3113</fpage>&#x2013;<lpage>3125</lpage>, <year>2016</year>.</mixed-citation></ref>
<ref id="ref-10"><label>[10]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>T.</given-names> <surname>Jiang</surname></string-name>, <string-name><given-names>X.</given-names> <surname>Chen</surname></string-name>, <string-name><given-names>Q.</given-names> <surname>Wu</surname></string-name>, <string-name><given-names>J.</given-names> <surname>Ma</surname></string-name>, <string-name><given-names>W.</given-names> <surname>Susilo</surname></string-name> <etal>et al.</etal></person-group>, &#x201C;<article-title>Secure and ef&#xFB01;cient cloud data deduplication with randomized tag</article-title>,&#x201D; <source>IEEE Transactions on Information Forensics and Security</source>, vol. <volume>12</volume>, no. <issue>3</issue>, pp. <fpage>532</fpage>&#x2013;<lpage>543</lpage>, <year>2016</year>.</mixed-citation></ref>
<ref id="ref-11"><label>[11]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>Y.</given-names> <surname>Wang</surname></string-name>, <string-name><given-names>Q.</given-names> <surname>Han</surname></string-name>, <string-name><given-names>G.</given-names> <surname>Cui</surname></string-name> and <string-name><given-names>J.</given-names> <surname>Sun</surname></string-name></person-group> &#x201C;<article-title>Hiding messages based on DNA sequence and recombinant DNA technique</article-title>,&#x201D; <source>IEEE Transactions on Nanotechnology</source>, vol. <volume>18</volume>, pp. <fpage>299</fpage>&#x2013;<lpage>307</lpage>, <year>2016</year>.</mixed-citation></ref>
<ref id="ref-12"><label>[12]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>M.</given-names> <surname>Sohal</surname></string-name> and <string-name><given-names>S.</given-names> <surname>Sharma</surname></string-name></person-group>, &#x201C;<article-title>Enhancement of cloud security using DNA inspired multifold cryptographic technique</article-title>,&#x201D; <source>International Journal of Security and Its Applications</source>, vol. <volume>11</volume>, pp. <fpage>15</fpage>&#x2013;<lpage>26</lpage>, <year>2017</year>.</mixed-citation></ref>
<ref id="ref-13"><label>[13]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>S.</given-names> <surname>Marwan</surname></string-name>, <string-name><given-names>A.</given-names> <surname>Shawish</surname></string-name> and <string-name><given-names>K.</given-names> <surname>Nagaty</surname></string-name></person-group>, &#x201C;<article-title>DNA-Based cryptographic methods for data hiding in DNA media</article-title>,&#x201D; <source>Biosystems</source>, vol. <volume>150</volume>, pp. <fpage>110</fpage>&#x2013;<lpage>118</lpage>, <year>2019</year>.</mixed-citation></ref>
<ref id="ref-14"><label>[14]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>H.</given-names> <surname>Houa</surname></string-name>, <string-name><given-names>J.</given-names> <surname>Yu</surname></string-name> and <string-name><given-names>R.</given-names> <surname>Hao</surname></string-name></person-group>, &#x201C;<article-title>Cloud storage auditing with deduplication supporting different security levels according to data popularity</article-title>,&#x201D; <source>Journal of Network and Computer Applications</source>, vol. <volume>134</volume>, pp. <fpage>26</fpage>&#x2013;<lpage>39</lpage>, <year>2019</year>.</mixed-citation></ref>
<ref id="ref-15"><label>[15]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>Y.</given-names> <surname>Miaoa</surname></string-name>, <string-name><given-names>J.</given-names> <surname>Maa</surname></string-name>, <string-name><given-names>X.</given-names> <surname>Liub</surname></string-name>, <string-name><given-names>Q.</given-names> <surname>Jianga</surname></string-name>, <string-name><given-names>J.</given-names> <surname>Zhanga</surname></string-name> <etal>et al.</etal></person-group>, &#x201C;<article-title>Verifiable conjunctive keyword search over mobile e-health cloud in shared multi-owner settings</article-title>,&#x201D; <source>Pervasive and Mobile Computing</source>, vol. <volume>40</volume>, pp. <fpage>205</fpage>&#x2013;<lpage>219</lpage>, <year>2017</year>.</mixed-citation></ref>
<ref id="ref-16"><label>[16]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>C. M.</given-names> <surname>Yu</surname></string-name>, <string-name><given-names>S. P.</given-names> <surname>Gochhayat</surname></string-name>, <string-name><given-names>M.</given-names> <surname>Conti</surname></string-name> and <string-name><given-names>C. S.</given-names> <surname>Lu</surname></string-name></person-group>, &#x201C;<article-title>Privacy aware data deduplication for side channel in cloud storage</article-title>,&#x201D; <source>IEEE Transactions on Cloud Computing</source>, vol. <volume>14</volume>, no. <issue>8</issue>, pp. <fpage>1</fpage>&#x2013;<lpage>13</lpage>, <year>2015</year>.</mixed-citation></ref>
<ref id="ref-17"><label>[17]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>M.</given-names> <surname>Sohal</surname></string-name> and <string-name><given-names>S.</given-names> <surname>Sharma</surname></string-name></person-group>, &#x201C;<article-title>BDNA-A DNA inspired symmetric key cryptographic technique to secure cloud computing</article-title>,&#x201D; <source>Journal of King Saud University-Computer and Information Sciences</source>, vol. <volume>7</volume>, no. <issue>1</issue>, pp. <fpage>11</fpage>&#x2013;<lpage>32</lpage>, <year>2018</year>.</mixed-citation></ref>
<ref id="ref-18"><label>[18]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>N.</given-names> <surname>Kaaniche</surname></string-name> and <string-name><given-names>M.</given-names> <surname>Laurent</surname></string-name></person-group>, &#x201C;<article-title>Data security and privacy preservation in cloud storage environments based on cryptographic mechanisms</article-title>,&#x201D; <source>Comupter Communications</source>, vol. <volume>111</volume>, no. <issue>1</issue>, pp. <fpage>120</fpage>&#x2013;<lpage>141</lpage>, <year>2017</year>.</mixed-citation></ref>
<ref id="ref-19"><label>[19]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>K.</given-names> <surname>Sinhaa</surname></string-name>, <string-name><given-names>A.</given-names> <surname>Priyaa</surname></string-name> and <string-name><given-names>P.</given-names> <surname>Paul</surname></string-name></person-group>, &#x201C;<article-title>K-RSA: Secure data storage technique for multimedia in cloud data server</article-title>,&#x201D; <source>Journal of Intelligent &#x0026; Fuzzy Systems</source>, vol. <volume>39</volume>, no. <issue>3</issue>, pp. <fpage>3297</fpage>&#x2013;<lpage>3314</lpage>, <year>2020</year>.</mixed-citation></ref>
<ref id="ref-20"><label>[20]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>S.</given-names> <surname>Namasudra</surname></string-name>, <string-name><given-names>D.</given-names> <surname>Devi</surname></string-name>, <string-name><given-names>S.</given-names> <surname>Kadry</surname></string-name>, <string-name><given-names>R.</given-names> <surname>Sundarasekar</surname></string-name> and <string-name><given-names>A.</given-names> <surname>Shanthini</surname></string-name></person-group>, &#x201C;<article-title>Towards DNA based data security in the cloud computing environment</article-title>,&#x201D; <source>Computer Communications</source>, vol. <volume>151</volume>, no. <issue>1</issue>, pp. <fpage>539</fpage>&#x2013;<lpage>547</lpage>, <year>2020</year>.</mixed-citation></ref>
<ref id="ref-21"><label>[21]</label><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><given-names>R.</given-names> <surname>Wazirali</surname></string-name>, <string-name><given-names>Z.</given-names> <surname>Chaczko</surname></string-name> and <string-name><given-names>L.</given-names> <surname>Carrion</surname></string-name></person-group>, &#x201C;<chapter-title>Bio-informatics with genetic steganography technique</chapter-title>,&#x201D; in <source>Computational Intelligence and Efficiency in Engineering Systems</source>, 1<sup>st</sup> ed., vol. 595, <publisher-name>Springer</publisher-name>, Cham, Studies in Computational Intelligence, pp. <fpage>333</fpage>&#x2013;<lpage>345</lpage>, <year>2015</year>.</mixed-citation></ref>
<ref id="ref-22"><label>[22]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>S.</given-names> <surname>Namasudra</surname></string-name>, <string-name><given-names>P.</given-names> <surname>Roy</surname></string-name>, <string-name><given-names>P.</given-names> <surname>Vijayakumar</surname></string-name>, <string-name><given-names>S.</given-names> <surname>Audithan</surname></string-name> and <string-name><given-names>B.</given-names> <surname>Balusamy</surname></string-name></person-group>, &#x201C;<article-title>Time efficient secure DNA based access control model for cloud computing environment</article-title>,&#x201D; <source>Future Generation Computer Systems</source>, vol. <volume>73</volume>, pp. <fpage>90</fpage>&#x2013;<lpage>105</lpage>, <year>2017</year>.</mixed-citation></ref>
<ref id="ref-23"><label>[23]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>S.</given-names> <surname>Chirakkarottu</surname></string-name> and <string-name><given-names>S.</given-names> <surname>Mathew</surname></string-name></person-group>, &#x201C;<article-title>A novel encryption method for medical images using 2D zaslavski map and DNA cryptography</article-title>,&#x201D; <source>SN Applied Sciences</source>, vol. <volume>2</volume>, no. <issue>1</issue>, pp. <fpage>1</fpage>&#x2013;<lpage>10</lpage>, <year>2020</year>.</mixed-citation></ref>
<ref id="ref-24"><label>[24]</label><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><given-names>J.</given-names> <surname>Balaraju</surname></string-name> and <string-name><given-names>P. P.</given-names> <surname>Rao</surname></string-name></person-group>, &#x201C;<article-title>Investigation and finding a DNA cryptography layer for securing data in hadoop cluster</article-title>,&#x201D; <source>International Journal of Advance Soft Computing Applications</source>, vol. <volume>12</volume>, no. <issue>3</issue>, pp. 55&#x2013;64, <year>2020</year>.</mixed-citation></ref>
<ref id="ref-25"><label>[25]</label><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><given-names>A.</given-names> <surname>Das</surname></string-name>, <string-name><given-names>S. K.</given-names> <surname>Sarma</surname></string-name> and <string-name><given-names>S.</given-names> <surname>Deka</surname></string-name></person-group>, &#x201C;<chapter-title>Data security with DNA cryptography</chapter-title>,&#x201D; in <source>Transactions on Engineering Technologies</source>, 1<sup>st</sup> ed., vol. 3, <publisher-name>Springer</publisher-name>, Singapore, Transactions on Engineering Technologies, pp. <fpage>159</fpage>&#x2013;<lpage>173</lpage>, <year>2021</year>.</mixed-citation></ref>
</ref-list>
</back>
</article>