The present invention relates generally to digital communications and control, and particularly to systems and methods for secure communications.
In a computer network handling sensitive data, portions of the network may be connected by one-way data links. The term “one-way link” is used in the context of the present patent application and in the claims to refer to a communication link that is physically configured to carry signals in one direction and to be incapable of carrying signals in the opposite direction. One-way links may be implemented, for example, using Waterfall® systems, which are manufactured by Waterfall Security Solutions, Ltd. (Rosh HaAyin, Israel). The Waterfall system provides a physical one-way connection based on fiberoptic communication, using an underlying proprietary transfer protocol. When a transmitting computer is connected by a Waterfall system (or other one-way link) to a receiving computer, the receiving computer can receive data from the transmitting computer but has no physical means of sending any return communications to the transmitting computer.
One-way links may be used to prevent data either from entering or leaving a protected facility. For example, confidential data that must not be accessed from external sites may be stored on a computer that is configured to receive data over a one-way link and has no physical outgoing link over which data might be transmitted to an external site. On the other hand, in some applications, the operator of the protected facility may be prepared to allow data to exit the facility freely via a one-way link, while preventing data from entering the facility in order to thwart hackers and cyber-terrorists.
In this latter category, for example, U.S. Pat. No. 7,649,452, whose disclosure is incorporated herein by reference, describes protection of control networks using a one-way link. As described in this patent, a method for monitoring a process includes receiving a signal from a sensor that is indicative of a physical attribute associated with the process and transmitting data indicative of the received signal over a one-way link. The transmitted data received from the one way link are used in monitoring the process. The method is described in the patent particularly in the context of Supervisory Control And Data Acquisition (SCADA) systems. A SCADA system receives monitoring data from the monitored facility via a one-way link. The SCADA system is unable to transmit any sort of data back to the monitored facility (although a separate, open-loop connection may be provided for this purpose), and therefore cannot be used as the base for an attack on the facility.
Embodiments of the present invention that are described hereinbelow provide apparatus and methods for automatically controlling inputs to a protected destination.
There is therefore provided, in accordance with an embodiment of the present invention, communication apparatus, including a one-way, hardware-actuated data relay, which includes a first hardware interface configured to receive a command from a communications network and a second hardware interface configured to convey the received command to a protected destination when the relay is actuated. A decoder includes a third hardware interface configured to receive a digital signature for the command from the communications network and hardware decoding logic coupled to verify the digital signature and to actuate the relay upon verifying the digital signature, whereby the command is conveyed via the second hardware interface to the protected destination.
In one embodiment, the apparatus includes a one-way link, which is separate from and independent of the one-way relay and is configured to convey output data from the protected destination to the communications network but is physically incapable of conveying input data from the communications network to the protected destination.
In a disclosed embodiment, the protected destination is a utility control station, and the command is configured to control an operating configuration of the station.
In some embodiments, the apparatus includes a transmission station, which includes hardware encoding logic, which is configured to generate the digital signature for the command so as to identify a source of the command. A communications processor is configured to transmit the digital signature over the network to the third hardware interface, and to send the command over the network from the source of the command to the first hardware interface. The hardware encoding logic may be contained in a user authentication unit, which is configured to authenticate an identity of a user of the transmission station before generating the digital signature.
In a disclosed embodiment, the apparatus includes hardware logic, which is coupled between the first and second hardware interfaces so as to receive the command from the first interface, to compare the received command to a set of hardware masks corresponding to permitted commands, and to pass the received command to the second interface only when the received command matches one of the masks.
There is also provided, in accordance with an embodiment of the present invention, communication apparatus, including a first hardware interface configured to receive a command from a communications network and a second hardware interface configured to convey the received command to a protected destination. Hardware logic is coupled between the first and second interfaces so as to receive the command from the first interface, to compare the received command to a set of hardware masks corresponding to permitted commands, and to pass the received command to the second interface only when the received command matches one of the masks.
In a disclosed embodiment, the permitted commands have a predefined data format such that each permitted command consists of a name and a permitted value associated with the name. In one embodiment, the protected destination is a utility control station, and the apparatus includes a monitor, which is coupled to receive the received command from the second interface and to decode the received command from the predefined data format to an inter-control center communications protocol for input to the utility control station. The apparatus may include a transmission station, which is configured to receive an input in accordance with the inter-control center communications protocol from a command source and to encode the input in accordance with the predefined data format for transmission over the network to the first interface.
There is additionally provided, in accordance with an embodiment of the present invention, a method for communication, which includes coupling a one-way, hardware-actuated relay to receive a command from a communications network and to convey the received command to a protected destination when the relay is actuated. A digital signature is received from the communications network and is verified using hardware decoding logic. Upon verifying the digital signature, the relay is actuated, whereby the command is conveyed to the protected destination.
There is further provided, in accordance with an embodiment of the present invention, a method for communication, which includes receiving a command directed to a protected destination from a communications network. The received command is compared to a set of hardware masks corresponding to permitted commands. The received command is passed to the protected destination only when the received command matches one of the hardware masks.
The present invention will be more fully understood from the following detailed description of the embodiments thereof, taken together with the drawings in which:
Unlike conventional firewalls, one-way links permit information to leave a protected facility without risk to the safety or availability of the network in the facility due to attacks originating on an external network. In practice, however, there is sometimes a need to transmit at least small amounts of information from an external network back into the protected facility.
There are a number of risks associated with such communications. One risk is that if malware has somehow been introduced into the protected network (possibly by insider collaboration), communications back into the protected network could be used to trigger an attack. For example, the malware could cause a computer in the facility to recognize a certain string communicated back into the protected network as a command to initiate some harmful action. Another risk is that an attacker might use the communications channel into the facility to cause unsafe or unreliable conditions in the protected network, by means of a buffer overflow attack, for instance. Such an attack could then be used to introduce remote control malware into the protected network, and provide an attacker with the means to interactively explore and sabotage the protected network.
Embodiments of the present invention that are described hereinbelow address these risks by permitting a controlled flow of small amounts of information into a protected network. The flow is automatically controlled so that software-based attacks on protected equipment become difficult or impossible to carry out, even if parts of the command and communications system themselves become compromised. In contrast to conventional firewalls, the control is carried out by hardware logic, rather than software. Consequently, remote attackers are unable to change the operating configuration of the protection logic or to cause it to perform any function other than those initially programmed by the logic designer. In the disclosed embodiments, the hardware logic is configured to control the format and content of commands that can be sent to a protected destination. The hardware logic may also authenticate these commands to ensure they were produced by an authorized transmitter. As a result, by compromising an authorized transmitter, an attacker may, at worst, be able to send an incorrect command to the destination, but will not be able to gain control over the protected facility.
Some embodiments of the present invention use the concept of a data relay—hardware that accepts and holds a set of digital input commands that are sent from a set of source hardware interfaces and directed to destination computer hardware, network(s) or CPU(s). When the relay is triggered, the inputs are transferred to the outputs of the data relay and so are made available to destination hardware interfaces of the destination computer hardware, CPU(s) or network(s). An optional authentication hardware component, such as a digital signature decoder, can be configured to trigger the data relay when authentication information, such as a digital signature, is found to match the digital input commands in the holding area of the data relay. An optional filtering hardware component, which may be part of the data relay, allows movement of the commands from the input interfaces to output interfaces if and only if the commands match a hardware mask or whitelist of allowed commands.
As noted earlier, data relays of this sort can be particularly useful in conjunction with one-way links, for example in situations in which information is allowed to flow freely out of a facility via a one-way link, while the flow of commands into the facility is strictly controlled. The principles of such data relays and secure communication proxies that are described herein, however, are by no means limited to this sort of operating environment and may be used with or without a one-way link, depending on system and application requirements.
Although the pictured example relates, by way of illustration, to an electric power utility, the principles of the present invention are not limited to this particular operating context. Rather, the apparatus and methods that are described below may be applied to utilities of other types (such as gas or water utilities, for instance), as well as in industrial environments and substantially any other application in which tight control is to be exercised over commands that may be input to a protected destination. Station 22 is just one example of such a destination, which is presented here for the sake of clarity of explanation. Certain embodiments of the present invention are described hereinbelow, for the sake of clarity and without limitation, with respect to the elements of system 20, but the principles of these embodiments and the techniques that they incorporate may similarly be applied in other operating environments in which a destination is to be protected from undesired data input and unauthorized access.
Station 22 is typically designed as a closed, secure facility, protected physically against unauthorized entry. A monitor 26 in station 22 inputs commands to switches 24 and monitors the operation of the switches and other components of the station. Typically, monitor 26 comprises multiple sensors and actuators, which are distributed throughout station 22 and report via a secure internal network to a controller (not shown), as described, for example, in the above-mentioned U.S. Pat. No. 7,649,452. Monitor 26 outputs data collected from the sensors and actuators via a one-way link 28 to a network 30, which conveys the data to terminal 32. Network 30 may comprise any suitable wired or wireless network, or a combination of such networks, including public networks, such as the Internet.
One-way link 28 conveys output data from station 22 to network 30 but is physically incapable of conveying input data from the network to the station. For this latter purpose, station 22 comprises an uplink controller 34, which typically has an interface coupled to network 30 and another interface to the protected elements of the station. In this example, controller 34 inputs commands to monitor 26, which then actuates switches 24 to carry out the commands. Uplink controller 34 comprises hardware logic, which authenticates the commands that are input to monitor 26 and limits the times, quantities, and/or content of these commands, as described further hereinbelow. Monitor 26 receives no inputs from network other than via uplink controller 34, which is typically contained in station 22 and is thus itself protected from physical and electrical tampering.
Commands initiated by an operator of terminal 32 (or possibly initiated autonomously by the terminal itself) are formatted by a processor 36, which typically comprises a general-purpose computer processor running standard software. The commands may be formulated in accordance with a standard protocol, such as the inter-control center communications protocol (ICCP), as is known in the art. A secure encoder 38 operates in conjunction with processor 36 so as to transmit inputs to uplink controller 34 in the proper, authenticated form. Typically (although not necessarily), encoder 38 also comprises hardware logic, to prevent an attacker from mimicking or gaining control over the encoding functions. Even if an attacker does gain control over encoder 38, however, the damage he or she will be able to do to station 22 will generally be limited to inputting incorrect commands (such as improper settings of switches 24), as other commands are blocked by the protective logic in uplink controller 34.
A communication interface 44 in terminal 32 generates a communication stream containing the encoded command for transmission over network 30 to station. Interface 44 may, for example, establish a secure connection (such as a Transport Layer Security [TLS] encrypted connection, as is known in the art) with a corresponding communication interface 46 of uplink controller 34. This sort of conventional data security measure adds a further layer of protection to the operation of the dedicated hardware logic.
Communication interface 46 passes commands that it receives to hardware decoding logic 48, which like encoder 42 typically contains no CPU or other software-driven components. Like encoder 42, decoder 48 may be part of a larger hardware/software decoder unit 49. Logic 48 may authenticate received commands, and accept only authentic commands. Logic 48 decodes accepted commands and compares each such command to a set of predefined hardware masks corresponding to permitted commands (such as permitted couples of names and values, as described above). Commands that match one of the masks are passed through to a command destination 50, such as monitor 26. Assuming monitor 26 comprises standard components, decoder unit 49 may decode these commands back into a conventional format, such as ICCP, to which these components are programmed to respond. Decoder 48 rejects commands that do not match any of the predefined hardware masks. As a result, only commands that invoke certain predefined, permitted actions in station 22 will reach monitor 26, while malformed or otherwise dangerous commands that could be used to mount an attack are blocked.
Authentication unit 52 may comprise a plug-in user authentication unit, which generates the digital signature only after authenticating the identity of the operator of terminal 32 who is inputting the commands. For this purpose, unit 52 may comprise, for example, a secure memory with a secret key and encryption circuits for generating the digital signature, as is known in the art. For enhanced security, unit 52 may comprise a keypad for input of a password by the user and/or a biometric identification device, such as a fingerprint reader. Additionally or alternatively, unit 52 may include a timestamp and/or sequence number in the signatures that it generates in order to foil replay attacks.
Uplink controller 34 has two interfaces to network 30: communication interface 46, which receives the digital signatures generated by authentication unit 52, and an input interface to a one-way, hardware-actuated relay 56, which receives the commands generated by processor 36. The two interfaces may be separate physical interfaces or simply separate ports on a single physical interface. Interface 46 passes the digital signatures to a decoder 54, comprising hardware decoding logic, which verifies the digital signature. Upon verifying that the signature is correct and authentic, decoder 54 actuates relay 56, so that the command sent by processor 36 is conveyed through the relay to monitor 26.
In this manner, the command input to monitor 26 is open for only short, controlled periods of time. All transmissions outside these periods (whether from terminal 32 or other sources) are blocked. Because decoder 54 and relay 56 are implemented in hardware, which is located inside the protected environment of station 22, it is essentially impossible to bypass their blocking functionality by means of a software attack. The time periods during which relay 56 is actuated may be short (typically less than 10 sec, and possibly less than sec, for instance), and the amount of data permitted through each time the relay opens may be restricted to a certain number of bytes. Consequently, even if an attacker is able to gain control of authentication unit 52, his or her ability to interact through uplink controller 34 with other elements of station 22 will still be very limited. The switching functions of decoder 54 and relay 56 may be combined with the masking function of the embodiment of
Upon successfully verifying an incoming digital signature, logic 54 signals a secure, internal microcontroller 72, which may similarly comprise an ARM9 processing unit with a memory 74. Microcontroller 72 instructs relay control logic 56 to open a one-way data relay from an input interface 76, which is connected to network 30, to an output interface 78, which is connected to monitor 26. Like interface 46, interfaces 76 and 78 comprise suitable hardware components, such as Ethernet interfaces, although other communication standards may similarly be supported.
In the embodiment of
In similar fashion, secure ICCP proxy 88 receives ICCP data reports from DCS 84 and converts and encodes the reports for transmission to proxy 86. Proxy 86 decodes and converts the data back into ICCP format and passes the data to EMS 82, as though the DCS had communicated the reports directly to the EMS using ICCP.
The configuration shown in
It thus will be appreciated that the embodiments described above are cited by way of example, and that the present invention is not limited to what has been particularly shown and described hereinabove. Rather, the scope of the present invention includes both combinations and subcombinations of the various features described hereinabove, as well as variations and modifications thereof which would occur to persons skilled in the art upon reading the foregoing description and which are not disclosed in the prior art.
Number | Name | Date | Kind |
---|---|---|---|
3377541 | Farkas | Apr 1968 | A |
4163289 | Schmidt | Jul 1979 | A |
4213177 | Schmidt | Jul 1980 | A |
4214302 | Schmidt | Jul 1980 | A |
4375665 | Schmidt | Mar 1983 | A |
4964046 | Mehrgardt et al. | Oct 1990 | A |
4985919 | Naruse et al. | Jan 1991 | A |
4987595 | Marino, Jr. et al. | Jan 1991 | A |
5140681 | Uchiyama et al. | Aug 1992 | A |
5163138 | Thirumalai | Nov 1992 | A |
5185877 | Bissett et al. | Feb 1993 | A |
5289478 | Barlow et al. | Feb 1994 | A |
5530758 | Marino, Jr. et al. | Jun 1996 | A |
5548646 | Aziz et al. | Aug 1996 | A |
5677952 | Blakley et al. | Oct 1997 | A |
5696822 | Nachenberg | Dec 1997 | A |
5732278 | Furber et al. | Mar 1998 | A |
5748871 | DuLac et al. | May 1998 | A |
5829046 | Tzelnic et al. | Oct 1998 | A |
5835726 | Shwed et al. | Nov 1998 | A |
5940507 | Cane et al. | Aug 1999 | A |
5946399 | Kitaj et al. | Aug 1999 | A |
5995628 | Kitaj et al. | Nov 1999 | A |
6023570 | Tang et al. | Feb 2000 | A |
6026502 | Wakayama | Feb 2000 | A |
6049611 | Tatebayashi et al. | Apr 2000 | A |
6167459 | Beardsley et al. | Dec 2000 | A |
6170023 | Beardsley et al. | Jan 2001 | B1 |
6185638 | Beardsley et al. | Feb 2001 | B1 |
6202095 | Beardsley et al. | Mar 2001 | B1 |
6239810 | Van Hook et al. | May 2001 | B1 |
6240514 | Inoue et al. | May 2001 | B1 |
6289377 | Lalwaney et al. | Sep 2001 | B1 |
6317831 | King | Nov 2001 | B1 |
6356546 | Beshai | Mar 2002 | B1 |
6467009 | Winegarden et al. | Oct 2002 | B1 |
6470449 | Blandford | Oct 2002 | B1 |
6574640 | Stahl | Jun 2003 | B1 |
6601126 | Zaidi et al. | Jul 2003 | B1 |
6615244 | Singhal | Sep 2003 | B1 |
6640308 | Keyghobad et al. | Oct 2003 | B1 |
6643701 | Aziz et al. | Nov 2003 | B1 |
6738388 | Stevenson et al. | May 2004 | B1 |
6754185 | Banerjee et al. | Jun 2004 | B1 |
6820110 | Engel et al. | Nov 2004 | B1 |
6862663 | Bateman | Mar 2005 | B1 |
6915369 | Dao et al. | Jul 2005 | B1 |
6915435 | Merriam | Jul 2005 | B1 |
6931549 | Ananda | Aug 2005 | B1 |
6957330 | Hughes | Oct 2005 | B1 |
6963817 | Ito et al. | Nov 2005 | B2 |
6966001 | Obara et al. | Nov 2005 | B2 |
6970183 | Monroe | Nov 2005 | B1 |
6986061 | Kunzinger | Jan 2006 | B1 |
7031322 | Matsuo | Apr 2006 | B1 |
7062587 | Zaidi et al. | Jun 2006 | B2 |
7143289 | Denning et al. | Nov 2006 | B2 |
7171566 | Durrant | Jan 2007 | B2 |
7200693 | Jeddeloh | Apr 2007 | B2 |
7254663 | Bartley et al. | Aug 2007 | B2 |
7260833 | Schaeffer | Aug 2007 | B1 |
7324515 | Chapman | Jan 2008 | B1 |
7366894 | Kalimuthu et al. | Apr 2008 | B1 |
7469311 | Tsu et al. | Dec 2008 | B1 |
7486651 | Hagiwara et al. | Feb 2009 | B2 |
7509141 | Koenck et al. | Mar 2009 | B1 |
7631189 | Ichinose et al. | Dec 2009 | B2 |
7649452 | Zilberstein et al. | Jan 2010 | B2 |
7660959 | Asher et al. | Feb 2010 | B2 |
7675867 | Mraz et al. | Mar 2010 | B1 |
7685436 | Davis et al. | Mar 2010 | B2 |
7685636 | Leake et al. | Mar 2010 | B2 |
7698470 | Ruckerbauer et al. | Apr 2010 | B2 |
7716467 | Deffet et al. | May 2010 | B1 |
7757074 | Sundarrajan et al. | Jul 2010 | B2 |
7761529 | Choubal et al. | Jul 2010 | B2 |
7761704 | Ho et al. | Jul 2010 | B2 |
7792300 | Caronni | Sep 2010 | B1 |
7814316 | Hughes et al. | Oct 2010 | B1 |
7815548 | Barre et al. | Oct 2010 | B2 |
7845011 | Hirai | Nov 2010 | B2 |
7849330 | Osaki | Dec 2010 | B2 |
7941828 | Jauer | May 2011 | B2 |
7992209 | Menoher et al. | Aug 2011 | B1 |
8041832 | Hughes et al. | Oct 2011 | B2 |
8046443 | Parker et al. | Oct 2011 | B2 |
8223205 | Frenkel et al. | Jul 2012 | B2 |
20010033332 | Kato et al. | Oct 2001 | A1 |
20020065775 | Monaghan | May 2002 | A1 |
20020066018 | Linnartz | May 2002 | A1 |
20020083120 | Soltis | Jun 2002 | A1 |
20020112181 | Smith | Aug 2002 | A1 |
20020114453 | Bartholet et al. | Aug 2002 | A1 |
20020178370 | Gurevich et al. | Nov 2002 | A1 |
20020186839 | Parker | Dec 2002 | A1 |
20020191866 | Tanabe | Dec 2002 | A1 |
20020199181 | Allen | Dec 2002 | A1 |
20030012378 | Yura | Jan 2003 | A1 |
20030037247 | Obara et al. | Feb 2003 | A1 |
20030039354 | Kimble et al. | Feb 2003 | A1 |
20030055792 | Kinoshita et al. | Mar 2003 | A1 |
20030061505 | Sperry et al. | Mar 2003 | A1 |
20030114204 | Allen et al. | Jun 2003 | A1 |
20030140090 | Rezvani et al. | Jul 2003 | A1 |
20030140239 | Kuroiwa et al. | Jul 2003 | A1 |
20030159029 | Brown et al. | Aug 2003 | A1 |
20030177401 | Arnold et al. | Sep 2003 | A1 |
20030188102 | Nagasoe et al. | Oct 2003 | A1 |
20030200460 | Morota et al. | Oct 2003 | A1 |
20030212845 | Court et al. | Nov 2003 | A1 |
20030217262 | Kawai et al. | Nov 2003 | A1 |
20040022107 | Zaidi et al. | Feb 2004 | A1 |
20040070620 | Fujisawa | Apr 2004 | A1 |
20040071311 | Choi et al. | Apr 2004 | A1 |
20040080615 | Klein et al. | Apr 2004 | A1 |
20040175123 | Lim et al. | Sep 2004 | A1 |
20040217890 | Woodward et al. | Nov 2004 | A1 |
20040247308 | Kawade | Dec 2004 | A1 |
20050015624 | Ginter et al. | Jan 2005 | A1 |
20050033990 | Harvey et al. | Feb 2005 | A1 |
20050060693 | Robison | Mar 2005 | A1 |
20050085964 | Knapp et al. | Apr 2005 | A1 |
20050091173 | Alve | Apr 2005 | A1 |
20050119967 | Ishiguro et al. | Jun 2005 | A1 |
20050120251 | Fukumori et al. | Jun 2005 | A1 |
20050122930 | Zhao et al. | Jun 2005 | A1 |
20050138369 | Lebovitz et al. | Jun 2005 | A1 |
20050165939 | Nikunen et al. | Jul 2005 | A1 |
20050216648 | Jeddeloh | Sep 2005 | A1 |
20050264415 | Katz | Dec 2005 | A1 |
20050270840 | Kudelski | Dec 2005 | A1 |
20060026292 | Namioka et al. | Feb 2006 | A1 |
20060047887 | Jeddeloh | Mar 2006 | A1 |
20060064550 | Katsuragi et al. | Mar 2006 | A1 |
20060085354 | Hirai | Apr 2006 | A1 |
20060085534 | Ralston et al. | Apr 2006 | A1 |
20060095629 | Gower et al. | May 2006 | A1 |
20060136724 | Takeshima et al. | Jun 2006 | A1 |
20060165108 | Uysal | Jul 2006 | A1 |
20060165347 | Mita | Jul 2006 | A1 |
20060179208 | Jeddeloh | Aug 2006 | A1 |
20060195704 | Cochran et al. | Aug 2006 | A1 |
20060220903 | Zigdon et al. | Oct 2006 | A1 |
20060224848 | Matulik et al. | Oct 2006 | A1 |
20060248582 | Panjwani et al. | Nov 2006 | A1 |
20060259431 | Poisner | Nov 2006 | A1 |
20060271617 | Hughes et al. | Nov 2006 | A1 |
20060288010 | Chen et al. | Dec 2006 | A1 |
20060294295 | Fukuzo | Dec 2006 | A1 |
20070028027 | Janzen et al. | Feb 2007 | A1 |
20070028134 | Gammel et al. | Feb 2007 | A1 |
20070043769 | Kasahara et al. | Feb 2007 | A1 |
20070055814 | Jeddeloh | Mar 2007 | A1 |
20070063866 | Webb | Mar 2007 | A1 |
20070112681 | Niwano et al. | May 2007 | A1 |
20070112863 | Niwata et al. | May 2007 | A1 |
20070174362 | Pham et al. | Jul 2007 | A1 |
20070192608 | De Arruda Villela | Aug 2007 | A1 |
20070203970 | Nguyen | Aug 2007 | A1 |
20070204140 | Shade | Aug 2007 | A1 |
20070283297 | Hein et al. | Dec 2007 | A1 |
20080005325 | Wynn et al. | Jan 2008 | A1 |
20080008207 | Kellum | Jan 2008 | A1 |
20080066192 | Greco et al. | Mar 2008 | A1 |
20080082835 | Asher et al. | Apr 2008 | A1 |
20080155273 | Conti | Jun 2008 | A1 |
20080244743 | Largman et al. | Oct 2008 | A1 |
20090002150 | Zilberstein | Jan 2009 | A1 |
20090019325 | Miyamoto et al. | Jan 2009 | A1 |
20090055647 | Yu | Feb 2009 | A1 |
20090113500 | Frenkel | Apr 2009 | A1 |
20090319773 | Frenkel | Dec 2009 | A1 |
20090328183 | Frenkel | Dec 2009 | A1 |
20100275039 | Frenkel et al. | Oct 2010 | A1 |
20110107023 | McCallister et al. | May 2011 | A1 |
20110213990 | Poisner | Sep 2011 | A1 |
20110296175 | Shin | Dec 2011 | A1 |
20120268596 | Frenkel et al. | Oct 2012 | A1 |
20130024700 | Peterson et al. | Jan 2013 | A1 |
20130152206 | Staubly | Jun 2013 | A1 |
20130297935 | Oswalt | Nov 2013 | A1 |
20140007194 | Tucker | Jan 2014 | A1 |
20140020109 | Mraz et al. | Jan 2014 | A1 |
20140040679 | Shimizu et al. | Feb 2014 | A1 |
20140122965 | Zeng et al. | May 2014 | A1 |
Number | Date | Country |
---|---|---|
1632833 | Mar 2006 | EP |
2371125 | Jul 2002 | GB |
0163879 | Aug 2001 | WO |
Entry |
---|
NPL1 (“Waterfall Technology”, Jun. 2009, Applicant's submitted prior art). |
U.S. Appl. No. 12/438,548 Office Action dated Jul. 11, 2013. |
Schneier, B., “Applied Cryptography”, Chapter 15, pp. 357-358, published by John Wiley & Sons, Inc, year 1996. |
U.S. Appl. No. 13/487,265 Office Action dated Nov. 22, 2013. |
U.S. Appl. No. 12/438,548 Office Action dated Feb. 22, 2013. |
U.S. Appl. No. 13/487,265 Office Action dated Mar. 6, 2014. |
EP Patent Application # 13182696.8 Search Report dated Apr. 3, 2014. |
EP Patent Application # 08702651.4 Search report dated May 11, 2012. |
Frenkel, L., “Unidirectional Information Transfer”, Web issue, Jun. 2005. |
U.S. Appl. No. 12/447,470 Official Action dated Sep. 14, 2011. |
U.S. Appl. No. 12/447,470 Official Action dated Feb. 9, 2012. |
U.S. Appl. No. 12/438,548 Official Action dated Mar. 6, 2012. |
U.S. Appl. No. 12/306,692 Official Action dated Feb. 13, 2012. |
European Patent Application # 07805530.8 Search report dated Mar. 6, 2012. |
IL Patent Application # 177,756 Official Action dated Aug. 17, 2010. |
IL Patent Application # 180,748 Official Action dated Oct. 25, 2010. |
IL Patent Application # 201473 Official Action dated May 8, 2011. |
U.S. Appl. No. 12/447,470 Official Action dated Mar. 25, 2011. |
U.S. Appl. No. 11/823,950 Official Action dated Jun. 22, 2009. |
U.S. Appl. No. 12/306,692 Official Action dated Sep. 28, 2011. |
International Application PCT/IL2008/000886 Search Report dated Nov. 13, 2008. |
International Application PCT/IL2008/000070 Search Report dated Jun. 16, 2008. |
International Application PCT/IL2007/001070 Search Report dated Jul. 25, 2008. |
International Application PCT/IL2006/001499 Search Report dated Apr. 8, 2008. |
International Application PCT/IIL2008/001513 Search Report dated Mar. 10, 2009. |
Innominate Security Technologies, “Press Release: Innominate joins Industrial Defender Enabled Partner Program”, Germany, Apr. 14, 2008 (http://www.innominate.com/content/view/288/120/lang,en/). |
Waterfall Security Solutions Ltd., “Waterfall One Way Link Technology”, 2008 ( http://www.waterfall-solutions.com/home/Waterfall.sub.--Technology.a-spx). |
MSISAC, “Cyber Security Procurement Language for Control Systems”, version 1.8, revision 3, Feb. 2008 (http://www.msisac.org/scada/documents/4march08scadaprocure.pdf). |
Axis Communications, “Axis Network Cameras”, 2008 (http://www.axis.com/products/video/camera/index.htm). |
Check Point Software Technologies Ltd., “Extended Unified Threat Management capabilities with new multi-layer messaging security deliver best all-inclusive security solution”, USA, Nov. 18, 2008 (http://www.checkpoint.com/press/2008/utm-1-edge-upgrade-111808.html). |
Einey, D., “Waterfall IP Surveillance Enabler”, Jul. 2007. |
U.S. Appl. No. 11/977,391 Official Action dated Jun. 14, 2011. |
U.S. Appl. No. 12/447,470 Official Action dated Aug. 30, 2012. |
EP Patent Application # 06832267.6 Search Report dated Jun. 3, 2014. |
IBM Technical Disclosure Bulletin, Separate Write/Read Logical Paths to Optimize Library Network File System Data Rates, vol. 37, No. 09, pp. 1-3, Sep. 1994. |
U.S. Appl. No. 14/248,419 Office Action dated Jul. 25, 2014. |
U.S. Appl. No. 12/306,692 Office Action Dated Aug. 12, 2014. |
EP Patent Application # 14162141.7 Search Report dated Jun. 3, 2014. |
U.S. Appl. No. 13/867,145 Office Action dated Aug. 14, 2015. |
IEEE Standards Information Network, “The Authoritative Dictionary of IEEE Terms”, IEEE Press, 7th Edition, p. 1154, 2000. |
U.S. Appl. No. 13/867,145 Office Action dated Feb. 26, 2016. |
U.S. Appl. No. 14/800,708 Office Action dated Mar. 25, 2016. |
Number | Date | Country | |
---|---|---|---|
20140068712 A1 | Mar 2014 | US |