Bilateral communication using multiple one-way data links

• US 8,266,689 B2
• Filed: 06/24/2011
• Issued: 09/11/2012
• Est. Priority Date: 07/19/2007
• Status: Active Grant

• Current Assignee: OWL Cyber Defense Solutions LLC
• Original Assignee: Owl Computing Technologies, Inc.
• Inventors: Menoher, Jeffrey Charles, Hope, James, Mraz, Ronald
• Primary Examiner(s): PERUNGAVOOR, VENKATANARAY
• Application Number:
  US13/167,932
• Publication Number:
  US 20110252116A1
• Time in Patent Office: 445 Days
• Field of Search: None
• US Class Current: 726/14
• CPC Class Codes: H04L 63/0209 Architectural arrangements, e.g. perimeter networks or demilitarized zones
• CPC Class Codes: H04L 63/0227 Filtering policies mail message filtering H04L51/212
• CPC Class Codes: H04L 63/105 Multiple levels of security
• CPC Class Codes: H04L 67/00 Network arrangements or protocols for supporting network services or applications user-to-user messaging H04L51/00; network arrangements, protocols or services for supporting real-time applications in data packet communications networks H04L65/00
• CPC Class Codes: H04L 67/131 Protocols for games, networked simulations or virtual reality
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

A bilateral data transfer system comprising a first node, a second node, a first one-way link for unidirectional transfer of first data from the first node to the second node, and a second one-way link for unidirectional transfer of second data from the second node to the first node, wherein the unidirectional transfer of the first data across the first one-way link and the unidirectional transfer of the second data across the second one-way link are independently administered by the bilateral data transfer system. Under such bilateral data transfer system, each of the one-way data links may be subject to separately administered security restrictions and data filtering processes. Hence, it enables secure bilateral communications across different network security domains.

Claims

1. A bilateral data transfer system comprising:

a first node;

a remote terminal client connected to the first node;

a second node;

a remote terminal server connected to the second node;

a first one-way link for unidirectional transfer of first data from the first node to the second node; and

a second one-way link for unidirectional transfer of second data from the second node to the first node,

wherein the first node comprises;

one or more processors;

a memory storing a first data sending application, a second data receiving application and a first session managing application;

and wherein the one or more processors are configured to execute;

the first data sending application for sending the first data to the second node over the first one-way link;

the second data receiving application for receiving the second data from the second node over the second one-way link; and

the first session managing application for blocking the first data from the second data receiving application and for blocking the second data from the first data sending application, and

wherein the second node comprises;

one or more processors;

a memory storing a first data receiving application, a second data sending application and a second session managing application;

wherein the one or more processors are configured to execute;

the first data receiving application for receiving the first data from the first node over the first one-way link;

the second data sending application for sending the second data to the first node over the second one-way link; and

the second session managing application for blocking the first data from the second data sending application and for blocking the second data from the first data receiving application, so that the unidirectional transfer of the first data across the first one-way link and the unidirectional transfer of the second data across the second one-way link are independently administered by the bilateral data transfer system,

wherein;

the first data comprises a request for data from the remote terminal client;

the second data comprises requested data from the remote terminal server;

the first session managing application is configured to route the first data from the remote terminal client only to the first data sending application and configured to route the second data from the second data receiving application only to the remote terminal client; and

the second session managing application is configured to route the first data from the first data receiving application only to the remote terminal server and configured to route the second data from the remote terminal server only to the second data send application.

2. The data transfer system of claim 1, further comprising:

a first data sending configuration file and a first data receiving configuration file for filtering and routing the first data, wherein the first data sending configuration file is accessible by the first data sending application and the first data receiving configuration file is accessible by the first data receiving application; and

a second data sending configuration file and a second data receiving configuration file for filtering and routing the second data, wherein the second data sending configuration file is accessible by the second data sending application and the second data receiving configuration file is accessible by the second data receiving application.

3. The data transfer system of claim 1, wherein the first session managing application is configured to implement bilateral TCP communications with the remote terminal client, and the second session managing application is configured to implement bilateral TCP communications with the remote terminal server.

4. The data transfer system of claim 1, wherein the first data sending and receiving applications and the second data sending and receiving applications are configured to respectively apply different security constraints to the unidirectional transfer of the first data over the first one-way link and the unidirectional transfer of the second data over the second one-way link.

5. The data transfer system of claim 1, further comprising a first data routing configuration file associated with the first session managing application and a second data routing configuration file associated with the second session managing application.

6. The data transfer system of claim 1, wherein:

the first node comprises a first software zone comprising the first data sending application, a second software zone comprising the second data receiving application, and a third software zone comprising the first session managing application; and

the second node comprises a fourth software zone comprising the second data sending application, a fifth software zone comprising the first data receiving application, and a sixth software zone comprising the second session managing application,

wherein each of the software zones is capable of separate administration.

7. The data transfer system of claim 1, wherein the second session managing application is configured to control a connection between the second node and the remote terminal server so that the remote terminal server cannot initiate the connection.

8. A non-transitory machine readable medium having instructions stored on at least one of a first node and a second node, wherein the first node and the second node are interconnected by a first one-way link for unidirectional transfer of first data from the first node to the second node and a second one-way link for unidirectional transfer of second data from the second node to the first node, the instructions, when executed by the first node, causing the first node to:

execute a first data sending application to send the first data to the second node over the first one-way link;

execute a second data receiving application to receive the second data from the second node over the second one-way link; and

execute a first session managing application to block the first data from the second data receiving application and to block the second data from the first data sending application, further the instructions, when executed by the second node, causing the second node to;

execute a first data receiving application to receive the first data from the first node over the first one-way link;

execute a second data sending application to send the second data to the first node over the second one-way link; and

execute a second session managing application to block the first data from the second data sending application and to block the second data from the first data receiving application, so that the unidirectional transfer of the first data across the first one-way link and the unidirectional transfer of the second data across the second one-way link are independently administered by the instructions,

wherein;

the first data comprises a request for data from a remote terminal client connected to the first node;

the second data comprises requested data from a remote terminal server connected to the second node;

the first node comprises a first software zone comprising the first data sending application, a second software zone comprising the second data receiving application, and a third software zone comprising the first session managing application;

the second node comprises a fourth software zone comprising the second data sending application, a fifth software zone comprising the first data receiving application, and a sixth software zone comprising the second session managing application; and

each of the software zones is capable of separate administration.

9. The non-transitory machine readable medium of claim 8, wherein:

the step to execute the first data sending application comprises the step to read a first data sending configuration file to route the first data;

the step to execute the first data receiving application comprises the step to read a first data receiving configuration file to route the first data;

the step to execute the second data sending application comprises the step to read a second data sending configuration file to route the second data; and

the step to execute the second data receiving application comprises the step to read a second data receiving configuration file to route the second data.

10. The non-transitory machine readable medium of claim 8, wherein:

the step to execute the first session managing application comprises the step to route the first data from the remote terminal client only to the first data sending application and the step to route the second data from the second data receiving application only to the remote terminal client; and

the step to execute the second session managing application comprises the step to route the first data from the first data receiving application only to the remote terminal server and the step to route the second data from the remote terminal server only to the second data sending application.

11. The non-transitory machine readable medium of claim 8, wherein:

the step to execute the first session managing application comprises the step to implement bilateral TCP communications between the first node and the remote terminal client; and

the step to execute the second session managing application comprises the step to implement bilateral TCP communications between the second node and the remote terminal server.

12. The non-transitory machine readable medium of claim 8, wherein:

the steps to execute the first data sending application and the first data receiving application comprise the step to apply a first security constraint to the unidirectional transfer of the first data over the first one-way link;

the steps to execute the second data sending application and the second data receiving application comprise the step to apply a second security constraint to the unidirectional transfer of the second data over the second one-way link; and

the first security constraint and the second security constraint are different.

13. The non-transitory machine readable medium of claim 8, wherein:

the step to execute the first session managing application comprises the step to read a first data routing configuration file; and

the step to execute the second session managing application comprises the step to read a second data routing configuration file.

14. A bilateral data transfer system comprising:

a first node;

a second node;

a first one-way link for unidirectional transfer of first data from the first node to the second node; and

a second one-way link for unidirectional transfer of second data from the second node to the first node,

wherein the first node comprises;

one or more processors;

a memory storing a first data sending application, a second data receiving application and a first session managing application;

and wherein the one or more processors are configured to execute;

the first data sending application for sending the first data to the second node over the first one-way link;

the second data receiving application for receiving the second data from the second node over the second one-way link; and

the first session managing application for blocking the first data from the second data receiving application and for blocking the second data from the first data sending application, and

wherein the second node comprises;

one or more processors;

a memory storing a first data receiving application, a second data sending application and a second session managing application;

wherein the one or more processors are configured to execute;

the first data receiving application for receiving the first data from the first node over the first one-way link;

the second data sending application for sending the second data to the first node over the second one-way link; and

the second session managing application for blocking the first data from the second data sending application and for blocking the second data from the first data receiving application, so that the unidirectional transfer of the first data across the first one-way link and the unidirectional transfer of the second data across the second one-way link are independently administered by the bilateral data transfer system,

wherein;

the first data comprises a request for data from a remote terminal client;

the second data comprises requested data from a remote terminal server;

the first node comprises a first software zone comprising the first data sending application, a second software zone comprising the second data receiving application, and a third software zone comprising the first session managing application;

the second node comprises a fourth software zone comprising the second data sending application, a fifth software zone comprising the first data receiving application, and a sixth software zone comprising the second session managing application; and

each of the software zones is capable of separate administration.

15. The data transfer system of claim 14, further comprising:

a first data sending configuration file and a first data receiving configuration file for filtering and routing the first data, wherein the first data sending configuration file is accessible by the first data sending application and the first data receiving configuration file is accessible by the first data receiving application; and

a second data sending configuration file and a second data receiving configuration file for filtering and routing the second data, wherein the second data sending configuration file is accessible by the second data sending application and the second data receiving configuration file is accessible by the second data receiving application.

16. The data transfer system of claim 14, further comprising the remote terminal client connected to the first node and the remote terminal server connected to the second node.

17. The data transfer system of claim 16, wherein:

the first session managing application is configured to route the first data from the remote terminal client only to the first data sending application and configured to route the second data from the second data receiving application only to the remote terminal client; and

the second session managing application is configured to route the first data from the first data receiving application only to the remote terminal server and configured to route the second data from the remote terminal server only to the second data send application.

18. The data transfer system of claim 17, wherein the first session managing application is configured to implement bilateral TCP communications with the remote terminal client, and the second session managing application is configured to implement bilateral TCP communications with the remote terminal server.

19. The data transfer system of claim 14, wherein the first data sending and receiving applications and the second data sending and receiving applications are configured to respectively apply different security constraints to the unidirectional transfer of the first data over the first one-way link and the unidirectional transfer of the second data over the second one-way link.

20. The data transfer system of claim 14, further comprising a first data routing configuration file associated with the first session managing application and a second data routing configuration file associated with the second session managing application.

21. The data transfer system of claim 16, wherein the second session managing application is configured to control a connection between the second node and the remote terminal server so that the remote terminal server cannot initiate the connection.