Embodiments disclosed herein relate generally to methods and systems for computer connectivity and, more particularly, to methods and systems for establishing and providing secure connections between computers.
The use of computer networks to store data and provide information to users is increasingly common. In fact, in many cases it may be necessary for a computer to be connected to a specific network to retrieve data desired or needed by a user. To connect to a specific network, a user at a client computer may utilize a network connection, such as the Internet, to connect to a computer belonging to the network.
The Internet is a loosely organized network of computers spanning the globe. Client computers, such as home computers, can connect to other clients and servers on the Internet through a local or regional Internet Service Provider (“ISP”) that further connects to larger regional ISPs or directly to one of the Internet's “backbones.” Regional and national backbones are interconnected through long range data transport connections such as satellite relays and undersea cables. Through these layers of interconnectivity, each computer connected to the Internet can connect to every other (or at least a large percentage) of other computers on the Internet. Utilizing the Internet, a user may connect to any of the networks within the Internet.
The arrangement of the Internet, however, presents a whole host of security concerns. These concerns revolve mainly around the fact that communications between a client computer and a server computer residing in a remote network may travel through a wide variety of other computers and networks before arriving at their eventual destinations. If these communications are not secured, they are readily accessible to anyone with a basic understanding of network communication protocols.
To alleviate these security concerns, a virtual private network or VPN may be established between a client computer and another network. A VPN may allow private and secure communications between computers over a public network, while maintaining privacy through the use of a tunneling protocol and security procedures. These tunneling protocols allow traffic to be encrypted at the edge of one network or at an originating computer, moved over a public network like any other data, and then decrypted when it reaches a remote network or receiving computer. This encrypted traffic acts like it is in a tunnel between the two networks or computers: even if an attacker can see the traffic, they cannot read it, and they cannot change the traffic without the changes being seen by the receiving party and therefore being rejected.
VPNs are similar to wide area networks (WAN), but the key feature of VPNs is that they are able to use public networks like the Internet rather than rely on expensive, private leased lines. At the same time, VPNs have the same security and encryption features as a private network, while adding the advantage of the economies of scale and remote accessibility of large public networks.
VPNs today are set up a variety of ways, and can be built over ATM, frame relay, and X.25 technologies. However, the most popular current method is to deploy IP-based VPNs, which offer more flexibility and ease of connectivity. Since most corporate intranets use IP or Web technologies, IP-VPNs can more transparently extend these capabilities over a wide network. An IP-VPN link can be set up anywhere in the world between two endpoints, and the IP network automatically handles the traffic routing.
A VPN, however, is not without its flaws. First of all, to establish a VPN, both computers must utilize identical VPN protocols. As there are a wide variety of VPN protocols in use, such as PPTP, IPsec, L2TP etc. this is by no means guaranteed. If identical protocols are not originally on one or more of the computers, identical protocols must be installed on both of these systems before a VPN may be established.
Additionally, even if the computers are running the same protocol, this protocol may still have to be manually setup and configured. In many cases, every time a remote user wishes to establish a VPN with a computer over an existing network he must bring up the VPN protocol he wishes to use and properly configure it to work with the remote computer or network he wishes to access.
These installation and configuration issues may present problems to someone who is not well versed in the area of network protocols, and may even present problems for those who are familiar with these protocols, as typically a remote user must configure his computer without access to the gateway to which he wishes to connect.
Even more problematic, however, is that setting up a VPN still presents security issues. Almost universally, a gateway at a remote network is not going to establish a VPN with a random remote computer. In most cases, the remote gateway requires a username and a password before it will establish a VPN connection. This username and password is sent from the remote user in an unsecured form, or encrypted using a weak encryption algorithm. As this username and password are easily snooped by malicious users of a public network, a security hole exists within the very process of trying to create a VPN to provide greater security.
Thus, a need exists for more secure methods and systems for establishing a secure connection between computers which require minimum amounts of manual configuration.
Systems and methods for establishing or providing a secure connection between networked computers are disclosed. A computer may make a request for a secure connection to another computer. In response, configuration data may be sent to the requesting computer. This configuration data may execute on the requesting computer in order to create a secure connection between the two computers. Using this secure connection, data may be passed between the two computers with a greater degree of privacy.
Furthermore, protocols inherent to particular operating systems may be utilized to setup and establish a secure connection between networked computers in an automated fashion, requiring no manual intervention or configuration by the user of a computer. The configuration data sent to the requesting computer may automatically configure a protocol on the requesting computer and automatically establish a secure connection with another networked computer.
In one embodiment, a connection is requested in a first protocol, data is sent in response to the request, a second protocol is configured using the data and a secure connection is established using the second protocol.
In another embodiment, the first protocol is HTTPS.
In yet another embodiment, the data is sent using the first protocol.
In other embodiments, the request for the connection includes a username and a password.
In still other embodiments, data is sent only if the username and password are verified.
In yet other embodiments, the data includes a controller.
In some embodiments, the controller is an Active X controller.
In a particular embodiment, the data includes a credential and the secured connection is established using the credential.
In one embodiment, the credential is dynamically generated in response to the request and includes a password and a username.
In additional embodiments, the credential is valid only for the duration of the secure connection.
In other embodiments, the second protocol is PPTP and is configured automatically using the controller.
In one embodiment, the secure connection is established automatically using the controller.
These, and other, aspects of the invention will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. The following description, while indicating various embodiments of the invention and numerous specific details thereof, is given by way of illustration and not of limitation. Many substitutions, modifications, additions or rearrangements may be made within the scope of the invention, and the invention includes all such substitutions, modifications, additions or rearrangements.
The drawings accompanying and forming part of this specification are included to depict certain aspects of the invention. A clearer impression of the invention, and of the components and operation of systems provided with the invention, will become more readily apparent by referring to the exemplary, and therefore nonlimiting, embodiments illustrated in the drawings, wherein identical reference numerals designate the same components. Note that the features illustrated in the drawings are not necessarily drawn to scale.
The invention and the various features and advantageous details thereof are explained more fully with reference to the nonlimiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well known starting materials, processing techniques, components and equipment are omitted so as not to unnecessarily obscure the invention in detail. It should be understood, however, that the detailed description and the specific examples, while indicating preferred embodiments of the invention, are given by way of illustration only and not by way of limitation. After reading the specification, various substitutions, modifications, additions and rearrangements will become apparent to those skilled in the art from this disclosure which do not depart from the scope of the appended claims.
Initially, a few terms are defined to aid the reader in an understanding of the following disclosure. The term “controller” is intended to mean any set of data or instructions operable to perform certain tasks or a combination of hardware (such as a processor) and software instructions capable of performing a certain task.
The term “networked” is intended to mean operable to communicate. For example, two networked computers are operable to communicate with one another using techniques known in the art, such as via a wireless or wired connection using TCP/IP. Two computers may be networked through a variety of networks, sub-networks, etc.
Before discussing embodiments of the invention, an exemplary architecture for use in illustrating embodiments of the invention is described. It will be apparent to those of ordinary skill in the art that this is a simple architecture intended for illustrative embodiments only, and that the systems and methods described herein may be employed with any variety of more complicated architectures. Each of the computers depicted may include desktops, laptops, PDAs or any other type of device capable of communicating, either via wireless or wired connection, over a network. Each network depicted, whether they be intranets or any other type of network, may include sub-networks or any combination of networks and sub-networks
Attention is now directed to systems and methods for establishing a secure connection between two computers over a network according to one embodiment of the invention. Typically, a user at a remote client computer wishes to establish a connection with an intranet or a computer within an intranet. To accomplish this, the remote client computer and a server computer belonging to the intranet may create a VPN so information may be securely transferred between the remote client computer and the server computer or other computers within the intranet. To securely establish this VPN with a minimum of configuration, the remote client computer may make a request for a VPN connection to the server. In response, the server may send configuration data to the remote client computer. This configuration data may execute on the remote client computer in order to create a secure VPN connection between the remote client and the server. Using this secure connection, data may be passed between server and remote client with a greater degree of privacy.
These systems and methods may be explained in more detail with reference to the exemplary hardware architecture of
In one particular embodiment, to obtain connectivity between remote client computer 140 and server 120 a transient VPN may be established between server 120 and remote client computer 140 using public network 130. This transient VPN may provide a dynamic, secure connection between remote client computer 140 and server 120 by creating a transient VPN endpoint on remote client computer 140 that connects through a VPN tunnel to server 120. This VPN connection may be established using a wide variety of VPN protocols, as are known in the art, such as PPTP, IPsec, L2TP, etc.
Furthermore, protocols inherent to particular operating systems may be utilized to setup and establish a transient VPN endpoint on remote client computer 140 in an automated fashion, requiring no manual intervention or configuration by the user of remote client computer 140. For example, suppose remote computer 140 and server are both executing a Windows based operating of the type developed by Microsoft, such as Windows98, WindowsXP, Windows2000, etc. As Windows based operating system have the PPTP VPN protocol built into them, this protocol may be used advantageously to automatically establish a VPN between remote client computer 140 and server 120 if both are executing a Windows based operating system.
Turning now to
At any time after the desired protocol is installed on the computers (Step 210), a secure connection may be requested by one of the computers (Step 220). For example, remote client computer 140 may request a secure connection from server computer 120. This request (Step 220) may be in any format used to communicate over the network connection between the two computers, such as FTP, HTTP or HTTPS. In response to this request (Step 220), a response may be sent to the requesting computer (Step 230). This response (Step 230) may be sent to the requesting computer using the same format used in the initial request (Step 220), such as FTP, HTTP or HTTPS, and include a set of data designed to establish a secure connection between the two computers using a particular protocol. This set of data may comprise a controller configured to execute on the requesting computer and a set of credentials to be used in conjunction with the controller.
The set of data sent in this response (Step 230) may provide information to be utilized by a protocol on the requesting computer when connecting to a particular networked computer using the protocol (Step 240). This information may include the IP address or host name of a server, the authentication domain name, whether MPPC is to be utilized, which call-control and management protocol is to be used, a DNS configuration etc. Providing this information to the protocol may be referred to as “configuring a protocol” and that phrase will be used as such herein. In some instances, a controller contained in the response to the requesting computer executes on the initiating computer and configures the protocol to establish a secure connection using the credentials contained in the response (Step 230).
After this configuration process (Step 240), a secure connection may be initiated using the configured protocol (Step 250), and a secure connection established (Step 260). In some instances, a request for a secure connection may be initiated by the same controller responsible for configuring the protocol, and include the credentials contained in the sent response (Step 230). After verifying the credentials a secure connection may be established (Step 260).
It will be clear to those of ordinary skill in the art that the method depicted in the flow diagram of
Note that
In fact, embodiments of the methods and systems of the invention may be particularly useful in establishing a secure connection between two computers by automatically configuring a protocol built into an operating systems executing on both of the computers, alleviating the need for a user to install or configure such a protocol manually.
Using this browser, a client at remote client computer 140 may navigate to a particular URL in a known manner, perhaps by typing it directly into an address window within the browser, accessing the URL in his bookmarks file, or navigating to the URL by clicking on an HTTP link within a page. By pointing his browser to a particular URL, the user at remote client computer 140 initiates a connection request to server 120 computer. This URL may also contain an HTML form requesting a username and password from a user at remote computer 140, in order to authenticate a user at remote computer 140.
In some embodiments, this connection request (Step 220) is sent from HTTP client on remote client computer 140 to server 120 using HTTP. However, to better secure the connection request, in other embodiments the connection request from remote client computer 140 to server computer is made using HTTPS, which may be sent via an SSL connection between remote client computer 140 and server computer 120.
In response to the connection request (Step 220) from remote client computer 140, server computer 120 may send data to remote client computer 140 which will facilitate the establishment of a VPN connection between server and remote client computer (Step 230). If the connection request (Step 220) from remote client computer 140 contained a username or password, server computer 120 may first authenticate or authorize the requesting user at remote client computer 140. Logic on server computer 120 may verify the username or password submitted in the connection request (Step 220) possibly by authenticating them against a form of user database (RADIUS, LDAP, etc.). If the user's authentication profile permits, server 120 may then send a response to remote client computer 140 with the configuration data (Step 230). This data may include VPN client software designed to utilize a VPN protocol on remote client computer 140 to automatically establish a secure VPN connection between server computer 120 and remote client computer 140 without any action by the user of remote client computer 140.
In one specific embodiment, the VPN client software is sent to remote client computer 140 using HTTPS, and includes a controller designed to establish a secure VPN connection between server 120 and remote client computer 140, and a set of credentials. These credentials may be session specific, and dynamically generated by server computer 120 using a random-seed. Additionally, this VPN client software may be digitally signed with an X.509 digital certificate, of the type know in the art, so that remote client computer 140 recognizes that the origin of the VPN client software is server computer 120. Once the origin of VPN client software is verified, it may then be installed or executed on remote client computer 140 to establish a secure VPN connection.
Once VPN client software 400 is downloaded and controller 410 executed, controller 410 may establish a secure VPN connection between remote client computer 140 and server 120. To continue with the above example, remote client computer 140 may be executing a Windows based operating system, and controller 410 may be an Active X controller designed specifically to configure the PPTP bundled in the Windows operating system software. Therefore, once VPN client software 400 is downloaded to remote client computer 140, Active X controller 410 may execute automatically on remote client computer 140, making system library calls to configure the PPTP resident on remote client computer 140 as a PPTP client.
Using the configured PPTP client, Active X controller 410 may then automatically establish a secure VPN connection with server computer 120. This secure connection may be automatically established by controller 410 by making additionally system library calls on remote client computer 140 to initiate a tunnel request (Step 240) from remote client computer 140 to server computer 120. As noted above, PPTP libraries are installed with most Windows based operating systems. Thus, Active X controller executing on remote client computer 140 may configure the PPTP to establish a secure VPN connection with remote server and initiate a tunnel request, without any interference or input by a user of remote client computer 140.
Additionally, in some embodiments, controller 410 may utilize credentials 420 in establishing the secure VPN connection between server computer 120 and remote client computer 140. As mentioned above, credentials 420 may have been dynamically generated by server computer 120 and sent in the response (Step 230) to initial connection request (Step 220). Credentials 420 may contain a password and username. Controller 410 may use this username and password as parameters when establishing the VPN connection between remote client computer and server computer. Credentials may be sent with tunnel request (Step 250) and verified by server computer 120 before establishing a VPN connection with remote computer 140. Since server computer 120 initially created credentials 420, server may identify the credentials from remote client computer 140 and associate a particular VPN connection with a particular remote client computer.
Credentials 420, including the username and password may then be used for the duration of that particular session between remote client computer 140 and server computer 140. Once the VPN connection between remote client computer and server computer is severed, username and password may lose their validity, preventing their unauthorized use in the future.
Embodiments of the systems and methods disclosed will be useful in a variety of architectures, as will be apparent to those of skill in the art after reading this disclosure.
For example, after remote client computer 140 enters the range of wireless router 510, remote client computer 140 may associate with access point 514. Remote client computer 140 may then request a secure connection with server 512 via a browser based interface. Client software 400, including controller 410 and credentials 420 may be downloaded to remote client computer 140 using HTTPS, at which point the controller automatically configures the PPTP on remote client computer 140 and establish a VPN tunnel between remote client computer 140 and wireless access point 514. From this point, wireless communications between remote client computer and access point 514 may be made using this VPN tunnel, and are therefore, more secure.
Although the present disclosure has been described in detail herein with reference to the illustrative embodiments, it should be understood that the description is by way of example only and is not to be construed in a limiting sense. It is to be further understood, therefore, that numerous changes in the details of the embodiments disclosed herein and additional embodiments will be apparent to, and may be made by, persons of ordinary skill in the art having reference to this description. Accordingly, the scope of the present disclosure should be determined by the following claims and their legal equivalents.
This is a continuation of U.S. patent application Ser. No. 12/617,211, filed Nov. 12, 2009, now U.S. Pat. No. 8,108,915, issued Jan. 31, 2012, entitled “SYSTEM AND METHOD FOR PROVIDING A SECURE CONNECTION BETWEEN NETWORKED COMPUTERS,” which is a continuation of U.S. patent application Ser. No. 10/922,041, filed Aug. 19, 2004, now U.S. Pat. No. 7,624,438, issued on Nov. 24, 2009, entitled “SYSTEM AND METHOD FOR PROVIDING A SECURE CONNECTION BETWEEN NETWORKED COMPUTERS,” which claims a benefit of priority under 35 U.S.C. Section 119(e) to the filing date of U.S. Provisional Application No. 60/496,629, filed Aug. 20, 2003, entitled “SYSTEM AND METHOD FOR PROVIDING A SECURE CONNECTION BETWEEN NETWORKED COMPUTERS,” the entire contents of which are hereby incorporated by reference herein for all purposes.
Number | Name | Date | Kind |
---|---|---|---|
5623601 | Vu | Apr 1997 | A |
5673393 | Marshall et al. | Sep 1997 | A |
5706427 | Tabuki | Jan 1998 | A |
5748901 | Afek et al. | May 1998 | A |
5835727 | Wong et al. | Nov 1998 | A |
5878231 | Baehr et al. | Mar 1999 | A |
5896499 | McKelvey | Apr 1999 | A |
5901148 | Bowen et al. | May 1999 | A |
5936542 | Kleinrock et al. | Aug 1999 | A |
5953506 | Kalra et al. | Sep 1999 | A |
5987134 | Shin et al. | Nov 1999 | A |
5996013 | Delp et al. | Nov 1999 | A |
6085241 | Otis | Jul 2000 | A |
6088451 | He et al. | Jul 2000 | A |
6092200 | Muniyappa et al. | Jul 2000 | A |
6108782 | Fletcher et al. | Aug 2000 | A |
6130892 | Short et al. | Oct 2000 | A |
6131116 | Riggins et al. | Oct 2000 | A |
6157953 | Chang et al. | Dec 2000 | A |
6173331 | Shimonishi | Jan 2001 | B1 |
6176883 | Holloway et al. | Jan 2001 | B1 |
6185567 | Ratnaraj et al. | Feb 2001 | B1 |
6194992 | Short et al. | Feb 2001 | B1 |
6199113 | Alegre et al. | Mar 2001 | B1 |
6205552 | Fudge | Mar 2001 | B1 |
6212558 | Antur et al. | Apr 2001 | B1 |
6219706 | Fan et al. | Apr 2001 | B1 |
6226752 | Gupta et al. | May 2001 | B1 |
6233607 | Taylor et al. | May 2001 | B1 |
6243815 | Antur et al. | Jun 2001 | B1 |
6266774 | Sampath et al. | Jul 2001 | B1 |
6275693 | Lin et al. | Aug 2001 | B1 |
6295294 | Odlyzko | Sep 2001 | B1 |
6321339 | French et al. | Nov 2001 | B1 |
6324648 | Grantges, Jr. | Nov 2001 | B1 |
6336133 | Morris et al. | Jan 2002 | B1 |
6404743 | Meandzija | Jun 2002 | B1 |
6421319 | Iwasaki | Jul 2002 | B1 |
6463474 | Fuh et al. | Oct 2002 | B1 |
6473793 | Dillon et al. | Oct 2002 | B1 |
6473801 | Basel | Oct 2002 | B1 |
6477143 | Ginossar | Nov 2002 | B1 |
6502131 | Vaid et al. | Dec 2002 | B1 |
6502135 | Munger et al. | Dec 2002 | B1 |
6516417 | Pegrum et al. | Feb 2003 | B1 |
6535879 | Behera | Mar 2003 | B1 |
6539431 | Sitaraman et al. | Mar 2003 | B1 |
6631416 | Bendinelli et al. | Oct 2003 | B2 |
6636894 | Short et al. | Oct 2003 | B1 |
6643260 | Kloth et al. | Nov 2003 | B1 |
6678733 | Brown et al. | Jan 2004 | B1 |
6708212 | Porras et al. | Mar 2004 | B2 |
6732179 | Brown et al. | May 2004 | B1 |
6735691 | Capps et al. | May 2004 | B1 |
6757740 | Parekh et al. | Jun 2004 | B1 |
6763468 | Gupta et al. | Jul 2004 | B2 |
6785252 | Zimmerman et al. | Aug 2004 | B1 |
6789110 | Short et al. | Sep 2004 | B1 |
6789118 | Rao | Sep 2004 | B1 |
6798746 | Kloth et al. | Sep 2004 | B1 |
6804783 | Wesinger et al. | Oct 2004 | B1 |
6816903 | Rakoshitz et al. | Nov 2004 | B1 |
6823385 | McKinnon et al. | Nov 2004 | B2 |
6834341 | Bahl et al. | Dec 2004 | B1 |
6839759 | Larson et al. | Jan 2005 | B2 |
6876668 | Chawla et al. | Apr 2005 | B1 |
6907530 | Wang | Jun 2005 | B2 |
6917622 | McKinnon et al. | Jul 2005 | B2 |
6976089 | Na et al. | Dec 2005 | B2 |
6996625 | Kaplan et al. | Feb 2006 | B2 |
7013331 | Das | Mar 2006 | B2 |
7085385 | Frantz et al. | Aug 2006 | B2 |
7085854 | Keane et al. | Aug 2006 | B2 |
7092727 | Li et al. | Aug 2006 | B1 |
7120934 | Ishikawa | Oct 2006 | B2 |
7143283 | Chen et al. | Nov 2006 | B1 |
7143435 | Droms et al. | Nov 2006 | B1 |
7146639 | Bartal et al. | Dec 2006 | B2 |
7181017 | Nagel et al. | Feb 2007 | B1 |
7181542 | Tuomenoksa et al. | Feb 2007 | B2 |
7181766 | Bendinelli et al. | Feb 2007 | B2 |
7185073 | Gai et al. | Feb 2007 | B1 |
7185358 | Schreiber et al. | Feb 2007 | B1 |
7185368 | Copeland, III | Feb 2007 | B2 |
7188180 | Larson et al. | Mar 2007 | B2 |
7194554 | Short et al. | Mar 2007 | B1 |
7216173 | Clayton et al. | May 2007 | B2 |
7257833 | Parekh et al. | Aug 2007 | B1 |
7266754 | Shah | Sep 2007 | B2 |
7272646 | Cooper et al. | Sep 2007 | B2 |
7290288 | Gregg et al. | Oct 2007 | B2 |
7310613 | Briel et al. | Dec 2007 | B2 |
7316029 | Parker et al. | Jan 2008 | B1 |
7324551 | Stammers | Jan 2008 | B1 |
7324947 | Jordan et al. | Jan 2008 | B2 |
7325042 | Soscia et al. | Jan 2008 | B1 |
7386888 | Liang et al. | Jun 2008 | B2 |
7406530 | Brown et al. | Jul 2008 | B2 |
7418504 | Larson et al. | Aug 2008 | B2 |
7420956 | Karaoguz et al. | Sep 2008 | B2 |
7444669 | Bahl et al. | Oct 2008 | B1 |
7448075 | Morand et al. | Nov 2008 | B2 |
7454792 | Cantrell et al. | Nov 2008 | B2 |
7490151 | Munger et al. | Feb 2009 | B2 |
7509625 | Johnston et al. | Mar 2009 | B2 |
7587512 | Ta et al. | Sep 2009 | B2 |
7590728 | Tonnesen et al. | Sep 2009 | B2 |
7610621 | Turley et al. | Oct 2009 | B2 |
7624438 | White et al. | Nov 2009 | B2 |
7634805 | Aroya | Dec 2009 | B2 |
7665130 | Johnston et al. | Feb 2010 | B2 |
8032933 | Turley et al. | Oct 2011 | B2 |
8108915 | White et al. | Jan 2012 | B2 |
8117639 | MacKinnon et al. | Feb 2012 | B2 |
8224983 | Ta et al. | Jul 2012 | B2 |
20010038639 | McKinnon et al. | Nov 2001 | A1 |
20010038640 | McKinnon et al. | Nov 2001 | A1 |
20010038645 | McKinnon et al. | Nov 2001 | A1 |
20010039576 | Kanada | Nov 2001 | A1 |
20010039582 | McKinnon et al. | Nov 2001 | A1 |
20020013844 | Garrett et al. | Jan 2002 | A1 |
20020021665 | Bhagavath et al. | Feb 2002 | A1 |
20020023160 | Garrett et al. | Feb 2002 | A1 |
20020023210 | Tuomenoksa et al. | Feb 2002 | A1 |
20020026503 | Bendinelli et al. | Feb 2002 | A1 |
20020026531 | Keane et al. | Feb 2002 | A1 |
20020029260 | Dobbins et al. | Mar 2002 | A1 |
20020029276 | Bendinelli et al. | Mar 2002 | A1 |
20020035699 | Crosbie | Mar 2002 | A1 |
20020042883 | Roux et al. | Apr 2002 | A1 |
20020046264 | Dillon et al. | Apr 2002 | A1 |
20020052950 | Pillai et al. | May 2002 | A1 |
20020053031 | Bendinelli et al. | May 2002 | A1 |
20020055968 | Wishoff et al. | May 2002 | A1 |
20020056008 | Keane et al. | May 2002 | A1 |
20020059408 | Pattabhiraman et al. | May 2002 | A1 |
20020075844 | Hagen | Jun 2002 | A1 |
20020085719 | Crosbie | Jul 2002 | A1 |
20020087713 | Cunningham | Jul 2002 | A1 |
20020090089 | Branigan | Jul 2002 | A1 |
20020091859 | Tuomenoksa et al. | Jul 2002 | A1 |
20020091944 | Anderson et al. | Jul 2002 | A1 |
20020099829 | Richards et al. | Jul 2002 | A1 |
20020112183 | Baird, III et al. | Aug 2002 | A1 |
20020112186 | Ford et al. | Aug 2002 | A1 |
20020120741 | Webb et al. | Aug 2002 | A1 |
20020123335 | Luna et al. | Sep 2002 | A1 |
20020124078 | Conrad | Sep 2002 | A1 |
20020124103 | Maruyama et al. | Sep 2002 | A1 |
20020129143 | McKinnon, III et al. | Sep 2002 | A1 |
20020131404 | Mehta et al. | Sep 2002 | A1 |
20020133581 | Schwartz et al. | Sep 2002 | A1 |
20020133586 | Shanklin et al. | Sep 2002 | A1 |
20020133589 | Gubbi et al. | Sep 2002 | A1 |
20020136226 | Christoffel et al. | Sep 2002 | A1 |
20020138631 | Friedel et al. | Sep 2002 | A1 |
20020138762 | Horne | Sep 2002 | A1 |
20020138763 | Delany et al. | Sep 2002 | A1 |
20020143964 | Guo et al. | Oct 2002 | A1 |
20020152284 | Cambray et al. | Oct 2002 | A1 |
20020162030 | Brezak et al. | Oct 2002 | A1 |
20020164952 | Singhal et al. | Nov 2002 | A1 |
20020165949 | Na et al. | Nov 2002 | A1 |
20020165990 | Singhal et al. | Nov 2002 | A1 |
20020169867 | Mann et al. | Nov 2002 | A1 |
20020174227 | Hartsell et al. | Nov 2002 | A1 |
20020178282 | Mysore et al. | Nov 2002 | A1 |
20020199007 | Clayton et al. | Dec 2002 | A1 |
20030041104 | Wingard et al. | Feb 2003 | A1 |
20030043846 | Purpura et al. | Mar 2003 | A1 |
20030046370 | Courtney | Mar 2003 | A1 |
20030055994 | Herrmann et al. | Mar 2003 | A1 |
20030059038 | Meyerson et al. | Mar 2003 | A1 |
20030061506 | Cooper | Mar 2003 | A1 |
20030069955 | Gieseke et al. | Apr 2003 | A1 |
20030069956 | Gieseke et al. | Apr 2003 | A1 |
20030070170 | Lennon | Apr 2003 | A1 |
20030078784 | Jordan et al. | Apr 2003 | A1 |
20030087629 | Juitt et al. | May 2003 | A1 |
20030110073 | Briel et al. | Jun 2003 | A1 |
20030115247 | Simpson et al. | Jun 2003 | A1 |
20030123442 | Drucker et al. | Jul 2003 | A1 |
20030126608 | Safadi et al. | Jul 2003 | A1 |
20030135753 | Batra et al. | Jul 2003 | A1 |
20030149751 | Bellinger et al. | Aug 2003 | A1 |
20030154399 | Zuk | Aug 2003 | A1 |
20030159072 | Bellinger et al. | Aug 2003 | A1 |
20030163603 | Fry et al. | Aug 2003 | A1 |
20030172167 | Judge et al. | Sep 2003 | A1 |
20030177477 | Fuchs | Sep 2003 | A1 |
20030182420 | Jones et al. | Sep 2003 | A1 |
20030212800 | Jones et al. | Nov 2003 | A1 |
20030212900 | Liu et al. | Nov 2003 | A1 |
20030217126 | Polcha et al. | Nov 2003 | A1 |
20040015719 | Lee | Jan 2004 | A1 |
20040047356 | Bauer | Mar 2004 | A1 |
20040049586 | Ocepek et al. | Mar 2004 | A1 |
20040064351 | Mikurak | Apr 2004 | A1 |
20040064560 | Zhang et al. | Apr 2004 | A1 |
20040064836 | Ludvig et al. | Apr 2004 | A1 |
20040073941 | Ludvig et al. | Apr 2004 | A1 |
20040083295 | Amara et al. | Apr 2004 | A1 |
20040085906 | Ohtani | May 2004 | A1 |
20040093513 | Cantrell | May 2004 | A1 |
20040103426 | Ludvig et al. | May 2004 | A1 |
20040107290 | Kaplan et al. | Jun 2004 | A1 |
20040122956 | Myers et al. | Jun 2004 | A1 |
20040172557 | Nakae et al. | Sep 2004 | A1 |
20040177276 | MacKinnon et al. | Sep 2004 | A1 |
20040179822 | Tsumagari et al. | Sep 2004 | A1 |
20040181816 | Kim et al. | Sep 2004 | A1 |
20040199635 | Ta et al. | Oct 2004 | A1 |
20040210633 | Brown et al. | Oct 2004 | A1 |
20040215957 | Moineau et al. | Oct 2004 | A1 |
20040268149 | Aaron | Dec 2004 | A1 |
20040268234 | Sampathkumar et al. | Dec 2004 | A1 |
20050021686 | Jai et al. | Jan 2005 | A1 |
20050021975 | Liu | Jan 2005 | A1 |
20050044350 | White et al. | Feb 2005 | A1 |
20050044422 | Cantrell | Feb 2005 | A1 |
20050066200 | Bahl et al. | Mar 2005 | A1 |
20050091303 | Suzuki | Apr 2005 | A1 |
20050138358 | Bahl et al. | Jun 2005 | A1 |
20050138416 | Qian et al. | Jun 2005 | A1 |
20050149721 | Lu | Jul 2005 | A1 |
20050193103 | Drabik | Sep 2005 | A1 |
20050195854 | Agmon et al. | Sep 2005 | A1 |
20050204022 | Johnston et al. | Sep 2005 | A1 |
20050204031 | Johnston et al. | Sep 2005 | A1 |
20050204050 | Turley | Sep 2005 | A1 |
20050204168 | Johnston et al. | Sep 2005 | A1 |
20050204169 | Tonnesen | Sep 2005 | A1 |
20050204402 | Turley et al. | Sep 2005 | A1 |
20060036723 | Yip et al. | Feb 2006 | A1 |
20060168229 | Shim et al. | Jul 2006 | A1 |
20060168454 | Venkatachary et al. | Jul 2006 | A1 |
20060173992 | Weber et al. | Aug 2006 | A1 |
20060184618 | Kurup et al. | Aug 2006 | A1 |
20070073718 | Ramer et al. | Mar 2007 | A1 |
20070186113 | Cuberson et al. | Aug 2007 | A1 |
20070208936 | Ramos Robles | Sep 2007 | A1 |
20070268878 | Clements | Nov 2007 | A1 |
20080066096 | Wollmershauser et al. | Mar 2008 | A1 |
20080098464 | Mizrah | Apr 2008 | A1 |
20080120661 | Ludvig et al. | May 2008 | A1 |
20080147840 | Roelens et al. | Jun 2008 | A1 |
20080276305 | Chan et al. | Nov 2008 | A1 |
20090279567 | Ta et al. | Nov 2009 | A1 |
20100064356 | Johnston et al. | Mar 2010 | A1 |
20100192213 | Ta et al. | Jul 2010 | A1 |
20110219444 | Turley et al. | Sep 2011 | A1 |
20110258687 | White et al. | Oct 2011 | A1 |
20120117615 | MacKinnon et al. | May 2012 | A1 |
Number | Date | Country |
---|---|---|
0 587 522 | Mar 1994 | EP |
WO 0177787 | Oct 2001 | WO |
WO 0209458 | Jan 2002 | WO |
WO 0223825 | Mar 2002 | WO |
WO 0241587 | May 2002 | WO |
WO 02077820 | Oct 2002 | WO |
WO 03021890 | Mar 2003 | WO |
WO 03098461 | Nov 2003 | WO |
WO 2004034229 | Apr 2004 | WO |
WO 2004036371 | Apr 2004 | WO |
WO 2005020035 | Mar 2005 | WO |
Entry |
---|
Notice of Allowance for U.S. Appl. No. 12/753,390, mailed Mar. 16, 2012, 5 pgs. |
Office Action for U.S. Appl. No. 12/619,560, mailed May 9, 2012, 7 pgs. |
Bauer, Mick, Designing and Using DMZ Networks to Protect Internet Servers, Linux Journal, Mar. 1, 2001, 6 pgs. at http://linuxjournal.com/article/4415, printed Mar. 22, 2012. |
Office Action for U.S. Appl. No. 13/173,764, mailed Jul. 17, 2012, 15 pgs. |
Lingblom, Marie, Bluesocket's New Gateway Based on Open Standards—WGX-4000 Switch Wireless Gateway, CRN, Burlington, MA, found at www.crn.channelsupersearch.com, Apr. 21, 2003, 2 pgs. |
“Boingo Wireless Service Installed at LaGuardia Airport,” Jun. 17, 2003, Copyright 2003 M2Communications Ltd., found at www.findarticles.com, Dec. 8, 2003, 1 pg. |
“West Point Unwired: the Military Academy at West Point Continues to Lead the Way in High-Tech Curriculum with Wireless Classroom Networking,” Communication News, Jun. 2003, Copyright 2003 M2 Communications Ltd., found at www.findarticles.com, 5 pgs., printed Dec. 8, 2003. |
Molta, Dave, “Wireless Hotspots Heat Up,” Mobile & Wireless Technology, pp. 1-8, May 15, 2003, Copyright 2003 M2Communications Ltd., found at www.networkcomputing.com, printed Dec. 8, 2003, 8 pgs. |
Jackson, William, “Wireless at West Point: Officers of the Future Use IT in Class Now, in the Field Later (Technology Report),” Apr. 21, 2003, GCN, pp. 1-3, www.gcn.com. |
Lingblom, Marie, Cranite Develops SMB Strategy, CRN, San Jose, CA, Jun. 23, 2003, 2 pgs. |
Dornan, Andy “Wireless LANs: Freedom vs. Security?” Network Magazine, Jul. 2003, pp. 36-39, www.networkmagazine.com. |
O'Shea, Dan, “PCTEL looks past patent suit toward fusion of Wi-Fi, PC” Telephony.online, Jun. 2, 2003, pp. 1-2, found at www.telephonyonline.com, Primedia Business Magazines and Media, printed Dec. 8, 2003. |
O'Shea, Dan, “Boingo to Launch Initiative Aimed at Carrier Market” Telephony.online, Mar. 10, 2003, 1 pg., found at www.telephonyonline.com, Primedia Business Magazines and Media, printed Dec. 8, 2003. |
International Search Report for International Patent Application No. PCT/US03/32912, completed Mar. 22, 2004, mailed Apr. 8, 2004, 6 pgs. |
International Search Report for International Patent Application No. PCT/US03/32268, completed Oct. 17, 2004, mailed Oct. 29, 2004, 6 pgs. |
Fan, Chen, et al, “Distributed Real Time Intrusion Detection System for 3G,” Proceedings of ICCC2004, 2004, pp. 1566-1570. |
Yu, Zhao-xu et al., “Fuzzy Logic Based Adaptive Congestion Control Scheme for High-Speed Network,” vol. 33, No. 4, Information and Control, Aug. 2004, pp. 389-393 (with English abstract). |
Hamano, Takafumi et al., “A Redirection-Based Defense Mechanism Against Flood-Type Attacks in Large Scale ISP Networks,” 10th Asia-Pacific Conf. on Comm. and 5th Int'l Symposium on Multi-Dimensional Mobile Comm., 2004, pp. 543-547, IEEE #07803-8601-09/04. |
Sarolahti, Pasi, “Congestion Control on Spurious TCP Retransmssion Timeouts,” Globecom 2003, pp. 682-686, IEEE #0-7803-7974-8. |
Estevez-Tapiador, Juan M., et al., “Measuring Normality in HTTP Traffic for Anomaly-Based Intrusion Detection,” Computer Networks 45 (2004), pp. 175-193, available at www.sciencedirect.com, El Sevier 2004 #13891286. |
Xing, Xu-Jia, et al., “A Survey of Computer Vulnerability Assessment,” Chinese Journal of Computers, vol. 27, No. 1, Jan. 2004, pp. 1-11 (with English abstract). |
Wen et al. “Development of a Snort-Based Security Network Management and Real-Time Intrusion Detection System,” Journal of Beijing Normal Univ. (Natural Science), vol. 40, No. 1, Feb. 2004, pp. 40-43 (with English abstract). |
Thottethodi, Methune, et al., “Exploiting Global Knowledge to Achieve Self-Tuned Congestion Control for k-Ary n-Cube Networks,” IEEE Transactions on Parallel and Distributed Systems, vol. 15, No. 3, Mar. 2004, pp. 257-272, IEEE #1045-9219/04. |
Trabelsi, Zouheir, et al., “Malicious Sniffing Systems Detection Platform,” 2004 IEEE, pp. 201-207, IEEE #0-7695-2068-5/04. |
Guangzhi, Qu, et al., “A Framework for Network Vulnerability Analysis,” Proceedings of the IASTED Int'l Conf., Comm., Internet & Information Tech., Nov. 18-20, 2004, St. Thomas, US Virgin Islands, pp. 289-294. |
Albuquerque, Celio, et al., “Network Border Patrol: Preventing Congestion Collapse and Promoting Fairness in the Internet,” IEEE/ACM Transactions on Networking, vol. 12, No. 1, Feb. 2004, pp. 173-186, IEEE #1063-6692/04. |
Wirbel, Loring, “Security Stampede Could Flatten IPSec,” Network Magazine, Jan. 2004, p. 12, available at www.networkmagazine.com. |
MacLeod, Calum, “Freeing the Shackles with Secure Remote Working,” Comtec, Oct. 2003, pp. 66-67. |
Fisher, Dennis, “SSL Simplifies VPN Security,” IT Week, Nov. 10, 2003, p. 40, available at www.eweek.com/security. |
Conry-Murray, Andrew, “SSL VPNs: Remote Access for the Masses,” Network Magazine, Oct. 2003, pp. 26-32, available at www.networkmagazine.com. |
“Permeo Supports Microsoft Network Access Protection for Simplified Secure Remote Access; Permeo's Base5 Support of Microsoft Technology Provides “Zero Touch” Policy Enforcement”, Apr. 25, 2005, 2 pgs., Newswire, found at www.nerac.com. #NDN-121-0552-8254-9. |
Permeo Drives Out Operational Costs, Simplifies Secure Remote Access, Mar. 25, 2005, 2 pgs., Newswire, found at www.nerac.com. #NDN-121-0549-5967-5. |
“Netilla Lauches SSL VPN for Citrix. (Industry Briefs) (Virtual Private Networks) (Brief Article),” Sep. 20, 2004, 2 pgs., Computer Reseller News, found at www.nerac.com. #NDN-218-0991-7652-9. |
“Netilla Lauches Secure Gateway Appliance Family of Application-Specific SSL VPN Products; Initial SGA-C Model Provides Secure Remote Access to Citrix MetaFrame Presentation Server Installations . . . ” Sep. 13, 2004, 3 pgs., PR Newswire, found at www.nerac.com. #NDN-218-0987-0667-2. |
“Secure Remote Access.(Network Security) (VPN Gateway 4400 Series) (Brief Article),” Mar. 1, 2004, 2 pgs., Communication News, vol. 41, found at www.nerac.com. #NDN-218-0925-2711-6. |
“Fortinet and Aventail Deliver Joint Solution for Clientless Remote Access with High-Performance Antivirus Protection; Integrated SSL VPN and Antivirus Offering Provides Clientless Remote Access with Complete Content Security”, Jan. 5, 2004, 3 pgs., PR Newswire, found at www.nerac.com. #NDN-218-0845-8319-2. |
Hamblen, Matt, “Cisco Targets SSL VPN Vendors, Adds Support for Clientless Security Protocol: Installed Base of VPN Devices May Give it an Edge, Despite Late Entry,” Nov. 17, 2003, 3 pgs., Computerworld, vol. 37, No. 46, found at www.nerac.com. #NDN-218-0841-5076-0. |
Hamzeh, K., et al., “Point-to-Point Tunneling Protocol—PPTP RFC 2637” Network Working Groups, Jul. 1999, pp. 1-54, Microsoft Corporation. |
International Search Report and Written Opinion for International Application No. PCT/US04/29249, completed Nov. 28, 2005, mailed Dec. 15, 2005, 10 pgs. |
Pfleeger, Charles P., Computer Network Security, Security in Computing, 1989, pp. 364-415, Ch. 10, PTR Prentice-Hall, Inc., Englewood Cliffs, NJ. |
Office Action for U.S. Appl. No. 10/922,041, mailed Jul. 13, 2007, 20 pgs. |
Stone, David, “Securing Wireless LANs with VPN”, Intel Information Technology White Paper, Intel Corp., May 2006, 8 pgs. Order N#313185-001US. |
Office Action for U.S. Appl. No. 10/683,317, mailed Oct. 9, 2007, 20 pgs. |
Office Action for U.S. Appl. No. 10/687,002, mailed Oct. 18, 2007, 10 pgs. |
Office Action for U.S. Appl. No. 11/078,223, mailed Oct. 31, 2007, 8 pgs. |
Office Action for U.S. Appl. No. 11/076,652, mailed Jan. 25, 2008, 9 pgs. |
Office Action for U.S. Appl. No. 10/687,002, mailed Apr. 17, 2008, 12 pgs. |
Office Action for U.S. Appl. No. 10/683,317, mailed Jun. 9, 2008, 15 pgs. |
Office Action for U.S. Appl. No. 11/076,672, mailed Jul. 9, 2008, 12 pgs. |
Office Action for U.S. Appl. No. 11/076,652, mailed Jul. 22, 2008, 8 pgs. |
Office Action for U.S. Appl. No. 11/076,591, mailed Aug. 13, 2008, 10 pgs. |
Office Action for U.S. Appl. No. 11/076,719, mailed Sep. 4, 2008, 7 pgs. |
SBC Technology Resources, Inc., XNMP-XML Network Management Protocol and Interface, Jul. 19, 2002, pp. 1-9, http://www.ietf.org/proceedings/02jul/slides. |
Shim, Choon B., “XNMP for IP Telephony Management,” Enterprise Networks & Servers, Jun. 2, 2006, 7 pgs. |
Office Action for U.S. Appl. No. 11/076,652, mailed Dec. 11, 2008, 8 pgs. |
Office Action for U.S. Appl. No. 10/687,002, mailed Jan. 7, 2009, 14 pgs. |
Office Action for U.S. Appl. No. 11/076,672, mailed Feb. 3, 2009, 10 pgs. |
Oh, et al., “Interaction Translation Methods for XML/SNMP Gateway,” Jul. 11, 2003, retrieved from http://web-archive.org/web/20030711162412/http://dpnm.postech.ac.kr/papers/DSOM/02/xml-snmp-gateway/xml-snmp-gateway.pdf, pp. 1-12. |
Office Action for U.S. Appl. No. 10/683,317, mailed Feb. 11, 2009, 17 pgs. |
Office Action for U.S. Appl. No. 11/076,591, mailed Feb. 13, 2009, 26 pgs. |
International Preliminary Report on Patentability for International Patent Application No. PCT/US03/032268 completed Jan. 4, 2005, 3 pgs. |
International Preliminary Report on Patentability for International Patent Application No. PCT/US03/032912 completed Jun. 28, 2004, 3 pgs. |
International Preliminary Report on Patentability (Ch. I) of the International Searching Authority for International Patent Application No. PCT/US04/029249 issued Feb. 21, 2006, 6 pgs. |
Office Action for U.S. Appl. No. 11/076,719, mailed Mar. 17, 2009, 8 pgs. |
Office Action for U.S. Appl. No. 10/922,041, mailed Dec. 6, 2005, 10 pgs. |
Office Action for U.S. Appl. No. 10/922,041, mailed Mar. 30, 2006, 18 pgs. |
Office Action for U.S. Appl. No. 10/922,041, mailed Aug. 11, 2006, 19 pgs. |
Office Action for U.S. Appl. No. 10/922,041, mailed Jan. 30, 2007, 20 pgs. |
Office Action for U.S. Appl. No. 10/683,317, mailed Apr. 5, 2007, 6 pgs. |
Office Action for U.S. Appl. No. 10/687,002, mailed May 2, 2007, 10 pgs. |
Office Action for U.S. Appl. No. 10/922,041, mailed May 8, 2009, 13 pgs. |
Office Action for U.S. Appl. No. 11/076,672, mailed Jul. 21, 2009, 11 pgs. |
Notice of Allowability for U.S. Appl. No. 11/076,646, mailed Jul. 24, 2009, 7 pgs. |
Crandell et al., “A Secure and Transparent Firewall Web Proxy,” Oct. 2003, USENIX, Retrieved from the internet on Jul. 15, 2009: <URL: http://www.usenix.org/event/lisa03/tech/full—papers/crandell/crandell.pdf>. |
Sommerlad, “Reverse Proxy Patterns,” 2003 Retrieved from the Internet on Jul. 15, 2009, 27 pages; <URL: http://www.modsecurity.org/archive/ReverseProxy-book-1.pdf>. |
Office Action for U.S. Appl. No. 11/076,591, mailed Aug. 6, 2009, 29 pgs. |
Office Action for U.S. Appl. No. 10/683,317, mailed Aug. 18, 2009, 17 pgs. |
Rashti et al, “A Multi-Dimensional Packet Classifier for NP-Based Firewalls,” Proceedings of the 2004 Int'l Symposium on Applications and the Internet, Jan. 2004, 5 pages, from the internet, printed Aug. 12, 2009: <URL: http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=1266123&isnumber=28312>. |
Office Action for U.S. Appl. No. 11/076,672, mailed Jan. 7, 2010, 9 pgs. |
Office Action for U.S. Appl. No. 11/076,591, mailed Feb. 2, 2010, 34 pgs. |
Office Action for U.S. Appl. No. 11/076,591, mailed Jul. 20, 2010, 33 pgs. |
Office Action for U.S. Appl. No. 10/683,317, mailed Jul. 23, 2010, 9 pgs. |
Office Action for U.S. Appl. No. 12/506,140, mailed Sep. 1, 2010, 11 pgs. |
Office Action for U.S. Appl. No. 12/579,566, mailed Oct. 6, 2010, 7 pgs. |
“Discussion of Conceptual Difference Between Cisco IOS Classic and Zone-Based Firewalls,” Oct. 2007, Cisco Systems, Inc., San Jose, CA, 4 pgs. |
Cisco IOS Firewall Zone-Based Policy Firewall, Release 12.4(6)T, Technical Discussion, Feb. 2006, 77 pgs., Cisco Systems, Inc., San Jose, CA. |
Zone-Based Policy Firewall Design and Application Guide, Document ID: 98628, Sep. 13, 2007, 49 pgs., Cisco Systems, Inc., San Jose, CA. |
SP Maj, W Makairanondh, D Veal, “An Evaluation of Firewall Configuration Methods,” IJSCSNS International Journal of Computer Science and Network Security, vol. 10, No. 8, Aug. 2010, 7 pgs. |
Using VPN with Zone-Based Policy Firewall, May 2009, Cisco Systems, Inc., San Jose, CA, 10 pgs. |
Cisco IOS Firewall Classic and Zone-Based Virtual Firewall Application Configuration Example, Document ID: 100595, Feb. 12, 2008, 20 pgs., Cisco Systems, Inc., San Jose, CA. |
Class-Based Policy Provisioning: Introducing Class-Based Policy Language (CPL), Aug. 2008, 36 pgs., Cisco Systems, Inc., San Jose, CA. |
Cisco IOS Zone Based Firewall Example, at http://www.linickx.com/archives/2945/cisco-ios-zon . . . , printed Dec. 7, 2010, 6 pgs., LINICKX.com. |
Zone-Based Policy Firewall, Published Feb. 22, 2006, Updated Jun. 19, 2006, 46 pgs., Cisco Systems, Inc., San Jose, CA. |
Applying Zone-based Firewall Policies in Cisco Security Manager, Published Mar. 2009, Revised Sep. 2009, Cisco Systems, Inc., San Jose, CA. |
“FreeBSD Handbook, Chapter 30 Firewalls,” 2003, found at www.freebsd.org/doc/handbook/firewalls-ipfw.html, printed Dec. 27, 2010, 13 pgs. |
Watters, Paul, “Solaris 8 Administrator's Guide, Chapter 4, Network Configuration,” O'Reilly & Associates, Inc., Jan. 2002, 17 pgs. |
Spitzner, Lance, “Configuring network interface cards; getting your interfaces to talk,” Mar. 23, 2004, 4 pgs. |
Gite, Vivek, “Redhat/CentOS/Fedora Linux Open Port,” Sep. 13, 2007, found at www.cyberciti.biz/faq/howto-rhel-linux-open-port-using-iptables/ printed Jan. 3, 2011, 7 pgs. |
Office Action for U.S. Appl. No. 10/683,317, mailed Jan. 3, 2011, 12 pgs. |
Office Action for U.S. Appl. No. 12/617,211, mailed Feb. 3, 2011, 14 pgs. |
“Managing Firewall Services,” User Guide for Cisco Security Manager 3.3.1, Oct. 2009, Ch. 11, 90 pgs., Cisco Systems, Inc., San Jose, CA. |
“Cisco Common Classification Policy Language,” Cisco Router and Security Device Manager 2.4 User's Guide, Ch. 34, 2007, 32 pgs., Cisco Systems, Inc., San Jose, CA. |
Guide to User Documentation for Cisco Security Manager 4.0, Jun. 18, 2010, Cisco Systems, Inc., San Jose, CA. |
Cisco Configuration Professional: Zone-Based Firewall Blocking Peer to Peer Traffic Configuration Example, Document ID: 112237, Updated Dec. 3, 2010, 25 pgs., Cisco Systems, Inc., San Jose, CA. |
Tuning Cisco IOS Classic and Zone-Based Policy Firewall Denial-of-Service Protection, 2006, 10 pgs., Cisco Systems, Inc., San Jose, CA. |
Holuska, Marty, Using Cisco IOS Firewalls to Implement a Network Security Policy, Fort Hays State University/INT 490, printed Dec. 6, 2010, 5 pgs., http://quasarint.com/Capstone/zb—policy.php. |
Cisco Feature Navigator, Cisco Systems, Inc., San Jose, CA, printed on Dec. 2, 2010, 4 pgs., at http://tools.cisco.com/ITDIT/CFN/Dispatch. |
Office Action for U.S. Appl. No. 12/506,140, mailed Feb. 18, 2011, 13 pgs. |
Notice of Allowance for U.S. Appl. No. 12/579,566, mailed Mar. 23, 2011, 12 pgs. |
Notice of Allowance for U.S. Appl. No. 12/579,566, mailed May 13, 2011, 8 pgs. |
Office Action for U.S. Appl. No. 10/683,317, mailed Jun. 8, 2011, 15 pgs. |
Office Action for U.S. Appl. No. 12/617,211, mailed Jul. 19, 2011, 18 pgs. |
Office Action for U.S. Appl. No. 12/506,140, mailed Aug. 4, 2011, 18 pgs. |
Notice of Allowance for U.S. Appl. No. 12/579,566, mailed Aug. 30, 2011, 9 pgs. |
Alshamsi, Abdelnasir, et al., “A Technical Comparison of IPSec and SSL,” Tokyo University of Technology, Jul. 8, 2004, 10 pgs. |
Fisher, Dennis, “NetScreen to Acquire Neoteris,” IT Security & Network Security News, Oct. 6, 2003, 1 page. |
Demaria, Mike, “Faster Than a Speeding VPN—Super Remote Access With Neoteris IVE,” Network Computing, Sep. 9, 2002, printed Nov. 9, 2011 from http://www.networkcomputing.com/data-protection/2296249, 3 pgs. |
Snyder, Joel, “SSL VPN Gateways,” Networkworld, Jan. 12, 2004, printed Nov. 9, 2011 from http://www.networkworld.com/reviews/2004/0112revmain.html, 10 pgs. |
“NetExtender for SSL-VPN,” SonicWALL SSL-VPN NetExtender, Apr. 27, 2006, 30 pgs. |
“IPSec vs. SSL VPN: Transition Criteria and Methodology,” 2007 Sonicwall, 13 pgs. |
Fisher, Dennis, “Symantec Acquires SSL VPN Vendor,” IT Security & Network Security News, Oct. 20, 2003, printed Nov. 9, 2011 from http://www.eweek.com/index2.php?option=content& task=v . . . 1 pg. |
Notice of Allowance for U.S. Appl. No. 12/617,211, mailed Nov. 10, 2011, 8 pgs. |
Notice of Allowance for U.S. Appl. No. 10/683,317, mailed Nov. 28, 2011, 11 pgs. |
Office Action for U.S. Appl. No. 12/753,390, mailed Dec. 8, 2011, 19 pgs. |
Notice of Allowance for U.S. Appl. No. 12/617,211, mailed Dec. 12, 2011, 8 pgs. |
Office Action for U.S. Appl. No. 13/092,488, mailed Jun. 11, 2012, 7 pgs. |
Number | Date | Country | |
---|---|---|---|
20120096517 A1 | Apr 2012 | US |
Number | Date | Country | |
---|---|---|---|
60496629 | Aug 2003 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12617211 | Nov 2009 | US |
Child | 13332639 | US | |
Parent | 10922041 | Aug 2004 | US |
Child | 12617211 | US |