US 8,356,336 B2Grant
System and method for double-capture/double-redirect to a different location
Issue Date:2013-01-15
•20 Claims
•3 Drawing Sheets
Abstract
Embodiments disclosed herein provide a system, method, and computer program product for providing network access control for a shared network. One embodiment of a network access controller may intercept a request to access a network resource from a browser application running on a client device associated with an anonymous user and determine whether the network resource is in a set of network destinations in the shared network. If the network resource is in the set of network destinations, the network access controller may direct the browser application to the network resource. If the network resource is not in the set of network destinations, the network access controller may redirect the browser application to a pre-authentication capture destination in the shared network. From the pre-authentication capture destination the anonymous user is free to visit any of the set of network destinations in the shared network without authentication.
Metadata
Assignee
- RPX Corporation
Inventors
- Keith Johnston
- Eric White
- John Martin
Application Information
Application Number:US 12/619,560
Filing Date:2009-11-16
Priority Date:2004-03-10
Art Unit:2432
Classifications
IPC:
H04L29/06
Patent Drawings (3 sheets)
Description
Cross Reference to Related Applications
[0001] This application is a continuation of U.S. patent application Ser. No. 11/076,646, filed Mar. 10, 2005 by inventors Keith Johnston, Eric White, and John Martin, entitled “SYSTEM AND METHOD FOR DOUBLE-CAPTURE/DOUBLE-REDIRECT TO A DIFFERENT LOCATION”, now U.S. Pat. No. 7,665,130, issued on Feb. 16, 2010, which claims a benefit of priority under 35 U.S.C. §119(e) to U.S. Provisional Applications No. 60/551,705, filed Mar. 10, 2004, entitled “SYSTEM AND METHOD FOR DOUBLE-CAPTURE/DOUBLE-REDIRECT TO A DIFFERENT LOCATION,” and No. 60/551,702, filed Mar. 10, 2004, entitled “SYSTEM AND METHOD FOR ACCESS SCOPE CONTROL (“WALLED GARDENS”) FOR CLIENTS OF A NETWORK ACCESS GATEWAY,” both of which are hereby fully incorporated by reference herein.
Technical Field
[0002] Embodiments disclosed herein relate to network access control and security. More particularly, embodiments disclosed herein relate to a system, method, and computer program product for providing network access control for a shared network.
Background
[0003] Network access providers utilizing Access Controlled Network Sharing technology to provide user-specific provisioned access to private/public networks may also have a need to allow controlled access for unauthenticated users to a restricted collection of network destinations.
[0004] For example, a shopping mall owner may want to provide any on-site customer possessing a wireless device (such as a laptop computer, PDA, etc.) with access to the Web server for the mall, plus one or more other Web sites that are associated with the mall (e.g., the local Web server for a tenant in the mall, such as a department store or movie theater). In this case, the collection of Web servers that the mall owner will allow an anonymous user to visit is referred to as the “walled garden”.
[0005] In addition, the mall owner may intend to provide unlimited web access to customers who agree to register with the mall owner, and identify themselves (by providing credentials—typically, in the form of a user identifier and a password that were assigned at the time they registered) whenever they wish to be granted full access to the Internet. The process of verifying a customer's credentials is referred to as “authentication”.
[0006] Previous solutions would either 1) require that the network destination of the authentication service (i.e., the “captive” portal) be specified explicitly in a link on at least one of the web pages within the set of destinations that are members of the “walled garden”, or 2) require that the end-user manually enter the web address of the authentication service in the address bar of their web browser.
Summary of the Disclosure
[0007] Embodiments disclosed herein provide a software-based system and method that enhances the function of a network access controller by introducing a “Pre-Authentication Capture Destination”. In the standard Access Controlled Network Sharing solution, an unauthenticated client who attempts to access the network is re-directed to a challenge screen or “captive portal”, where they must provide their network login credentials (e.g., user name and password).
[0008] If a Pre-Authentication Capture Destination is specified, then this behavior changes. Any attempt by an unauthenticated client to access a network resource that is not in a list of allowed destinations (i.e., the list of servers that make up the “walled garden”) will result in the client being re-directed by the Network Access Controller to the Pre-Authentication Capture Destination. The unauthenticated client is then free to visit any of the servers that are included in the walled garden without authentication. Any attempt to access a web site or location that is outside of the walled garden will cause the client to be re-directed back to the Pre-Authentication Capture Destination.
[0009] At some point, the unauthenticated client may want to use network access privileges that are only available to an authenticated user. Consequently, the client must then be re-directed to an authentication URL (or “captive” portal), where they may login (or register as a new user). To accomplish this re-direction, at least one of the web sites within the walled garden can include an HTML link that references a site that is not in the walled garden and includes a special token within the “query” portion of the link's target HTTP URL (as defined in the IETF RFC-2616—“Hypertext Transfer Protocol—HTTP/1.1” and RFC-1738 “Uniform Resource Locators (URL)” specifications). This special token, referred to as the “Authentication Token”, is a unique sequence of characters that are valid for use in the query portion of a URL. When the client attempts to access the referenced site, they will be captured by the Network Access Controller. However, because of the presence of the Authentication token within the HTTP URL, the Network Access Controller will re-direct the client to the authentication screen, rather than redirecting them back to the Pre-Authentication Capture Destination.
[0010] Note that there is no requirement for any web page in the walled garden to have prior knowledge of the actual authentication screen location. Consequently, the same collection of walled garden sites may be used to service multiple Network Access controllers, where each controller may utilize a different authentication portal.
[0011] Embodiments disclosed herein enable a public/private network service provider to automatically redirect anonymous clients to a pre-defined destination within a limited set of network destinations, and provides a mechanism for accessing the authentication service without requiring that the web servers in the “walled garden” know the actual authentication URL. The automatic redirection occurs whenever the anonymous client attempts to access a network destination outside of the allowed set. The anonymous client does not have to enter the network URL of a server in the “walled garden”—instead, they just have to attempt to access any well-known URL (such as www.yahoo.com), and they will be redirected to the pre-defined destination.
Brief Description of the Drawings
[0012] A more complete understanding of the present invention and the advantages thereof may be acquired by referring to the following description, taken in conjunction with the accompanying drawings in which like reference numbers indicate like features and wherein:
[0013] FIG. 1 is a diagrammatic representation of a system depicting the network access capability afforded to an unauthenticated client, according to one embodiment disclosed herein;
[0014] FIG. 2 is a diagrammatic representation of a system depicting the network access capability afforded to an authenticated client, according to one embodiment disclosed herein; and
[0015] FIG. 3 is a diagrammatic representation of the flow of control (decision diagram) for a network access sharing device implementing the double-capture, double-redirect method, according to one embodiment disclosed herein.
Detailed Description
[0016] The following applications are hereby fully incorporated by reference herein in their entirety: U.S. patent application Ser. No. 10/683,317, pending, filed Oct. 10, 2003 by Richard MacKinnon, Kelly Looney, and Eric White, entitled “SYSTEM AND METHOD FOR PROVIDING ACCESS CONTROL”; U.S. Provisional Application No. 60/551,698, filed Mar. 10, 2004 by Patrick Turley, entitled “SYSTEM AND METHOD FOR BEHAVIOR-BASED FIREWALL MODELING,” which converted into U.S. patent application Ser. No. 11/076,719, filed Mar. 10, 2005 by Richard MacKinnon, Kelly Looney, and Eric White, entitled “SYSTEM AND METHOD FOR BEHAVIOR-BASED FIREWALL MODELING,” issued as U.S. Pat. No. 7,610,621; U.S. Provisional Application No. 60/551,754, filed Mar. 10, 2004 by Keith Johnston, entitled “SYSTEM AND METHOD FOR COMPREHENSIVE CODE GENERATION FOR SYSTEM MANAGEMENT,” which converted into U.S. patent application Ser. No. 11/078,223, filed Mar. 10, 2005 by Keith Johnston, entitled “SYSTEM AND METHOD FOR COMPREHENSIVE CODE GENERATION FOR SYSTEM MANAGEMENT,” issued as U.S. Pat. No. 7,509,625; U.S. Provisional Application No. 60/551,703, filed Mar. 10, 2004 by Patrick Turley and Keith Johnston, entitled “SYSTEM AND METHOD FOR PROVIDING A CENTRALIZED DESCRIPTION/CONFIGURATION OF CLIENT DEVICES ON A NETWORK ACCESS GATEWAY”; U.S. Provisional Application No. 60/551,702, filed Mar. 10, 2004 by Patrick Turley, Keith Johnston, and Steven D. Tonnesen, entitled “SYSTEM AND METHOD FOR ACCESS SCOPE CONTROL (“WALLED GARDENS”) FOR CLIENTS OF A NETWORK ACCESS GATEWAY,” which converted into U.S. patent application Ser. No. 11/076,591, pending, filed Mar. 10, 2005 by Patrick Turley, Keith Johnston, and Steven D. Tonnesen, entitled “METHOD AND SYSTEM FOR CONTROLLING NETWORK ACCESS”; U.S. Provisional Application No. 60/551,699, filed Mar. 10, 2004 by Patrick Turley, et al., entitled “SYSTEM AND METHOD FOR DYNAMIC BANDWIDTH CONTROL”; U.S. Provisional Application No. 60/551,697, filed Mar. 10, 2004 by Steven D. Tonnesen, entitled “SYSTEM AND METHOD FOR DETECTION OF ABERRANT NETWORK BEHAVIOR BY CLIENTS OF A NETWORK ACCESS GATEWAY,” which converted into U.S. patent application Ser. No. 11/076,652, filed Mar. 10, 2005 by Steven D. Tonnesen, entitled “SYSTEM AND METHOD FOR DETECTION OF ABERRANT NETWORK BEHAVIOR BY CLIENTS OF A NETWORK ACCESS GATEWAY,” issued as U.S. Pat. No. 7,590,728; U.S. Provisional Application No. 60/551,705, filed Mar. 10, 2004 by Keith Johnston, et al., entitled “SYSTEM AND METHOD FOR DOUBLE-CAPTURE/DOUBLE-REDIRECT TO A DIFFERENT LOCATION,” which converted into U.S. patent application Ser. No. 11/076,646, now allowed, filed Mar. 10, 2005 by Keith Johnston, et al., entitled “SYSTEM AND METHOD FOR DOUBLE-CAPTURE/DOUBLE-REDIRECT TO A DIFFERENT LOCATION”; U.S. Provisional Application No. 60/551,704, filed Mar. 10, 2004 by Keith Johnston and Mario Garcia, entitled “SYSTEM AND METHOD FOR NETWORK MANAGEMENT XML ARCHITECTURAL ABSTRACTION,” which converted into U.S. patent application Ser. No. 11/076,672, pending, filed Mar. 10, 2005 by Keith Johnston and Mario Garcia, entitled “SYSTEM AND METHOD FOR NETWORK MANAGEMENT XML ARCHITECTURAL ABSTRACTION”; and U.S. Provisional Application No. 60/660,408, filed Mar. 10, 2005 by Patrick Turley, et al., entitled “SYSTEM AND METHOD FOR PROVIDING A CENTRALIZED DESCRIPTION/CONFIGURATION OF CLIENT DEVICES ON A NETWORK ACCESS GATEWAY.”
[0017] Preferred embodiments disclosed herein are illustrated in the accompanying drawings, with like numerals being used to refer to like and corresponding parts of the various drawings.
[0018] Network access providers utilizing Access Controlled Network Sharing technology to provide user-specific provisioned access to private/public networks may also have a need to allow controlled access for unauthenticated users to a restricted collection of network destinations. An example of Access Controlled Network Sharing technology is described in U.S. patent application Ser. No. 10/683,317, filed Oct. 10, 2003 by Richard MacKinnon, Kelly Looney, and Eric White, entitled “SYSTEM AND METHOD FOR PROVIDING ACCESS CONTROL.” An example of a restricted collection of network destinations is referred to as the “walled garden” in U.S. Provisional Application No. 60/551,702, filed Mar. 10, 2004 by Patrick Turley, Keith Johnston and Steven D. Tonnesen, entitled “SYSTEM AND METHOD FOR ACCESS SCOPE CONTROL (“WALLED GARDENS”) FOR CLIENTS OF A NETWORK ACCESS GATEWAY,” which converted into U.S. patent application Ser. No. 11/076,591, filed Mar. 10, 2005 by Patrick Turley, Keith Johnston and Steven D. Tonnesen, entitled “METHOD AND SYSTEM FOR CONTROLLING NETWORK ACCESS.”
[0019] To illustrate by example, assume that the following configuration has been set in the Network Access Controller 2, as depicted in FIG. 1 :
[0020] Walled Garden 5 contains three servers:
[0021] wg1.com (Server 6)
[0022] wg2.com (Server 7)
[0023] auth.com (Server 8)
[0024] The Pre-Authentication Capture Destination for the embodiment of FIG. 1 will be designated http://wg1.com/welcome.html.
[0025] The Authentication Capture Destination for the embodiment of FIG. 1 will be designated https://auth.com/login.jsp.
[0026] As shown in the embodiment of FIG. 1 , assume that an anonymous user has access to one of the Client network access devices 1. This user launches a Web browser and enters “www.yahoo.com” (an “external” URL, i.e., a destination that is not in the Walled Garden 5) in the address bar, and presses <Return>. The Network Access Controller 2 uses its internal Firewall 3 function to recognize the attempt by an unknown user to access an “external” location (represented by the Internet cloud 4 in FIG. 1 ), intercepts the request, and sends an HTTP redirect to the Client's browser, specifying the Pre-Authentication Capture URL “http://wg1.com/welcome.html”. The browser then automatically performs an HTTP Get to retrieve that Web page from the wg1.com server.
[0027] At this point, the anonymous user may access Web locations on any of the three servers that are in the Walled Garden 5. For this example, assume that the Web pages on the wg1.com Server 6 include links to Web pages on the wg2.com Server 7. The anonymous user would be able to click on any of these links and view the referenced pages hosted on Server 7. However, if one of these Web pages contained a link to an “external” web site, and the user clicked on that link, then the Network Access Controller would again redirect the Client's browser back to the Pre-Authentication Capture URL http://wg1.com/welcome.html, hosted on Server 6.
[0028] Now, assume that the anonymous user decides that they want to be authenticated, so that they may be allowed access to an “external” network destination. To enable the user to login, an HTML link is included on the welcome page at “http://wg1.com/welcome.html”. The link's reference URL identifies a server that is outside of the Walled Garden 5, and includes the special token string “proceedToAuthenticationURL=true” within the query portion. Note that the exact form of this special token need not be predefined; the special token is simply uniquely identifiable.
[0029] When the user clicks on this link, the Network Access Controller 2 intercepts the request. However, instead of redirecting the Client's browser to the Pre-Authentication Capture URL, the Network Access Controller 2 recognizes the presence of the token, and redirects the browser to the Authentication URL http://auth.com/login.jsp, hosted on the “auth.com” Server 8.
[0030] At this point, the user is presented with a Login page, and enters a username/password. Assuming that these credentials are valid, the “auth.com” Server 8 sends an “authorize” command to the Network Access Controller 2. This command instructs the Network Access Controller 2 to allow “external” access for the authenticated user.
[0031] As shown in FIG. 2 , the Client now has access to the Internet 4 (“External Network”). If the user now enters “www.yahoo.com” in the Web browser's address bar, the Network Access Controller 2 would no longer intercept this request, and the welcome page from the Yahoo web site would be displayed.
[0032] Note that, in one embodiment, this “external” access is only granted to the authenticated user. An anonymous user on a different Client would still be restricted to the Walled Garden 5.
[0033] One embodiment of the decision logic (and associated flow) that can be executed by the Network Access Controller 2 is depicted in FIG. 3 . The Network Access Controller continuously monitors for network access from network access client devices 1 on its first network interface at step 18.
[0034] When a network packet is received (step 19), the Network Access Controller 2 determines if the packet is being sent by an authenticated client (step 20).
[0035] If the packet is from an authenticated client, then the Network Access Controller 2 allows the packet to pass through and be routed to its target destination (“Yes” decision fork).
[0036] If the packet is from an unauthenticated client, then the Network Access Controller 2 determines if the destination of the packet is one of the servers within the Walled Garden 5 (step 21).
[0037] If the packet is from an unauthenticated client and the destination is a server in the Walled Garden 5, then the Network Access Controller 2 allows the packet to pass through and be routed to its target server (“Yes” decision fork).
[0038] If the packet is from an unauthenticated client and the destination is not a server in the Walled Garden 5, then the Network Access Controller 2 determines if a Pre-Authentication URL has been specified (step 22).
[0039] If the packet is from an unauthenticated client, the destination is not a server in the Walled Garden 5, and a Pre-Authentication URL has not been specified, then the Network Access Controller 2 directs the client to the Authentication URL (step 24).
[0040] If the packet is from an unauthenticated client, the destination is not a server in the Walled Garden 5, and a Pre-Authentication URL has been specified, then the Network Access Controller 2 determines if the packet contains the Authentication Token (step 23).
[0041] If the packet is from an unauthenticated client, the destination is not a server in the Walled Garden 5, a Pre-Authentication URL has been specified, and the packet does not contain the Authentication Token, then the Network Access Controller 2 directs the client to the Pre-Authentication URL (step 25).
[0042] If the packet is from an unauthenticated client, the destination is not a server in the Walled Garden 5, a Pre-Authentication URL has been specified, and the packet contains the Authentication Token, then the Network Access Controller 2 directs the client to the Authentication URL (step 24).
[0043] While the present disclosure has been described with reference to particular embodiments, it should be understood that the embodiments are illustrative and that the scope of the invention is not limited to these embodiments. Many variations, modifications, additions and improvements to the embodiments described above are possible. It is contemplated that these variations, modifications, additions and improvements fall within the scope of the invention as detailed in the following claims.
Claims
What is claimed is:
1. A method for automatic pre-authentication redirection of network traffic, comprising:
providing a network access controller in a shared network, wherein the shared network comprises a plurality of server computers and a set of network destinations hosted on the plurality of server computers;
intercepting at the network access controller a request to access a network resource from a browser application running on a client device within the shared network associated with an anonymous user;
determining whether the network resource referenced in the request is in the set of network destinations hosted on the plurality of server computers in the shared network;
if the network resource is in the set of network destinations hosted on the plurality of server computers in the shared network, directing the browser application running on the client device within the shared network associated with the anonymous user to the network resource; and
if the network resource is not in the set of network destinations hosted on the plurality of server computers in the shared network, redirecting the browser application running on the client device within the shared network associated with the anonymous user to a pre-authentication capture destination hosted on a first server computer, wherein the first server computer is one of the plurality of server computers in the shared network and wherein from the pre-authentication capture destination the anonymous user is free to visit any of the set of network destinations hosted on the plurality of server computers in the shared network without authentication.
2. The method according to claim 1, wherein the network resource is at a network location external to the shared network.
3. The method according to claim 1, wherein the redirecting further comprises sending from the network access controller to the client device a response containing an identifier identifying the pre-authentication capture destination.
4. The method according to claim 1, further comprising:
redirecting the browser application running on the client device back to the preauthentication capture destination when the anonymous user attempts to access any network resource that is not in the set of network destinations hosted on the plurality of server computers in the shared network.
5. The method according to claim 1, further comprising:
intercepting at the network access controller a second request from the browser application running on the client device associated with the anonymous user to access a second network resource that is not in the set of network destinations; and
determining whether the second request contains an authentication token.
6. The method according to claim 5, wherein the second request does not contain the authentication token, further comprising redirecting the browser application running on the client device associated with the anonymous user back to the pre-authentication capture destination hosted on the first server computer in the shared network.
7. The method according to claim 5, wherein the second request contains the authentication token, further comprising redirecting the browser application running on the client device associated with the anonymous user to an authentication page hosted on a second server computer in the shared network.
8. The method according to claim 7, wherein the anonymous user is authenticated by the second server computer for network access external to the shared network.
9. A computer program product comprising a non-transitory computer readable storage medium storing computer instructions translatable by a processor to perform:
intercepting at a network access controller a request to access a network resource from a browser application running on a client device within the shared network associated with an anonymous user;
determining whether the network resource referenced in the request is in a set of network destinations hosted on a plurality of server computers in a shared network;
if the network resource is in the set of network destinations hosted on the plurality of server computers in the shared network, directing the browser application running on the client device within the shared network associated with the anonymous user to the network resource; and
if the network resource is not in the set of network destinations hosted on the plurality of server computers in the shared network, redirecting the browser application running on the client device within the shared network associated with the anonymous user to a pre-authentication capture destination hosted on a first server computer, wherein the first server computer is one of the plurality of server computers in the shared network and wherein from the pre-authentication capture destination the anonymous user is free to visit any of the set of network destinations hosted on the plurality of server computers in the shared network without authentication.
10. The computer program product of claim 9, wherein the redirecting further comprises sending from the network access controller to the client device a response containing an identifier identifying the pre-authentication capture destination.
11. The computer program product of claim 9, wherein the computer instructions are further translatable by the processor to perform:
redirecting the browser application running on the client device back to the preauthentication capture destination when the anonymous user attempts to access any network resource that is not in the set of network destinations hosted on the plurality of server computers in the shared network.
12. The computer program product of claim 9, wherein the computer instructions are further translatable by the processor to perform:
intercepting at the network access controller a second request from the browser application running on the client device associated with the anonymous user to access a second network resource that is not in the set of network destinations; and
determining whether the second request contains an authentication token.
13. The computer program product of claim 12, wherein the second request does not contain the authentication token and wherein the computer instructions are further translatable by the processor to perform:
redirecting the browser application running on the client device associated with the anonymous user back to the pre-authentication capture destination hosted on the first server computer in the shared network.
14. The computer program product of claim 12, wherein the second request contains the authentication token and wherein the computer instructions are further translatable by the processor to perform:
redirecting the browser application running on the client device associated with the anonymous user to an authentication page hosted on a second server computer in the shared network.
15. The computer program product of claim 14, wherein the anonymous user is authenticated by the second server computer for network access external to the shared network and wherein the computer instructions are further translatable by the processor to perform:
allowing the client device access to the second network resource.
16. An apparatus for controlling network access, comprising:
a processor within a shared network; and
a computer readable storage medium storing computer instructions translatable by the processor to perform:
intercepting a request to access a network resource from a browser application running on a client device within the shared network coupled to the apparatus, wherein the client device is associated with an anonymous user;
determining whether the network resource referenced in the request is in a set of network destinations hosted on a plurality of server computers coupled to the apparatus, wherein the plurality of server computers resides on the shared network;
if the network resource is in the set of network destinations hosted on the plurality of server computers in the shared network, directing the browser application running on the client device within the shared network associated with the anonymous user to the network resource; and
if the network resource is not in the set of network destinations hosted on the plurality of server computers in the shared network, redirecting the browser application running on the client device within the shared network associated with the anonymous user to a pre-authentication capture destination hosted on a first server computer, wherein the first server computer is one of the plurality of server computers in the shared network and wherein from the pre-authentication capture destination the anonymous user is free to visit any of the set of network destinations hosted on the plurality of server computers in the shared network without authentication.
17. The apparatus of claim 16, wherein the computer instructions are further translatable by the processor to redirect the browser application running on the client device back to the preauthentication capture destination when the anonymous user attempts to access any network resource that is not in the set of network destinations hosted on the plurality of server computers in the shared network.
18. The apparatus of claim 16, further comprising:
a first network interface coupled to the processor, wherein the computer instructions are further translatable by the processor to continuously monitor for network access from client devices on the first network interface.
19. The apparatus of claim 18, wherein the computer instructions are further translatable by the processor to perform:
intercepting a second request from the browser application running on the client device associated with the anonymous user to access a second network resource that is not in the set of network destinations; and
determining whether the second request contains an authentication token.
20. The apparatus of claim 19, wherein the computer instructions are further translatable by the processor to perform:
if the second request does not contain the authentication token, redirecting the browser application running on the client device associated with the anonymous user back to the preauthentication capture destination hosted on the first server computer in the shared network; and
if the second request contains the authentication token, redirecting the browser application running on the client device associated with the anonymous user to an authentication page hosted on a second server computer in the shared network.
Patent Citations (83)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5623601(A) | 1997-04-01 | Vu | Applicant |
| US5835727(A) | 1998-11-01 | Wong et al. | Applicant |
| US6199113(B1) | 2001-03-01 | Alegre et al. | Applicant |
| US6226752(B1) | 2001-05-01 | Gupta et al. | Applicant |
| US6266774(B1) | 2001-07-01 | Sampath et al. | Applicant |
| US6502135(B1) | 2002-12-01 | Munger et al. | Applicant |
| US6631416(B2) | 2003-10-01 | Bendinelli et al. | Applicant |
| US6643260(B1) | 2003-11-01 | Kloth et al. | Applicant |
| US6678733(B1) | 2004-01-01 | Brown et al. | Applicant |
| US6763468(B2) | 2004-07-01 | Gupta et al. | Applicant |
| US6789118(B1) | 2004-09-01 | Rao | Applicant |
| US6798746(B1) | 2004-09-01 | Kloth et al. | Applicant |
| US6816903(B1) | 2004-11-01 | Rakoshitz et al. | Applicant |
| US6834341(B1) | 2004-12-01 | Bahl et al. | Applicant |
| US6839759(B2) | 2005-01-01 | Larson et al. | Applicant |
| US6876668(B1) | 2005-04-01 | Chawla et al. | Applicant |
| US6907530(B2) | 2005-06-01 | Wang | Applicant |
| US6976089(B2) | 2005-12-01 | Na et al. | Applicant |
| US6996625(B2) | 2006-02-01 | Kaplan et al. | Applicant |
| US7085385(B2) | 2006-08-01 | Frantz et al. | Applicant |
| US7085854(B2) | 2006-08-01 | Keane et al. | Applicant |
| US7092727(B1) | 2006-08-01 | Li et al. | Applicant |
| US7143435(B1) | 2006-11-01 | Droms et al. | Applicant |
| US7181542(B2) | 2007-02-01 | Tuomenoksa et al. | Applicant |
| US7181766(B2) | 2007-02-01 | Bendinelli et al. | Applicant |
| US7185073(B1) | 2007-02-01 | Gai et al. | Applicant |
| US7185358(B1) | 2007-02-01 | Schreiber et al. | Applicant |
| US7188180(B2) | 2007-03-01 | Larson et al. | Applicant |
| US7194554(B1) | 2007-03-01 | Short et al. | Applicant |
| US7216173(B2) | 2007-05-01 | Clayton et al. | Applicant |
| US7257833(B1) | 2007-08-01 | Parekh et al. | Applicant |
| US7290288(B2) | 2007-10-01 | Gregg et al. | Applicant |
| US7310613(B2) | 2007-12-01 | Briel et al. | Applicant |
| US7316029(B1) | 2008-01-01 | Parker et al. | Applicant |
| US7324551(B1) | 2008-01-01 | Stammers | Applicant |
| US7386888(B2) | 2008-06-01 | Liang et al. | Applicant |
| US7418504(B2) | 2008-08-01 | Larson et al. | Applicant |
| US7444669(B1) | 2008-10-01 | Bahl et al. | Applicant |
| US7448075(B2) | 2008-11-01 | Morand et al. | Applicant |
| US7454792(B2) | 2008-11-01 | Cantrell et al. | Applicant |
| US7490151(B2) | 2009-02-01 | Munger et al. | Applicant |
| US7587512(B2) | 2009-09-01 | Ta et al. | Applicant |
| US7590728(B2) | 2009-09-01 | Tonnesen et al. | Applicant |
| US7610621(B2) | 2009-10-01 | Turley et al. | Applicant |
| US7624438(B2) | 2009-11-01 | White | Applicant |
| US7665130(B2) | 2010-02-01 | Johnston et al. | Applicant |
| US8032933(B2) | 2011-10-01 | Turley et al. | Applicant |
| US8108915(B2) | 2012-01-01 | White et al. | Applicant |
| US8117639(B2) | 2012-02-01 | MacKinnon et al. | Applicant |
| US2002/0023210(A1) | 2002-02-01 | Tuomenoksa et al. | Applicant |
| US2002/0026503(A1) | 2002-02-01 | Bendinelli et al. | Applicant |
| US2002/0026531(A1) | 2002-02-01 | Keane et al. | Applicant |
| US2002/0029276(A1) | 2002-03-01 | Bendinelli et al. | Applicant |
| US2002/0053031(A1) | 2002-05-01 | Bendinelli et al. | Applicant |
| US2002/0056008(A1) | 2002-05-01 | Keane et al. | Applicant |
| US2002/0091859(A1) | 2002-07-01 | Tuomenoksa et al. | Applicant |
| US2002/0099829(A1) | 2002-07-01 | Richards et al. | Applicant |
| US2002/0133586(A1) | 2002-09-01 | Shanklin et al. | Applicant |
| US2002/0138631(A1) | 2002-09-01 | Friedel et al. | Applicant |
| US2002/0165949(A1) | 2002-11-01 | Na et al. | Applicant |
| US2003/0069955(A1) | 2003-04-01 | Gieseke et al. | Applicant |
| US2003/0110073(A1) | 2003-06-01 | Briel et al. | Applicant |
| US2003/0115247(A1) | 2003-06-01 | Simpson et al. | Applicant |
| US2003/0123442(A1) | 2003-07-01 | Drucker et al. | Applicant |
| US2003/0182420(A1) | 2003-09-01 | Jones et al. | Applicant |
| US2003/0212900(A1) | 2003-11-01 | Liu et al. | Applicant |
| US2004/0064351(A1) | 2004-04-01 | Mikurak | Applicant |
| US2004/0064560(A1) | 2004-04-01 | Zhang et al. | Applicant |
| US2004/0083295(A1) | 2004-04-01 | Amara et al. | Applicant |
| US2004/0107290(A1) | 2004-06-01 | Kaplan et al. | Applicant |
| US2004/0177276(A1) | 2004-09-01 | MacKinnon et al. | Examiner |
| US2004/0215957(A1) | 2004-10-01 | Moineau et al. | Applicant |
| US2004/0268149(A1) | 2004-12-01 | Aaron | Applicant |
| US2005/0021975(A1) | 2005-01-01 | Liu | Applicant |
| US2005/0066200(A1) | 2005-03-01 | Bahl et al. | Applicant |
| US2005/0138358(A1) | 2005-06-01 | Bahl et al. | Applicant |
| US2006/0168454(A1) | 2006-07-01 | Venkatachary et al. | Applicant |
| US2008/0098464(A1) | 2008-04-01 | Mizrah | Applicant |
| US2009/0279567(A1) | 2009-11-01 | Ta et al. | Applicant |
| US2010/0192213(A1) | 2010-07-01 | Ta et al. | Applicant |
| US2011/0219444(A1) | 2011-09-01 | Turley et al. | Applicant |
| US2011/0258687(A1) | 2011-10-01 | White et al. | Applicant |
| US2012/0096517(A1) | 2012-04-01 | White et al. | Applicant |
Non-Patent Literature (55)
- Crandell et al., A Secure and Transparent Firewall Web Proxy, USENIX, Oct. 2003.Examiner
- Bauer, Designing and Using DMZ Networks to Protect Internet Servers, Linux Journal, Mar. 2001.Examiner
- Office Action for U.S. Appl. No. 12/753,390, mailed Dec. 8, 2011, 19 pgs.Applicant
- Notice of Allowance for U.S. Appl. No. 12/617,211, mailed Dec. 12, 2011, 8 pgs.Applicant
- “FreeBSD Handbook, Chapter 30 Firewalls,” 2003, found at www.freebsd.org/doc/handbook/firewalls-ipfw.html, printed Dec. 27, 2010, 13 pgs.Applicant
- Watters, Paul, “Solaris 8 Administrator's Guide. Chapter 4, Network Configuration,” O'Reilly & Associates, Inc., Jan. 2002, 17 pgs.Applicant
- Spitzner, Lance, “Configuring network interface cards; getting your interfaces to talk,” Mar. 23, 2004, 4 pgs.Applicant
- 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.Applicant
- Office Action for U.S. Appl. No. 10/683,317, dated Jan. 3, 2011, 12 pgs.Applicant
- Office Action issued in U.S. Appl. No. 11/076,672, mailed Jan. 7, 2010, 9 pgs.Applicant
- “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.Applicant
- Office Action for U.S. Appl. No. 12/506,140, mailed Feb. 18, 2011, 13 pgs.Applicant
- Office Action issued in U.S. Appl. No. 11/076,591, mailed Jul. 20, 2010, 33 pgs.Applicant
- Office Action issued in U.S. Appl. No. 10/683,317, mailed Jul. 23, 2010, 9 pgs.Applicant
- Office Action for U.S. Appl. No. 12/579,566, mailed Oct. 6, 2010, 7 pgs.Applicant
- 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>.Applicant
- 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>.Applicant
- Williamson, Matthew, “Throttling Viruses: Restricting Propagation to Defeat Malicious Mobile Code,” Proceedings of the 18th Annual Computer Security Applications Conference, 2002 IEEE, 8 pages.Applicant
- Williamson, et al, “Virus Throttling,” Virus Bulletin Research Feature 1, Mar. 2003, 4 pages.Applicant
- 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.Applicant
- Using VPN with Zone-Based Policy Firewall, May 2009, Cisco Systems, Inc., San Jose, CA, 10 pgs.Applicant
- 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.Applicant
- Class-Based Policy Provisioning: Introducing Class-Based Policy Language (CPL), Aug. 2008, 36 pgs., Cisco Systems, Inc., San Jose, CA.Applicant
- Cisco IOS Zone Based Firewall Example, at http://www.linickx.com/archives/2945/cisco-ios-zon . . . , printed Dec. 7, 2010, 6 pgs., LINICKX.com.Applicant
- Zone-Based Policy Firewall, Published Feb. 22, 2006, Updated Jun. 19, 2006, 46 pgs., Cisco Systems, Inc., San Jose, CA.Applicant
- Applying Zone-based Firewall Policies in Cisco Security Manager, Published Mar. 2009, Revised Sep. 2009, 64 pgs., Cisco Systems, Inc., San Jose, CA.Applicant
- Office Action for U.S. Appl. No. 12/506,140, mailed Aug. 4, 2011, 18 pgs.Applicant
- Office Action for U.S. Appl. No. 12/506,140, mailed Sep. 1, 2010, 11 pgs.Applicant
- Notice of Allowance for U.S. Appl. No. 12/579,566, mailed Aug. 26, 2011, 9 pgs.Applicant
- Office Action issued in U.S. Appl. No. 12/617,211, dated Feb. 3, 2011, 14 pgs.Applicant
- “Managing Firewall Services,” User Guide for Cisco Security Manager 3.3.1, Oct. 2009, Ch. 11, 90 pgs., Cisco Systems, Inc., San Jose, CA.Applicant
- “Cisco Common Classification Policy Language,” Cisco Router and Security Device Manager 2.4 User's Guide, Ch. 34, 2008, 32 pgs., Cisco Systems, Inc., San Jose, CA.Applicant
- Guide to User Documentation for Cisco Security Manager 4.0, Jun. 18, 2010, 6 pgs., Cisco Systems, Inc., San Jose, CA.Applicant
- 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.Applicant
- Tuning Cisco IOS Classic and Zone-Based Policy Firewall Denial-of-Service Protection, 2006, 10 pgs., Cisco Systems, Inc., San Jose, CA.Applicant
- Holuska, Marty, Using Cisco IOS Firewalls to Implement a Network Security Policy, Fort Hays State University/INT 490, printed Dec. 6, 2010, 5 pgs., at http://quasarint.com/Capstone/zb—policy.php.Applicant
- Cisco Feature Navigator, Cisco Systems, Inc., San Jose, CA, at http://tools.cisco.com/ITDIT/CFN/Dispatch, printed on Dec. 2, 2010, 4 pgs.Applicant
- Notice of Allowance for U.S. Appl. No. 12/753,390, mailed Mar. 16, 2012, 5 pgs.Applicant
- Notice of Allowance for U.S. Appl. No. 12,579,566, mailed Mar. 23, 2011, 12 pgs.Applicant
- Notice of Allowance for U.S. Appl. No. 12,579,566, mailed May 13, 2011, 8 pgs.Applicant
- Office Action for U.S. Appl. No. 10/683,317, mailed Jun. 8, 2011, 15 pgs.Applicant
- Office Action for U.S. Appl. No. 12/617,211, mailed Jul. 19, 2011, 18 pgs.Applicant
- Discussion of Conceptual Difference Between Cisco IOS Classic and Zone-Based Firewalls, Oct. 2007, 4 pgs., Cisco Systems, Inc., San Jose, CA.Applicant
- Cisco IOS Firewall Zone-Based Policy Firewall, Release 12.4(6)T, Technical Discussion, Feb. 2006, 77 pgs., Cisco Systems, Inc., San Jose, CA.Applicant
- Zone-Based Policy Firewall Design and Application Guide, Document ID: 98628, Sep. 13, 2007, 49 pgs., Cisco Systems, Inc., San Jose, CA.Applicant
- Office Action issued in U.S. Appl. No. 11/076,591, mailed Feb. 2, 2010, 34 pgs.Applicant
- Alshamsi, Abdelnasir, et al., “A Technical Comparison of IPSec and SSL,” Tokyo University of Technology, Jul. 8, 2004, 10 pages.Applicant
- Fisher, Dennis, “NetScreen to Acquire Neoteris,” IT Security & Network Security News, Oct. 6, 2003, 1 page.Applicant
- 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 pages.Applicant
- Snyder, Joel, “SSL VPN Gateways,” Networkworld, Jan. 12, 2004, printed Nov. 9, 2011 from http://www.networkworld.com/reviews/2004/0112revmain.html, 10 pages.Applicant
- “NetExtender for SSL-VPN,” SonicWALL SSL-VPN NetExtender, Apr. 27, 2006, 30 pages.Applicant
- “IPSec vs. SSL VPN: Transition Criteria and Methodology,” 2007 Sonicwall, 13 pages.Applicant
- 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 page.Applicant
- Notice of Allowance issued in U.S. Appl. No. 12/617,211, mailed Nov. 10, 2011, 8 pages.Applicant
- Notice of Allowance issued in U.S. Appl. No. 10/683,317, mailed Nov. 28, 2011, 11 pages.Applicant