PROGRAMMABLE SECURITY TOKEN

• US 20140230017A1
• Filed: 02/12/2013
• Published: 08/14/2014
• Est. Priority Date: 02/12/2013
• Status: Abandoned Application

• Current Assignee: Appsense Incorporated
• Original Assignee: Appsense Incorporated
• Inventors: SAIB, Joseph
• Application Number:
  US13/765,159
• Publication Number:
  US 20140230017A1
• Time in Patent Office: Days
• US Class Current: 726/4
• CPC Class Codes: G06F 21/34 involving the use of external additional devices, e.g. dongles or smart cards
• CPC Class Codes: G06F 2221/2137 Time limited access, e.g. to a computer or data
• CPC Class Codes: G06Q 20/3555 Personalisation of two or more cards
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263

Abstract

Systems and methods are described for programmable security token. A programmable security token includes an input interface configured to receive post-vendor customization of a parameter used to generate a security code, an authorization module configured to authorize the post-vendor customization, a configuration module configured to perform the post-vendor customization when the post-vendor customization is authorized, an execution module configured to generate the security code using at least the customized parameter, wherein the security code is suitable for an authentication server, and an output interface configured to output the generated security code.

Claims

1. A programmable security token, comprising:

an input interface configured to receive post-vendor customization of a parameter used to generate a security code;

an authorization module configured to authorize the post-vendor customization;

a configuration module configured to perform the post-vendor customization when the post-vendor customization is authorized;

an execution module configured to generate the security code using at least the customized parameter, wherein the security code is suitable for an authentication server; and

an output interface configured to output the generated security code.

2. The programmable security token of claim 1, wherein the parameter is one of a certificate, an algorithm, a seed, or a random number.

3. The programmable security token of claim 1, further comprising:

a certificate module configured to manage a certificate used to generate the security code;

an algorithm module configure to manage an algorithm used to generate the security code;

a seed module configured to manage a seed used to generate the security code; and

a random number module configured to generate a random number used to generate the security code.

4. The programmable security token of claim 1, wherein the authorization module is further configured to authorize the post-vendor customization if an authorization certificate is received at the input interface.

5. The programmable security token of claim 4, wherein the authorization certificate is a passcode.

6. The programmable security token of claim 1, wherein the authorization module is further configured to authorize the post-vendor customization a single time only.

7. The programmable security token of claim 1, wherein the input interface is in the form of a wired connection.

8. The programmable security token of claim 1, wherein the input interface is in the form of a wireless connection.

9. The programmable security token of claim 1, wherein the parameter is a certificate that is associated with a different authentication server.

10. A computerized method of using a programmable security token, comprising:

receiving, at the programmable security token, a request to customize a parameter used to generate a security code;

determining whether the request to customize the parameter is authorized;

performing the post-vendor customization of the parameter as a function of whether the request is authorized;

generating a security code using at least the customized parameter;

outputting the generated security code; and

transmitting the generated security code to an authentication server according to the customization of the parameter.

11. The computerized method of using a programmable security token of claim 10, wherein the parameter is one of a certificate, an algorithm, a seed, or a random number.

12. The computerized method of using a programmable security token of claim 10, further comprising authorizing the post-vendor customization if an authorization certificate is received.

13. The computerized method of using a programmable security token of claim 10, wherein the authorization certificate is a passcode.

14. The computerized method of using a programmable security token of claim 10, further comprising prohibiting the post-vendor customization after a previous post-vendor customization has been performed.

15. A programmable security token, comprising:

a housing;

an input interface configured to receive post-vendor customization of a parameter used to generate a security code;

a power source positioned inside the housing configured to provide power to the programmable security token;

a non-transitory computer readable medium positioned inside the housing and having executable instructions;

a processor positioned inside the housing and configured to execute the executable instructions to;

authorize the post-vendor customization of the parameter;

perform the post-vendor customization of the parameter; and

generate the security code using at least the customized parameter; and

an output interface configured to output the generated security code.

16. The programmable security token of claim 15, wherein the parameter is one of a certificate, an algorithm, a seed, or a random number.

17. The programmable security token of claim 15, wherein the executable instructions are further operable to cause the processor to authorize the post-vendor customization when an authorization certificate is received.

18. The programmable security token of claim 17, wherein the authorization certificate is a passcode.

19. The programmable security token of claim 15, wherein the executable instructions are further operable to cause the processor prohibit the post-vendor customization after a previous post-vendor customization has been performed.