SYSTEMS AND METHODS FOR ESTABLISHING A SECURE COMMUNICATION CHANNEL USING A BROWSER COMPONENT

• US 20100318802A1
• Filed: 11/20/2008
• Published: 12/16/2010
• Est. Priority Date: 11/20/2007
• Status: Abandoned Application

• Current Assignee: Ajit Balakrishnan
• Original Assignee: Ajit Balakrishnan
• Inventors: Balakrishnan, Ajit
• Application Number:
  US12/743,859
• Publication Number:
  US 20100318802A1
• Time in Patent Office: Days
• US Class Current: 713/172
• CPC Class Codes: G06F 21/445 by mutual authentication, e.g. between devices or programs
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 2463/061 applying further key derivation, e.g. deriving traffic keys from a pair-wise master key cryptographic mechanisms or cryptographic arrangements for generation of secret information including derivation or calculation of cryptographic keys or passwords H04L9/0861
• CPC Class Codes: H04L 63/0869 for achieving mutual authentication cryptographic mechanisms or cryptographic arrangements for mutual authentication H04L9/3273
• CPC Class Codes: H04L 63/1441 Countermeasures against malicious traffic countermeasures against attacks on cryptographic mechanisms H04L9/002
• CPC Class Codes: H04L 63/1483 service impersonation, e.g. phishing, pharming or web spoofing detection of rogue wireless access points H04W12/12
• CPC Class Codes: H04L 69/02 Protocol performance
• CPC Class Codes: H04L 9/0838 Key agreement, i.e. key establishment technique in which a shared key is derived by parties as a function of information contributed by, or associated with, each of these network architectures or network communication protocols for key exchange in a packet data network H04L63/061
• CPC Class Codes: 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

Abstract

A system for providing a secure channel for communication comprises a client comprising a browser, a secure server and a browser component installed on the client that enables a user to establish a connection with the secure server, the browser component configured to generate a first token. The secure server is configured to generate a second token, and wherein the client is provided with access to the secure server upon verification of the first token and the second token.

Claims

1. A method for authenticating a communication channel over a communication network, the method comprising:

establishing a connection between a client and a secure server;

authenticating both the secure server and the client; and

providing the client access to information and/or services on the secure server upon authentication.

2. The method of claim 1 further comprising generating a client token and a secure server token, wherein authenticating comprises verifying the client token and the secure server token.

3. The method of claim 2, wherein authenticating comprises verifying the client token by the secure server, and verifying the secure server token by the client

4. The method of claim 3, wherein the establishing connection comprises using a browser component.

5. The method of claim 3, wherein the browser component comprises a field for providing network based search.

6. The method of claim 3, wherein the client token is generated by the browser component.

7. The method of claim 2, wherein generating the client token involves processing a shared key of the secure server and a unique relative identity key of the client.

8. The method of claim 7, wherein the shared key is derived at least in part the from a unique relative identity key of the secure server.

9. The method of claim 8, wherein verifying the secure server token by the client comprises generating an encryption key from the secure server token and the unique relative identity key of the client, and comparing the generated encryption key with a known value of the encryption key.

10. The method of claim 2, wherein the secure server token is generated by the secure server.

11. The method of claim 2, wherein generating the secure server token involves processing a shared key of the client and a unique relative identity key of the secure server.

12. The method of claim 11, wherein the shared key of the client is derived at least in part the from a unique relative identity key of the client.

13. The method of claim 12, wherein verifying the client token by the secure server comprises generating an encryption key from the client token and the unique relative identity key of the secure server, and comparing the generated encryption key with a known value of the encryption key.

14. The method of claim 2, wherein the information and/or services on the secure server comprises an information stored on a secure zone on the secure server and/or services provided by the secure zone on the server.

15. The method of claim 14, wherein the secure server is a bank server, and the secure zone comprises a page providing login access to user'"'"'s account.

16. The method of claim 14, wherein the secure server is a bank server, and the secure zone comprises a page providing funds transfer by the user.

17. The method of claim 14, wherein the secure server is an identity record server, and the secure zone comprises a page providing a login access to a user'"'"'s identity record.

18. The method of claim 2, wherein the verifying occurs in parallel.

19. The method of claim 5, further comprising activating functional features on the browser component upon authentication.

20. The method of claim 19, wherein the functional features include information and/or services allowed by the secure server conditional upon authentication of the client.

21. The method of claim 2, wherein a secure gateway is associated with at least one of the secure server or the client, and wherein the secure gateway generates at least one of the token for the secure server, and the token for the client.

22. The method of claim 2, wherein a secure gateway is associated with at least one of the secure server and the client, and wherein the secure gateway verifies at least one of the client token, and the secure server token.

23. A system for providing a secure channel for communication comprising:

a client comprising a browser;

a secure server; and

a browser component installed on the client that enables a user to establish a connection with the secure server, wherein the client is provided with access to the secure server upon authentication of the secure server and the client.

24. The system of claim 23, wherein the browser component authenticates the secure server and the secure server authenticates the client based on the browser component.

25. The system of claim 24, wherein the browser component generates a client token and the secure server generates a secure server token.

26. The system of claim 23, wherein the client communicates with the secure server via a communication channel.

27. The system of claim 25, wherein the browser component further comprises a plurality of functional features that are activated upon verification of the client token and the secure server tokens.

28. The system of claim 25, wherein the browser component comprises a search field.

29. A system for providing secure communication over a communication channel, the system comprising:

a web browser;

a browser component configured to provide a secure communication channel over a network.

30. The system of claim 29, wherein the browser component is a toolbar.

31. The system of claim 30, wherein the tool bar comprises a search field.

32. The system of claim 31, wherein the toolbar provides the secure communication channel based upon an authentication of the toolbar and a remote secure server.

33. The system of claim 32, wherein the authentication comprises a mutual authentication of the toolbar and the secure server.

34. A computer readable storage medium having processor executable instructions that when executed, cause a computing device to perform a method, the method comprising:

activating a toolbar on the computing device;

establishing a connection between the computing device and an external entity;

generating a client token from the toolbar and receiving a secure server token from the external entity at the toolbar;

verifying the secure server token; and

providing the toolbar access to the external entity in response to the client token being verified by the external entity.

35. A computer readable storage medium having processor executable instructions that when executed, cause a computing device to perform a method, the method comprising:

establishing a connection between the computing device and an external entity comprising a toolbar;

receiving a client token from the toolbar and generating a secure server token by the computing device;

verifying the client token; and

providing the toolbar access to the computing device in response to the secure server token being verified by the toolbar.