SECURITY GATEWAY COMMUNICATION

• US 20140215642A1
• Filed: 07/20/2012
• Published: 07/31/2014
• Est. Priority Date: 07/20/2011
• Status: Active Grant

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Huxham, Horatio Nelson
• Granted Patent: US 8,909,556 B2
• Time in Patent Office: Days
• US Class Current: 726/28
• CPC Class Codes: G06Q 20/027 involving a payment switch or gateway
• CPC Class Codes: G06Q 20/3223 Realising banking transactions through M-devices
• CPC Class Codes: G06Q 20/3226 Use of secure elements separate from M-devices
• CPC Class Codes: G06Q 20/3229 Use of the SIM of a M-device as secure element
• CPC Class Codes: G06Q 20/325 using wireless networks
• CPC Class Codes: G06Q 20/3278 RFID or NFC payments by means of M-devices
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/3823 combining multiple encryption tools for a transaction
• CPC Class Codes: H04L 2463/102 applying security measure for e-commerce
• CPC Class Codes: H04L 63/02 for separating internal from external traffic, e.g. firewalls
• CPC Class Codes: H04L 63/0281 Proxies
• CPC Class Codes: H04L 63/0464 using hop-by-hop encryption, i.e. wherein an intermediate entity decrypts the information and re-encrypts it before forwarding it
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04W 12/02 Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
• CPC Class Codes: H04W 12/033 of the user plane, e.g. user's traffic
• CPC Class Codes: H04W 12/08 Access security
• CPC Class Codes: H05K 3/321 by conductive adhesives
• CPC Class Codes: Y10T 29/4913 Assembling to base an electrical component, e.g., capacitor, etc.
• CPC Class Codes: Y10T 29/53174 Means to fasten electrical component to wiring board, base, or substrate

Abstract

A gateway device and methods performed therein to prevent unauthorized client devices from connecting to the host network of the gateway device is described. The gateway device does not respond right away to an individual client message sent to the gateway device. Instead, the gateway device only responds to a predetermined sequence of the client messages, which is only known to the gateway device and authorized client devices. Because the gateway device will not respond to random client messages and the likelihood that an unauthorized client device can correctly guess the predetermined sequence of the client messages is low, the risk of a malicious party being able to hack into the host network, for example, by using port scanning techniques, can be mitigated.

Claims

1. A method in a gateway device for establishing a communication channel between a client device communicatively coupled to a client interface of the gateway device and a server communicatively coupled to a host interface of the gateway device, the method comprising:

receiving client messages on the client interface,

refraining from sending a client response message out the client interface until a predetermined sequence of client messages is received on the client interface;

sending a predetermined sequence of server messages out the host interface; and

establishing a communication channel to communicate user messages between the client device and the server, the communication channel being established after;

receiving the predetermined sequence of client messages on the client interface; and

receiving a server response message on the host interface only after the predetermined sequence of server messages has been sent by the gateway device.

2. The method of claim 1, wherein the predetermined sequence of client messages is a predetermined sequence of client synchronize messages, and the predetermined sequence of server messages is a predetermined sequence of server synchronize messages.

3. The method of claim 2, wherein the client interface comprises a plurality of client ports, and the predetermined sequence of client messages comprises client synchronize messages that are received on the plurality of client ports in a predetermined client port order.

4. The method of claim 2, wherein the predetermined sequence of server synchronize messages comprises server synchronize messages having a predetermined order of destination port identifiers.

5. The method of claim 2, further comprising:

sending, in response to receiving the predetermined sequence of client synchronize messages, a predetermined sequence of client synchronize-acknowledgment messages out the client interface; and

receiving a client acknowledge message on the client interface only after the predetermined sequence of client synchronize-acknowledgment messages has been sent by the gateway device, wherein the communication channel is established after receiving the client acknowledge message.

6. The method of claim 1, further comprising:

receiving the user messages on the established communication channel from the client device, wherein the user messages include authentication codes;

verifying, by the gateway device, the authentication codes of the user messages; and

transmitting the verified user messages to the server on the established communication channel.

7. The method of claim 1, further comprising:

receiving the user messages on the established communication channel from the client device in an encrypted format;

decrypting, by the gateway device, the user messages; and

transmitting the user messages to the server on the established communication channel.

8. The method of claim 7, further comprising:

re-encrypting, by the gateway device, the user messages prior to transmitting the user messages to the server.

9. The method of claim 7, wherein the client device is communicatively coupled to a wireless provider network, and the user messages originated from a mobile device as Short Message Service (SMS) messages or Unstructured Supplementary Service Data (USSD) messages.

10. The method of claim 7, wherein the user messages originated from a mobile device as Radio Frequency (RF) communications or Near Field Communication (NFC) communications.

11. The method of claim 7, wherein the user messages are associated with payment transactions.

12. A gateway device comprising:

a client interface including a plurality of client ports;

a host interface including a plurality of host ports;

a processor coupled to the client interface and the host interface; and

a machine readable storage medium storing executable program code, which when executed by the processor, causes the processor to;

receive client messages on the client interface from a client device,

refrain from sending a client response message out the client interface until a predetermined sequence of client messages is received on the client interface;

send a predetermined sequence of server messages out the host interface to a server; and

establish a communication channel to communicate user messages between the client device and the server, the communication channel being established after receiving the predetermined sequence of client messages on the client interface, and receiving a server response message on the host interface only after the predetermined sequence of server messages has been sent.

13. The gateway device of claim 12, wherein the predetermined sequence of client messages is a predetermined sequence of client synchronize messages, and the predetermined sequence of server messages is a predetermined sequence of server synchronize messages.

14. The gateway device of claim 13, wherein the client interface comprises a plurality of client ports, and the predetermined sequence of client messages comprises client synchronize messages that are received on the plurality of client ports in a predetermined client port order.

15. The gateway device of claim 13, wherein the predetermined sequence of server synchronize messages comprises server synchronize messages having a predetermined order of destination port identifiers.

16. The gateway device of claim 13, wherein the machine readable storage medium storing executable program code, which when executed by the processor, further causes the processor to:

send, in response to receiving the predetermined sequence of client synchronize messages, a predetermined sequence of client synchronize-acknowledgment messages out the client interface; and

receive a client acknowledge message on the client interface only after the predetermined sequence of client synchronize-acknowledgment messages has been sent, wherein the communication channel is established after the client acknowledge message is received.

17. The gateway device of claim 12, wherein the machine readable storage medium storing executable program code, which when executed by the processor, further causes the processor to:

receive the user messages on the established communication channel from the client device, wherein the user messages include authentication codes;

verify the authentication codes of the user messages; and

transmit the verified user messages to the server on the established communication channel.

18. The gateway device of claim 12, wherein the machine readable storage medium storing executable program code, which when executed by the processor, further causes the processor to:

receive the user messages on the established communication channel from the client device in an encrypted format;

decrypt the user messages; and

transmit the user messages to the server on the established communication channel.

19. The gateway device of claim 18, wherein the machine readable storage medium storing executable program code, which when executed by the processor, further causes the processor to:

re-encrypt the user messages prior to transmitting the user messages to the server.

20. The gateway device of claim 18, wherein the client device is communicatively coupled to a wireless provider network, and the user messages originated from a mobile device as Short Message Service (SMS) messages or Unstructured Supplementary Service Data (USSD) messages.

21. The gateway device of claim 18, wherein the user messages originated from a mobile device as Radio Frequency (RF) communications or Near Field Communication (NFC) communications.

22. The gateway device of claim 18, wherein the user messages are associated with payment transactions.