# US 10,313,112 B2 · Browser security module > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,313,112 B2 - Document ID: US10313112B2 - Status: Granted - Kind: B2 - Application number: 14/980,033 - Filed: 2015-12-28 - Published: 2017-06-29 - Granted: 2019-06-04 - Earliest claimed: 2011-12-06 - Assignees: Amazon Technologies, Inc. - Applicants: Amazon Technologies, Inc. - Inventors: Nathan R. Fitch; Gregory B. Roth; Graeme D. Baer - Web page: https://patentgrep.com/patent/US10313112B2 ## CPC - H04L 9/085: {Secret sharing or secret splitting, e.g. threshold schemes} - H04L 9/0825: {using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates} - H04L 9/3226: {using a predetermined code, e.g. password, passphrase or PIN (network architectures or network communication protocols for supporting authentication of entities using passwords in a packet data network H04L63/083)} - H04L 9/3234: {involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token (network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853)} - H04L 9/3247: {involving digital signatures} - H04L 63/04: {for providing a confidential data exchange among entities communicating through data packet networks} - H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload} - H04L 63/06: {for supporting key management in a packet data network (cryptographic mechanisms or cryptographic arrangements for key management H04L9/08)} - H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP] - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Authenticated requests can be sent without requiring the requests to include or potentially expose secret information used for the authentication process. A client device use a security credential such as a key to sign a request to be sent to a recipient. When the request is received, the recipient determines whether the request was signed using the correct key for the sender. In some embodiments a client token is included with the request that statelessly encodes the key, enabling a recipient capable of decoding the client token to determine the key and compare that key to the signature of the request. The sender can store the secret information in a secure location, such as a browser security module, such that the secret information is not exposed to the browser or script executing on the client device. ## Claims ### Claim 1 A computer-implemented method, comprising: receiving a secure key via a link received at a browser on a client device from an authentication server; receiving first active content at the browser; executing the first active content, wherein the first active content causes the secure key to be stored in a security module associated with the browser, the security module having an interface enabling active content executing in the browser to cause the security module to perform one or more operations using the secure key; receiving, at the browser, second active content associated with a domain, the second active content, when executed, contacting the security module; performing, by the security module, an operation of the one or more operations using the secure key, the operation based at least in part on a characteristic of the second active content or the domain associated with the active content; and enabling the second active content to obtain a result of the operation from the security module and send a request using the result to a server to obtain content from the server upon authentication by the server that the result was produced using the secure key, without exposing the secure key to the second active content. ### Claim 2 (depends on 1) The computer-implemented method of claim 1, wherein the security module has bindings to one or more types of active content or active script, the one or more types of active content or active script enabling the secure key to be managed by the security module. ### Claim 3 (depends on 1) The computer-implemented method of claim 1, further comprising: receiving, by the security module, an outbound request to a server generated by the active content, the outbound request including information indicating the outbound request is to be signed using a specific key or credential stored at the security module; replacing, by the security module, the information with a signature generated at least in part using the specific key or credential; and causing, by the security module, the outbound request with the signature to be sent to the server. ### Claim 4 (depends on 1) The computer-implemented method of claim 1, further comprising: receiving, by the security module, an inbound message to the active content, the inbound message including at least one of a credential or signature; removing, by the security module, the at least one of a credential or signature from the inbound message; and sending, by the security module, the inbound message to the active content. ### Claim 5 (depends on 1) The computer-implemented method of claim 1, further comprising: receiving the secure key to the client device through a secure channel to the security module, the secure channel being inaccessible to the active content. ### Claim 6 (depends on 1) The computer-implemented method of claim 1, wherein the security module is operable to provide an encrypted token including the secure key with the result, the active content being unable to decrypt the encrypted token to access the secure key. ### Claim 7 (depends on 1) The computer-implemented method of claim 1, wherein the secure key is obtained by the client device by using a link fragment provided to the client device. ### Claim 8 (depends on 1) The computer-implemented method of claim 1, wherein a user is able to communicate with the security module using a first secure channel for the entry of secure information and using a second secure channel for the manipulation of metadata pertaining to an authorized use of the secure information. ### Claim 9 (depends on 1) The computer-implemented method of claim 1, wherein the result includes at least one of a request signed using the secure key, a request verified using the secure key, data encrypted using the secure key, or data decrypted using the secure key. ### Claim 10 A computer-implemented method, comprising: receiving a set of security credentials via a link received a browser on a client device from an authentication server; receiving first active script at the browser, executing the first active script, wherein the first active script causes the set of security credentials, including at least a secure key encoded by a client token, to be stored in a security module associated with the browser, the security module having an interface enabling active content executing in the browser to cause the security module to perform one or more operations using the secure key; receiving second active content, wherein the second active content, when executed in the browser, contacts the security module to produce a result using the secure key, the result including the client token; performing, by the security module, an operation of the one or more operations using the secure key, the operation based at least in part on a characteristic of the second active content; enabling the active content executing in the browser to receive-the result of the operation from the security module, without exposing the secure key to the second active content; and sending, via the second active content, a request using the result to a server to obtain content upon authentication by the server that the result was produced using the secure key. ### Claim 11 (depends on 10) The computer-implemented method of claim 10, wherein the secure key is received through a secure channel from a user or generated by the security module. ### Claim 12 (depends on 10) The computer-implemented method of claim 10, wherein the security module has bindings to one or more types of active content or active script, the one or more types of active content or active script enabling the secure key to be managed by the security module. ### Claim 13 (depends on 10) The computer-implemented method of claim 10, wherein the result includes at least one of a request signed using the secure key, a request verified using the secure key, data encrypted using the secure key, or data decrypted using the secure key. ### Claim 14 (depends on 10) The computer-implemented method of claim 10, wherein the secure key is obtained from an authentication entity through use of a fragment of the link provided to the client device. ### Claim 15 (depends on 10) The computer-implemented method of claim 10, wherein a user is able to communicate with the security module using a first secure channel for the entry of secure information and using a second secure channel for the manipulation of metadata pertaining to an authorized use of that secure information. ### Claim 16 (depends on 10) The computer-implemented method of claim 10, wherein the active content executing in the browser is determined to be able to contact the security module to produce a result using the secure key based at least in part upon at least one policy associated with the secure key. ### Claim 17 (depends on 10) The computer-implemented method of claim 10, wherein the browser and the active content are unable to access at least the secure key, the active content operable to contact the security module to sign the result using the secure key and to submit the result to the security module. ### Claim 18 A computing device, comprising: a device processor; a security module associated with a browser application on the computing device; and memory including instructions that, when executed by the device processor, cause the computing device to: receive a secure key via a link at a browser on a client device; receive first active content at the browser; execute the first active content, wherein the first active content causes the secure key to be stored in a security module associated with the browser, the security module having an interface enabling active content executing in the browser to cause the security module to perform one or more operations using the secure key; receive, at the browser, second active content, the second active content, when executed, contacting the security module to produce a result using the secure key; perform, by the security module, an operation of the one or more operations using the secure key, the operation based at least in part on a characteristic of the second active content; enable the second active content to receive the result of the operation without exposing the key to the active content; and sending, via the second active content, a request using the result to a server to obtain content upon authentication by the server that the result was produced using the secure key. ### Claim 19 (depends on 18) The computing device of claim 18, wherein the secure key is obtained from an authentication entity through use of a fragment of the link provided to the client device. ### Claim 20 (depends on 18) The computing device of claim 18, wherein the instructions, when executed, further cause the computing device to: enforce at least one policy indicating which active content of a plurality of active content is permitted to perform certain operations using the secure key.