WO2016153806A1 - One-way network interface - Google Patents
One-way network interface Download PDFInfo
- Publication number
- WO2016153806A1 WO2016153806A1 PCT/US2016/021786 US2016021786W WO2016153806A1 WO 2016153806 A1 WO2016153806 A1 WO 2016153806A1 US 2016021786 W US2016021786 W US 2016021786W WO 2016153806 A1 WO2016153806 A1 WO 2016153806A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- area
- network interface
- coupled
- processor
- input
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/30—Peripheral units, e.g. input or output ports
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/64—Hybrid switching systems
- H04L12/6418—Hybrid transport
Definitions
- This disclosure relates generally to a one-way cross-domain solution included on a network interface card.
- a cross-domain solution is a system that provides the ability to access or transfer data between two networks having differing security domains or between a computer in one security domain and a network in another security domain.
- a CDS may be one-way only (from a low to a high domain or from a high to a low domain) or may be two- way.
- highly engineered solutions such as the Owl Computing Technologies ® Dual Diode, provide a direct point-to-point optical link between the two networks having differing security domains (with data transfer in either the low-to- high direction or in the low-to-high direction).
- the unidirectionality of the data transfer is enforced in the circuitry of the network interface cards at both network endpoints and in the cable interconnects.
- the hardware provides an added layer of assurance of unidirectional information flow and non-bypassable operation.
- it is easy to prove that data is not bypassing the Dual Diode because the optical link, which is the only physical channel for communications, can only carry information in a single direction since there is no receiving circuit coupled to the transmit end of the optical link and no transmitting circuit coupled to the receive end of the optical link.
- the computing platforms coupled to a network are personal computers or workstations.
- the personal computer at the send node must be configured so that only an optical transmitter coupled to the send node interfaces to a first end of a one-way optical data link (e.g., an optical fiber) and, on the other hand, the personal computer at the receive node must be configured so that only an optical receiver coupled to the receive node interfaces to a second opposite end of the one-way optical data link.
- a one-way optical data link e.g., an optical fiber
- a first personal computer or server is located on the send side and includes a network interface card coupled to the send side network and a transmit-only interface card coupled to the send side of an optical fiber.
- a second personal computer or server is located on the receive side and includes a network interface card coupled to the receive side network and a receive-only interface card coupled to the receive side of an optical fiber.
- the one-way data link is configured to transfer data only from the input to the output and to prevent any signal from passing from the output to the input.
- a destination processor is mounted on the single printed circuit card. The destination processor has an input coupled to the output of the one-way data link and a network interface. The destination processor is configured to forward information received on the input to a remote computer via the network interface.
- the transmit-only interface card may also include an external power interface.
- the destination processor may be coupled to an external power interface to receive power such that the destination processor only receives power via the external power interface.
- the single printed circuit board may have three separate contiguous areas, a first area containing the destination processor, a second area containing the network controller and the source processor and a third area disposed directly between the first area and the second area. In this case, the third area will contain no electrical connections between the first area and the second area and the one-way data link will span the third area with the input thereof within the second area and the output thereof within the first area.
- a receive-only network interface card for a host computer includes a single printed circuit card configured to be mounted in the host computer.
- a network controller is mounted on the single printed circuit card.
- the network controller is coupled to the host computer via a host computer interface and has a network interface.
- a destination processor is mounted on the single printed circuit card.
- the destination processor has a separate input and is coupled to the network interface of the network controller.
- the destination processor is configured to forward information received on the separate input to the network interface.
- a one-way data link is mounted on the single printed circuit card.
- the one-way data link has an input and an output coupled to the separate input of the destination processor.
- the one-way data link is configured to transfer data only from the input to the output and to prevent any signal from passing from the output to the input.
- a source processor is mounted on the single printed circuit card.
- the source processor has a network interface and an output coupled to the input of the one-way data link.
- the source processor is configured to forward information received from a remote computer via the network interface on the output.
- the receive-only network interface card may also include an external power interface.
- the source processor may be coupled to the external power interface to receive power such that the source processor only receives power via the external power interface.
- the single printed circuit board may have three separate contiguous areas, a first area containing the source processor, a second area containing the network controller and the destination processor and a third area disposed directly between the first area and the second area. In this case, the third area will contain no electrical connections between the first area and the second area and the one-way data link will span the third area with the input thereof within the first area and the output thereof within the second area.
- FIG. 1 is a block diagram of a one-way receive-only network interface card according to the present disclosure.
- FIG. 2 is a block diagram of a one-way transmit-only network interface card according to the present disclosure.
- a one-way receive- only network interface card 100 includes a LAN interface 101 and a power interface 102 which are both coupled to a destination CPU 103.
- LAN interface 101 is used to couple to a local area network and may be, for example, an RJ-45 socket with appropriate electrical connections.
- Power interface 102 may include, for example, any conventional connector and is used to provide power for destination CPU 103.
- the externally provided power source may be a conventional wall plug with an integrated transformer and also include any necessary voltage regulation circuits, or the required power regulation circuits may instead be included within power interface 102.
- Destination CPU 103 may include an integrated Ethernet controller for managing communications with a LAN coupled via LAN interface 101 or a separate Ethernet controller (not shown) may be coupled between LAN interface 101 and destination CPU 103.
- the one-way receive-only network interface card 100 also includes a PCIe interface 109 for coupling to a host computer's internal expansion bus.
- a PCIe interface 109 is shown in FIG. 1, as one of ordinary skill in the art will readily recognize, in alternative embodiments, interface 109 may be alternatively configured for connection to any other type of computer expansion bus.
- PCIe interface 109 is coupled to an Ethernet controller 108, which in turn, is coupled to source CPU 107 via an integrated Ethernet controller.
- Ethernet controller 108 communicates with source CPU 107 using Ethernet protocol.
- the integrated Ethernet controller in source CPU 107 may alternatively be provided as a separate integrated circuit (not shown) provided between Ethernet controller 108 and source CPU 107.
- Source CPU 107 is coupled to destination CPU 103 via a one-way transfer system 111.
- One-way transfer system 111 may comprise, for example, a send node 106, a one-way data link 105, and a receive node 104.
- the one-way data link 105 may comprise, for example, an optocoupler-type device having an input coupled to send node 106 and an output coupled to the receive node 104.
- one-way data link 105 may consist of discrete components such as an LED coupled to a photocoupler via an optical fiber, with the LED coupled to an output of the send node 106 and the photocoupler coupled to an input of the receive node 104.
- one-way receive-only network interface card 100 are mounted so that all the transmit-side components are on a first side of boundary line 1 10 (e.g., to the right of line 1 10) and all the receive-side components are on a second opposite side of boundary line 110 (e.g., to the left of line 110).
- No circuit board traces cross boundary line 1 10 and the only component that crosses boundary 110 is one-way data link 105.
- the one-way data link 105 is an optocoupler device
- the input pins of the optocoupler device are mounted on the right side of boundary 1 10 and the output pins of that device are mounted on the left side of boundary 1 10.
- boundary line 1 10 consists of an area of empty space on network interface card 100 between the area in which the transmit-side components mounted and the area in which the receive-side components mounted. No electrical conductors pass across the area of empty space forming boundary line 110 such that the one-way data link is the only way to communicate from the transmit-side components to the receive-side components.
- the transmit-only network interface card 100 shown in FIG. 1 allows the host computer to communicate with the source CPU 107 directly, e.g., via Ethernet protocol, and likewise allows destination CPU 103 to communicate with remote computers (not shown) via an external network (also not shown) using, for example, Ethernet protocol.
- the host computer may send TCP/IP packets to a TCP client proxy running on source CPU 107, which are then transferred to destination CPU 103 via the one-way transfer system 111 (preferably without the IP information), and a preconfigured TCP server proxy running on destination CPU 103 may then send the TCP/IP packets to a predetermined remote computer (based on the preconfiguration).
- a number of other communication methodologies may also be implemented, either in conjunction with TCP and/or UDP or in the alternative to UDP and/or UDP, including but not limited to the following services provided by Owl Computing Technologies, Inc.: Secure File/Directory Transfer System (DFTS); Remote File Transfer Service (RFTS), Secure Network Transfer Service (SNTS); and Remote Printing Transfer Service (RPTS).
- DFTS Secure File/Directory Transfer System
- RFTS Remote File Transfer Service
- SNTS Secure Network Transfer Service
- RPTS Remote Printing Transfer Service
- a one-way transmit- only network interface card 200 includes a LAN interface 101 and a power interface 102 which are both coupled to a source CPU 207.
- Power interface 102 provides power for source CPU 207 in the same manner as power interface 102 in FIG. 1. External power is provided to source CPU 207 to maintain separation of the transmit and receive circuits across boundary 210, as discussed below.
- Source CPU 207 may include an integrated Ethernet controller for managing communications with a LAN coupled via LAN interface 101 or a separate Ethernet controller (not shown) may be coupled between LAN interface 101 and source CPU 207.
- the one-way receive-only network interface card 200 also includes a PCIe interface 109 for coupling to a host computer's internal expansion bus.
- PCIe interface 109 is coupled to an Ethernet controller 108, which in turn, is coupled to destination CPU 203 via an integrated Ethernet controller.
- Ethernet controller 108 communicates with destination CPU 203 using Ethernet protocol.
- the integrated Ethernet controller in destination CPU 203 may alternatively be provided as a separate integrated circuit (not shown) provided between Ethernet controller 108 and destination CPU 203.
- Source CPU 207 is coupled to destination CPU 203 via a one-way transfer system 211.
- One-way transfer system 211 may comprise, for example, a send node 206, a one-way data link 205, and a receive node 204.
- the one-way data link 205 may comprise, for example, an optocoupler having an input coupled to the send node 206 and an output coupled to the receive node 204.
- one-way data link 205 may consist of discrete components such as an LED coupled to a photocoupler via an optical fiber, with the LED coupled to the send node 206 and the photocoupler coupled to the receive node 204.
- Boundary line 210 thus consists of an area of empty space on network interface card 200 between the area in which the transmit-side components mounted and the area in which the receive-side components mounted. As with the FIG. 1 embodiment, no electrical conductors pass across the area of empty space forming boundary line 210 such that the one-way data link is the only way to communicate from the transmit- side components to the receive-side components.
- the network interface card 200 shown in FIG. 2 allows remote computers (not shown) to communicate with source CPU 207 via a network coupled to LAN interface 101, using the same type of communication methodologies discussed above with respect to network interface card 100, e.g., TCP/IP packet transfer, UDP packet transfer, DFTS, RFTS), SNTS, and RPTS, but in the reverse direction (since the ultimate destination for all information is the host computer).
- Source CPU 207 in turn, then transfers information (packets, files, etc.) across one-way transfer system 211 to destination CPU 202, which, in turn forwards such information to the host computer.
- Network interface card 200 ensures that information (packets, files, etc.) may only pass from source CPU 207 to destination CPU 203 and that no information or signals of any kind pass from destination CPU 203 to source CPU 207 (and onto the network coupled to LAN interface 101).
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Small-Scale Networks (AREA)
- Power Sources (AREA)
Abstract
Two embodiments of a one-way network interface card are disclosed, a transmit-only version and a receive-only version. A network controller mounted on the circuit card is coupled to the host computer via a host computer interface. A first processor is coupled to a network interface of the network controller. A second processor has a separate network interface for communicating with a remote computer. A one-way link is coupled between the first processor and the second processor. For the transmit-only embodiment, the one-way link only allows information to be transferred from the first processor to the second processor, and thus information may only pass from the host computer to the remote computer. For the receive-only embodiment, the one-way link only allows information to be transferred from the second processor to the first processor, and thus information may only pass from the remote computer to the host computer.
Description
ONE-WAY NETWORK INTERFACE
FIELD
[0001] This disclosure relates generally to a one-way cross-domain solution included on a network interface card.
BACKGROUND
[0002] A cross-domain solution (CDS) is a system that provides the ability to access or transfer data between two networks having differing security domains or between a computer in one security domain and a network in another security domain. A CDS may be one-way only (from a low to a high domain or from a high to a low domain) or may be two- way. For a one-way CDS linking two networks, highly engineered solutions, such as the Owl Computing Technologies® Dual Diode, provide a direct point-to-point optical link between the two networks having differing security domains (with data transfer in either the low-to- high direction or in the low-to-high direction). The unidirectionality of the data transfer is enforced in the circuitry of the network interface cards at both network endpoints and in the cable interconnects. In this way, the hardware provides an added layer of assurance of unidirectional information flow and non-bypassable operation. In contrast to software based one-way data transfer systems, it is easy to prove that data is not bypassing the Dual Diode because the optical link, which is the only physical channel for communications, can only carry information in a single direction since there is no receiving circuit coupled to the transmit end of the optical link and no transmitting circuit coupled to the receive end of the optical link.
[0003] Typically, the computing platforms coupled to a network are personal computers or workstations. When implementing a one-way data transfer system from a send
node coupled to a first network to a receive node coupled to a second network, to achieve and maintain the unidirectionality of data flow over a one-way optical data link coupling the send node to the receive node, the personal computer at the send node must be configured so that only an optical transmitter coupled to the send node interfaces to a first end of a one-way optical data link (e.g., an optical fiber) and, on the other hand, the personal computer at the receive node must be configured so that only an optical receiver coupled to the receive node interfaces to a second opposite end of the one-way optical data link. As disclosed in U.S. Patent No. 8,068,415 B2 to Mraz ("the '415 patent"), one solution is to provide a transmit- only interface card in the personal computer at the send node and a receive-only interface card in the personal computer at the receive node, with an optical fiber coupling the transmit- only interface card to the receive-only interface card. In this situation, the transmit-only interface card does not include any receive circuitry and thus is capable only of transmitting information while the receive-only interface card does not include any transmit circuitry and thus is capable only of receiving information. The system disclosed in the '415 patent thus requires two personal computers or servers. In this configuration, a first personal computer or server is located on the send side and includes a network interface card coupled to the send side network and a transmit-only interface card coupled to the send side of an optical fiber. Also, a second personal computer or server is located on the receive side and includes a network interface card coupled to the receive side network and a receive-only interface card coupled to the receive side of an optical fiber. The requirement for using two personal computers or servers for the cross-domain system is less than optimal.
[0004] Accordingly, there is a need for a cross-domain system which overcomes the problems identified above.
SUMMARY
[0005] In one aspect, a transmit-only network interface card for a host computer is provided. The transmit-only network interface includes a single printed circuit card configured to be mounted in the host computer. Also, a network controller is mounted on the single printed circuit card. The network controller is coupled to the host computer via a host computer interface and has a network interface. A source processor is mounted on the single printed circuit card. The source processor is coupled to the network interface of the network controller and is configured to forward information received from the network interface on a separate output, A one-way data link is mounted on the single printed circuit card. The oneway data link has an input coupled to the separate output of the source processor and an output. The one-way data link is configured to transfer data only from the input to the output and to prevent any signal from passing from the output to the input. A destination processor is mounted on the single printed circuit card. The destination processor has an input coupled to the output of the one-way data link and a network interface. The destination processor is configured to forward information received on the input to a remote computer via the network interface.
[0006] In a further aspect, the transmit-only interface card may also include an external power interface. The destination processor may be coupled to an external power interface to receive power such that the destination processor only receives power via the external power interface. The single printed circuit board may have three separate contiguous areas, a first area containing the destination processor, a second area containing the network controller and the source processor and a third area disposed directly between the first area and the second area. In this case, the third area will contain no electrical connections between
the first area and the second area and the one-way data link will span the third area with the input thereof within the second area and the output thereof within the first area.
[0007] In another aspect, a receive-only network interface card for a host computer is provided. The receive-only network interface card includes a single printed circuit card configured to be mounted in the host computer. A network controller is mounted on the single printed circuit card. The network controller is coupled to the host computer via a host computer interface and has a network interface. A destination processor is mounted on the single printed circuit card. The destination processor has a separate input and is coupled to the network interface of the network controller. The destination processor is configured to forward information received on the separate input to the network interface. A one-way data link is mounted on the single printed circuit card. The one-way data link has an input and an output coupled to the separate input of the destination processor. The one-way data link is configured to transfer data only from the input to the output and to prevent any signal from passing from the output to the input. A source processor is mounted on the single printed circuit card. The source processor has a network interface and an output coupled to the input of the one-way data link. The source processor is configured to forward information received from a remote computer via the network interface on the output.
[0008] In a further aspect, the receive-only network interface card may also include an external power interface. The source processor may be coupled to the external power interface to receive power such that the source processor only receives power via the external power interface. The single printed circuit board may have three separate contiguous areas, a first area containing the source processor, a second area containing the network controller and the destination processor and a third area disposed directly between the first area and the second area. In this case, the third area will contain no electrical connections between the first
area and the second area and the one-way data link will span the third area with the input thereof within the first area and the output thereof within the second area.
[0009] The features, functions, and advantages can be achieved independently in various embodiments of the present disclosure or may be combined in yet other embodiments in which further details can be seen with reference to the following description and drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
[00010] The following detailed description, given by way of example and not intended to limit the present invention solely thereto, will best be understood in conjunction with the accompanying drawings in which:
[00011] FIG. 1 is a block diagram of a one-way receive-only network interface card according to the present disclosure; and
[00012] FIG. 2 is a block diagram of a one-way transmit-only network interface card according to the present disclosure.
DETAILED DESCRIPTION
[00013] In the present disclosure, like reference numbers refer to like elements throughout the drawings, which illustrate various exemplary embodiments of the present invention.
[00014] Referring now to the drawings, and in particular to FIG. 1, a one-way receive- only network interface card 100 includes a LAN interface 101 and a power interface 102 which are both coupled to a destination CPU 103. LAN interface 101 is used to couple to a local area network and may be, for example, an RJ-45 socket with appropriate electrical connections. Power interface 102 may include, for example, any conventional connector and
is used to provide power for destination CPU 103. As one of ordinary skill in the art may readily recognize, the externally provided power source may be a conventional wall plug with an integrated transformer and also include any necessary voltage regulation circuits, or the required power regulation circuits may instead be included within power interface 102. External power is provided to destination CPU 103 to maintain separation of the transmit and receive circuits across boundary 110, as discussed below. Destination CPU 103 may include an integrated Ethernet controller for managing communications with a LAN coupled via LAN interface 101 or a separate Ethernet controller (not shown) may be coupled between LAN interface 101 and destination CPU 103.
[00015] The one-way receive-only network interface card 100 also includes a PCIe interface 109 for coupling to a host computer's internal expansion bus. Although a PCIe interface 109 is shown in FIG. 1, as one of ordinary skill in the art will readily recognize, in alternative embodiments, interface 109 may be alternatively configured for connection to any other type of computer expansion bus. PCIe interface 109 is coupled to an Ethernet controller 108, which in turn, is coupled to source CPU 107 via an integrated Ethernet controller. In a presently preferred embodiment, Ethernet controller 108 communicates with source CPU 107 using Ethernet protocol. As with the destination CPU 103, the integrated Ethernet controller in source CPU 107 may alternatively be provided as a separate integrated circuit (not shown) provided between Ethernet controller 108 and source CPU 107.
[00016] Source CPU 107 is coupled to destination CPU 103 via a one-way transfer system 111. One-way transfer system 111 may comprise, for example, a send node 106, a one-way data link 105, and a receive node 104. The one-way data link 105 may comprise, for example, an optocoupler-type device having an input coupled to send node 106 and an output coupled to the receive node 104. In the alternative, one-way data link 105 may consist of
discrete components such as an LED coupled to a photocoupler via an optical fiber, with the LED coupled to an output of the send node 106 and the photocoupler coupled to an input of the receive node 104.
[00017] To ensure secure communications, the various components on one-way receive-only network interface card 100 are mounted so that all the transmit-side components are on a first side of boundary line 1 10 (e.g., to the right of line 1 10) and all the receive-side components are on a second opposite side of boundary line 110 (e.g., to the left of line 110). No circuit board traces cross boundary line 1 10 and the only component that crosses boundary 110 is one-way data link 105. For example, when the one-way data link 105 is an optocoupler device, the input pins of the optocoupler device are mounted on the right side of boundary 1 10 and the output pins of that device are mounted on the left side of boundary 1 10. In another example, when the one-way data link 105 is formed from discrete components, the LED is mounted on the right side of boundary 1 10, the photocoupler is mounted on the left side of boundary 1 10 and the optical fiber crosses the boundary 110. In effect, boundary line 1 10 consists of an area of empty space on network interface card 100 between the area in which the transmit-side components mounted and the area in which the receive-side components mounted. No electrical conductors pass across the area of empty space forming boundary line 110 such that the one-way data link is the only way to communicate from the transmit-side components to the receive-side components.
[00018] In operation, the transmit-only network interface card 100 shown in FIG. 1 allows the host computer to communicate with the source CPU 107 directly, e.g., via Ethernet protocol, and likewise allows destination CPU 103 to communicate with remote computers (not shown) via an external network (also not shown) using, for example, Ethernet protocol. In particular, the host computer may send TCP/IP packets to a TCP client proxy running on
source CPU 107, which are then transferred to destination CPU 103 via the one-way transfer system 111 (preferably without the IP information), and a preconfigured TCP server proxy running on destination CPU 103 may then send the TCP/IP packets to a predetermined remote computer (based on the preconfiguration). This process of TCP communications across a one-way data link is detailed in U.S. Patent No. 8,139,581 Bl ("the '581 patent"), which is incorporated by reference in its entirety herein, and ensures that information may only pass from source CPU 107 to destination CPU 103 and that no information or signals of any kind pass from destination CPU 103 to source CPU 107. In one alternative communication methodology, the host computer may send UDP packets to a UDP socket of the Ethernet port of source CPU 107 for transmission across one-way transfer system 111 and ultimately to a remote computer via destination CPU 103. This process is also described in more detail in the '581 patent. System 100 may also implement combined UDP/TCP communications as described in the '581 patent. A number of other communication methodologies may also be implemented, either in conjunction with TCP and/or UDP or in the alternative to UDP and/or UDP, including but not limited to the following services provided by Owl Computing Technologies, Inc.: Secure File/Directory Transfer System (DFTS); Remote File Transfer Service (RFTS), Secure Network Transfer Service (SNTS); and Remote Printing Transfer Service (RPTS).
[00019] Referring now to FIG. 2, in an alternative embodiment, a one-way transmit- only network interface card 200 includes a LAN interface 101 and a power interface 102 which are both coupled to a source CPU 207. Power interface 102 provides power for source CPU 207 in the same manner as power interface 102 in FIG. 1. External power is provided to source CPU 207 to maintain separation of the transmit and receive circuits across boundary 210, as discussed below. Source CPU 207 may include an integrated Ethernet controller for
managing communications with a LAN coupled via LAN interface 101 or a separate Ethernet controller (not shown) may be coupled between LAN interface 101 and source CPU 207.
[00020] The one-way receive-only network interface card 200 also includes a PCIe interface 109 for coupling to a host computer's internal expansion bus. As with the FIG. 1 embodiment, although a PCIe interface 109 is shown in FIG. 2, as one of ordinary skill in the art will readily recognize, the network interface cards of instant disclosure can be applied to any type of computer expansion bus adapted to receive expansion cards by providing the appropriate interface and connector. PCIe interface 109 is coupled to an Ethernet controller 108, which in turn, is coupled to destination CPU 203 via an integrated Ethernet controller. In a presently preferred embodiment, Ethernet controller 108 communicates with destination CPU 203 using Ethernet protocol. As with the source CPU 207, the integrated Ethernet controller in destination CPU 203 may alternatively be provided as a separate integrated circuit (not shown) provided between Ethernet controller 108 and destination CPU 203.
[00021] Source CPU 207 is coupled to destination CPU 203 via a one-way transfer system 211. One-way transfer system 211 may comprise, for example, a send node 206, a one-way data link 205, and a receive node 204. The one-way data link 205 may comprise, for example, an optocoupler having an input coupled to the send node 206 and an output coupled to the receive node 204. In the alternative, one-way data link 205 may consist of discrete components such as an LED coupled to a photocoupler via an optical fiber, with the LED coupled to the send node 206 and the photocoupler coupled to the receive node 204. As with the FIG. 1 embodiment, the components are mounted on separate sides of boundary line 210, with the transmit-related devices mounted on the left side of boundary line 210 and the receive-related devices mounted on the right side of boundary line 210, and with the one-way data link 205 the only device which crosses boundary line 210 (and with no circuit board
traces crossing boundary line 210). Boundary line 210 thus consists of an area of empty space on network interface card 200 between the area in which the transmit-side components mounted and the area in which the receive-side components mounted. As with the FIG. 1 embodiment, no electrical conductors pass across the area of empty space forming boundary line 210 such that the one-way data link is the only way to communicate from the transmit- side components to the receive-side components.
[00022] In operation, the network interface card 200 shown in FIG. 2 allows remote computers (not shown) to communicate with source CPU 207 via a network coupled to LAN interface 101, using the same type of communication methodologies discussed above with respect to network interface card 100, e.g., TCP/IP packet transfer, UDP packet transfer, DFTS, RFTS), SNTS, and RPTS, but in the reverse direction (since the ultimate destination for all information is the host computer). Source CPU 207, in turn, then transfers information (packets, files, etc.) across one-way transfer system 211 to destination CPU 202, which, in turn forwards such information to the host computer. Network interface card 200 ensures that information (packets, files, etc.) may only pass from source CPU 207 to destination CPU 203 and that no information or signals of any kind pass from destination CPU 203 to source CPU 207 (and onto the network coupled to LAN interface 101).
[00023] Although the present invention has been particularly shown and described with reference to the preferred embodiments and various aspects thereof, it will be appreciated by those of ordinary skill in the art that various changes and modifications may be made without departing from the spirit and scope of the invention. It is intended that the appended claims be interpreted as including the embodiments described herein, the alternatives mentioned above, and all equivalents thereto.
Claims
1. A transmit-only network interface card for a host computer, comprising: a single printed circuit card configured to be mounted in the host computer; a network controller mounted on the single printed circuit card and coupled to the host computer via a host computer interface and having a network interface; a source processor mounted on the single printed circuit card, the source processor coupled to the network interface of the network controller and configured to forward information received from the network interface on a separate output; a one-way data link mounted on the single printed circuit card, the one-way data link having an input coupled to the separate output of the source processor and an output, the oneway data link configured to transfer data only from the input to the output and to prevent any signal from passing from the output to the input; and a destination processor mounted on the single printed circuit card, the destination processor having an input coupled to the output of the one-way data link and a network interface, the destination processor configured to forward information received on the input to a remote computer via the network interface.
2. The transmit-only network interface card of claim 1, further comprising an external power interface, wherein the destination processor is coupled to the external power interface to receive power such that the destination processor only receives power via the external power interface.
3. The transmit-only network interface card of claim 1, wherein the single printed circuit board has three separate contiguous areas, a first area containing the destination processor, a
second area containing the network controller and the source processor and a third area disposed directly between the first area and the second area, the third area containing no electrical connections between the first area and the second area, the one-way data link spanning the third area with the input thereof within the second area and the output thereof within the first area.
4. A receive-only network interface card for a host computer, comprising: a single printed circuit card configured to be mounted in the host computer; a network controller mounted on the single printed circuit card and coupled to the host computer via a host computer interface and having a network interface; a destination processor mounted on the single printed circuit card, the destination processor having a separate input and coupled to the network interface of the network controller, the destination processor configured to forward information received on the separate input to the network interface; a one-way data link mounted on the single printed circuit card, the one-way data link having an input and an output coupled to the separate input of the destination processor, the one-way data link configured to transfer data only from the input to the output and to prevent any signal from passing from the output to the input; and a source processor mounted on the single printed circuit card, the source processor having a network interface and an output coupled to the input of the one-way data link, the source processor configured to forward information received from a remote computer via the network interface on the output.
5. The receive-only network interface card of claim 4, further comprising an external power interface, wherein the source processor is coupled to the external power interface to receive power such that the source processor only receives power via the external power interface.
6. The receive-only network interface card of claim 5, wherein the single printed circuit board has three separate contiguous areas, a first area containing the source processor, a second area containing the network controller and the destination processor and a third area disposed directly between the first area and the second area, the third area containing no electrical connections between the first area and the second area, the one-way data link spanning the third area with the input thereof within the first area and the output thereof within the second area.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| EP16769315.9A EP3275146A4 (en) | 2015-03-24 | 2016-03-10 | One-way network interface |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US14/666,508 US9853918B2 (en) | 2015-03-24 | 2015-03-24 | One-way network interface |
| US14/666,508 | 2015-03-24 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2016153806A1 true WO2016153806A1 (en) | 2016-09-29 |
Family
ID=56976085
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/US2016/021786 Ceased WO2016153806A1 (en) | 2015-03-24 | 2016-03-10 | One-way network interface |
Country Status (3)
| Country | Link |
|---|---|
| US (1) | US9853918B2 (en) |
| EP (1) | EP3275146A4 (en) |
| WO (1) | WO2016153806A1 (en) |
Families Citing this family (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9853918B2 (en) * | 2015-03-24 | 2017-12-26 | Owl Cyber Defense Solutions, Llc | One-way network interface |
| EP3229437A1 (en) * | 2016-04-07 | 2017-10-11 | Walter Steven Rosenbaum | Communication device and method for protecting a communication system against applying unauthorized code |
| DE102016116152A1 (en) * | 2016-04-30 | 2017-11-02 | Krohne Messtechnik Gmbh | Electrical device with a functional device |
| US10142289B1 (en) | 2018-03-27 | 2018-11-27 | Owl Cyber Defense Solutions, Llc | Secure interface for a mobile communications device |
| DE102018119411A1 (en) * | 2018-08-09 | 2020-02-13 | Endress+Hauser Process Solutions Ag | Field device of automation technology |
| US10990737B2 (en) | 2019-04-23 | 2021-04-27 | Owl Cyber Defense Solutions, Llc | Secure one-way network gateway |
| US11496233B2 (en) | 2020-12-23 | 2022-11-08 | BlackBear (Taiwan) Industrial Networking Security Ltd. | Communication system and communication method for one-way transmission |
| US11477048B2 (en) | 2021-01-15 | 2022-10-18 | BlackBear (Taiwan) Industrial Networking Security Ltd. | Communication method for one-way transmission based on VLAN ID and switch device using the same |
| US11611409B2 (en) | 2021-06-14 | 2023-03-21 | BlackBear (Taiwan) Industrial Networking Security Ltd. | Communication system and communication method for reporting compromised state in one-way transmission |
| US11853813B2 (en) | 2021-11-23 | 2023-12-26 | Oracle International Corporation | Cloud based cross domain system—CDS with disaggregated parts |
| US12095868B2 (en) * | 2021-11-23 | 2024-09-17 | Oracle International Corporation | Cloud based cross domain system—virtual data diode |
| US11863455B2 (en) | 2021-11-23 | 2024-01-02 | Oracle International Corporation | Cloud based cross domain system—CDSaaS |
| US11991185B2 (en) | 2022-02-14 | 2024-05-21 | BlackBear (Taiwan) Industrial Networking Security Ltd. | Method for secure data transmission and system using the same |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090230255A1 (en) * | 2008-03-11 | 2009-09-17 | Lemonovich John E | Cab signal receiver demodulator employing redundant, diverse field programmable gate arrays |
| US20100127103A1 (en) * | 2008-11-25 | 2010-05-27 | Toman Benjamin J | Flotation drive assembly for mechanized irrigation systems |
| US20110153969A1 (en) * | 2009-12-18 | 2011-06-23 | William Petrick | Device and method to control communications between and access to computer networks, systems or devices |
Family Cites Families (28)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5703562A (en) | 1996-11-20 | 1997-12-30 | Sandia Corporation | Method for transferring data from an unsecured computer to a secured computer |
| US6970473B1 (en) * | 1999-02-18 | 2005-11-29 | Sony Corporation | Communication method and communication apparatus |
| US7675867B1 (en) | 2006-04-19 | 2010-03-09 | Owl Computing Technologies, Inc. | One-way data transfer system with built-in data verification mechanism |
| US8068415B2 (en) | 2007-04-18 | 2011-11-29 | Owl Computing Technologies, Inc. | Secure one-way data transfer using communication interface circuitry |
| US7941526B1 (en) | 2007-04-19 | 2011-05-10 | Owl Computing Technologies, Inc. | Transmission of syslog messages over a one-way data link |
| US8352450B1 (en) | 2007-04-19 | 2013-01-08 | Owl Computing Technologies, Inc. | Database update through a one-way data link |
| US8139581B1 (en) | 2007-04-19 | 2012-03-20 | Owl Computing Technologies, Inc. | Concurrent data transfer involving two or more transport layer protocols over a single one-way data link |
| US7992209B1 (en) | 2007-07-19 | 2011-08-02 | Owl Computing Technologies, Inc. | Bilateral communication using multiple one-way data links |
| US8829479B2 (en) | 2008-11-21 | 2014-09-09 | L-3 Communications Corporation | Isolated high-speed digital interface for vehicles |
| US9305189B2 (en) | 2009-04-14 | 2016-04-05 | Owl Computing Technologies, Inc. | Ruggedized, compact and integrated one-way controlled interface to enforce confidentiality of a secure enclave |
| GB2495018B (en) | 2010-07-19 | 2017-02-22 | Owl Computing Tech Inc | Secure acknowledgment device for one-way data transfer system |
| US9081520B2 (en) | 2010-12-22 | 2015-07-14 | Owl Computing Technologies, Inc. | Remote print file transfer and spooling application for use with a one-way data link |
| US8516580B2 (en) | 2011-04-27 | 2013-08-20 | Owl Computing Technologies, Inc. | Method and system for processing a file to identify unexpected file types |
| US8646094B2 (en) | 2011-12-07 | 2014-02-04 | Owl Computing Technologies, Inc. | Method and apparatus for preventing unauthorized access to information stored in a non-volatile memory |
| US9678921B2 (en) | 2012-03-21 | 2017-06-13 | Owl Computing Technologies, Llc | Method and apparatus for data transfer reconciliation |
| US9736121B2 (en) | 2012-07-16 | 2017-08-15 | Owl Cyber Defense Solutions, Llc | File manifest filter for unidirectional transfer of files |
| US9065878B2 (en) | 2012-09-27 | 2015-06-23 | Owl Computing Technologies, Inc. | System and method for providing a remote virtual screen view |
| US8938795B2 (en) | 2012-11-19 | 2015-01-20 | Owl Computing Technologies, Inc. | System for real-time cross-domain system packet filtering |
| US8887276B2 (en) | 2012-11-21 | 2014-11-11 | Owl Computing Technologies, Inc. | System for providing a secure video display |
| US8997202B2 (en) | 2012-12-06 | 2015-03-31 | Owl Computing Technologies, Inc. | System for secure transfer of information from an industrial control system network |
| US9712543B2 (en) | 2013-01-23 | 2017-07-18 | Owl Cyber Defense Solutions, LLP | System for remotely monitoring status information of devices connected to a network |
| US8776254B1 (en) | 2013-01-23 | 2014-07-08 | Owl Computing Technologies, Inc. | System and method for the secure unidirectional transfer of software and software updates |
| US10218586B2 (en) | 2013-01-23 | 2019-02-26 | Owl Cyber Defense Solutions, Llc | System and method for enabling the capture and securing of dynamically selected digital information |
| US9306953B2 (en) | 2013-02-19 | 2016-04-05 | Owl Computing Technologies, Inc. | System and method for secure unidirectional transfer of commands to control equipment |
| US9094401B2 (en) | 2013-02-19 | 2015-07-28 | Owl Computing Technologies, Inc. | Secure front-end interface |
| US9596245B2 (en) | 2013-04-04 | 2017-03-14 | Owl Computing Technologies, Inc. | Secure one-way interface for a network device |
| US8898227B1 (en) | 2013-05-10 | 2014-11-25 | Owl Computing Technologies, Inc. | NFS storage via multiple one-way data links |
| US9853918B2 (en) * | 2015-03-24 | 2017-12-26 | Owl Cyber Defense Solutions, Llc | One-way network interface |
-
2015
- 2015-03-24 US US14/666,508 patent/US9853918B2/en active Active
-
2016
- 2016-03-10 WO PCT/US2016/021786 patent/WO2016153806A1/en not_active Ceased
- 2016-03-10 EP EP16769315.9A patent/EP3275146A4/en not_active Withdrawn
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090230255A1 (en) * | 2008-03-11 | 2009-09-17 | Lemonovich John E | Cab signal receiver demodulator employing redundant, diverse field programmable gate arrays |
| US20100127103A1 (en) * | 2008-11-25 | 2010-05-27 | Toman Benjamin J | Flotation drive assembly for mechanized irrigation systems |
| US20110153969A1 (en) * | 2009-12-18 | 2011-06-23 | William Petrick | Device and method to control communications between and access to computer networks, systems or devices |
Non-Patent Citations (1)
| Title |
|---|
| See also references of EP3275146A4 * |
Also Published As
| Publication number | Publication date |
|---|---|
| EP3275146A4 (en) | 2018-10-31 |
| US9853918B2 (en) | 2017-12-26 |
| US20160285786A1 (en) | 2016-09-29 |
| EP3275146A1 (en) | 2018-01-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9853918B2 (en) | One-way network interface | |
| US10903875B2 (en) | Virtualized physical layer adapted for EHF contactless communication | |
| US8068415B2 (en) | Secure one-way data transfer using communication interface circuitry | |
| EP3462328B1 (en) | Serial connection between management controller and microcontroller | |
| CN101488884B (en) | Network multi-computer controller, data processing device and application method | |
| CN104185969B (en) | PROFINET Ethernet adapter | |
| US9880869B2 (en) | Single computer-based virtual cross-domain solutions | |
| US8327038B2 (en) | Secured system for transferring data between two equipments | |
| CN106471780B (en) | Method, system and logic for configuring a local link based on a remote link partner | |
| US8284798B2 (en) | PoE communication bus, interface, and protocol between PoE subsystem and PHY or switch subsystems | |
| US9197490B2 (en) | System and method for providing remote management of a switching device | |
| US20160352651A1 (en) | Non-transparent bridge method and apparatus for configuring high-dimensional pci-express networks | |
| US9300348B2 (en) | Dual electrical compact small form-factor pluggable module | |
| CN114175581B (en) | A network adapter for one-way data transfer | |
| JP2008522550A (en) | Multirate optical transponder | |
| KR100628320B1 (en) | JP PIP Accelerator | |
| CN101222409B (en) | Bridging system and method for point-to-point link and shared link | |
| JP7193760B2 (en) | Communication device and communication method | |
| TW201123671A (en) | Distributed power management devices | |
| KR200382771Y1 (en) | A one body type equipment having a vpn and modem there inside | |
| BR112017011050B1 (en) | METHOD AND NETWORK SYSTEM FOR IMPLEMENTING SOURCE IP ADDRESS TRANSPARENCY IN A COMMUNICATION NETWORK |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 16769315 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |