Setting up a security access system
First Claim
1. A machine-implemented method comprising:
- installing on a hardware system one or more instructions, which when implemented cause the hardware system to implement a process including at least,in response to receiving a request for performing a task, sending a passcode from the hardware system to a hardware module for authentication, the passcode having been previously stored on the hardware system, andgenerating the passcode from an access key that was generated from user information;
sending an access key generated from user information, from the hardware module to the hardware system to enable the hardware system to perform the generating of the passcode;
the hardware module storing one or more machine instructions, which when implemented cause the hardware module to at least implement a setup process that only requires input from the user of the hardware module without requiring input from another, and to at least send from the hardware module to the hardware system the request to perform the task at the hardware system;
wherein the access key is not stored on the hardware system after the sending of the passcode.
1 Assignment
0 Petitions
Accused Products
Abstract
In an embodiment, a secure module is provided that provides access keys to an unsecured system. In an embodiment, the secure module may generate passcodes and supply the passcodes to the unsecured system. In an embodiment, the access keys are sent to the unsecured system after receiving the passcode from the unsecured system. In an embodiment, after authenticating the passcode, the secure module does not store the passcode in its memory. In an embodiment, the unsecured module requires the access key to execute a set of instructions or another entity. In an embodiment, the unsecured system does not store access keys. In an embodiment, the unsecured system erases the access key once the unsecured system no longer requires the access key. In an embodiment, the unsecured system receives a new passcode to replace the stored passcode after using the stored passcode. Each of these embodiments may be used separately.
84 Citations
27 Claims
-
1. A machine-implemented method comprising:
-
installing on a hardware system one or more instructions, which when implemented cause the hardware system to implement a process including at least, in response to receiving a request for performing a task, sending a passcode from the hardware system to a hardware module for authentication, the passcode having been previously stored on the hardware system, and generating the passcode from an access key that was generated from user information; sending an access key generated from user information, from the hardware module to the hardware system to enable the hardware system to perform the generating of the passcode; the hardware module storing one or more machine instructions, which when implemented cause the hardware module to at least implement a setup process that only requires input from the user of the hardware module without requiring input from another, and to at least send from the hardware module to the hardware system the request to perform the task at the hardware system; wherein the access key is not stored on the hardware system after the sending of the passcode. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A machine-implemented method comprising:
-
acquiring user data; extracting user information from the user data; storing the user information; applying a one-way method to the user information, therein generating an access key; wherein the one-way method includes at least a hash function; and sending the access key from a module to a system to enable the system to generate a passcode; wherein the generated passcode is not stored on the module after the sending of the passcode. - View Dependent Claims (11, 12)
-
-
13. A machine-implemented method comprising:
-
acquiring user data; extracting user information from the user data; storing the user information; applying a one-way method to the user information, therein generating an encryption key; sending the encryption key to a system to enable the system to generate a passcode based on the encryption key; and storing the encryption key on a module; wherein the generated passcode is not stored on the module. - View Dependent Claims (14, 15)
-
-
16. A machine-implemented method comprising:
-
installing one or more instructions that require an access key on a hardware system; installing one or more instructions on the hardware system, which when implemented cause the hardware system to implement a method including at least sending a passcode, generated from an access key that is generated from user information, from the hardware system to a hardware module in response to a request to perform a task; receiving an access key generated from user information at the hardware system upon verification of the passcode; and using the access key to execute the instructions installed on the hardware system; wherein the hardware system does not store the access key. - View Dependent Claims (17, 18, 19)
-
-
20. A machine-implemented method comprising:
-
installing on a hardware system one or more machine instructions, which when implemented cause the hardware system to at least perform a requested task using an access key;
wherein the hardware system does not store the access key;the hardware module implementing a setup process that only requires input form a user of the hardware module for which the access key and passcode are generated, the process including at least acquiring user data; extracting user information from the user data; storing the user information; applying a one-way method to the user information, therein generating an access key;
wherein the one way method includes at least a hash function;the hardware module storing one or more instructions, which when implemented cause the hardware module to implement a method including at least sending the request to perform the task to the hardware system; in response to sending the request, receiving from the hardware system a passcode for authentication that was previously stored at the hardware system;
wherein the passcode was generated from the access key;comparing the passcode that was received with a passcode generated on the hardware module; and sending the access key from the hardware module to the hardware system upon verification of the passcode that was received.
-
-
21. A machine-implemented method comprising:
-
acquiring user data; extracting user information from the user data at a hardware module having at least one processor and a storage area; storing the user information in the storage area; the at least one processor applying a one-way method to the user information, therein generating the access key;
wherein the one-way method includes at least a hash function; andsending an access key from the hardware module to a hardware system to enable the hardware system to generate a passcode; wherein the generated passcode is not stored on the hardware module after the sending of the passcode. - View Dependent Claims (22, 23)
-
-
24. A machine-implemented method comprising:
-
acquiring user data at a hardware module having a processor system having at least one processor; extracting user information from the user data at the hardware module; storing the user information at the hardware module; the processor system of the hardware module applying a one-way method to the user information, therein generating the access key; the hardware module sending the encryption to s hardware system to enable the hardware system to generate a passcode based on the encryption key; and storing the encryption key on the hardware module; wherein the generated passcode is not stored on the hardware module. - View Dependent Claims (25, 26)
-
-
27. A machine-implemented method comprising:
-
installing on a hardware system one or more instructions, which when implemented cause the hardware system to implement a process including at least, in response to receiving a request for performing a task, sending a passcode from the hardware system to a hardware module for authentication, the passcode having been previously stored on the hardware system, and generating the passcode from an access key that was generated from user information; receiving an access key generated from user information, at the hardware system from the hardware module to enable the hardware system to perform the generating of the passcode; the hardware module storing one or more machine instructions, which when implemented cause the hardware module to at least implement a setup process that only requires input from the user of the hardware module without requiring input from another, and to at least send from the hardware module to the hardware system the request to perform the task at the hardware system; wherein the access key is not stored on the hardware system after the sending of the passcode.
-
Specification