WO2018017168A2 - Système et procédé de chiffrement et de déchiffrement sur la base d'une distribution de clés quantiques - Google Patents

Système et procédé de chiffrement et de déchiffrement sur la base d'une distribution de clés quantiques Download PDF

Info

Publication number
WO2018017168A2
WO2018017168A2 PCT/US2017/027221 US2017027221W WO2018017168A2 WO 2018017168 A2 WO2018017168 A2 WO 2018017168A2 US 2017027221 W US2017027221 W US 2017027221W WO 2018017168 A2 WO2018017168 A2 WO 2018017168A2
Authority
WO
WIPO (PCT)
Prior art keywords
key
label
request
data
new
Prior art date
Application number
PCT/US2017/027221
Other languages
English (en)
Other versions
WO2018017168A3 (fr
Inventor
Peng Yuan
Zhiqiang Wang
Original Assignee
Alibaba Group Holding Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN201610252306.5A external-priority patent/CN107306286B/zh
Priority claimed from CN201610298847.1A external-priority patent/CN107347058B/zh
Application filed by Alibaba Group Holding Limited filed Critical Alibaba Group Holding Limited
Priority to JP2018548709A priority Critical patent/JP7073268B2/ja
Priority to KR1020187029994A priority patent/KR102432299B1/ko
Priority to SG11201808947XA priority patent/SG11201808947XA/en
Priority to EP17831457.1A priority patent/EP3453135B1/fr
Publication of WO2018017168A2 publication Critical patent/WO2018017168A2/fr
Publication of WO2018017168A3 publication Critical patent/WO2018017168A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0891—Revocation or update of secret information, e.g. encryption key update or rekeying
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
    • H04L9/0852—Quantum cryptography

Definitions

  • This disclosure is generally related to the field of data encryption. More specifically, this disclosure is related to a method and system for encryption and decryption based on quantum key distribution.
  • Sensitive data such as company data and customer data
  • Sensitive data may be vulnerable to security leaks.
  • One solution to protect such sensitive data is based on data storage encryption technology, which generally involves applying a specific technology to encrypt data before writing the data onto a storage device, and to subsequently decrypt the data when reading the stored data.
  • a typical data storage encryption system may include, e.g., host software encryption, an encrypted storage security switch, an embedded special encryption device, and an encryption mechanism based on the storage device itself.
  • a typical logical architecture for such features may include an encryption/decryption unit and a key management center.
  • the encryption/decryption unit can encrypt data to be stored using a key (which is typically fixed or infrequently updated), and can also decrypt stored data with the fixed key.
  • the key management center can store the fixed key, and can also perform other key management- related functions, such as selecting new keys and deleting unused or previously used keys.
  • Replacing or updating a fixed (“original") key may occur only under specific circumstances, e.g., when establishing a secure transmission channel based on an asymmetric encryption algorithm via the key management center and transmitting the new key to the encryption/decryption unit, or by a specific administrative user who physically visits the actual site to manually update the key, e.g., by copying a new key to the system.
  • the system when replacing or updating a key, the system must retain access to both the original key and the original encrypted data in order to retain the ability to decrypt the original encrypted data.
  • this typical data storage encryption system may result in several problems.
  • Second, the key distribution process (e.g., selecting or replacing a key) may pose a security risk.
  • adopting an asymmetric encryption algorithm for a key distribution process requires transmissions between two entities. These transmissions may be susceptible to eavesdropping and algorithm hacking.
  • a manual update may face the risk of malicious disclosure.
  • the system may require administrative users (e.g., management and maintenance personnel) to perform additional and potentially computationally complex work to handle the original key and the original encrypted data. These problems may decrease the efficiency and security of the data storage encryption system.
  • One embodiment of the present invention provides a system for facilitating storage encryption and decryption.
  • the system receives a first request to encrypt data, wherein the first request indicates the data to be encrypted.
  • the system encrypts the data based on a key, and determines a key label for the key.
  • the system transmits the encrypted data and the key label to a remote device, thereby facilitating secure encryption and decryption of data on the remote device.
  • the system updates the key based on a dynamic key refreshment protocol by performing several operations.
  • the system obtains a first new key from a first key pool.
  • the system transmits a first synchronization request to a key-managing device, which causes the key-managing device to obtain from a second key pool of the key-managing device a second new key which is the same as the first new key.
  • the system obtains a first new key label for the first new key, wherein the first new key label is the same as a second new key label obtained for the second new key, wherein the first new key is the key used to encrypt the data, and wherein the first new key label is the determined key label.
  • the dynamic key refreshment protocol is based on one or more of: determining that a predetermined time interval has passed; and receiving the first request.
  • the first new key and the second new key are obtained based on a same method, and the first new key label and the second new key label are obtained based on a same algorithm.
  • the system computes a first hash value of the first new key.
  • the system includes the first hash value in the first synchronization request, which allows the key-managing device to verify the second new key by confirming that a second hash value of the second new key is the same as the first hash value.
  • a quantum engine of the computer system generates one or more key sequences based on a quantum communication with a quantum engine of a key- managing device.
  • the computer system stores the generated key sequences in a first key pool of the computer system.
  • the key-managing device stores the generated key sequences in a second key pool of the key-managing device.
  • the computer system generates a first key label for a respective key sequence in the first key pool.
  • the key-managing device generates a second key label for a respective key sequence in the second key pool, wherein the first key label and the second key label are generated based on a same algorithm.
  • the system receives a second request to decrypt the encrypted data, wherein the second request indicates the encrypted data and the key label.
  • the system transmits a third request for the updated key, wherein the third request includes the key label.
  • the system receives the updated key, and decrypts the encrypted data based on the received updated key.
  • the third request is transmitted to a key-managing device, and the updated key is received from the key-managing device.
  • the system Prior to transmitting the third request to the key-managing device, the system obtains obtaining a third key from the first key pool, and transmits a second synchronization request to the key-managing device, which causes the key-managing device to obtain from a second key pool of the key-managing device a fourth key which is the same as the third key.
  • the system encrypts, based on the third key, the key label included in the third request, wherein the received updated key is encrypted based on the fourth key.
  • the system decrypts, based on the third key, the encrypted received updated key.
  • Another embodiment of the present invention provides a system for facilitating storage encryption and decryption.
  • the system receives, based on a dynamic key refreshment protocol, a first synchronization request which indicates a first key obtained from a first key pool.
  • the system obtains a second key from a second key pool, wherein the second key is the same as the first key.
  • the system obtains a second key label for the second key, wherein the second key label is the same as a first key label obtained for the first key.
  • the system stores the second key and the second key label, thereby facilitating secure encryption and decryption of data on a remote device.
  • the first synchronization request includes a first hash value of the first key.
  • the system computes a second hash value of the second key.
  • the system verifies the second key by confirming that the second hash value is the same as the first hash value.
  • the second key and the second key label are stored in a database associated with the computing system.
  • the system receives a request for the second key, wherein the request includes the second key label.
  • the system retrieves the second key from the database based on the second key label included in the request for the second key.
  • the system returns the retrieved second key.
  • the request is received from a security device, and the retrieved second key is returned to the security device.
  • the system Prior to receiving the request from the security device: the system receives, from the security device, a second synchronization request associated with a third key from the first key pool, wherein the second key label included in the request for the second key is encrypted based on the third key; the system obtains, from the second key pool, a fourth key which is the same as the third key; and the system decrypts the encrypted second key label based on the fourth key.
  • the system Prior to returning the retrieved second key, the system encrypts the retrieved second key based on the fourth key.
  • FIG. 1 illustrates an exemplary environment that facilitates storage encryption and decryption, in accordance with an embodiment of the present application.
  • FIG. 2 illustrates an exemplary environment that facilitates storage encryption and decryption, including exemplary communications, in accordance with an embodiment of the present application.
  • FIG. 3A presents a flowchart illustrating a method by a security device for encrypting data to be stored on a storage device, in accordance with an embodiment of the present application.
  • FIG. 3B presents a flowchart illustrating a method by a security device for updating a key, in accordance with an embodiment of the present application.
  • FIG. 3C presents a flowchart illustrating a method by a security device for decrypting data stored on a storage device, in accordance with an embodiment of the present application.
  • FIG. 4 presents a flowchart illustrating a method for generating keys based on a quantum key distribution protocol, in accordance with an embodiment of the present application.
  • FIG. 5A presents a flowchart illustrating a method by a key-managing device for facilitating storage encryption and decryption, in accordance with an embodiment of the present application.
  • FIG. 5B presents a flowchart illustrating a method by a key-managing device for retrieving a key based on a corresponding key label, in accordance with an embodiment of the present application.
  • FIG. 6 illustrates an exemplary computer system that facilitates storage encryption and decryption, in accordance with an embodiment of the present application.
  • FIG. 7 illustrates an exemplary apparatus that facilitates storage encryption and decryption, in accordance with an embodiment of the present application.
  • Embodiments of the present invention solve the problem of security-related deficiencies in a data storage encryption system by applying a quantum key distribution protocol to generate keys, and by storing a corresponding key label for a generated key.
  • an encryption/decryption unit (a "security device") and a key management center (a “key-managing device”) may share a fixed (“original") key with which to encrypt data to be stored and to decrypt the stored data ("original data”).
  • Replacing or updating such a fixed key may require the system to retain access to both the original key and the original encrypted data. This may result in several deficiencies.
  • the stored encrypted data may be vulnerable to a brute force attack.
  • the key distribution process (e.g., selecting or updating a key) may pose a security risk.
  • adopting an asymmetric encryption algorithm for a key distribution process requires transmissions between two entities. These transmissions may be susceptible to eavesdropping and algorithm hacking. Furthermore, a manual update may face the risk of malicious disclosure.
  • the system may require administrative users (e.g., management and maintenance personnel) to perform additional and potentially computationally complex work to handle the original key and the original encrypted data.
  • Embodiments of the present invention address these issues by applying a quantum key distribution technology to generate and distribute keys, selecting a new key periodically or continuously (i.e., updating the key), and storing a corresponding key label for an updated key.
  • the system upon receiving a request to encrypt data to be stored on a storage device, the system updates a key based on a dynamic key refreshment protocol, such as periodically (based on a certain time interval) or continuously (based on a "one storage per key” method).
  • the system determines a key label for the selected key, encrypts the data using the selected key, and returns both the encrypted data and the corresponding key label for storage in the storage device.
  • a key-managing device and a security device can generate the same pools of keys (i.e., the same key sequences in each respective key pool) by communicating via a quantum channel or a quantum key distribution protocol.
  • a quantum channel or a quantum key distribution protocol is based on the principle of quantum mechanics, which guarantees the security of the key distribution process, as described herein. Communication via such a protocol further allows the key-managing device and the security device to coordinate and synchronize the selection of the same key and the
  • the system may flexibly encrypt data using different keys, which increases the security of the data storage.
  • the key-managing device and the security device can determine a same corresponding key label for an updated key, which label can be subsequently used to retrieve the updated key and correctly decrypt the stored data.
  • different keys may be used to encrypt the data to be stored. This allows an increased diversity in the granularity of the key usage, which can both increase the security of the data storage and simplify the process of replacing or updating the key.
  • Embodiments of the present invention provide a technological solution (e.g., applying a quantum key distribution technology, updating a key based on a dynamic key refreshment protocol, and storing a corresponding key label for the updated key for subsequent decrypting of the data) to the technological problem of secure data storage encryption (as in the above-described risks in a typical data storage encryption system).
  • a technological solution e.g., applying a quantum key distribution technology, updating a key based on a dynamic key refreshment protocol, and storing a corresponding key label for the updated key for subsequent decrypting of the data
  • Quantum key distribution technology refers to operations performed by a quantum engine or a quantum device of a first entity (e.g., a key-managing device) and a second entity (e.g., a security device).
  • the first and second entities each generate the same random key sequence after performing standard processing operations, such as original key negotiation, key screening, error correction, and privacy amplification.
  • the first and second entities may each store the key sequences in a respective key pool.
  • Exemplary quantum key distribution protocols include the BB84, B91, and B92 protocols, as well as other protocols which have been proposed to improve the code rate, such as continuous variable QKD, DSP-QKP, and SARG.
  • the first entity (“Alice") can randomly generate a set of binary data strings, and can select a basic vector based on the data strings to prepare a corresponding encoded quantum state to be sent to the second entity (“Bob") via a quantum channel.
  • Bob can disclose his own basic vector via a classical channel (i.e., an electrical or wired channel which is not a quantum channel), which allows both Alice and Bob to select a key using the same basic vector.
  • a classical channel i.e., an electrical or wired channel which is not a quantum channel
  • key sequence refers to a sequence consisting of a number of key bits.
  • key pool refers to a memory area which stores key sequences generated upon performing a quantum key distribution operation.
  • key label refers to an identifier or identifying information used to distinguish between different keys.
  • the key label may be in the form of, e.g., numerical values or character strings.
  • synchronization request refers to a request sent by a security device to a key-managing device, which request triggers the key-managing device to obtain a key from its key pool which is the same as a key from the key pool of the security device.
  • FIG. 1 illustrates an exemplary environment 100 that facilitates storage encryption and decryption, in accordance with an embodiment of the present application.
  • Environment 100 can include a computing device 110 which is associated with a user 112.
  • Computing device 110 can include, for example, a tablet, a mobile phone, an electronic reader, a laptop computer, a desktop computer, or any other computing device.
  • Environment 100 can also include a server 120, a server 130, and a storage device 140, which may communicate with each other (and computing device 110) via a network 102.
  • Server 120 may be, e.g., a security device 120 with an encryption/decryption system 121, which includes: a data decryption module 122 which decrypts data based on a key label; a data encryption module 126 which encrypts data and returns the encrypted data and a corresponding key label; a key pool 127 which may be associated with data encryption module 126; and a quantum engine 128 which generates key sequences based on a quantum key distribution protocol or operation.
  • an encryption/decryption system 121 which includes: a data decryption module 122 which decrypts data based on a key label; a data encryption module 126 which encrypts data and returns the encrypted data and a corresponding key label; a key pool 127 which may be associated with data encryption module 126; and a quantum engine 128 which generates key sequences based on a quantum key distribution protocol or operation.
  • Server 130 may be, e.g., a key-managing device 130 with a key management system 131, which includes: a key provision module 132 which processes requests for keys by querying a key database 134; key database 134 which stores keys and their corresponding key labels; a key storage module 136 which processes requests for synchronized and updated keys from a key pool generated during a quantum key distribution protocol or operation; and a quantum engine 138 which generates key sequences based on a quantum key distribution protocol or operation.
  • a key provision module 132 which processes requests for keys by querying a key database 134
  • key database 134 which stores keys and their corresponding key labels
  • a key storage module 136 which processes requests for synchronized and updated keys from a key pool generated during a quantum key distribution protocol or operation
  • a quantum engine 138 which generates key sequences based on a quantum key distribution protocol or operation.
  • Data decryption module 122 can communicate with key provision module 132 via a communication 104, and data encryption module 126 can communicate with key storage module 136 via a communication 106.
  • Quantum engine 128 can communicate with quantum engine 138 via a communication 108, which can be via a quantum channel as part of a quantum key distribution protocol or operation.
  • user 112 may send, via computing device 110, a request 152 to encrypt data which is to be stored on storage device 140.
  • Security device 120 can receive request 152, update a key based on a dynamic key refreshment protocol (e.g., periodically at a certain time interval or continuously for each new request), obtain a key label for the updated key, encrypt the data using the updated key, and send a packet 154 to storage device 140, where packet 154 can indicate the encrypted data and the corresponding key label.
  • a dynamic key refreshment protocol e.g., periodically at a certain time interval or continuously for each new request
  • an application or function which can interface with storage device 140 may send a request (not shown) to decrypt the encrypted data stored on storage device 140.
  • This may trigger storage device 140 to send a packet 156 to security device 120, where packet 156 can indicate the encrypted data and the corresponding key label (similar to packet 154).
  • Security device 120 can receive a request to decrypt data based on received packet 156, obtain a key based on the key label included in packet 156, decrypt the data using the obtained key, and send a packet 158 back to the interfacing application or function, e.g., computing device 110 associated with user 112, wherein packet 158 can indicate the decrypted data.
  • FIG. 2 illustrates an exemplary environment 200 that facilitates storage encryption and decryption, including exemplary communications, in accordance with an embodiment of the present application.
  • Environment 200 can include security device 120, key-managing device 130, and storage device 140, as in environment 100 of FIG. 1. While environment 200 depicts various modules as residing inside each of security device 120 and key-managing device 130, in some embodiments, one or more of these modules may reside within a single system or entity.
  • quantum engine 128 and quantum engine 138 can perform a quantum key distribution protocol 240, which generates the same key sequences and stores the generated key sequences in, respectively, key pool 127 and key pool 137.
  • data encryption module 126 can receive a request 201 to encrypt data 202 which is to be stored on storage device 140.
  • Request 201 can indicate data of a packet 202.
  • the system Prior to indicating data 202 in request 201, the system can perform fractionation, compression, and other data processing on data 202.
  • a functional unit may trigger data encryption module 126 to encrypt data 202 via an application programming interface (API) or by transmitting a message (such as request 201).
  • API application programming interface
  • Data encryption module 126 can update a key based on a dynamic key refreshment protocol. For example, when the dynamic key refreshment protocol is based on the passage of a certain time period or interval, or based on simply receiving a new request (e.g., request 201), data encryption module may proceed with updating the key by obtaining a new key via a synchronization request, as described below. When the dynamic key refreshment protocol determines that the key is not to be updated (e.g., a certain time interval has not yet passed), the system may use a key which has been most recently used for an encryption operation. In some embodiments, request 201 may include an instruction to update the key, and data encryption module 126 or any other module may process such an included instructions.
  • Data encryption module 126 can obtain a key from key pool 127 (function 204), and send a synchronization request 206 to key storage module 136.
  • Synchronization request 206 can indicate that key storage module 136 is to obtain a key from key pool 137 which is the same as the key obtained by data encryption module 126. That is, upon receiving synchronization request 206, key storage module 136 can obtain a key from key pool 137 (function 208), where the obtained key is the same as the key obtained by data encryption module 126 from key pool 127 (as in function 204).
  • Functions 204 and 208 may be based on applying the same predetermined method to obtain the same key from the respective key pool.
  • the key may be obtained by a method which is based on information such as a key selection position and a key length, which may be indicated or carried in synchronization request 206. Any method may be used to obtain the key, as long as the same key is obtained in function 208 as in function 204.
  • Key storage module 136 can generate a key label (function 210) for the obtained key, and send both the obtained key and the generated key label to key database 134 (function 212).
  • Data encryption module 126 can also obtain or generate the key label for the obtained key (function 214).
  • Functions 210 and 214 may be based on applying the same predetermined algorithm to generate the key label, or based on a communication between security device 120 and key-managing device 130 regarding the same predetermined algorithm. For example, in applying the same algorithm, a counter may be used to generate the key label for the key. The initial value of the counter may be set to a value of zero, and the counter value may be increased by one for each key replacement.
  • the counter value may be indicated in the key label.
  • Both security device 120 and key-managing device 130 may use this same algorithm to ensure the generation of the same key label.
  • the security device may generate the key label, and subsequently send the generated key label to the key-managing device so that the key-managing device has the same generated key label for the key.
  • the key-managing device may generate the key label, and subsequently send the generated key label to the security device so that the security device has the same generated key label for the key.
  • Data encryption module 126 may encrypt the data (function 216) based on the obtained key, and send both the encrypted data and the corresponding key label (packet 218) to storage device 140.
  • the system can use a symmetric encryption algorithm, e.g., RC2, RC4, Data Encryption Standard (DES), 3DES, or Advanced Encryption Standard (AES).
  • a symmetric encryption algorithm e.g., RC2, RC4, Data Encryption Standard (DES), 3DES, or Advanced Encryption Standard (AES).
  • data decryption module 122 can receive a request 221 to decrypt data of a packet 222, which indicates the encrypted data and the corresponding key label, as previously stored on storage device 140.
  • Request 221 may be received from, e.g., a functional unit with an access interface to storage device 140, as described above in relation to request 201.
  • Data decryption module 122 can send a request 224 to key provision module 132.
  • Request 224 can include the key label, and can further indicate a request for the key corresponding to the included key label.
  • Key provision module 132 can receive request 224 and retrieve the requested key from key database 134 based on the corresponding key label (function 226).
  • environment 200 depicts a system which facilitates secure encryption and decryption of data on a remote device (e.g., a storage device) by updating a key based on a dynamic key refreshment protocol, storing a key label for the updated key, and applying a quantum key distribution protocol to ensure the synchronization and security of key distribution.
  • a remote device e.g., a storage device
  • the system allows a new key to be selected (e.g., updating a key) on a periodic basis (e.g., based on a predetermined time interval) or on a continuous basis (e.g., based on receiving a request to encrypt data, that is, a "one key one storage" method).
  • FIG. 3A presents a flowchart 300 illustrating a method by a security device for encrypting data to be stored on a storage device, in accordance with an embodiment of the present application.
  • the system receives, by a security device, a first request to encrypt data which is to be stored on a remote device, wherein the first request indicates the data (operation 302).
  • the system updates the key based on a dynamic key refreshment protocol (operation 304).
  • the system determines a key label for the updated key (operation 306).
  • the system encrypts the data based on the updated key (operation 308).
  • the system transmits the encrypted data and the key label to the remote device, thereby facilitating secure encryption and decryption of data on the remote device (operation 310).
  • FIG. 3B presents a flowchart 320 illustrating a method by a security device for updating a key, in accordance with an embodiment of the present application.
  • the system determines whether to update the key based on a dynamic key refreshment protocol (decision 322). If the system determines not to update the key (decision 322), the system selects a key most recently used for an encryption operation (operation 324), and the operation returns. If the system determines to update the key based on a dynamic key refreshment protocol (decision 322), the system obtains a first new key from a first key pool (operation 332). The first key pool may be associated with the security device. The system transmits a first
  • a key-managing device which causes the key-managing device to obtain from a second key pool of the key-managing device a second new key which is the same as the first new key, wherein the first new key and the second new key are obtained based on a same method (operation 334).
  • the system obtains a first new key label for the first new key, wherein the first new key label is the same as a second new key label obtained for the second new key, wherein the first new key label and the second new key label are obtained based on a same algorithm (operation 336).
  • the system may also delete both the key most recently used for an encryption operation, and the corresponding key label. This reduces the amount of storage space required, and also decreases the risk of key exposure by allowing the key-managing device to maintain centralized management.
  • the system may compute a hash of the first new key, and include the computed hash value in the first synchronization request, which allows the key- managing device to verify the second new key by confirming that a second hash value of the second new key is the same as the first hash value. If the first and second hash values do not match, the security device and the key-managing device may re-select the key via another exchange or negotiation.
  • FIG. 3C presents a flowchart 340 illustrating a method by a security device for decrypting data stored on a storage device, in accordance with an embodiment of the present application.
  • the system receives a second request to decrypt encrypted data, wherein the second request indicates the encrypted data and the key label (operation 342).
  • the system transmits a third request for the updated key, wherein the third request includes the key label (operation 344).
  • the system receives the updated key (operation 346), and decrypts the encrypted data based on the received updated key (operation 348).
  • the system can encrypt the key label using another key (“third key”) and based on a symmetric encryption algorithm (as described above) and included the encrypted key label in the third request.
  • the system can obtain this third key from the first key pool (of the system or security device), and transmit a second synchronization request to the key-managing device, which causes the key-managing device to obtain from the second key pool (of the key-managing device) a fourth key which is the same as the third key.
  • the system can then encrypt, based on the third key, the key label included in the third request (as part of operation 344).
  • the key-managing device can decrypt the encrypted key label based on the fourth key, and also encrypt the received updated key based on the fourth key (as part of operation 346). Finally, the system can decrypt the encrypted received updated key based on the third key.
  • FIG. 4 presents a flowchart 400 illustrating a method for generating keys based on a quantum key distribution protocol, in accordance with an embodiment of the present application.
  • a quantum engine of a computer system e.g., a security device
  • the two quantum engines may communicate as part of a quantum key distribution protocol, via a quantum channel.
  • the advantages of such a protocol are described above.
  • the computer system stores the generated key sequences in a first key pool of the computer system (operation 404).
  • the key-managing device stores the generated key sequences in a second key pool of the key-managing device (operation 406).
  • the computer system generates a first key label for a respective key sequence in the first key pool based a predetermined algorithm (operation 408).
  • the key-managing device generates a second key label for a respective key sequence in the second key pool based on the (same) predetermined algorithm (operation 410).
  • FIG. 5A presents a flowchart 500 illustrating a method by a key-managing device for facilitating storage encryption and decryption, in accordance with an embodiment of the present application.
  • the system receives, based on a dynamic key refreshment protocol, a first synchronization request which indicates a first key obtained from a first key pool (operation 502).
  • the system obtains a second key from a second key pool, wherein the second key is the same as the first key, wherein the first key and the second key are obtained based on a same method (operation 504).
  • the system obtains a second key label for the second key, wherein the second key label is the same as a first key label obtained for the first key, wherein the first key label and the second key label are obtained based on a same algorithm (operation 506).
  • the system stores the second key and the second key label, thereby facilitating secure encryption and decryption of data on a remote device (operation 508).
  • FIG. 5B presents a flowchart 520 illustrating a method by a key-managing device for retrieving a key based on a corresponding key label, in accordance with an embodiment of the present application.
  • the system receives a request for the second key, wherein the request includes the second key label (operation 522).
  • the system retrieves the second key from a database associated with the system based on the second key label included in the request for the second key (operation 524).
  • the system returns the retrieved second key (operation 526).
  • FIG. 6 illustrates an exemplary computer system 600 that facilitates storage encryption and decryption, in accordance with an embodiment of the present application.
  • Computer system 600 includes a processor 602, a memory 604, a quantum engine 606, and a storage device 608.
  • Memory 604 can include a volatile memory (e.g., RAM) that serves as a managed memory, and can be used to store one or more memory pools.
  • computer system 600 can be coupled to a display device 610, a keyboard 612, and a pointing device 614.
  • Quantum engine 606 can generate quantum keys and communicate via a quantum or photonic communication with another system by distributing and maintaining a same pool of keys.
  • Storage device 608 can store an operating system 616, a content-processing system 618, and data 632.
  • Content-processing system 618 can include instructions, which when executed by computer system 600, can cause computer system 600 to perform methods and/or processes described in this disclosure.
  • content-processing system 618 can include: a communication module 620 for transmitting and receiving keys or requests which indicate data, keys, or key labels, including via a quantum or photonic communication; a key-selecting module 622 for updating a key based on a dynamic key refreshment protocol and for selected a most recently used key for an encryption operation; a key label-managing module 624 for generating key labels and for determining a key label for a key; an encrypting/decrypting module 626 for encrypting or decrypting data based on a key; a key-generating module 628 for generating key sequences or keys to be stored in a key pool; and a verification module 630 for verifying a key whose hash value is included in a request.
  • Data 632 can include any data that is required as input or that is generated as output by the methods and/or processes described in this disclosure. Specifically, data 632 can store at least: data to be encrypted and stored; a request to encrypt data to be stored on a storage device; a key; an updated key; a dynamic key refreshment protocol; a key label for a key; a key pool; a key sequence; a synchronization request; a predetermined time interval; an indicator of receiving a request; a method used to obtain a key from a key pool; an algorithm used to obtain or determine a key label for a key; a hash value; a hash value of a key; a request to decrypt encrypted data; a request for a key, where the request include a key label for the requested key; a database; encrypted data; decrypted data; and an encrypted or decrypted key or key label.
  • FIG. 7 illustrates an exemplary apparatus 700 that facilitates storage encryption and decryption, in accordance with an embodiment of the present application.
  • Apparatus 700 can comprise a plurality of units or apparatuses which may communicate with one another via a wired, wireless, quantum light, or electrical communication channel.
  • Device 700 may be realized using one or more integrated circuits, and may include fewer or more units or apparatuses than those shown in FIG. 7. Further, device 700 may be integrated in a computer system, or realized as a separate device which is capable of communicating with other computer systems and/or devices.
  • device 700 can comprise units 702-712 which perform functions or operations similar to modules 620-630 of computer system 600 of FIG. 6, including: a communication unit 702; a key-selecting unit 704; a key label-managing unit 706; an encrypting/decrypting unit 708; a key-generating unit 710; and a verification unit 712.
  • the data structures and code described in this detailed description are typically stored on a computer-readable storage medium, which may be any device or medium that can store code and/or data for use by a computer system.
  • the computer-readable storage medium includes, but is not limited to, volatile memory, non-volatile memory, magnetic and optical storage devices such as disk drives, magnetic tape, CDs (compact discs), DVDs (digital versatile discs or digital video discs), or other media capable of storing computer-readable media now known or later developed.
  • the methods and processes described in the detailed description section can be embodied as code and/or data, which can be stored in a computer-readable storage medium as described above.
  • a computer system reads and executes the code and/or data stored on the computer-readable storage medium, the computer system performs the methods and processes embodied as data structures and code and stored within the computer-readable storage medium.
  • the methods and processes described above can be included in hardware modules.
  • the hardware modules can include, but are not limited to, application-specific integrated circuit (ASIC) chips, field-programmable gate arrays (FPGAs), and other programmable-logic devices now known or later developed.
  • ASIC application-specific integrated circuit
  • FPGA field-programmable gate arrays
  • the hardware modules When the hardware modules are activated, the hardware modules perform the methods and processes included within the hardware modules.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Storage Device Security (AREA)

Abstract

Un mode de réalisation de la présente invention concerne un système conçu pour faciliter le chiffrement et le déchiffrement d'un stockage. En cours de fonctionnement, le système reçoit une première demande de chiffrement de données devant être stockées sur un dispositif distant, la première demande indiquant les données. Le système met à jour une clé sur la base d'un protocole de rafraîchissement de clé dynamique, détermine une étiquette de clé pour la clé mise à jour et chiffre les données sur la base de la clé mise à jour puis transmet les données chiffrées et l'étiquette de clé au dispositif distant, ce qui facilite les chiffrement et déchiffrement sécurisés des données sur le dispositif distant.
PCT/US2017/027221 2016-04-21 2017-04-12 Système et procédé de chiffrement et de déchiffrement sur la base d'une distribution de clés quantiques WO2018017168A2 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2018548709A JP7073268B2 (ja) 2016-05-06 2017-04-12 量子鍵配送に基づく暗号化及び復号のためのシステム及び方法
KR1020187029994A KR102432299B1 (ko) 2016-05-06 2017-04-12 양자 키 분배에 기초하는 암호화 및 복호화를 위한 시스템 및 방법
SG11201808947XA SG11201808947XA (en) 2016-05-06 2017-04-12 System and method for encryption and decryption based on quantum key distribution
EP17831457.1A EP3453135B1 (fr) 2016-05-06 2017-04-12 Système et procédé de chiffrement et de déchiffrement sur la base d'une distribution de clés quantiques

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
CN201610252306.5A CN107306286B (zh) 2016-04-21 2016-04-21 离线考勤的处理方法及装置
CN201610252306.5 2016-04-21
CN201610298847.1A CN107347058B (zh) 2016-05-06 2016-05-06 数据加密方法、数据解密方法、装置及系统
CN201610298847.1 2016-05-06
US15/481,338 2017-04-06
US15/481,338 US10693635B2 (en) 2016-05-06 2017-04-06 System and method for encryption and decryption based on quantum key distribution

Publications (2)

Publication Number Publication Date
WO2018017168A2 true WO2018017168A2 (fr) 2018-01-25
WO2018017168A3 WO2018017168A3 (fr) 2018-03-22

Family

ID=60992679

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/027221 WO2018017168A2 (fr) 2016-04-21 2017-04-12 Système et procédé de chiffrement et de déchiffrement sur la base d'une distribution de clés quantiques

Country Status (1)

Country Link
WO (1) WO2018017168A2 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110048833A (zh) * 2019-03-04 2019-07-23 全球能源互联网研究院有限公司 基于量子卫星密钥网络的电力业务加密方法及装置
CN110719164A (zh) * 2019-09-30 2020-01-21 南方电网调峰调频发电有限公司信息通信分公司 量子离线密钥同步的授时方法
CN111988260A (zh) * 2019-05-21 2020-11-24 科大国盾量子技术股份有限公司 一种对称密钥管理系统、传输方法及装置
GB2601926A (en) * 2019-11-08 2022-06-15 Arqit Ltd Quantum-safe networking
GB2602208A (en) * 2019-11-08 2022-06-22 Arqit Ltd Quantum-safe networking
CN115085920A (zh) * 2022-07-15 2022-09-20 矩阵时光数字科技有限公司 一种密钥管理方法、装置、设备、系统及介质
CN116232762A (zh) * 2023-05-05 2023-06-06 广东广宇科技发展有限公司 一种基于量子密钥的加密数据传输方法

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7181011B2 (en) * 2004-05-24 2007-02-20 Magiq Technologies, Inc. Key bank systems and methods for QKD
US20080165973A1 (en) * 2007-01-09 2008-07-10 Miranda Gavillan Jose G Retrieval and Display of Encryption Labels From an Encryption Key Manager
US8111828B2 (en) * 2007-07-31 2012-02-07 Hewlett-Packard Development Company, L.P. Management of cryptographic keys for securing stored data
US9323901B1 (en) * 2007-09-28 2016-04-26 Emc Corporation Data classification for digital rights management
US8194858B2 (en) * 2009-02-19 2012-06-05 Physical Optics Corporation Chaotic cipher system and method for secure communication

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110048833B (zh) * 2019-03-04 2021-10-29 全球能源互联网研究院有限公司 基于量子卫星密钥网络的电力业务加密方法及装置
CN110048833A (zh) * 2019-03-04 2019-07-23 全球能源互联网研究院有限公司 基于量子卫星密钥网络的电力业务加密方法及装置
CN111988260B (zh) * 2019-05-21 2023-01-31 科大国盾量子技术股份有限公司 一种对称密钥管理系统、传输方法及装置
CN111988260A (zh) * 2019-05-21 2020-11-24 科大国盾量子技术股份有限公司 一种对称密钥管理系统、传输方法及装置
CN110719164A (zh) * 2019-09-30 2020-01-21 南方电网调峰调频发电有限公司信息通信分公司 量子离线密钥同步的授时方法
GB2601926A (en) * 2019-11-08 2022-06-15 Arqit Ltd Quantum-safe networking
GB2602208A (en) * 2019-11-08 2022-06-22 Arqit Ltd Quantum-safe networking
GB2602208B (en) * 2019-11-08 2022-12-14 Arqit Ltd Quantum-safe networking
GB2601926B (en) * 2019-11-08 2023-01-18 Arqit Ltd Quantum-safe networking
CN115085920A (zh) * 2022-07-15 2022-09-20 矩阵时光数字科技有限公司 一种密钥管理方法、装置、设备、系统及介质
CN115085920B (zh) * 2022-07-15 2024-01-16 矩阵时光数字科技有限公司 一种密钥管理方法、装置、设备、系统及介质
CN116232762A (zh) * 2023-05-05 2023-06-06 广东广宇科技发展有限公司 一种基于量子密钥的加密数据传输方法
CN116232762B (zh) * 2023-05-05 2023-08-01 广东广宇科技发展有限公司 一种基于量子密钥的加密数据传输方法

Also Published As

Publication number Publication date
WO2018017168A3 (fr) 2018-03-22

Similar Documents

Publication Publication Date Title
US11658814B2 (en) System and method for encryption and decryption based on quantum key distribution
JP7312892B2 (ja) 暗号化された資産暗号化鍵パーツのサブセットを使用して資産暗号化鍵のアセンブリを可能にする暗号化された資産暗号化鍵パーツ
US10785019B2 (en) Data transmission method and apparatus
WO2018017168A2 (fr) Système et procédé de chiffrement et de déchiffrement sur la base d'une distribution de clés quantiques
US9122888B2 (en) System and method to create resilient site master-key for automated access
US8712041B2 (en) Content protection apparatus and content encryption and decryption apparatus using white-box encryption table
WO2019204426A1 (fr) Système de stockage hors ligne et procédé d'utilisation
US20030138105A1 (en) Storing keys in a cryptology device
JP2020513183A (ja) データのトークン化
JP2007508778A (ja) 暗号用鍵の世代の効率的な管理
US9244864B2 (en) Information providing system, information processing apparatus, computer readable medium, and information providing method for providing encrypted information
KR101648364B1 (ko) 대칭키 암호화와 비대칭키 이중 암호화를 복합적으로 적용한 암/복호화 속도개선 방법
JP2016158189A (ja) 鍵付替え方向制御システムおよび鍵付替え方向制御方法
JP7190035B2 (ja) 個人情報処理のための暗号化システム及び方法
US7913089B2 (en) Identification information creating apparatus, identification information resolving apparatus, information system utilizing the apparatuses, controlling method and program thereof
WO2019099014A1 (fr) Génération de clé cryptographique pour magasins de données partagés logiquement
US9559840B2 (en) Low-bandwidth time-embargoed content disclosure
JPWO2018043466A1 (ja) データ抽出システム、データ抽出方法、登録装置及びプログラム
JP5945525B2 (ja) 鍵交換システム、鍵交換装置、その方法、及びプログラム
KR101595056B1 (ko) 인터클라우드 환경에서의 데이터 공유 시스템 및 공유 방법
EP4009212A1 (fr) Gestion de consentement
JP6108012B2 (ja) 情報配信システム、情報処理装置及びプログラム
JP5524601B2 (ja) プログラム、電子機器、サーバシステム及び情報提供システム
Sohana et al. Agent command manipulation system using two keys encryption model
TW201315191A (zh) 基於完整列矩陣之再加密方法

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2018548709

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20187029994

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17831457

Country of ref document: EP

Kind code of ref document: A2

WPC Withdrawal of priority claims after completion of the technical preparations for international publication

Ref document number: 201610252306.5

Country of ref document: CN

Date of ref document: 20180927

Free format text: WITHDRAWN AFTER TECHNICAL PREPARATION FINISHED

ENP Entry into the national phase

Ref document number: 2017831457

Country of ref document: EP

Effective date: 20181206