Data security using keys provided on demand
By implementing cryptographic operations using request-provided keys and disabling access post-use, the solution addresses the challenge of securing data access across complex network configurations, ensuring data security even in the event of a breach.
Patent Information
- Application Number
- JP2020181042
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2013-09-25
- Filing Date
- 2020-10-29
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2034-09-23
AI Technical Summary
Ensuring secure access to computing resources and data across complex network configurations, particularly when organizations utilize external computing resources, is challenging due to the difficulty in controlling access to cryptographic keys used for encryption and decryption.
A request processing entity implements cryptographic operations using a key provided in the request, then disables access to the key after use, ensuring the service provider has limited access and control over the data, even in the event of a security breach.
This approach ensures that the service provider cannot decrypt encrypted data once the key is no longer needed, maintaining data security and integrity by controlling access to cryptographic keys.
Smart Images

Figure 0007581013000001 
Figure 0007581013000002 
Figure 0007581013000003
Abstract
Description
[Technical field]
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application incorporates by reference for all purposes the entire disclosures of U.S. patent application Ser. No. 14 / 037,282, entitled "RESOURCE LOCATORS WITH KEYS," filed Sep. 25, 2013, and U.S. patent application Ser. No. 14 / 037,292, entitled "DATA SECURITY USING REQUEST-SUPPLIED KEYS," filed Sep. 25, 2013. [Background technology]
[0002] The security of computing resources and associated data is critical in many situations. As one example, organizations often utilize a network of computing devices to provide a robust set of services to their users. The networks often span multiple geographic boundaries and are therefore often connected to other networks. For example, an organization may use both an internal network of computing resources and computing resources managed by others to support its operations. An organization's computers may communicate with other organizations' computers to access and / or provide data, for example, while utilizing the services of the other organization. In many cases, organizations build and operate remote networks using hardware managed by other organizations, thereby reducing infrastructure costs and achieving other benefits. Such configurations of computing resources can make it difficult to reliably guarantee access to the resources and data held by the organization, especially as such configurations grow in size and complexity. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] US Patent No. 2013 / 0198519 Summary of the Invention [Means for solving the problem]
[0004] A request is presented to a request processing entity, which includes a cryptographic key to be used in fulfilling the request. Upon receiving the request, the request processing entity extracts the key from the request and fulfills the request by performing one or more cryptographic operations using the key. The one or more cryptographic operations may include encryption / decryption of data that may / is stored by a subsystem of the request processing entity in encrypted form. Once the request is fulfilled, the request processing entity may perform one or more operations to disable access to the key included in the request, thereby rendering it unusable. [Brief description of the drawings]
[0005] Various embodiments according to the present disclosure will be described with reference to the drawings.
[0006] [Figure 1] FIG. 1 illustrates an exemplary example of an environment in which various embodiments can be implemented. [Diagram 2] FIG. 1 illustrates an illustrative example of an environment in which various embodiments can be implemented. [Diagram 3] FIG. 2 illustrates an illustrative example of a representation of a request according to at least one embodiment. [Figure 4] FIG. 2 illustrates an illustrative example of a request submission process according to at least one embodiment. [Diagram 5] FIG. 2 illustrates an exemplary implementation of a process for handling requests in accordance with at least one embodiment. [Figure 6] FIG. 2 illustrates an illustrative example of a representation of a request according to at least one embodiment. [Figure 7] FIG. 2 illustrates an example implementation of a process for handling a PUT request in accordance with at least one embodiment. [Figure 8] FIG. 2 illustrates an example implementation of a submission process for a GET request in accordance with at least one embodiment. [Figure 9] 1A-1C illustrate examples of request wording according to various embodiments. [Figure 10] FIG. 2 illustrates an illustrative example of a request submission process according to at least one embodiment. [Figure 11] FIG. 1 illustrates an exemplary example of an environment in which various embodiments can be implemented. [Figure 12] FIG. 2 illustrates an exemplary implementation of a process for handling requests in accordance with at least one embodiment. [Figure 13] FIG. 1 illustrates an exemplary example of an environment in which various embodiments can be implemented. [Figure 14] FIG. 2 illustrates an exemplary implementation of a process for handling requests in accordance with at least one embodiment. [Figure 15] FIG. 1 illustrates an environment in which various embodiments can be implemented. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0007] In the following description, various embodiments are described. For convenience of explanation, specific configurations and details are described to fully understand these embodiments. However, it will be apparent to those skilled in the art that these embodiments can be practiced without the specific details. Furthermore, well-known features may be omitted or simplified to avoid obscuring the description of the embodiments.
[0008] Techniques described and proposed herein relate to the submission and processing of requests where the request includes a cryptographic key. The request may be generated and submitted by a customer of a service provider, such as a service provider of computing resources. Processing the request may include using the key included in the request to perform one or more cryptographic operations, such as encryption, decryption, and generating an electronic (digital) signature on the data. In some embodiments, techniques described and proposed herein are used to enable server-side encryption (and / or related techniques, such as decryption), where the key to be used for encryption / decryption is controlled by the client (i.e., the customer's device or a device acting on behalf of the customer).
[0009] In various embodiments, use of the key provided in the request is performed such that the service provider does not have access to the key except for the limited time for which the key is used. For example, the service provider may operate a data storage service. A customer may send data to the service provider for storage by the data storage service. The request to the service provider may include a key to be used to encrypt the data. The service provider may obtain the key from the request and use the key to encrypt the data. The encrypted data may then be durably stored with the data storage service. When the key is no longer needed (e.g., when encryption of the data is complete), the service provider may perform one or more operations to prevent access to the key, such as destroying or allowing the destruction of an in-memory copy of the key. If the data in plaintext form has been copied, those copies may be destroyed or allowed to be destroyed as well. The customer may be assured that once the key and the plaintext data are destroyed, the provider will not be able to decrypt the data. Thus, even if a security breach or other event at the provider results in unauthorized access to the data from the customer, the breach alone will not enable access to the data in plaintext form.
[0010] The key may be provided in the request in various ways according to various embodiments. For example, in some embodiments, the key is included in the request in a plaintext form. The plaintext key may be a symmetric key used for a symmetric key algorithm. The plaintext key may be the public key of a public-private key pair for an asymmetric key algorithm. In this case, the service provider does not have access to the private key of the key pair, and the private key is accessible to an entity (e.g., a customer) that can decrypt it with the private key. In some embodiments, the request includes the key in an encrypted (wrapped) form. For example, the key may be encrypted so that it can be decrypted by the service provider or another entity at the direction of the service provider. The key used to encrypt the key included in the request may be a secret shared with an entity (e.g., the service provider) that can decrypt it, or the public key of a public-private key pair. In this case, the private key will be used by the entity to decrypt the encrypted key to process the request. [NOTE: Paragraph spacing needs to be updated. do.
[0011] Upon receiving the request with the key, the service provider may access the key contained in the request and, if necessary, decrypt or have it decrypted before processing the request. It may also perform other operations, such as by verifying the digital signature of the request or verifying whether the execution of the request complies with any applicable policies. Other details of the operations that may be performed are described in further detail below.
[0012] An exemplary example of an environment 100 in which various embodiments may be implemented is shown in FIG. 1. In the environment 100, a customer 102 transmits a request 104 to a service provider 106. The customer 102 may, for example, utilize the services of the service provider 106. The service provider may provide any type of service related to data that may be utilized by the customer. Exemplary services include data storage services, database services, services for processing data, and the like. To submit the request 104 to the service provider 106, the customer 102 may utilize one or more customer devices to transmit the request, such as a personal or laptop computer, a handheld device, a tablet computing device, an e-book reader, and / or others as described in more detail below in connection with FIG. 15. Additionally, the request 104 may be submitted according to one or more automated processes of the customer 102. For example, the request 104 may be submitted as a result of human operation of the customer 102's device interacting with a browser or other application running on the customer 102's device. The request 104 may be an electronic request transmitted over a network, such as the Internet or other network, or a combination of networks as described below. In some embodiments, for example, request 104 is a web service request to a web service interface provided by service provider 106. In general, request 104 may be structured according to a variety of protocols to enable the request to be submitted electronically.
[0013] As shown in FIG. 1, the request 104 includes data 108 and an encryption key 110. The data may include a variety of information and may be formatted in a variety of ways according to various embodiments. For example, in some embodiments, the data is organized as a file, such as a media file. The data may be formatted in other ways. The data may be organized for inclusion in a database or otherwise. The encryption key 110 may be a key used to encrypt the data 108 or otherwise perform one or more encryption operations on the data, as described in more detail below. It should be noted that the encryption key 110 may be included in the request 104 in a variety of ways, as described in more detail below. For example, in some embodiments, the request 104 includes the encryption key 110 in a clear text form. In other embodiments, the request 104 includes the encryption key in an encrypted form. For example, the encryption key 110 may be encrypted with another key, as described in more detail below, to allow the service provider 106 or another system associated with the other key to decrypt the encryption key 110. Thus, when a request 104 is presented by a customer 102 to a service provider 106, the service provider 106 may use an encryption key 110 to encrypt the data 108 received in the request 104, thereby generating encrypted data 112.
[0014] The encrypted data 112 may then be stored in a data storage system 114. Although the data storage system 114 is shown as being separate from the service provider 106, it may be a subsystem of the service provider 106. For example, the request 104 may be presented to a web server of the service provider 106, which is configured to provide access to the data storage system 114. In general, the data storage system 114 may be operated as a service to customers, thereby allowing the customers to utilize the resources of the service provider 106 for the purpose of storing data. In other embodiments, the data storage system 114 and the service provider 106 may also be separate. The data storage system 114 may be operated by an entity that is a third party between the service provider 106 and the customer 102, for example, or in some embodiments, the data storage system 114 may be a subsystem of the customer 102, i.e., a subsystem of the system of the customer 102. It should be noted that terms such as "customer" and "service" provider may have many meanings, which will be clear from the context. For example, the term "customer" may refer to an entity (e.g., a legal entity such as an organization or individual) or a system (e.g., a computing device or a network of computing devices) that supports the operation of a customer entity. Similarly, the term "service provider" may refer to a legal entity or system that supports the operation of a service provider entity.
[0015] As shown in FIG. 1, when encrypting the data 108 to generate the encrypted data 112, the service provider 106 may perform one or more operations to prevent the service provider 106 from accessing the encryption key 110. This is depicted in FIG. 1 as the service provider 106 passing the encryption key 110 to an icon labeled a trash can. It should be noted that while the figures show the encryption key 110 being passed to a trash can for ease of illustration, in various embodiments, the operation to prevent access to the encryption key 110 may not necessarily involve the transfer of the encryption key 110. For example, in some embodiments, in response to receiving the request 104 and using the encryption key 110, the service provider 106 may perform one or more operations to destroy the encryption key 110. The destruction of the encryption key 110 may be performed in various ways according to various embodiments. For example, in some embodiments, the encryption key 110 and the request 104 are not persistently stored by the service provider 106, but are maintained in volatile memory on-board the service provider's 106 device.
[0016] Destruction of the encryption key 110 may be performed by allowing one or more memory locations in which the encryption key 110 is stored to be overwritten with other data, such as data received as part of a subsequent request. Other operations may also be performed. For example, if the encryption key 110 is stored in a volatile or non-volatile memory, the encryption key 110 may be destroyed by overwriting one or more memory locations used to store the encryption key 110 with other data, such as random data or non-random data, such as a series of zero data (e.g., via one or more write operations intended to destroy the encryption key). In general, any operation that revokes the service provider 106's access to the encryption key 110 may be utilized. In this manner, the customer 102 may present a request to the service provider 106 with an encryption key that the customer 102 desires to be used to encrypt the data 108. Additionally, the service provider 106, in various embodiments, is configured to prevent access to the encryption key 110 after it has been used, so that the service provider can assure the customer 102 that once the request 104 is processed, the data 108 will not be accessible by decryption of the decrypted data 112. In other words, the security of the data 112 is ultimately controlled by the customer 102, with the service provider 106 having limited access to the data for a limited time.
[0017] It should be noted that while various processes resulting in encrypted data (and corresponding decrypted data) are used for illustrative purposes throughout, these various processes may vary according to other embodiments. For example, the exemplary encryption process shown herein illustrates encryption with a key provided by the service provider's customer, where the encryption is performed in a manner that denies the service provider access to the key used after a certain time has passed. However, more complex schemes may be utilized, where more than one key is used to control access to the data. For example, with reference to FIG. 1, in some embodiments, the data may be encrypted with both a key provided by the customer in the request and a key held by or accessible to the service provider. In this manner, cooperation between the customer 102 and the service provider 106 is required to access the data 108, in order to have the ability to decrypt the encrypted data. In some embodiments, for example, the data 108 may be encrypted with one key and then re-encrypted with another key. In other embodiments, the encryption key 110 may be combined with another key to generate yet another key, which is used to encrypt the data 108. Such variations may apply to many parties in addition to the customer 102 and the service provider 106. Thus, generally, coordinated action by multiple entities is required to lawfully access encrypted data, i.e., data in clear text form. Other variations are considered within the scope of this disclosure.
[0018] In addition, although various embodiments described herein have described requests having certain types of data, the request may include other types of data. For example, the request may include data about various parameters of the request, which may be used by the service provider to determine whether and / or how to implement the request. In general, requests as described herein are simplified for ease of explanation. The request may include various data appropriate to the context, such as, for example, an identity of the requestor, a network address from which the request originates, an identity of an entity that generated some or all of the request and / or other types of data.
[0019] Additionally, while FIG. 1 illustrates the request 104 having data 108 to be encrypted, it should be noted that a request within the scope of this disclosure does not necessarily have data to be encrypted. For example, in some embodiments, a request may have a reference to data (e.g., an identifier for a data object, which may be in the form of a URL) that is not necessarily included in the request. Processing such a request may include retrieving the data using the reference. As another example, a request may be missing data because the request includes retrieving data as one or more requested operations. A request to retrieve data may include an encryption key, but the data may be stored elsewhere. Processing the request may include accessing the encrypted data and decrypting it using the encryption key provided in the request. Other variations are considered within the scope of this disclosure.
[0020] An exemplary embodiment of an environment of a service provider 200 according to various embodiments is shown in FIG. 2. As shown in FIG. 2, the service provider 200 includes a customer interface 202. The customer interface may be a subsystem of the service provider 200. This interface allows for submission of requests from customers that may be processed by the service provider 200, as described above in connection with FIG. 1. Thus, the customer interface may include suitable computing devices to provide customers with the ability to submit requests to the service provider 200. The customer interface may include, for example, one or more web servers configured to receive requests via the Internet or another network. Although not illustrated as such, other infrastructure may be included in the customer interface 202. Such infrastructure may include suitable network equipment to enable the customer interface 202 to operate properly for the customers of the service provider 200.
[0021] When a request is received through customer interface 202, it may be received along with appropriate authentication information. For example, as shown in FIG. 2, request 204 may be received along with a signature 206 of the request. This signature may be generated according to various embodiments. For example, the customer submitting request 204 may generate signature 206 using secret information shared between the customer and service provider 200. As another example, the customer may have signed request 204 using a private key of a private / public key pair using an asymmetric digital signature scheme. In general, any type of information used to authenticate request 204 may be used, and in some embodiments, the request may be submitted without such information. Additionally, in some embodiments, a digital signature for the request is generated using a different cryptographic key than the cryptographic key provided in the request, while in some embodiments, the digital signature is generated using the same key provided in the request.
[0022] However, as shown in FIG. 2, when the request 204 is received through the customer interface 202, the request 204 is provided (e.g., via the internal network of the service provider 200) to an authentication system 208 of the service provider 200 along with the signature 206. Alternatively, a portion of the request sufficient to generate the electronic signature 206 may be provided rather than the entire request. The authentication system 208 may be a subsystem of the service provider 200 configured to authenticate the request, such as by verifying the electronic signature provided with the request. Upon verifying the signature 206 of the request 204, the authentication system 208 may provide a response to the customer interface 202, thereby indicating whether the signature 206 is valid. The device of the customer interface 202 may use the information provided by the authentication system 208 to determine how to process the request 204. For example, if the authentication system 208 indicates that the signature 206 is invalid, the customer interface 202 may reject the request. Similarly, if information from authentication system 208 indicates that signature 206 of request 204 is valid, customer interface 202 may cause request 204 to be processed.
[0023] Although not shown in the drawings, the authentication system 208, or another system operating within or on behalf of the service provider 200, may be operational to perform other operations in connection with determining how to handle a request. For example, the authentication system 208, or another system operating in conjunction therewith, may be used to determine one or more policies that may be critical to whether a request can be fulfilled. The policy determination may be based at least in part on a variety of factors, including the identity of the requestor submitting the request, the time, a logical identifier of the location where the data is or may be stored, and other information appropriate to the context. The policies may be handled through appropriately configured application programming interface (API) calls through the customer interface 202 or another interface.
[0024] Returning to the embodiment shown in FIG. 2, if the authentication system 208 determines that the signature 206 is valid, the customer interface 202 may decide to process the request. Processing the request may require transferring encrypted data 210 between the customer interface 202 and the request processing infrastructure 212. The request processing infrastructure 212 may comprise one or more devices that collectively operate to provide the services of the service provider 200. For example, as shown in FIG. 2, the request processing infrastructure may comprise a number of data storage systems 214 used to store data on behalf of the customers of the service provider 200. Although not shown, other infrastructures may be included, including network communication infrastructures. For example, the movement of data over a network between the customer interface 202 and the request processing infrastructure 212 may occur in a variety of ways according to various embodiments, depending on the various requests that may be submitted through the customer interface 202. For example, if the request 204 is a request to store data, the customer interface may encrypt the data using a key provided in the request 204 and transmit the encrypted data 210 to the request processing infrastructure 212 for storage in one or more of the data storage systems 214.
[0025] Similarly, if the request 204 is a request to read data, the customer interface 202 may send a communication to the request processing infrastructure 212, which may provide the customer interface 202 with data retrieved from one or more of the data storage systems 214. The customer interface 202 may then use the key provided in the request 204 to decrypt the encrypted data 210 and provide the decrypted data to the customer who submitted the request 204. It should be noted that the service provider 200 environment depicted in FIG. 2 is simplified for illustrative purposes and may include numerous other devices and subsystems, such as an accounting system that keeps track of a customer's usage of the service provider 200. Additionally, the service provider 200 may include facilities located in various geographic locations for redundancy and / or availability purposes.
[0026] An exemplary embodiment of a request 300 according to various embodiments is shown in FIG. 3. In this case, the request may be as described above in connection with FIGS. 1-2. As shown in the embodiment shown in FIG. 3, the request 300 includes a symmetric key. The symmetric key may be a cryptographic key used to both encrypt and decrypt data. In one embodiment, the symmetric key 302 of the request 300 is provided in plaintext form in the request 300. It should be noted that while in some embodiments the symmetric key is provided in plaintext form in the request 300, the transfer of the request from the customer to the service provider, or generally between entities, may require various protocols to ensure the security of any data included in the request 300. For example, the transfer of the request 300 may require transport layer security (TLS) and / or another protocol, such that the symmetric key 302 is encrypted during transmission from one entity to another. Additionally, although FIG. 3 illustrates the request 300 having a symmetric key 302, the request 300 may include other data not shown in the figures. Such data as described above may include various request parameters, authentication information, data to be encrypted, and / or other information.
[0027] In addition, while FIG. 3 illustrates a request with a key, as with all requests described and illustrated herein, various other data may be stored in the request. Such data may include the data to be operated on and / or various metadata, including contextual information about the request and authentication information that may be used to verify the authenticity of the request. Various request parameters may be included in the request. For example, a request parameter may specify that server-side encryption is to be used to encrypt the data using a key provided with the request. In the absence of such a parameter and / or indicative of no use of server-side encryption, the request may be processed without encryption regardless of whether a key is included in the request. Additionally, in the case of requests presented with a digital signature, a parameter may specify which portion of the request was used to generate the digital signature. Such a parameter may indicate which portion of the request should be used to verify the digital signature, which may allow requests to be modified after they are generated, such as by adding data to be operated on during execution of the request. In general, requests are simplified in this disclosure for ease of explanation.
[0028] An illustrative example of a process 400 that may be used to send and receive a response to a request according to various embodiments is shown in FIG. 4. Process 400 may be performed by any suitable system, such as a customer device as described above and below in connection with FIG. 15. In one embodiment, process 400 includes obtaining 402 an encryption key. The encryption key may be obtained in 402 in various ways according to various embodiments. For example, in some embodiments, the encryption key is obtained in 402 by generating the encryption key. The encryption key may be generated using, for example, a random number generator or a key derivation function such as public key derivation function 2 (PPKDF2) or Bcrypt. The encryption key may be obtained in other ways as well 402. For example, the encryption key may be accessed from a data storage device. As another example, the encryption key may be a password, passphrase, or other type of passcode accessed from memory and / or entered by a user of the system executing process 400. In general, any method may be used for obtaining 402 the encryption key.
[0029] Having obtained the encryption key at 402, the process 400 may include generating a request with the obtained encryption key (i.e., generating a request including the obtained encryption key) at 404. The request may be generated by arranging the data for the request in a manner suitable for transmission according to a format that can be processed by the system to which the request is to be presented. Once generated at 404, the generated request may be submitted at 406. Submitting the generated request at 406 may be performed in any suitable manner, such as by sending the generated request to an Internet Protocol (IP) address of a web server configured to receive the generated request. Other operations may also be performed, for example, in some embodiments, the request is generated from a uniform resource locator (URL). Communication with a domain name service (DNS) may occur to obtain an IP address of the system to which the generated request is then submitted at 406. In general, any method may be performed to issue the request.
[0030] Once submitted, the request may be processed by the system to which the generated request was submitted 406. Thus, process 400 may include receiving 408 a response to the request, or the response may be an appropriately configured response depending on the protocol used to submit the request. It should be noted that receiving a response to the request is not required for all embodiments. For example, some protocols may allow a request to be submitted without acknowledgment that the request was received and / or performed. As an illustrative example, the request may be a request to store data. In some embodiments, once submitted, the request may be considered to have been processed or may have already been processed if acknowledgment of the processing of the request may not be required.
[0031] An illustrative example of a process 500 for processing a request is shown in FIG. 5, where the request may be received as described above or submitted according to a process such as process 400 as described above. Process 500 may be performed by any suitable system, such as by a device (e.g., a server) operative to provide a customer interface as described above. In one embodiment, process 500 includes receiving 502 a request with an encryption key. The request may be received at 502 in various ways according to various embodiments. For example, the request may be submitted over a network according to a communication protocol as described above or the request may be received according to such a protocol. In general, the request may be received at 502 using any suitable method.
[0032] Upon receiving the request, process 500 may include determining 504 whether to implement the request. The determination 504 of whether to implement the request may be made in various ways according to various embodiments. For example, as described above, in some cases, the request may be received along with a digital signature of the request. Thus, the determination may be made by determining whether the signature is valid. The determination of whether the signature is valid may be performed in various ways. For example, the system performing process 500 may verify the signature itself, or may transmit the signature and the request (or generally, the data that was signed to generate the signature) to another system operable to verify the digital signature. Additionally, as described above, the decision 504 of whether to implement the request may include performing a determination of whether one or more policies preclude implementation of the request. In general, any method may be performed in determining whether to implement the request.
[0033] Additionally, while FIG. 5 and other processes depicted herein depict a determination of whether to implement a request, in various embodiments, the system may implement any appropriately configured request without the need for a valid electronic signature and / or compliance with a policy. Returning to the embodiment depicted in FIG. 5, if a determination is made at 504 not to implement the request, such as when the signature is invalid and / or a policy precludes implementing the request, process 500 may include rejecting 506 the request. Rejecting 506 the request may be performed in various ways according to various embodiments. For example, a response to the request may be provided indicating that the request was denied and / or providing information regarding why the request was rejected. As another example, rejecting the request may simply be performed by taking no action, i.e., by not providing a response to the request and simply not implementing the request. In general, any manner in which a request may not be implemented may be considered as rejecting the request.
[0034] However, if it is determined to implement the request, the process 500 may include extracting 508 a cryptographic key from the request. The extracted cryptographic key may then be used at 510 to perform one or more requested cryptographic operations, i.e., to perform one or more cryptographic operations involved in implementing the request. The one or more cryptographic operations may vary depending on various embodiments and even depending on the type of request received. In some embodiments, for example, the one or more cryptographic operations may include encryption of data included in the request and / or encryption of other data. As another example, the one or more cryptographic operations may include decryption of data referenced by and / or provided in the request. In general, any type of cryptographic operation may be performed as part of the one or more cryptographic operations, such as key derivation and / or digital signature generation and / or verification. Furthermore, while various exemplary embodiments described herein have shown a single cryptographic operation, such as encryption, many types of cryptographic operations may be performed in implementing a request. As an example, one or more keys provided in the request may be used to encrypt data and generate a digital signature for the data and / or the encrypted data. In this case, the digital signature can be used to later verify that the data has been modified. Other variations are considered to be within the scope of this disclosure.
[0035] Upon performing one or more cryptographic operations, process 500 may include providing 512 a response to the request. This response may vary depending on various embodiments and also depending on the type of request made. For example, if the request was to read data, the response may include the data that was read and decrypted. If the request was to store data, the response may be an acknowledgement that the data was stored. A checksum or other verification information may be provided with the response. At some point after performing one or more cryptographic operations involved in fulfilling the request, process 500 may include disabling 514 access to the extracted cryptographic key. In this case, access may be lost in a variety of ways, as described above.
[0036] An exemplary embodiment of a request 600 according to various embodiments is shown in Figure 6. As shown in Figure 6, unlike the request described above in connection with Figure 3, the request 600 includes a customer public key 602. This key may be the public key of a public / private key pair, where the private key is held by or on behalf of the customer. As with other requests described herein, the request 600 may include other data as described above. The request 600 may be presented as described above in connection with Figure 4.
[0037] An exemplary embodiment of process 700 is shown in FIG. 7. This process may be used to process a request including a customer public key as described above in connection with FIG. 6. Process 700 may be performed by any suitable system, such as a system that provides a customer interface as described above. As shown in FIG. 7, process 700 includes receiving 702 a PUT request with a customer public key, in other words a PUT request having a customer public key as part of the request (i.e., a request to store data). The request may be received at 702 as described above, or in general in any suitable manner. Upon receiving 702 a PUT request with a customer public key, process 700 may include determining 704 whether to implement the request. In this case, the determination of whether to implement the request may be made as described above. If it is determined at 704 that the request should not be implemented, process 700 may include rejecting 706 the request as described above. However, if it is determined at 704 that the request should be implemented, process 700 may include extracting 708 the customer public key from the request for use. In one embodiment, process 700 includes obtaining 710 an encryption key. In this case, the encryption key may be a symmetric key as described above. The encryption may be obtained 710 in any suitable manner as described above. For example, the encryption key may be accessed from a data store or may be generated. The encryption key obtained 710 may be used 712 to encrypt data provided in the request or data requested by the request to be encrypted. The customer public key may be used 714 to encrypt (wrap) the encryption key. In this manner, the encrypted encryption key is decryptable using the private key corresponding to the customer public key. Thus, if the provider performing process 700 does not have access to the encrypted encryption key, the provider will not be able to decrypt the encrypted encryption key.
[0038] Process 700 may include storing 716 the encrypted data. The encrypted data may be sent, for example, to a data storage system for persistent storage of the data. A response to the request may be provided 718 including the encrypted encryption key. The system executing process 700 may revoke 720 access to the encryption key as described above. Thus, once the system executing process 700 loses access to the encryption key 720, it can no longer decrypt the encrypted data. Thus, the use of a private key corresponding to the customer public key is generally required to decrypt the encrypted data legitimately (i.e., without guessing the key or otherwise gaining access to the data in an unauthorized manner) by first decrypting the encryption key to decrypt the decrypted data.
[0039] It should be noted that, as with any process described herein, variations are considered to be within the scope of this disclosure. As an example, a process for processing a PUT request is shown in FIG. 7, where the request includes a customer public key. Such requests can be processed in various ways according to various embodiments. In some embodiments, for example, the customer public key may be used to encrypt data received in the request instead of using an encryption key that is then wrapped by the public key, although using a symmetric encryption key is generally more computationally efficient. In this way, the data can only be decrypted by an entity that has access to the private key that corresponds to the customer public key. This entity, in various embodiments, may be only the customer that issued the request.
[0040] As another example of a variation considered within the scope of this disclosure, the encrypted encryption key may be stored with the encrypted data and may or may not be transmitted in response to a request. In such an embodiment for decrypting data, the encryption key may be accessed from a storage device provided to an entity capable of decrypting the encryption key (e.g., a customer who has a private key that can be used to decrypt the encryption key). The storage device may then return a decrypted encryption key to enable decryption of the data. For example, upon a customer request to read the data, the provider may send an initial response (including the encrypted encryption key), including a notification that the encryption key will be required for decryption. The customer may decrypt the encryption key and return the decrypted encryption key to the provider, thereby allowing the provider to determine whether the encryption key is required. Cipher The provider may be able to decrypt the encrypted data and provide the decrypted data to the customer. Other variations, including those in which the ciphertext is provided by the provider to the customer along with an encrypted key that can be used to decrypt the ciphertext, are also considered to be within the scope of this disclosure. For example, in an embodiment in which server-side encryption is used for PUT requests but client-side encryption is used to gain access to stored data, the provider may provide instructions to properly process the data (e.g., by properly normalizing the data for decryption) or may provide executable instructions in the form of a client library to ensure that the decryption is performed correctly (i.e., to ensure that the decryption is performed in a manner that results in successful decryption of the data).
[0041] An exemplary embodiment of a process 800 for obtaining data is shown in FIG. 8. The data is stored in encrypted form by another system, such as by a provider as described above. Process 800 may be performed by any suitable system, such as by a device of a customer of the provider as described above. In one embodiment, process 800 includes obtaining 802 an encrypted encryption key. For example, the encrypted encryption key may have been received by performance of process 700 described above or a variation thereof. Obtaining the encrypted encryption key may include receiving the encrypted encryption key or accessing the encrypted encryption key from persistent data storage. In general, the encrypted encryption key may be obtained at 802 in any suitable manner.
[0042] A private key corresponding to the public key used to encrypt the encryption key may be used at 804 to decrypt the encrypted encryption key. Once the decrypted encryption key is obtained, process 800 may include generating 806 a GET request with the decrypted encryption key, and submitting (e.g., sending) 808 the generated GET request, as described above. The system receiving the GET request may process the request by using the encryption key included in the request to decrypt the data encrypted by the encryption key. A response may then be received at 810, which may include appropriate information, such as the data provided in the GET request that was decrypted using the decrypted encryption key.
[0043] As with any process described herein, variations of process 800 are considered within the scope of this disclosure. For example, when the encrypted encryption key is stored with the data encrypted under the encrypted encryption key, the encrypted encryption key may be obtained by accessing the encrypted encryption key from a remote storage device. As another example, in some embodiments, process 800 may include submitting a GET request that is implemented by providing data encrypted under the encrypted encryption key. A system performing process 800 may retrieve the encrypted data and decrypt the encrypted data using the decrypted encryption key. In other words, process 800 may be modified to decrypt the data on the client side even if the data was encrypted on the server side.
[0044] Exemplary examples of various requests are shown in FIG. 9. These requests may include encryption keys wrapped (i.e., encrypted) in various formats according to various embodiments. For example, an exemplary example of a request 902 is shown in FIG. 9 with a symmetric key 904 encrypted under a secret 906 shared with the provider, where the secret shared with the provider may be another symmetric key shared between the customer and the provider. As another example, an example of a request 908 is shown in FIG. 9 with a symmetric key 910 encrypted under a provider public key 912, where the provider public key may be a public key corresponding to a public-private key pair whose corresponding private key is accessible by the provider. Another request 914 includes a symmetric key 916 encrypted under a secret 918 shared with a third party, where the third party is an entity that is a third party to both the customer and the provider. As yet another example, a request 920 is shown in FIG. 9 with a symmetric key 922 encrypted under a third party public key 924, where the third party may be a third party to both the customer and the provider. As previously mentioned, the requests shown in FIG. 9 may include other information.
[0045] An illustrative example of a process 1000 that may be used to submit a request according to various embodiments is shown in FIG. 10. Process 1000 may be performed by any suitable system, such as by a system of a customer of the provider as described above. In one embodiment, process 1000 includes obtaining 1002 an encryption key, where the encryption key may be obtained at 1002 as described above. The obtained encryption key may be used to generate 1004 a wrapped encryption key. Such a wrapped encryption key is the encryption key obtained above, which has been encrypted under another key. An example of a wrapped encryption key has already been described in connection with FIG. 9. Process 1000 may include generating 1006 a request with a wrapped encryption key. That is, the request may be generated to include the wrapped encryption key. The generated request may then be submitted at 1008 as described above. In various embodiments, process 1000 may include receiving 1010 a response to the request submitted at 1008.
[0046] As discussed above, many embodiments are considered within the scope of this disclosure. In some embodiments, data security can be achieved by the interaction of a customer and a service provider without the use of a third party system to unwrap the key required for the cryptographic operation. Thus, an illustrative example of an environment 1100 in which various embodiments can be implemented is shown in FIG. 11. Similar to FIG. 1, but as shown in FIG. 11, the environment 1100 includes a customer 1102 that submits a request 1104 to a service provider 1106. In this example, the request 1104 includes an encryption key 1108. This encryption key is wrapped by another key, as shown by the brackets surrounding the encryption key. The service provider 1106 has access to a key 1110 that can be used to unwrap the encryption key, thereby allowing the service provider 1106 to perform the cryptographic operation using the encryption key 1108.
[0047] An exemplary embodiment of a process 1200 is shown in FIG. 12. This process may be used to process a request that includes a wrapped encryption key. Process 1200 may be performed by any suitable system, such as by a web server of service provider 1106 described above in connection with FIG. 11. In an embodiment, process 1200 includes receiving 1202 a request having a wrapped encryption key. A decision may be made at 1204 whether to implement the request. If it is determined at 1204 not to implement the request, process 1200 may include rejecting 1206 the request as described above. However, if it is determined at 1204 that the request should be implemented, process 1200 may include extracting 1208 the wrapped encryption key from the request.
[0048] A key usable to unwrap the encryption key may be obtained at 1210. Obtaining the key usable to unwrap the encryption key may be performed in various ways according to various embodiments. For example, the key usable to unwrap the wrapped encryption key may be stored by a system performing process 1200. An identifier of the key usable to unwrap the wrapped encryption key may be used to look up the key usable to unwrap the wrapped encryption key from other keys that may be stored by the system. This identifier may be provided in the request received at 1202 or may be determined, such as by cooperation with the entity that submitted the request. Once the key usable to unwrap the wrapped encryption key is obtained at 1210, process 1200 may include using 1212 the obtained key to unwrap the wrapped encryption key. In this manner, an unwrapped encryption key is obtained. The unwrapped encryption key may be used at 1214 to perform one or more cryptographic operations involved in implementing the request received at 1202. A response to the request may be provided at 1216 as described above, preventing access to the unwrapped encryption key at 1218.
[0049] In some embodiments, as previously discussed, third party involvement is part of maintaining the security of the data. Thus, an illustrative example of an environment 1300 in which various embodiments may be implemented is shown in FIG. 13. The illustrated environment 1300 includes a customer 1302 that presents a request 1304 to a service provider 1306 as described above. Also, as described above, the request 1304 may include an encryption key 1308 that has been wrapped by another key as described above in connection with FIG. 9. However, in the example of FIG. 13, a subsystem of the service provider 1306 that receives the request (or, in some embodiments, all subsystems of the service provider) may not have access to a key that can be used to unwrap the encryption key 1308. Thus, the environment 1300 includes a key management system 1310 that has access to a key 1312 that can be used to unwrap the wrapped encryption key 1308. The key management system 1310 may be any system operable to manage encryption keys on behalf of one or more customers of the service provider 1306.
[0050] The key management system 1310 may be implemented in various ways according to various embodiments. In some embodiments, the key management system may be a subsystem of the service provider 1306. The subsystem may be implemented, for example, by a hardware security module (HSM) hosted by the service provider 1306 or another type of security module that securely stores encryption keys. In some embodiments, the key management system 1310 is implemented as a separate service of the service provider 1306. This service may be one of several services offered by the service provider 1306 and may be accessible to the customer 1302 over a network as described below. In some embodiments, the key management system is a system as described above, but implemented by a third party to the service provider 1306 and the customer 1302. In such an embodiment, neither the customer 1302 nor the service provider 1306 has access to a key that can be used to unwrap the encryption key 1308 unless the key 1312 that can be used to unwrap the encryption key has been shared with one or more of the customer 1302 or the service provider 1306. Other variations are considered within the scope of this disclosure. For example, the key management system 1310 may be implemented as part of the customer 1302 in some embodiments. In general, the key management system 1310 is a system with which the service provider 1306 must communicate to unwrap, or generally become unwrapped, the encryption key 1308 with a key 1312 that can be used to unwrap the encryption key. Communication between the service provider 1306 and the key management system 1310 may occur over one or more networks and in accordance with one or more suitable network protocols. The network may be, for example, the Internet or any suitable network as described below.
[0051] An exemplary embodiment of a process 1400 is shown in FIG. 14. This process may be performed to process a request including a wrapped encryption key as described above in connection with FIG. 13. In one embodiment, the process 1400 includes receiving 1402 a request with a wrapped encryption key as described above. As described above in connection with other processes, a decision may be made at 1404 as to whether to implement the request, and if it is determined at 1404 that the request should not be implemented, the process 1400 may include rejecting 1406 the request. On the other hand, if it is determined at 1404 that the request should be implemented, the process 1400 may include extracting the wrapped encryption key from the request. The wrapped encryption key may be sent to an unwrapping system at 1410. This system may be a key management system as described above in connection with FIG. 13, or generally any system with access to a key that can be used to unwrap the wrapped encryption key.
[0052] The wrapped encryption key may be sent to the unwrapping system in the form of a request. The request is suitably configured for execution by the unwrapping system. For example, the request may be formatted according to a format accessible to the unwrapping system and may include information usable by the unwrapping system to determine whether to execute the request. Such information may include, for example, authentication information used to authenticate the request to the unwrapping system and / or the request received at 1402 with the wrapped encryption key. For example, the request may provide other information that may be used to determine whether execution of the request to the unwrapping system complies with one or more policies, or the information may be contextual data, as described above. Another piece of information may include an identifier of a key that can be used to unwrap the wrapped encryption key. If the unwrapping system is to execute the request sent at 1410, the process 1400 may include receiving 1412 the unwrapped encryption key from the unwrapping system. The unwrapped encryption key may be used at 1414 to perform one or more cryptographic operations involved in executing the request received at 1402. A response to the request may be provided at 1416 as described above, preventing access to the unwrapped encryption key at 1418.
[0053] Embodiments of the present disclosure can be described in light of the following clauses. 1. A computer-implemented method comprising: Under the control of one or more computer systems of the service provider, the one or more computer systems being configured with executable instructions; receiving a request from a requestor corresponding to a customer of the service provider, the implementation of the request including performing one or more cryptographic operations on data provided with the request and using a cryptographic key provided in the request, the service provider not having access to the cryptographic key until the time of receiving the request; implementing the request by using the provided cryptographic key as part of performing the one or more cryptographic operations on the specified data; providing a result of performing the one or more cryptographic operations to a data storage system; and performing one or more operations that render the cryptographic key inaccessible to the service provider at a time after performance of the one or more cryptographic operations. 2. The computer-implemented method of claim 1, wherein executing the request includes parsing the request to extract the cryptographic key from the request in plaintext form. 3. The encryption key is a public key of a public-private key pair that is not accessible to the service provider; 3. The computer-implemented method of claim 1 or 2, wherein the one or more cryptographic operations include performing an asymmetric algorithm with the public key. 4. The encryption key provided in the request is encrypted under another key; The computer-implemented method further includes decrypting the encryption key provided in the request; 4. The computer-implemented method of any one of clauses 1 to 3, wherein performing the one or more cryptographic operations using the supplied cryptographic key includes performing the one or more cryptographic operations using the decrypted supplied cryptographic key. 5. The computer-implemented method of any one of clauses 1 to 4, wherein decrypting the encryption key provided in the request includes transferring the encryption key to another entity for decryption. 6. A system comprising: one or more processors; When executed by the one or more processors, the system includes: receiving a request from a requestor over a network, the implementation of the request including performing one or more cryptographic operations on data specified in the request using information usable to authenticate the request, including a cryptographic key supplied in the request; performing said one or more cryptographic operations on said specified data as a result of receiving and authenticating said request; and providing a result of performing said one or more cryptographic operations; a memory containing instructions for performing A system equipped with. 7. The system of clause 6, wherein the request is a request to read encrypted data from a data storage system, and the information is usable to authenticate the request using the encryption key supplied in the request. 8. The system of clause 6 or clause 7, wherein the information is usable to authenticate the request by including an electronic signature generated based at least in part on a second cryptographic key that is different from the cryptographic key supplied in the request. 9. The one or more cryptographic operations include encrypting the specified data; The system of any one of clauses 6 to 8, wherein providing the results of the one or more cryptographic operations includes transferring the specified data in encrypted form to a data storage system for persistent storage. 10. The system of any one of clauses 6 to 9, wherein the instructions further include causing the system to perform one or more operations at a time after performance of the one or more cryptographic operations to disable access to the cryptographic key provided in the request. 11. The encryption key provided in the request is in encrypted form; The instructions further include causing the system to obtain the encryption key in a decrypted form; The system of any one of clauses 6 to 10, wherein performing the one or more cryptographic operations utilizes the cryptographic key in a decrypted form. 12. The encryption key provided in the request is the public key of a public-private key pair; performing the one or more cryptographic operations on the designated data, encrypting said specified data with a symmetric key; and Encrypting the symmetric key using the public key. 12. The system of claim 6 to 11, 13. The system of any one of clauses 6 to 12, wherein the system does not have access to the encryption key until the request is received. 14. The encryption key provided in the request is provided in the request in encrypted form; the system further includes a subsystem configured to securely store, inaccessible from outside the subsystem, a plurality of encryption keys, including a particular encryption key that can be used to decrypt the encryption key provided in encrypted form; 14. The system of claim 6 through claim 13, wherein the instructions further cause the system to decrypt the cryptographic key provided in encrypted form for use in performing the one or more cryptographic operations. 15. The system of any one of clauses 6 to 14, wherein the information is usable to authenticate the request using the cryptographic key to authenticate the request. 16. A non-transitory computer-readable storage medium, which, when executed by one or more processors of a computer system, causes the computer system to: generating an application programming interface request formatted for a service provider application programming interface, the application programming interface request including a cryptographic key and specifying one or more cryptographic operations that may be performed on data by the service provider using the included cryptographic key; and enabling transmission of the generated application programming interface request, along with authentication information generated based at least in part on the application programming interface request, over a network to a service provider, thereby causing the service provider to perform the one or more cryptographic operations on the data using the cryptographic key. A non-transitory computer-readable storage medium having stored thereon instructions to cause a 17. The non-transitory computer-readable storage medium of clause 16, wherein the application programming interface request is for storing data in a data storage system of the service provider, and the one or more cryptographic operations include encrypting the data before storing it in the data storage system. 18. The non-transitory computer-readable storage medium of clause 16 or clause 17, wherein the application programming interface request is for reading data in a data storage system, the data being stored in the data storage system in encrypted form, and the one or more encryption operations include decrypting the data after reading it from the data storage system. 19. The non-transitory computer-readable storage medium of clauses 16 to 18, wherein the encryption key is included in the application programming interface request in encrypted form, such that the service provider can use the encrypted form of the encryption key to obtain an unencrypted form of the encryption key for use in performing the one or more cryptographic operations. 20. The non-transitory computer-readable storage medium of any one of clauses 16 to 19, wherein the encryption key is inaccessible to the service provider until receipt of the request. 21. The non-transitory computer-readable storage medium of any one of clauses 16 to 20, wherein the transmitted application programming interface request is devoid of data. 22. The non-transitory computer-readable storage medium of any one of clauses 16 to 21, wherein the authentication information is generated based at least in part on another cryptographic key that is different from the cryptographic key included in the application programming interface request. 23. The non-transitory computer-readable storage medium of clauses 16 to 22, wherein the application programming interface request further includes information required by the service provider to determine whether implementation of the request complies with one or more policies applicable to the request.
[0054] As noted at various times throughout the disclosure above, many other variations are considered within the scope of the present disclosure. For example, as noted above, many variations utilize symmetric and / or asymmetric cryptographic primitives. Symmetric key algorithms may include a variety of methods for performing cryptographic operations on data, including block ciphers, stream ciphers, and digital signature methods. Exemplary symmetric key algorithms include, but are not limited to, advanced encryption standard (AES), data encryption standard (DES), triple DES (3DES), Serpent, Twofish, Blowfish, CAST5, RC4, and the international data encryption algorithm (IDEA). Symmetric key algorithms may also include those used to generate the output of one-way functions, including, but are not limited to, hash-based message authentication code (HMAC), message authentication code (MAC) in general, PBKDF2, and algorithms utilizing Bcrypt. Asymmetric key algorithms may also include different methods for performing cryptographic operations on data.Exemplary algorithms include, but are not limited to, those using the Diffie-Hellman key exchange protocol, the digital signature standard (DSS), the digital signature algorithm, the ElGamal algorithm, various elliptic curve algorithms, password-authenticated key agreement techniques, the pallier cryptosystem, the RSA encryption algorithm (PKCS#1), the Cramer-Shoup cryptosystem, the YAK authenticated key agreement protocol, cryptosystems using NTRU cryptography, the McEliece cryptosystem, etc. Elliptic curve algorithms include the elliptic curve Diffie-Hellman (ECDH) key exchange scheme, the Elliptic Curve Integrated Encryption Scheme (ECIES), the Elliptic Curve Digital Signature Algorithm (ECDSA), the ECMQV key exchange scheme, and the ECQV implicit certificate scheme. Other algorithms and combinations of algorithms are considered to be within the scope of this disclosure.
[0055] Additionally, as previously discussed, various embodiments of the present disclosure relate to the use of cryptographic keys included in requests to perform various cryptographic operations. While these keys have been described as being used to perform such operations, it should be noted that various embodiments of the present disclosure include cases where the keys are transformed in some manner before use. As an example, if the key included in the request is a passcode, the passcode may be transformed (e.g., using a key derivation function) before being used to perform another cryptographic operation. Furthermore, while the disclosure above describes certain types of keys (e.g., cryptographic keys), such keys may be similarly transformed before use. Other variations include providing multiple keys in the request and specifying how the multiple keys should be used in the request parameters and / or request formatting.
[0056] Other variations considered within the scope of this disclosure include embodiments utilizing signed uniform resource locators (URLs). Referring to an environment such as that depicted in FIG. 1, including a customer of a service provider, the customer may pre-generate a URL that includes a digital signature for a portion of the URL and / or other information, such as a cryptographic key. The customer may provide this URL to another entity, which may use the URL to submit a request to the service provider, causing the service provider to perform one or more operations under the customer's authentication. The service provider may receive the request submitted with the URL, verify the digital signature, and perform one or more operations using the key provided in the URL. In this manner, various benefits are obtained, including server-side encryption and decryption with customer control of the key, and inaccessibility of the provider's key except when necessary. The use of signed URLs and variations thereof is described in detail in co-filed U.S. patent application Ser. No. 14 / 037,282, entitled "Resource Locators With Keys," which is incorporated by reference in its entirety.
[0057] Aspects of an exemplary environment 1500 for implementing aspects according to various embodiments are shown in FIG. 15. It will be appreciated that while a web-based environment is used for convenience of explanation, various environments may be used to implement various embodiments, as desired. The environment includes an electronic client device 1502. The device may comprise any suitable device operable to send and receive requests, messages or information over a suitable network 1504 and to transmit information back to a user of the device. Examples of such client devices include personal computers, mobile phones, handheld messaging devices, laptop computers, tablet computers, set-top boxes, personal data assistants, embedded computer systems, e-book readers, and the like. The network may include any suitable network, such as an intranet, the Internet, a cellular network, a local area network, or other such network, or combinations thereof. The components used in such a system may depend, at least in part, on the type of network and / or environment selected. Protocols and components for communicating over such networks are well known and will not be described in detail herein. Communication over the network may be enabled by wired or wireless communication and combinations thereof. In this embodiment, the network includes the Internet because the environment includes a web server 1506 that receives requests and serves content in response thereto, however, as will be apparent to one skilled in the art, alternative devices that serve similar purposes can be used with other networks.
[0058] The exemplary environment includes at least one application server 1508 and one data storage device 1510. It should be understood that there can be multiple application servers, application tiers or other application elements, application processes, or application components, which can be coupled or otherwise configured to interact to perform tasks such as retrieving data from an appropriate data storage device. A server as used herein may be implemented in a variety of ways, such as a hardware device or a virtual computer system. In some circumstances, a server may refer to a programming module running on a computer system. The term "data storage device" as used herein refers to any device or combination of devices capable of storing, accessing, and retrieving data. This device may include any combination and number of data servers, databases, data storage devices, and data storage media in any standard, distributed, or clustered environment. An application server may include any suitable hardware and software for executing aspects of one or more applications for client devices, integrating with data storage devices as necessary, and handling some (even most) of the data access and business logic for the applications. The application server may provide access control services in conjunction with data storage devices and may generate content, such as text, graphics, audio, and / or video, that may be transmitted to users. In this embodiment, such content may be provided to users by a web server in the form of HyperText Markup Language (HTML), Extensible Markup Language (XML), or another suitable structured language. All request and response processing, as well as the passing of content between client device 1502 and application server 1508, may be performed by the web server.It should be understood that the web server and application server are not required, but are merely exemplary components, as the structured code described herein may be executed on any suitable device or host machine, such as those described elsewhere herein. Additionally, operations described herein as being performed by one device may be collectively performed by multiple devices, which may form a distributed system, unless otherwise clear from the context.
[0059] The data store 1510 may include multiple independent data tables, databases, or other data storage mechanisms and media, thereby storing data related to certain aspects of the present disclosure. For example, the illustrated data store may include mechanisms for storing production data 1512 and user information 1516, which may be used to serve content for the production side. The data store is also illustrated as including mechanisms for storing log data 1514, which may be used for reporting, analysis, or other such purposes. It should be understood that there may be many other aspects that may need to be stored in the data store, such as page image information and access rights information, which may be stored in any of the mechanisms listed above or in another mechanism within the data store 1510, as appropriate. The data store 1510 may operate through logic associated with the device to receive instructions from the application server 1508 and responsively retrieve, update, or process data. In one embodiment, a user may submit a search request for a type of item through a device operated by the user. In this case, the data store may access user information to verify the user's identity, and may access catalog details to obtain information about that type of item. This information may then be returned to the user, such as in a list of results on a web page that the user can view via a browser running on the user device 1502. Information about a particular item of interest may be viewed on a dedicated page or window in the browser. It should be noted, however, that embodiments of the present disclosure are not necessarily limited to web page related aspects, but may be more broadly applicable to the handling of requests in general, where these requests are not necessarily requests for content.
[0060] Each server typically includes an operating system that provides executable program instructions for the general management and operation of the server, and typically includes a computer-readable storage medium (e.g., a hard disk, random access memory, read-only memory, etc.) that stores instructions that, when executed by the server's processor, cause the server to perform its intended functions. Suitable implementations of server operating systems and general functions are known or commercially available, and will be readily implemented by those of skill in the art, especially in light of the disclosure herein.
[0061] In one embodiment, the environment is a distributed computing environment utilizing multiple computer systems and components interconnected via communications links, using one or more computer networks or direct connections. However, those skilled in the art will appreciate that such a system may operate similarly in systems having fewer or more components than those depicted in Figure 15. Thus, the depiction of system 1500 in Figure 15 should be considered exemplary in nature and not limiting of the scope of the present disclosure.
[0062] Furthermore, various embodiments may be implemented in a variety of operating environments. These environments may include, in some cases, one or more user computers, computing devices, or processing devices that may be used to run any number of applications. User or client devices may include any number of general purpose personal computers, such as desktop, laptop, or tablet computers running standard operating systems, as well as portable, wireless, and handheld devices running mobile software and capable of multiple network and messaging protocols. Such systems may also include multiple workstations running a wide variety of commercially available operating systems and other known applications for purposes such as development and database management. These devices may also include other electronic devices, such as dummy terminals, thin clients, gaming systems, and other devices capable of communicating over a network.
[0063] Various embodiments of the present disclosure are adapted to support communications using a wide variety of commercially available protocols utilizing at least one network as would be known to one of ordinary skill in the art, such as Transmission Control Protocol / Internet Protocol (TCP / IP), protocols operating at various layers of the Open System Interconnection (OSI) model, File Transfer Protocol (FTP), Universal Plug and Play (UpnP), Network File System (NFS), Common Internet File System (CIFS), and AppleTalk. Examples of networks include local area networks, wide area networks, virtual private networks, the Internet, intranets, extranets, public switched telephone networks, infrared networks, wireless networks, and any combination thereof.
[0064] In embodiments utilizing web servers, the web servers may run a wide variety of server or mid-tier applications, such as a Hypertext Transfer Protocol (HTTP) server, an FTP server, a Common Gateway Interface (CGI) server, a data server, a Java server, and a business application server. One or more of the servers may be capable of running programs or scripts in response to requests from user devices, such as by running one or more web applications that may be implemented as one or more scripts or programs written in any programming language, such as Java, C, C#, or C++, or any scripting language such as Perl, Python, or TCL, and combinations thereof. One or more of the servers may include a database server. Database servers include, but are not limited to, those commercially available from Oracle, Microsoft, Sybase, and IBM.
[0065] The environment may include various data storage devices and other memory and storage media as described above. These may reside in various locations, such as on storage media local to (and / or residing on) one or more computers, or remote from any or all of the computers across a network. In a particular set of embodiments, the information may reside on a storage-area network (SAN) known to those skilled in the art. Similarly, any necessary files to perform functions attributed to a computer, server, or other network device may be stored locally and / or remotely as necessary. Where the system includes computerized devices, each such device may include hardware elements that may be electronically connected via a bus, including, for example, at least one central processing unit (CPU or processor), at least one input device (e.g., mouse, keyboard, controller, touch screen, or keypad), and at least one output device (e.g., display, printer, or speaker). Such a system may also include one or more storage devices, such as disk drives, optical storage devices, and solid-state storage devices such as random access memory (RAM) or read-only memory (ROM), as well as removable media devices, memory cards, flash cards, and the like.
[0066] Such devices may also include computer-readable storage medium readers, communication devices (e.g., modems, network cards (wireless or wired), infrared communication devices, etc.), as described above, and working memory. The computer-readable storage medium readers may be connected to or configured to accept computer-readable storage media, representing remote, local, fixed and / or removable storage devices, as well as storage media, for containing, storing, transmitting and retrieving computer-readable information on a temporary and / or more permanent basis. The systems and various devices also typically include a number of software applications, modules, services, or other elements located within at least one working memory device, including an operating system and application programs, such as client applications or web browsers. It should be understood that alternative embodiments may have numerous variations from those described above. For example, customized hardware may be used as well, and / or specific elements may be implemented in hardware, software (including portable software, such as applets), or both. Additionally, connections to other computing devices, such as network input / output devices, may be employed.
[0067] Storage media and computer readable media for containing the code or portions of the code may include any suitable media known or used in the art, including storage media and communication media, such as, but not limited to, volatile and non-volatile, removable and non-removable media, implemented using any method or technology for storage and / or transmission of information, such as computer readable instructions, data structures, program modules or other data. Such media may include RAM, ROM, Electrically Erasable Programmable Read-Only Memory (EEPROM), Flash memory or other memory technology, Compact Disc Read-Only Memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage, or any other medium that can be used to store the desired information and that can be accessed by a system device. Based on the disclosure and teachings provided herein, a person skilled in the art will recognize other suitable ways and / or methods for implementing various embodiments.
[0068] Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense, however it will be apparent that various modifications and changes may be made thereto without departing from the broader concept and scope of the invention as set forth in the appended claims.
[0069] Other variations are within the concept of the present disclosure. Thus, while the disclosed techniques are susceptible to various modifications and alternative constructions, certain illustrated embodiments thereof are shown in the drawings and have been described in detail above. It should be understood, however, that there is no intention to limit the invention to the particular forms or forms disclosed, but rather, the intention is to cover all modifications, alternative constructions and equivalents falling within the concept and scope of the invention as defined in the appended claims.
[0070] Unless indicated herein or clearly contradicted by context, use of the terms "a" and "an" and "the" and similar referents in the context of describing the disclosed embodiments (particularly in the context of the claims that follow) should be construed to include both the singular and the plural. Unless otherwise indicated, the terms "comprising," "having," "including," and "containing" should be construed as open-ended terms (i.e., meaning "including, but not limited to"). The term "connected" is unmodified and, when referring to a physical connection, should be construed as being partially or wholly contained within, attached to, or joined to one another, even if there are intervening elements. Recitations of ranges of values herein, unless otherwise indicated herein, are merely intended to serve as a shorthand method of individually referring to each separate value falling within the range, and each separate value is incorporated herein as if it were individually recited herein. Use of the term "set" (e.g., a set of items) or the term "subset" should be construed as a non-empty collection containing one or more elements, unless otherwise stated or contravened by context. Furthermore, unless otherwise stated or contravened by context, the term "subset" of a corresponding set does not necessarily refer to a proper subset of the corresponding set, and a subset and a corresponding set may be equivalent.
[0071] Conjunctions such as phrases of the form "at least one of A, B, and C" or "at least one of A, B, and C" are understood with the context in which they are normally used to indicate that an item, term, etc. may be either A or B or C, or any non-empty subset of the set consisting of A, B, and C, unless expressly stated otherwise or clearly contradicted by context. For example, in an illustrative example of a set having three elements used in the above conjunctions, "at least one of A, B, and C" and "at least one of A, B, and C" refer to any of the following sets: {A}, {B}, {C}, {A,B}, {A,C}, {B,C}, {A,B,C}. Thus, such conjunctions are not generally intended to imply that an embodiment necessarily includes at least one A, at least one B, and at least one C, respectively.
[0072] The operations of the processes described herein may be performed in any suitable order unless otherwise indicated herein or clearly contradicted by context. The processes described herein (or variations and / or combinations thereof) may be performed under the control of one or more computer systems configured with executable instructions, and may be implemented by hardware or a combination thereof as code (e.g., executable instructions, one or more computer programs, or one or more applications) collectively executed by one or more processors. The code may be stored in a computer-readable storage medium, for example, in the form of a computer program including a plurality of instructions executable by one or more processors. The computer-readable storage medium may be non-transitory.
[0073] The use of any and all examples or exemplary phrases (e.g., "such as") provided herein is intended merely to better describe embodiments of the invention and does not impose limitations on the scope of the invention unless otherwise claimed. No language in the specification should be construed as indicating any non-claimed element essential to the practice of the invention.
[0074] Preferred embodiments of the present disclosure are described herein, including the best mode for carrying out the invention known to the inventors. Variations of these preferred embodiments may become apparent to those skilled in the art upon reading the foregoing description. The inventors anticipate that those skilled in the art will adopt such variations as necessary, and intend that the embodiments of the present disclosure be carried out in ways other than as specifically described herein. Accordingly, the scope of the present disclosure includes all modifications and equivalents of the subject matter recited in the claims appended hereto as permitted by applicable law. Moreover, any combination of the above-described elements in all possible variations thereof is encompassed by the scope of the present disclosure unless otherwise indicated herein or clearly contradicted by context.
[0075] All references cited in this specification, including publications, patent applications, and patents, are hereby incorporated by reference to the same extent as if each reference was individually and specifically indicated to be incorporated by reference and was set forth in its entirety herein.
Claims
1. A service provider computer receiving a request from a customer computer over a network, the request including reference data and an encrypted encryption key; the service provider computer transmitting the encrypted encryption key to a key management system for decrypting the encrypted encryption key; receiving, by the service provider computer, a decrypted encryption key from the key management system; decrypting, by the service provider computer, the encrypted data accessed by the reference data using the decrypted encryption key; providing the decrypted data to the customer's computer by the service provider's computer; 16. A computer-implemented method of data security comprising:
2. The encrypted encryption key is decrypted by the key management system using the private key of an asymmetric key pair, and the encrypted encryption key is encrypted by a customer's computer using the public key of the asymmetric key pair.
10. The computer-implemented method of claim 1.
3. The computer-implemented method of claim 1 or claim 2, wherein the request includes authentication information that can be used to verify authenticity of the request.
4. The computer-implemented method of claim 2, wherein the service provider computer does not have access to the private key of the asymmetric key pair.
5. 3. The computer-implemented method of claim 2, wherein the encrypted cryptographic key is a public key of the customer's computer.
6. A computer-implemented method as described in any one of claims 1 to 5, wherein the encrypted cryptographic key is generated using a random number generator or a key derivation function.
7. A computer-implemented method as described in any one of claims 1 to 6, further comprising destroying the encryption key to prevent the service provider's computer from accessing the decrypted encryption key.
8. A computer-implemented method as described in any one of claims 1 to 7, further comprising, after receiving the request, the service provider computer making a decision as to whether to implement the request.
9. A system comprising a customer computer, a service provider computer, and a key management system, the system comprising: receiving, by the service provider computer, a request from the customer computer over a network, the request including reference data and an encrypted encryption key; the service provider computer transmitting the encrypted encryption key to the key management system for decryption of the encrypted encryption key; receiving, by the service provider computer, a decrypted encryption key from the key management system; decrypting, by the service provider computer, the encrypted data accessed by the reference data using the decrypted encryption key; providing the decrypted data to the customer's computer by the service provider's computer; Including, the system.
10. The system of claim 9 , wherein the encryption key is a passcode for the customer.
11. 11. The system of claim 9 or claim 10, wherein the request includes a digital signature that can be used to authenticate the request.
12. A system as described in any one of claims 9 to 11, further comprising generation of an electronic signature by the customer's computer.
13. A system as described in any one of claims 9 to 12, wherein the reference data includes an object identifier.
14. A system as described in any one of claims 9 to 13, further comprising, after decrypting the data accessed by the reference data, the service provider computer destroying the decrypted cryptographic key.
15. The system of any one of claims 9 to 14, wherein the encryption key is a symmetric key.
16. the first computer communicating, over a network, to a second computer a request including the reference data and the encrypted encryption key; the second computer communicating the encrypted encryption key to a key management system for decrypting the encrypted encryption key; the key management system communicating the decrypted encryption key to the second computer; the second computer decrypts the encrypted data accessed by the reference data using the decrypted encryption key, and provides the decrypted data to the first computer; system.
17. The system of claim 16, wherein the request includes an electronic signature generated by the first computer.
18. 18. The system of claim 16 or claim 17, wherein the decrypted encryption key is rendered inaccessible to the second computer.
Citation Information
Patent Citations
Data storing method, system therefor and recording medium for data storage processing
JP2001027964A
Strong authentication token with visual output of PKI signatures
US20130198519A1
