<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Classical and post-quantum encryption for GDPR ⋆</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Maksim</forename><surname>Iavich</surname></persName>
							<email>miavich@cu.edu.ge</email>
							<affiliation key="aff0">
								<orgName type="institution">Caucasus University</orgName>
								<address>
									<addrLine>1 Paata Saakadze str</addrLine>
									<postCode>0102</postCode>
									<settlement>Tbilisi</settlement>
									<country key="GE">Georgia</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Oksana</forename><surname>Kovalchuk</surname></persName>
							<email>oksana.kovalchuk@gmail.com</email>
							<affiliation key="aff1">
								<orgName type="institution">Sokhumi State University</orgName>
								<address>
									<addrLine>61 Politkovskaya str</addrLine>
									<postCode>0186</postCode>
									<settlement>Tbilisi</settlement>
									<country key="GE">Georgia</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Sergiy</forename><surname>Gnatyuk</surname></persName>
							<email>s.gnatyuk@nau.edu.ua</email>
							<affiliation key="aff2">
								<orgName type="institution">National Aviation University</orgName>
								<address>
									<addrLine>1 Liubomyra Huzara ave</addrLine>
									<postCode>03058</postCode>
									<settlement>Kyiv</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Yuliia</forename><surname>Khavikova</surname></persName>
							<affiliation key="aff3">
								<orgName type="institution">State University of Trade and Economics</orgName>
								<address>
									<addrLine>19 Kyoto str</addrLine>
									<postCode>02156</postCode>
									<settlement>Kyiv</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Volodymyr</forename><surname>Sokolov</surname></persName>
							<email>v.sokolov@kubg.edu.ua</email>
							<affiliation key="aff4">
								<orgName type="institution">Borys Grinchenko Kyiv Metropolitan University</orgName>
								<address>
									<addrLine>18/2, Bulvarno-Kudriavska str</addrLine>
									<postCode>04053</postCode>
									<settlement>Kyiv</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Classical and post-quantum encryption for GDPR ⋆</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">761BE86AA75ED1BEEDB9B7B6269884A6</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2025-04-23T19:06+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>GDPR</term>
					<term>AES-256</term>
					<term>encryption</term>
					<term>post-quantum cryptography</term>
					<term>cryptographical application1</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>In the dynamic digital landscape, the General Data Protection Regulation (GDPR) stands as a transformative force, which aims to secure individual privacy and redefine organizational practices in personal data handling. This paper analyzes the multifaceted layers of GDPR in detail, it elucidates its principles, rights for data subjects, and obligations for data controllers and processors. The main attention is paid to encryption standards, with specific recommendations for data protection in both classical and postquantum epochs. In the classical setting, the paper aims to employ AES-128 in data storage, striking a balance between security and performance. For communication, the SSL protocol is used, with a caveat to transition to TLS for contemporary applications. In the post-quantum epoch, where there will be fullyfledged quantum computers, the paper proposes a shift to AES-256 for data storage and introduces CRYSTALS-Kyber, an asymmetric cryptography algorithm secure against quantum attacks, for secure communication. The recommendations emphasize the need for creating precise cryptographical recommendations, particularly in the face of evolving threats. Compliance with GDPR and other data protection regulations remains very important, ensuring the security and integrity of data in the 21 st century.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Introduction</head><p>Because of the rapid evolution of digital technologies, the security of data has become very important <ref type="bibr" target="#b0">[1,</ref><ref type="bibr" target="#b1">2]</ref>. As people have to share their personal information online, concerns about data privacy and security have become impor-tant. In response to these concerns, the Euro-pean Union (EU) has elaborated the General Data Protection Regulation (GDPR), a land-mark legislation designed to secure the rights and privacy of individuals in the digital realm.</p><p>The GDPR, which came into effect on May 25, 2018, represents a paradigm shift in data protection, emphasizing transparency, accountability, and individual empowerment. Its main goal is to provide individuals with greater control over their data while imposing strict rules on organizations that process such information. Because of the importance of GDPR, this paper aims to analyze the regulatory framework, exploring its fundamental principles, the rights it affords to data subjects and the obligations it places upon data controllers and processors <ref type="bibr" target="#b2">[3]</ref><ref type="bibr" target="#b3">[4]</ref><ref type="bibr" target="#b4">[5]</ref>.</p><p>As we study GDPR, it becomes evident that this regulation is not a legal framework but a catalyst for an important organizational shift towards a more privacyoriented approach. By understanding the nuances and implications of the GDPR, businesses, policymakers, and individuals can actively contribute to the responsible and ethical use of personal data in the digital era <ref type="bibr" target="#b5">[6]</ref><ref type="bibr" target="#b6">[7]</ref><ref type="bibr" target="#b7">[8]</ref>.</p><p>This paper studies the multifaceted layers of the GDPR, providing a comprehensive of these layers. Through this exploration, we aim to foster a deeper understanding of the GDPR's significance, its impact on various stakeholders, and the evolving landscape of data protection in the 21 st century. The main aim of the paper is to analyze the encryption standards for data protection. Based on the analysis the goal of the paper is to offer a detailed recommendation for data encryption in ongoing and post-quantum epochs.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">GDPR layers</head><p>Let's mention analyze the various layers of the GDPR and their implications: 0000-0002-3109-7971 (M. Iavich); 0000-0002-2354-6545 (O. Kovalchuk); 0000-0003-4992-0564 (S. Gnatyuk); 0000-0003-1017-3602 (Y. Khavikova); 0000-0002-9349-7946 (V. Sokolov)</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.1.">Principles</head><p>Lawfulness, Fairness, and Transparency: This principle ensures that organizations process personal data legally and transparently. It emphasizes the importance of informing individuals about the processing activities and the reasons behind them, fostering trust and accountability.</p><p>Purpose Limitation and Data Minimization: These principles emphasize the need for organizations to clearly define the purposes for which they collect data and to collect only the minimum necessary data for those purposes. This helps prevent the indiscriminate collection and processing of personal information.</p><p>Accuracy and Storage Limitation: These principles highlight the importance of maintaining accurate and up-to-date data and ensuring that personal data is not stored longer than necessary. This promotes data quality and relevance.</p><p>Integrity and Confidentiality: Organizations must implement security measures to protect personal data from unauthorized access, disclosure, alteration, and destruction, ensuring the integrity and confidentiality of the data.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.2.">Data subject rights</head><p>The recognition of robust data subject rights empowers individuals to have control over their data. This includes the right to access their information, rectify inaccuracies, and even request the deletion of their data under certain circumstances. These rights enhance individual autonomy and privacy.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.3.">3. Lawful basis for processing</head><p>Requiring a lawful basis for processing ensures that organizations have a legitimate reason for collecting and processing personal data. This prevents arbitrary or unjustified processing and encourages responsible data management.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.4.">Consent</head><p>The GDPR introduces a higher standard for obtaining and managing consent. It ensures that individuals are fully informed and have given clear affirmative action, fostering a more transparent and ethically grounded approach to data processing.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.5.">Data protection officer</head><p>The appointment of a Data Protection Officer (DPO) is a proactive step toward ensuring that organizations have a designated person responsible for overseeing data protection compliance. This demonstrates a commitment to accountability and effective governance.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.6.">Data processing records</head><p>Maintaining records of data processing activities promotes transparency and accountability. It helps organizations keep track of their data processing practices and facilitates cooperation with data protection authorities during audits.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.7.">Data protection impact assessments</head><p>Data Protection Impact Assessments (DPIAs) are a proactive tool for identifying and mitigating potential risks associated with data processing activities. This encourages organizations to assess and address privacy risks before initiating certain processing operations, aligning with a risk-based approach to data protection.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.8.">Cross-border data transfers</head><p>The restrictions on cross-border data transfers ensure that personal data leaving the EU enjoys an adequate level of protection. This protects the privacy rights of individuals, even when their data is transferred internationally.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.9.">Data breach notification</head><p>The mandatory reporting of data breaches within 72 hours enhances transparency and enables swift action to mitigate potential harm. This requirement emphasizes the importance of timely and effective responses to security incidents.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.10.">Accountability and governance</head><p>The principles of accountability and governance require organizations to take responsibility for their data processing activities. This involves adopting internal policies, conducting training, and maintaining documentation, fostering a culture of compliance and transparency.</p><p>As we can see, the layers of GDPR collectively create an interesting and important framework that prioritizes the rights and privacy of individuals, fosters transparency, and promotes responsible data governance across organizations. Compliance with these layers not only ensures legal adherence but also contributes to a more ethical and trustworthy data ecosystem.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Encryption in GDPR</head><p>The GDPR does not explicitly mandate the use of specific security technologies like data encryption. However, GDPR does require organizations to implement appropriate technical and organizational measures to ensure a level of security appropriate to the risk. Encryption is recognized as one of the security measures that can help protect personal data, and it is explicitly mentioned in several articles of the regulation. Here are the four most relevant aspects of GDPR related to data encryption:</p><p>1. Security of Processing (Article 32): Article 32 of the GDPR outlines the security of processing requirements. It states that controllers and processors must implement appropriate technical and organizational measures to ensure a level of security appropriate to the risk. This includes the pseudonymization and encryption of personal data.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Pseudonymization (Recital 78):</head><p>Recital 78 of the GDPR specifically mentions pseudonymization as a security measure. Pseudonymization is a process that involves replacing or encrypting personal data in a way that prevents attributing it to a specific data subject without additional information.</p><p>3. Notification of a Personal Data Breach to the Supervisory Authority (Article 33):</p><p>In the event of a personal data breach, Article 33 requires the data controller to notify the supervisory authority without undue delay, unless the breach is unlikely to result in a risk to the rights and freedoms of individuals. Encryption is mentioned as a measure to mitigate the risks associated with a data breach.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Communication of a Personal Data Breach to the Data Subject (Article 34):</head><p>Article 34 states that, in certain cases, the data controller is required to communicate the personal data breach to the data subject without undue delay. However, this communication is not necessary if the data is unintelligible due to encryption or other security measures.</p><p>In summary, while GDPR doesn't explicitly mandate data encryption, it strongly encourages its use as part of a broader set of security measures. The implementation of encryption, especially when combined with other security practices like pseudo-nymization, helps organizations meet the GDPR's requirements for securing personal data and mitigating the risks associated with data breaches. Organizations should assess the risks associated with their data processing activities and implement security measures, including encryption, based on the principle of proportionality.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Problem statement and solution</head><p>As we can see GDPR does not explicitly mandate data encryption. Without the recommendation of concrete encryption standards, it is complicated for organizations to choose the needed standards. It can lead to security breaches. For the local data storage, we can use symmetric encryption.</p><p>AES, which stands for Advanced Encryption Standard, is a widely used symmetric encryption algorithm that plays a crucial role in securing data, including its storage. AES was established as a standard by the National Institute of Standards and Technology (NIST) in 2001, replacing the Data Encryption Standard (DES). AES is known for its efficiency, security, and versatility, making it a popular choice for encrypting sensitive information.</p><p>Here are key aspects of using AES as a method for storing data <ref type="bibr" target="#b8">[9]</ref>:</p><p>AES is a symmetric encryption algorithm, meaning the same key is used for both encryption and decryption. This simplicity in key management makes AES efficient for storing and retrieving encrypted data. AES supports key lengths of 128, 192, and 256 bits. Longer key lengths generally provide stronger security, but they may require more computational resources. The choice of key length depends on the desired level of security and the specific implementation.</p><p>AES operates as a block cipher, encrypting data in fixed-size blocks. The standard block size for AES is 128 bits. Each block undergoes multiple rounds of encryption and transformation, contributing to the algorithm's security.</p><p>AES can be used in various modes of operation, such as Electronic Codebook (ECB), Cipher Block Chaining (CBC), Counter (CTR), and others. The mode of operation determines how the algorithm encrypts data blocks and adds a layer of complexity and security.</p><p>The cryptosystem is commonly employed for dataat-rest encryption, securing data stored on devices such as hard drives, SSDs, and other storage media. Encrypting data at rest helps protect sensitive information from unauthorized access, especially in the event of physical theft or data breaches.</p><p>AES is often used to meet various security and compliance standards, including those related to data protection and privacy. Its acceptance as a secure encryption algorithm by international organizations and regulatory bodies makes it a suitable choice for organizations handling sensitive data.</p><p>AES encryption can be also integrated into various storage systems, including databases and file systems. This integration allows organizations to encrypt data at the storage level, providing an additional layer of protection beyond application-level encryption.</p><p>The cryptosystem is designed to be computationally efficient, but the performance impact of encryption can vary based on factors such as key length, mode of operation, and the hardware used. Modern processors often include hardware acceleration for AES, optimizing performance.</p><p>IT must be mentioned, that effective key management is crucial when using AES. Safeguarding encryption keys is essential to maintaining the security of encrypted data. Organizations should implement secure key storage and distribution practices.</p><p>Choosing Advanced Encryption Standard (AES) for GDPR Compliance in the realm of General Data Protection Regulation (GDPR) compliance, the selection of a robust encryption standard is obligatory for securing personal data. As we mentioned above it stands out as a highly secure and good choice that aligns with GDPR principles. AES, a symmetric encryption algorithm, has earned its reputation for security through rigorous cryptographic analysis. Its implementation provides sufficient protection for sensitive information, addressing the GDPR's mandate for robust data protection. Especially well-suited for encrypting stored information, AES's symmetric nature ensures efficient and effective encryption, meeting GDPR's emphasis on securing data at rest. This approach guarantees that personal data remains confidential and protected from unauthorized access. The cryptosystem aligns seamlessly with GDPR principles, including data minimization, integrity, and confidentiality. By employing AES for data encryption, organizations adhere to GDPR's mandate to store and manage only necessary information while maintaining data integrity and confidentiality through encryption. In the unfortunate event of a data breach, GDPR necessitates prompt notification to the supervisory authority and, in certain cases, to data subjects. The cryptosystem plays an important role in breach mitigation by rendering the encrypted data unreadable without the proper decryption key, reducing the risk of harm to individuals. GDPR encourages the use of pseudonymization as an additional security measure. AES, integrated into a broader pseudonymization strategy, adds an extra layer of complexity, making it challenging to associate encrypted data with specific individuals without the requisite decryption keys. Widely adopted across industries, AES's versatility allows for seamless integration into various systems, databases, and storage solutions. Its international recognition contributes to a consistent and effective approach to data encryption, aligning with GDPR's emphasis on protecting personal data regardless of geographical boundaries.</p><p>Therefore, selecting AES as the encryption standard for GDPR compliance reflects a commitment to the secure processing and storage of personal data. While encryption is a crucial aspect of GDPR compliance, organizations should adopt a holistic approach, considering additional technical and organizational measures to ensure comprehensive data protection. The key size can be chosen as a 128-bit length.</p><p>For communication encryption, we offer to use asymmetric encryption. Using SSL (Secure Sockets Layer) or its successor, TLS (Transport Layer Security), for data transfer is a common and recommended practice to ensure the secure transmission of data, and it aligns well with GDPR requirements for protecting personal data during transit <ref type="bibr" target="#b9">[10]</ref>. Here's an overview of how SSL/TLS can be considered as an encryption standard for GDPR compliance: SSL/TLS protocols are designed to provide a secure channel for data transmission over the internet. This is achieved through encryption, which protects the confidentiality and integrity of the data being transferred between a user's browser and a web server. GDPR emphasizes the principles of data protection, including the need to process personal data securely. Using SSL/TLS for data transfer helps organizations comply with these principles by ensuring that sensitive information is encrypted during transmission, preventing unauthorized access or interception.</p><p>SSL/TLS protocols use strong encryption algorithms to secure data. The choice of encryption algorithms and key lengths in the configuration of SSL/TLS can be aligned with GDPR's emphasis on adopting appropriate technical measures to protect personal data.</p><p>GDPR grants individuals the right to have their data processed securely. By implementing SSL/TLS, organizations contribute to the protection of data subject rights, especially during data transfer processes where the risk of interception is higher.</p><p>SSL/TLS contributes to secure communication between data subjects and data controllers. When obtaining consent or communicating with individuals regarding their data, the use of encrypted channels helps maintain the confidentiality and integrity of the information exchanged.</p><p>The protocol not only encrypts data but also provides a mechanism for server authentication. Verifying the identity of the server helps prevent manin-the-middle attacks, ensuring that data is transmitted to and from legitimate sources.</p><p>In the event of a personal data breach, GDPR mandates timely notification. The use of SSL/TLS can mitigate the risk of data breaches during transmission, reducing the likelihood of unauthorized access and the need for such notifications.</p><p>The protocol is considered a standard and best practice for securing data in transit. Its widespread adoption across the internet and acceptance as a secure communication protocol contribute to its alignment with industry standards, reinforcing its suitability for GDPR compliance.</p><p>It's important to note that while SSL/TLS is crucial for securing data in transit, a comprehensive GDPR compliance strategy should encompass other security measures, including encryption at rest, access controls, and secure data processing practices. Additionally, organizations should stay informed about evolving encryption standards and vulnerabilities to ensure the ongoing effectiveness of their security measures.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Secure encryption under GDPR</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.1.">Encryption as a security measure</head><p>Article 32 of the GDPR explicitly mentions encryption as a security measure that organizations should consider to protect personal data. Encryption helps ensure the confidentiality, integrity, and availability of data by making it unreadable to unauthorized parties.</p><p>While encryption is not mandatory, it is strongly recommended, especially for protecting sensitive data. The GDPR promotes a risk-based approach, where encryption is one of the methods to mitigate risks to personal data.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.2.">Data breach notification</head><p>Under Article 34, if a data breach occurs and the personal data is encrypted, the breach is less likely to pose a high risk to the rights and freedoms of individuals. As a result, if the data is properly encrypted, organizations might not need to notify the affected individuals, provided the encryption is robust and the decryption key has not been compromised.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.3.">Data protection by design and by default</head><p>Article 25 encourages organizations to implement appropriate technical and organizational measures, such as encryption, from the outset of data processing activities. This concept, known as "data protection by design and by default", aims to integrate privacy features directly into the processing systems and services.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.4.">Pseudonymization</head><p>Encryption is often used as a tool for pseudonymization, a process mentioned in GDPR that reduces the risks to data subjects. Pseudonymization involves processing personal data in such a manner that it cannot be attributed to a specific individual without additional information, which must be kept separately and securely.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.5.">Impact on data processing</head><p>When data is encrypted, it may affect how it can be processed. For instance, encrypted data typically cannot be searched or analyzed in its encrypted form, which may necessitate the development of secure and efficient decryption processes within an organization.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.">Solution for post-quantum epoch</head><p>Grover's algorithm is a quantum algorithm that addresses the problem of unstructured search, and it has implications for symmetric-key cryptography, including algorithms like AES. Grover's algorithm offers a quadratic speedup for unstructured search problems <ref type="bibr" target="#b10">[11]</ref>.</p><p>In the context of symmetric-key cryptography, Grover's algorithm can be used to search an unsorted database or find the key for a symmetric encryption algorithm. Grover's algorithm implies that the time complexity of a brute-force search is reduced from O(2 n ) to O(2 n/2 ), where "n" is the key length. This means that the security strength provided by a key length of "n" bits against a brute-force search is halved when subjected to Grover's algorithm.</p><p>For example, if you have a symmetric key with a length of 128 bits, classically it would take an exhaustive search of 2 128 operations to find the key. With Grover's algorithm, the time complexity is reduced to the square root of 2 128 , which is 2 64 operations. Therefore, the effective security strength is reduced to 64 bits against a quantum search. To maintain a certain level of security against quantum attacks, it's generally recommended to use longer key lengths with symmetric key algorithms. For instance, if you were aiming for 128-bit security against a quantum attack, you might use a key length of 256 bits with a symmetric algorithm like AES.</p><p>Therefore, we offer to use the key length of 256 bits for AES to securely store data.</p><p>For communication asymmetric cryptography must be involved. Quantum computers can break the existing asymmetric cryptography using Shor's algorithm <ref type="bibr" target="#b11">[12]</ref>.</p><p>Shor's algorithm is a quantum algorithm designed to efficiently factorize large numbers and compute discrete logarithms, which poses a significant risk to widely used encryption methods like RSA and ECC. In particular, RSA's security, dependent on the difficulty of factoring large numbers, and ECC, relying on the elliptic curve discrete logarithm problem, are compromised by Shor's algorithm on a sufficiently powerful quantum computer <ref type="bibr" target="#b12">[13,</ref><ref type="bibr" target="#b13">14]</ref>.</p><p>On a different front, Grover's algorithm, a quantum search algorithm, has implications for symmetric encryption and impacts the effective key length. While not directly breaking public-key cryptography, Grover's algorithm provides a quadratic speedup for unstructured search problems, effectively halving the security provided by symmetric encryption key lengths. This prompts the need for longer key lengths in symmetric encryption to maintain equivalent security levels in the face of quantum threats <ref type="bibr" target="#b14">[15]</ref><ref type="bibr" target="#b15">[16]</ref><ref type="bibr" target="#b16">[17]</ref>.</p><p>To counter these quantum risks, ongoing efforts in postquantum cryptography are focused on developing encryption algorithms resistant to quantum attacks. Researchers are exploring alternative mathematical problems and cryptographic techniques to ensure the continued security of digital communication in a quantum computing era.</p><p>Therefore, for asymmetric encryption, we offer to use already existing NIST standards. GAITHERSBURG, Md.-The National Institute of Standards and Technology (NIST), part of the U.S. Department of Commerce, has taken a significant step in addressing the potential threat posed by future quantum computers to digital security. NIST has unveiled the initial group of encryption tools designed to withstand quantum computer attacks, which could jeopardize the privacy of information crucial to daily digital activities such as online banking and email communication. These selected encryption algorithms are anticipated to be part of NIST's forthcoming post-quantum cryptographic standard, expected to be finalized within approximately two years.</p><p>Gina M. Raimondo, the Secretary of Commerce, emphasized the importance of this announcement as a milestone in fortifying sensitive data against potential cyber threats from quantum computers. NIST has played a crucial role in managing a six-year effort that began in 2016, urging cryptographers globally to create and vet encryption methods capable of resisting attacks from more powerful quantum computers. The unveiling of these encryption algorithms marks a pivotal stage in NIST's post-quantum cryptography <ref type="bibr" target="#b17">[18]</ref> standardization project.</p><p>Under Secretary of Commerce for Standards and Technology and NIST Director Laurie E. Locascio highlighted NIST's forward-looking approach to anticipate the needs of U.S. industry and society. The agency's post-quantum cryptography program, drawing on top cryptography experts worldwide, has produced the first set of quantum-resistant algorithms aimed at establishing a standard to significantly enhance digital information security. This initial selection includes four encryption algorithms designed to resist quantum attacks. Four additional algorithms are currently under consideration, with the finalists expected to be announced in the future. The decision to reveal choices in two stages is driven by the necessity for a diverse range of defense tools. Different systems and tasks utilizing encryption demand tailored solutions, diverse approaches, and multiple algorithms to address potential vulnerabilities.</p><p>It must be mentioned that encryption is a fundamental mechanism that employs mathematical principles to safeguard electronic information and faces a potential challenge from quantum computers. Unlike conventional computers, quantum computers could rapidly solve math problems currently deemed intractable, rendering existing encryption systems vulnerable. The selected quantum-resistant algorithms, designed for general encryption and digital signatures, rely on math problems that both conventional and quantum computers should find challenging to solve. The chosen algorithm for general encryption is CRYSTALS-Kyber, recognized for its smaller encryption keys facilitating easy exchange between parties and operational speed <ref type="bibr" target="#b18">[19]</ref><ref type="bibr" target="#b19">[20]</ref><ref type="bibr" target="#b20">[21]</ref><ref type="bibr" target="#b21">[22]</ref><ref type="bibr" target="#b22">[23]</ref><ref type="bibr" target="#b23">[24]</ref>.</p><p>Therefore, we offer to use CRYSTALS-Kyber as asymmetric encryption.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="7.">Final recommendations for NIST encryption standards</head><p>Classical setting:</p><p>1. Data Storage (AES-128):</p><p>Using AES-128 for data storage is a common and secure practice. It provides a good balance between security and performance in most scenarios.</p><p>2. Communication (SSL Protocol): SSL (Secure Sockets Layer) has been widely used for securing communication over the internet. Note that the latest version of SSL is TLS (Transport Layer Security), and it's recommended to use TLS instead for modern applications <ref type="bibr" target="#b23">[24]</ref><ref type="bibr" target="#b24">[25]</ref><ref type="bibr" target="#b25">[26]</ref>.</p><p>Post-Quantum Epoch: Data Storage (AES-256):</p><p>In a post-quantum epoch, where quantum computers may pose a threat to certain cryptographic algorithms, it's prudent to use a higher key size for encryption. AES-256 provides stronger security compared to AES-128 and is considered more resilient to potential quantum attacks.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Communication (Asymmetric Cryptography-CRYSTALS-Kyber):</head><p>In a post-quantum era, asymmetric algorithms may become vulnerable to attacks by quantum computers. As a result, using asymmetric cryptography that is considered quantum-resistant becomes essential. CRYSTALS-Kyber is a post-quantum key exchange algorithm, and choosing it for communication aligns with the goal of future-proofing against quantum threats.</p><p>It's important to stay informed about the latest developments in cryptography and regularly update cryptographic protocols and algorithms to maintain the security of data in changing threat landscapes. Additionally, compliance with relevant data protection regulations, such as GDPR, should always be considered in cryptographic decisions <ref type="bibr" target="#b26">[27]</ref><ref type="bibr" target="#b27">[28]</ref><ref type="bibr" target="#b28">[29]</ref><ref type="bibr" target="#b29">[30]</ref>.</p><p>The pseudo-code for the usage of the offered technologies can look as follows: </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="8.">Conclusions and future plans</head><p>Cryptography is an essential tool for GDPR compliance, providing the means to protect personal data effectively. By implementing strong cryptographic measures, organizations can significantly reduce the risk of data breaches and ensure that they meet the stringent requirements of the GDPR. The best practices for Using Cryptography under GDPR are the following:</p><p> Key Management: Proper management of encryption keys is critical to ensuring that encrypted data remains secure. Keys must be stored and managed securely to prevent unauthorized access.  Regular Audits and Updates: Cryptographic algorithms and their implementations should be regularly audited and updated to protect against emerging threats.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head></head><p>Compliance with Standards: Use cryptographic methods that comply with recognized standards, such as those from the NIST or the European Telecommunications Standards Institute (ETSI).</p><p>In conclusion, our cryptographic recommendations aim to establish a robust and adaptable security foundation for our system. For data storage in the classical epoch, we offer to use of AES-128, a widely recognized and efficient symmetric encryption algorithm. This choice strikes a balance between security and computational efficiency, making it suitable for protecting stored data in various scenarios.</p><p>For secure communication, we recommend the use of SSL/TLS protocols, incorporating modern cipher suites such as those based on AES in combination with RSA or ECC for key exchange. SSL ensures the confidentiality and integrity of data during transmission, and our approach aligns with current best practices for secure communication.</p><p>In anticipation of future challenges posed by quantum computing, our transition to post-quantum algorithms is exemplified by the adoption of CRYSTALS-Kyber for secure communication. This step reflects our commitment to staying ahead of emerging threats and safeguarding sensitive information.</p><p>In our future research, we think of offering the postquantum model for SSL.</p></div>		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgment</head><p>This work was funded by the Shota Rustaveli National Foundation of Georgia (SRNSFG) (NFR-22-14060).</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Assessing Approaches of IT Infrastructure Audit</title>
		<author>
			<persName><forename type="first">F</forename><surname>Kipchuk</surname></persName>
		</author>
		<idno type="DOI">10.1109/picst54195.2021.9772181</idno>
	</analytic>
	<monogr>
		<title level="m">IEEE 8th International Conference on Problems of Infocommunications</title>
				<imprint>
			<date type="published" when="2021">2021</date>
			<biblScope unit="page" from="213" to="217" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Security Rating Metrics for Distributed Wireless Systems</title>
		<author>
			<persName><forename type="first">V</forename><surname>Buriachok</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Sokolov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Skladannyi</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">8th International Conference on &quot;Mathematics. Informa-tion Technologies. Education</title>
				<imprint>
			<date type="published" when="2019">2019</date>
			<biblScope unit="volume">2386</biblScope>
			<biblScope unit="page" from="222" to="233" />
		</imprint>
	</monogr>
	<note>Modern Machine Learning Technologies and Data Science</note>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Protecting Objects of Critical Information Infrastructure from Wartime Cyber Attacks by Decentralizing the Telecommunications Network</title>
		<author>
			<persName><forename type="first">P</forename><surname>Anakhov</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Cybersecurity Providing in Information and Telecommunication Systems</title>
		<imprint>
			<biblScope unit="volume">3550</biblScope>
			<biblScope unit="page" from="240" to="245" />
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Increasing the Functional Network Stability in the Depression Zone of the Hydroelectric Power Station Reservoir</title>
		<author>
			<persName><forename type="first">P</forename><surname>Anakhov</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Emerging Technology Trends on the Smart Industry and the Internet of Things</title>
		<imprint>
			<biblScope unit="volume">3149</biblScope>
			<biblScope unit="page" from="169" to="176" />
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Formation of Dependability and Cyber Protection Model in Information Systems of Situational Center</title>
		<author>
			<persName><forename type="first">V</forename><surname>Grechaninov</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Emerging Technology Trends on the Smart Industry and the Internet of Things</title>
				<imprint>
			<date type="published" when="2022">2022</date>
			<biblScope unit="volume">3149</biblScope>
			<biblScope unit="page" from="107" to="117" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">The Impact of GDPR on Global Technology Development</title>
		<author>
			<persName><forename type="first">H</forename><surname>Li</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Yu</forename><forename type="middle">L</forename></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Wu</surname></persName>
		</author>
		<idno type="DOI">10.1080/1097198X.2019.1569186</idno>
	</analytic>
	<monogr>
		<title level="j">J. Global Inf. Technol. Manag</title>
		<imprint>
			<biblScope unit="volume">22</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="1" to="6" />
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">What the GDPR Means for Businesses</title>
		<author>
			<persName><forename type="first">C</forename><surname>Tankard</surname></persName>
		</author>
		<idno type="DOI">10.1016/S1353-4858(16)30056-3</idno>
	</analytic>
	<monogr>
		<title level="j">Netw. Secur</title>
		<imprint>
			<biblScope unit="volume">2016</biblScope>
			<biblScope unit="issue">6</biblScope>
			<biblScope unit="page" from="5" to="8" />
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Privacy and Market Concentration: Intended and Unintended Consequences of the GDPR</title>
		<author>
			<persName><forename type="first">G</forename><surname>Johnson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Shriver</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Goldberg</surname></persName>
		</author>
		<idno type="DOI">10.1287/mnsc.2023.4709</idno>
	</analytic>
	<monogr>
		<title level="j">Manag. Sci</title>
		<imprint>
			<biblScope unit="volume">69</biblScope>
			<biblScope unit="issue">10</biblScope>
			<biblScope unit="page" from="5695" to="6415" />
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<monogr>
		<author>
			<persName><forename type="first">J</forename><surname>Daemen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Rijmen</surname></persName>
		</author>
		<title level="m">AES Proposal</title>
				<imprint>
			<publisher>Rijndael</publisher>
			<date type="published" when="1999">1999</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Analysis of the SSL 3.0 Protocol</title>
		<author>
			<persName><forename type="first">D</forename><surname>Wagner</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Schneier</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">The Second USENIX Workshop on Electronic Commerce Proceedings</title>
				<imprint>
			<date type="published" when="1996">1996</date>
			<biblScope unit="volume">1</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<monogr>
		<title level="m" type="main">Searching in Grover&apos;s Algorithm</title>
		<author>
			<persName><forename type="first">R</forename><surname>Jozsa</surname></persName>
		</author>
		<idno type="DOI">10.48550/arXiv.quant-ph/9901021</idno>
		<imprint>
			<date type="published" when="1999">1999</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">Realization of a Scalable Shor Algorithm</title>
		<author>
			<persName><forename type="first">T</forename><surname>Monz</surname></persName>
		</author>
		<idno type="DOI">10.1126/science.aad9480</idno>
	</analytic>
	<monogr>
		<title level="j">Science</title>
		<imprint>
			<biblScope unit="volume">351</biblScope>
			<biblScope unit="issue">6277</biblScope>
			<biblScope unit="page" from="1068" to="1070" />
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Shor&apos;s Algorithm</title>
		<author>
			<persName><forename type="first">H</forename><surname>Wong</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Introduction to Quantum Computing: From a Layperson to a Programmer in 30 Steps</title>
				<meeting><address><addrLine>Cham</addrLine></address></meeting>
		<imprint>
			<publisher>Springer International Publishing</publisher>
			<date type="published" when="2023">2023</date>
			<biblScope unit="page" from="289" to="298" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<monogr>
		<title level="m" type="main">Chaotic Roots of the Modular Multiplication Dynamical System in Shor&apos;s Algorithm</title>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">M</forename><surname>Patoary</surname></persName>
		</author>
		<idno type="DOI">10.48550/arXiv.2306.16446</idno>
		<imprint>
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">High-Speed and Secure PRNG for Cryptographic Applications</title>
		<author>
			<persName><forename type="first">Z</forename><surname>Hu</surname></persName>
		</author>
		<idno type="DOI">10.5815/ijcnis.2020.03.01</idno>
	</analytic>
	<monogr>
		<title level="j">Int. J. Comput. Network Inf. Secur</title>
		<imprint>
			<biblScope unit="volume">12</biblScope>
			<biblScope unit="issue">3</biblScope>
			<biblScope unit="page" from="1" to="10" />
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">Lattice based Merkle</title>
		<author>
			<persName><forename type="first">M</forename><surname>Iavich</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">International Conference on Information Technologies</title>
				<imprint>
			<date type="published" when="2019">2019</date>
			<biblScope unit="volume">2470</biblScope>
			<biblScope unit="page" from="13" to="16" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title level="a" type="main">Modular Reduction Based on the Divider by Blocking Negative Remainders</title>
		<author>
			<persName><forename type="first">S</forename><surname>Tynymbayev</surname></persName>
		</author>
		<idno type="DOI">10.32014/2019.2518-170x.60</idno>
	</analytic>
	<monogr>
		<title level="j">News of the National Academy of Sciences of the Republic of Kazakhstan, Series of Geology and Technical Sciences</title>
		<imprint>
			<biblScope unit="volume">2</biblScope>
			<biblScope unit="page" from="238" to="248" />
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title level="a" type="main">Multifunctional CRS Encryption Scheme on Isogenies of Non-Supersingular Edwards Curves</title>
		<author>
			<persName><forename type="first">A</forename><surname>Bessalov</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Workshop on Classic, Quantum, and Post-Quantum Cryptography</title>
		<imprint>
			<biblScope unit="volume">3504</biblScope>
			<biblScope unit="page" from="12" to="25" />
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b18">
	<analytic>
		<title level="a" type="main">A Post-Quantum Digital Signature Using Verkle Trees and Lattices</title>
		<author>
			<persName><forename type="first">M</forename><surname>Iavich</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Kuchukhidze</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Bocu</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Symmetry</title>
		<imprint>
			<biblScope unit="volume">15</biblScope>
			<biblScope unit="issue">12</biblScope>
			<biblScope unit="page">2165</biblScope>
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b19">
	<monogr>
		<title level="m" type="main">Digital Signature Design Using Verkle Tree</title>
		<author>
			<persName><forename type="first">M</forename><surname>Iavich</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Kuchukhidze</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b20">
	<analytic>
		<title level="a" type="main">Breaking a Fifth-order Masked Implementation of Crystals-kyber by Copy-paste</title>
		<author>
			<persName><forename type="first">E</forename><surname>Dubrova</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 10 th ACM Asia Public-Key Cryptography Workshop</title>
				<meeting>the 10 th ACM Asia Public-Key Cryptography Workshop</meeting>
		<imprint>
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b21">
	<analytic>
		<title level="a" type="main">CRYSTALS-Kyber Algorithm Specifications and Supporting Documentation</title>
		<author>
			<persName><forename type="first">R</forename><surname>Avanzi</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">NIST PQC Round</title>
		<imprint>
			<biblScope unit="volume">2</biblScope>
			<biblScope unit="issue">4</biblScope>
			<biblScope unit="page" from="1" to="43" />
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b22">
	<analytic>
		<title level="a" type="main">Securing CRYSTALS-Kyber in FPGA Using Duplication and Clock Randomization</title>
		<author>
			<persName><forename type="first">M</forename><surname>Moraitis</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">IEEE Design &amp; Test</title>
		<imprint>
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b23">
	<analytic>
		<title level="a" type="main">New Secure Block Cipher for Critical Applications: Design, Implementation, Speed and Security Analysis</title>
		<author>
			<persName><forename type="first">S</forename><surname>Gnatyuk</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Advances in Intelligent Systems and Computing</title>
				<imprint>
			<date type="published" when="2020">2020</date>
			<biblScope unit="page" from="93" to="104" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b24">
	<analytic>
		<title level="a" type="main">Modeling CSIKE Algorithm on Non-Cyclic Edwards Curves</title>
		<author>
			<persName><forename type="first">A</forename><surname>Bessalov</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Cybersecurity Providing in Information and Telecommunication Systems</title>
		<imprint>
			<biblScope unit="volume">3288</biblScope>
			<biblScope unit="page" from="1" to="10" />
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b25">
	<analytic>
		<title level="a" type="main">Method of Algorithm Building for Modular Reducing by Irreducible Polynomial</title>
		<author>
			<persName><forename type="first">S</forename><surname>Gnatyuk</surname></persName>
		</author>
		<idno type="DOI">10.1109/iccas.2016.7832498</idno>
	</analytic>
	<monogr>
		<title level="m">16th International Conference on Control, Automation and Systems</title>
				<imprint>
			<date type="published" when="2016">2016</date>
			<biblScope unit="page" from="1476" to="1479" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b26">
	<analytic>
		<title level="a" type="main">Implementation of the CSIDH Algorithm Model on Supersingular Twisted and Quadratic Edwards Curves</title>
		<author>
			<persName><forename type="first">A</forename><surname>Bessalov</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Workshop on Cybersecurity Providing in Information and Telecommunication Systems</title>
		<imprint>
			<biblScope unit="volume">3187</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="302" to="309" />
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b27">
	<analytic>
		<title level="a" type="main">Streaming Authenticated Data Structures</title>
		<author>
			<persName><forename type="first">C</forename><surname>Papamanthou</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-642-38348-9_22</idno>
	</analytic>
	<monogr>
		<title level="s">Advances in Cryptology-EUROCRYPT</title>
		<imprint>
			<biblScope unit="page" from="353" to="370" />
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b28">
	<analytic>
		<title level="a" type="main">CSIKE-ENC Combined Encryption Scheme with Optimized Degrees of Isogeny Distribution</title>
		<author>
			<persName><forename type="first">A</forename><surname>Bessalov</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Workshop on Cybersecurity Providing in Information and Telecommunication Systems</title>
		<imprint>
			<biblScope unit="volume">3421</biblScope>
			<biblScope unit="page" from="36" to="45" />
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b29">
	<analytic>
		<title level="a" type="main">Aggregating and Thresholdizing Hash-Based Signatures Using STARKs</title>
		<author>
			<persName><forename type="first">I</forename><surname>Khaburzaniya</surname></persName>
		</author>
		<idno type="DOI">10.1145/3488932.3524128</idno>
	</analytic>
	<monogr>
		<title level="j">ACM Asia Conf. Comput. Commun. Secur</title>
		<imprint>
			<biblScope unit="page" from="393" to="407" />
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
