USRE50745E1 - Reverse access method for securing front-end applications and others - Google Patents

Reverse access method for securing front-end applications and others

Info

Publication number
USRE50745E1
USRE50745E1 US18/778,056 US201318778056A USRE50745E US RE50745 E1 USRE50745 E1 US RE50745E1 US 201318778056 A US201318778056 A US 201318778056A US RE50745 E USRE50745 E US RE50745E
Authority
US
United States
Prior art keywords
dmz
network
lan
server
tcp
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
US18/778,056
Inventor
Amir Mizhar
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NetNut Ltd
Original Assignee
NetNut Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=46467095&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=USRE50745(E1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by NetNut Ltd filed Critical NetNut Ltd
Priority to US18/778,056 priority Critical patent/USRE50745E1/en
Assigned to SAFE-T DATA A.R LTD. reassignment SAFE-T DATA A.R LTD. MERGER Assignors: RSAccess Ltd.
Assigned to NETNUT LTD. reassignment NETNUT LTD. ASSIGNMENT OF ASSIGNOR'S INTEREST Assignors: SAFE-T DATA A.R. LTD.
Assigned to RSACCESS LTD reassignment RSACCESS LTD ASSIGNMENT OF ASSIGNOR'S INTEREST Assignors: MIZHAR, AMIR
Application granted granted Critical
Publication of USRE50745E1 publication Critical patent/USRE50745E1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0209—Architectural arrangements, e.g. perimeter networks or demilitarized zones
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/029—Firewall traversal, e.g. tunnelling or, creating pinholes

Definitions

  • the following is an invention for securing electronically stored data, the computer on which the data resides on and the communications of the computer with its computer network.
  • the DMZ is a sub-network that contains the organization's external services to a larger untrusted network (usually the Internet), potential hackers and malicious code may gain access to the DMZ, but rarely do they gain access to the LAN.
  • the computers on the DMZ have limited connectivity to the computers on the LAN and are usually separated by a firewall that controls the traffic between the DMZ computers and the LAN computers.
  • the DMZ can be seen as an additional layer of security to the LAN.
  • a DMZ requires the duplication of relevant data and computer programs so they can reside on both the DMZ computers and on the LAN computers. This duplication of data and computer programs has several drawbacks. It can be costly to purchase additional licenses required to install multiple instances of the same computer program on both the LAN and on the DMZ. Supporting and managing duplicate computer programs and data on the LAN and on the DMZ can be costly and difficult. Furthermore, since the DMZ interfaces with the external systems, the data on the DMZ is vulnerable to hacking attacks and external malicious code.
  • the following invention aims to overcome these disadvantages and to provide an efficient system for protecting the data on the LAN.
  • FIG. 1 describes the System that includes the LAN ( 30 ) which includes the Service ( 33 ), the LAN Server ( 31 ) and the LAN Controller ( 32 ); The, the DMZ ( 20 ) 5 which includes the DMZ Server ( 21 ), the DMZ Stack Pool Service ( 22 );, and the WAN ( 10 );, and the connections between these components.
  • the present invention provides a System for securing the data and the hosts that reside in the LAN and in the same time enable users to communicate with the LAN in a secured way.
  • WAN Wide Area Network
  • DMZ De-5 Militarized Zone
  • LAN Local Area Network
  • LAN Server Server running in the LAN
  • DMZ Server Server running in the DMZ ( 21 )
  • DMZ Stack Pool Service Stores and handles Client's Requests ( 22 ) in the DMZ
  • Client Request HTTP/HTTPS (Web browser)/
  • Client Connection Information IP-address/Port number of the relevant destination service inside the LAN
  • LAN Controller a controller running in the LAN that manages the Client Connection Information ( 32 );
  • Connection Binder Handshake between two TCP/IP sockets
  • Service HTTP/HTTPS (Web Server)/SSH/SFTP/FTP/FTPS/RDP/SMTP/TLS, and any other TCP/IP 15 based services.
  • WAN Wide Area Network
  • DMZ De-Militarized Zone (20)
  • LAN Local Area Network (30)
  • LAN Server Server running in the LAN (31);
  • DMZ Server Server running in the DMZ (21);
  • DMZ Stack Pool Service Stores and handles Client's Requests (22) in the DMZ
  • Client Request HTTP/HTTPS (Web browser)/
  • the objective of this invention is to provide a secured connection between servers in the LAN and the clients in the WAN.
  • FIG. 1 describes the main components of the System.
  • the LAN ( 30 ) includes the Service ( 33 ), the LAN Server ( 31 ) and the LAN Controller ( 32 );
  • the DMZ ( 20 ) includes the DMZ Server ( 21 ), the DMZ Stack Pool Service ( 22 ); and the WAN ( 10 ) that by its nature includes the clients and the ‘outside’ world.
  • FIG. 1 describes the connections between the System components.
  • First step The Client Request (of the client ( 11 )) reaches the DMZ Server ( 21 ).
  • One of the innovative aspects of the System is that the LAN Controller ( 32 ) constantly, and/or on a predefined set of time basis, checks for Client Requests stored in the DMZ Stack Pool Service ( 22 ).
  • the Fifth step The LAN Server ( 31 ) then generates two TCP/IP connections: One connection is to the Service ( 33 ), which is the destination service, based on 5 the Client Connection Information.
  • the second connection is an outbound connection ( 42 ) to the DMZ Server ( 21 ).
  • the LAN Server ( 31 ) creates a Connection Binder in the LAN Server between the Service ( 33 ) and the outbound connection ( 42 ).
  • Connection Binder in the DMZ Server, binds the Client Request and 15 the outbound connection ( 42 ) arriving from the LAN Server, the Client Request is then streamed through the DMZ Server and the LAN Server over the System, and then the client request data streams from the Service ( 33 ) to the Client ( 11 ).
  • LAN Server ( 31 ) no administrative management is required in the LAN Server ( 31 ) to establish or maintain 5 communications after it is initially installed and configured on the LAN ( 30 ) and on the DMZ ( 20 ).
  • the LAN Controller ( 32 ) permanently or periodically queries the DMZ Stack Pool Service ( 22 ) for incoming Client Requests.
  • the DMZ Server ( 20 ) will accept all Client Requests and route them to the LAN-Server ( 31 ), without changing the data that the Client Requests contains.
  • HTTPS connection protocol will be transmitted over the System, as with any other common protocols such as SSH/SFTP/FTP/FTPS/RDP/SMTP/TLS/ or any other TCP/IP based protocols.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • General Engineering & Computer Science (AREA)
  • Computing Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Bioethics (AREA)
  • General Health & Medical Sciences (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Small-Scale Networks (AREA)

Abstract

A System that provides a secured connection between servers on the LAN and clients on the WAN comprises the LAN (which includes LAN Server and LAN Controller) and the DMZ (which includes DMZ Server and DMZ Stack Pool Service). Wherein the Client Request reaches the DMZ Server it stores it in the DMZ Stack Pool Service and the LAN Controller establishes outbound TCP based connection to the DMZ Stack Pool Service that passes the Client Connection Information to the LAN Server via the LAN Controller. Then the LAN Server then generates a connection between the Service and DMZ Server.

Description

This application is a continuation reissue application of U.S. application Ser. No. 16/838,401, filed on Apr. 2, 2020, which is a reissue of U.S. application Ser. No. 14/379,305, filed Aug. 18, 2014 (issued as U.S. Pat. No. 9.935,958, on Apr. 3, 2018), which is a National Stage of International Application No. PCT/IL2013/000017 having a filing date of Feb. 13, 2013, which claims foreign priority from Israeli Application No. 218185 having a filing date of Feb. 19, 2012. Each of the foregoing applications is incorporated by reference in its entirety.
Notice: More than one reissue application has been filed for the reissue of U.S. Pat. No. 9,935,958. The reissue application Ser. Nos. are 16/838,401 and the present application.
The following is an invention for securing electronically stored data, the computer on which the data resides on and the communications of the computer with its computer network.
BACKGROUND ART
It is a well-known fact that the computers in an organization's internal network (also known as the local area network or LAN) which provide services to users outside of the organization are highly prone to attacks from external hackers and malicious code. Due to this risk, it is a common practice to protect the LAN by placing external-facing computers in a segregated sub-network and thereby shield the rest of the network in case of an attack. This sub-network is commonly known as the DMZ (or De-Militarized Zone). Any computer running programs that provide services to users outside of the organization^ organization's internal network can be placed on the DMZ. The most common type of computers are web servers, email servers, FTP servers and VoIP servers. Since the DMZ is a sub-network that contains the organization's external services to a larger untrusted network (usually the Internet), potential hackers and malicious code may gain access to the DMZ, but rarely do they gain access to the LAN. The computers on the DMZ have limited connectivity to the computers on the LAN and are usually separated by a firewall that controls the traffic between the DMZ computers and the LAN computers. The DMZ can be seen as an additional layer of security to the LAN.
Organizations that have Internet portals which enable communications with the general public via the Internet are vulnerable to infiltration from the outside. Therefore, many of these organizations establish a DMZ to protect their sensitive data and to reduce the ability of hackers to infiltrate the LAN. The ways and methods under which the DMZ works is known to any expert in the field, and therefore there is no need to describe them here in further detail.
Establishing a DMZ requires the duplication of relevant data and computer programs so they can reside on both the DMZ computers and on the LAN computers. This duplication of data and computer programs has several drawbacks. It can be costly to purchase additional licenses required to install multiple instances of the same computer program on both the LAN and on the DMZ. Supporting and managing duplicate computer programs and data on the LAN and on the DMZ can be costly and difficult. Furthermore, since the DMZ interfaces with the external systems, the data on the DMZ is vulnerable to hacking attacks and external malicious code.
The following invention aims to overcome these disadvantages and to provide an efficient system for protecting the data on the LAN.
DESCRIPTION OF THE DRAWINGS
The intention of the drawings attached to the application is not to limit the scope of the invention and its application. The drawings are intended only to 5 illustrate the invention and they constitute only one of its many possible implementations.
FIG. 1 describes the System that includes the LAN (30) which includes the Service (33), the LAN Server (31) and the LAN Controller (32); The, the DMZ (20) 5 which includes the DMZ Server (21), the DMZ Stack Pool Service (22);, and the WAN (10);, and the connections between these components.
 THE INVENTION
As described above, there is a strong need for a computer system that enables users to communicate with the LAN and in the same time protects the LAN from external threats. The following invention provides an efficient solution for the issues that are mentioned above.
The present invention provides a System for securing the data and the hosts that reside in the LAN and in the same time enable users to communicate with the LAN in a secured way.
For the sake of clarity and for simplifying the explanation of the System, the following terms are used: WAN: Wide Area Network (10); DMZ: De-5 Militarized Zone (20); LAN: Local Area Network (30); LAN Server: Server running in the LAN (31); DMZ Server: Server running in the DMZ (21); DMZ Stack Pool Service: Stores and handles Client's Requests (22) in the DMZ; Client Request: HTTP/HTTPS (Web browser)/
SSH/SFTP/FTP/FTPS/RDP/SMTP/TLS, and any other TCP/IP based protocols; 10 Client Connection Information: IP-address/Port number of the relevant destination service inside the LAN; LAN Controller: a controller running in the LAN that manages the Client Connection Information (32); Connection Binder: Handshake between two TCP/IP sockets; Service: HTTP/HTTPS (Web Server)/SSH/SFTP/FTP/FTPS/RDP/SMTP/TLS, and any other TCP/IP 15 based services.For the sake of clarity and for simplifying the explanation of the System, the following terms are used: WAN: Wide Area Network (10); DMZ: De-Militarized Zone (20); LAN: Local Area Network (30); LAN Server: Server running in the LAN (31); DMZ Server: Server running in the DMZ (21); DMZ Stack Pool Service: Stores and handles Client's Requests (22) in the DMZ; Client Request: HTTP/HTTPS (Web browser)/SSH/SFTP/FTP/FTPS/RDP/SMTP/TLS, and any other TCP/IP based protocols; Client Connection Information: IP-address/Port number of the relevant destination service inside the LAN; LAN Controller: a controller running in the LAN that manages the Client Connection Information (32); Connection Binder: Handshake between two TCP/IP sockets; Service: HTTP/HTTPS (Web Server)/SSH/SFTP/FTP/FTPS/RDP/SMTP/TLS. and any other TCP/IP based services.
The objective of this invention is to provide a secured connection between servers in the LAN and the clients in the WAN.
FIG. 1 describes the main components of the System. The LAN (30) includes the Service (33), the LAN Server (31) and the LAN Controller (32); The DMZ (20) includes the DMZ Server (21), the DMZ Stack Pool Service (22); and the WAN (10) that by its nature includes the clients and the ‘outside’ world. In addition, FIG. 1 describes the connections between the System components.
The connections between the System components will be described while 10 describing the System flow. The connection flow of the System is as follow:
First step: The Client Request (of the client (11)) reaches the DMZ Server (21). Second step: The DMZ Server (21) stores the Client Request in the DMZ Stack Pool Service (22). Third step: The LAN Controller (32) establishes outbound 15 TCP based connection (41) to the DMZ Stack Pool Service (22). One of the innovative aspects of the System is that the LAN Controller (32) constantly, and/or on a predefined set of time basis, checks for Client Requests stored in the DMZ Stack Pool Service (22). Fourth step: The DMZ Stack Pool Service (22) then passes the Client Connection Information, to the LAN Server (31) via 20 the LAN Controller (32).
The Fifth step: The LAN Server (31) then generates two TCP/IP connections: One connection is to the Service (33), which is the destination service, based on 5 the Client Connection Information. The second connection is an outbound connection (42) to the DMZ Server (21). In addition the LAN Server (31) creates a Connection Binder in the LAN Server between the Service (33) and the outbound connection (42). The Sixth step: The DMZ Server (21) then creates a Connection Binder in the DMZ Server between the incoming Client 10 Request (that is stored in the DMZ Stack Pool Service (22)) and the outbound connection (42) arriving from the LAN Server (31), and by that completes the route of the Client Request.
Once the Connection Binder, in the DMZ Server, binds the Client Request and 15 the outbound connection (42) arriving from the LAN Server, the Client Request is then streamed through the DMZ Server and the LAN Server over the System, and then the client request data streams from the Service (33) to the Client (11).
In accordance with this invention as described above, no administrative management is required in the LAN Server (31) to establish or maintain 5 communications after it is initially installed and configured on the LAN (30) and on the DMZ (20). The LAN Controller (32) permanently or periodically queries the DMZ Stack Pool Service (22) for incoming Client Requests. The DMZ Server (20) will accept all Client Requests and route them to the LAN-Server (31), without changing the data that the Client Requests contains. For 10 example, if a Client Request uses the HTTPS connection protocol, then the HTTPS connection protocol will be transmitted over the System, as with any other common protocols such as SSH/SFTP/FTP/FTPS/RDP/SMTP/TLS/ or any other TCP/IP based protocols.

Claims (24)

What is claimed:
1. A system for reverse access, said system comprising:
a De-Militarized Zone (DMZ) Stack Pool Service located in a De-Militarized Zone, the DMZ Stack Pool Service being arranged to store requests received from a client, wherein said requests are stored at the TCP/IP level;
a local area network (LAN) Controller configured to check for existence in said DMZ Stack Pool Service of said requests, wherein said checking is performed at the TCP/IP level and said LAN Controller is located in a LAN; and
a DMZ server configured to receive said requests from a LAN server of said LAN, and to route said requests to said client, wherein receiving and routing by said DMZ server occurs at the TCP/IP level;
wherein said DMZ Stack Pool Service, said LAN Controller, and said DMZ server do not change the data of said requests and the system requires no administrative management after initial installation and configuration.
2. The system of claim 1, wherein computer programs and sensitive data of said LAN server reside only in the LAN.
3. A method for reverse access, said method comprising:
storing requests received from a client, wherein said requests are stored in a De-Militarized zone (DMZ) Stack Pool Service at the TCP/IP level, wherein said DMZ Stack Pool Service is located in a De-Militarized Zone;
checking at the TCP/IP level, said DMZ Stack Pool Service for existence of said requests, wherein said checking is performed by a local area network (LAN) Controller located in a LAN; and
receiving said requests from a LAN server of said LAN and routing said requests to said client;
wherein said storing and routing occurs at the TCP/IP level and said storing and routing does not change data of said requests; and
wherein said method requires no administrative management of the LAN server after initial installation and configuration.
4. The method of claim 3, wherein computer programs and sensitive data of said LAN server, reside only in the LAN.
5. A system for reverse access, the system comprising:
a De-Militarized Zone (DMZ) Stack Pool Service executing on a device in a DMZ, the DMZ Stack Pool Service being configured to store a request received from a client, wherein the request is stored at a TCP/IP level using a TCP/IP protocol;
a network Controller located in a network, the network Controller being configured to check for existence of the request in the DMZ Stack Pool Service, wherein the checking is performed at the TCP/IP level; and
a DMZ server configured to provide data responsive to the request to the client, wherein the providing by the DMZ server occurs at the TCP/IP level using the TCP/IP protocol;
wherein the DMZ server does not change the data of the request and the
system requires no administrative management after initial installation and configuration to perform the storing, checking, and providing.
6. The system of claim 5, wherein a computer program and certain data of the system reside only in the network.
7. The system of claim 5, wherein the network Controller passes client connection information to a server of the network.
8. The system of claim 7, wherein the client connection information includes an Internet Protocol (IP) address associated with a service on the network.
9. The system of claim 7, wherein the client connection information includes a port number associated with a service on the network.
10. The system of claim 5, wherein the DMZ is a subnetwork of the network.
11. The system of claim 10, wherein the subnetwork is configured to interface with computers outside of the network and with computers inside the network.
12. The system of claim 5, wherein the network is a web server network.
13. The system of claim 5, wherein the network is an email network.
14. The system of claim 5, wherein the network is a file storage network.
15. The system of claim 5, wherein the network is an Internet Protocol-based telephone network.
16. A method for reverse access, the method comprising:
storing a request received from a client in a De-Militarized Zone (DMZ) Stack Pool Service, in a DMZ, at a TCP/IP level using a TCP/IP protocol;
checking, at the TCP/IP level, the DMZ Stack Pool Service for existence of the request, wherein the checking is performed by a network Controller located in a network;
establishing an outbound connection from a network server of the network and routing data responsive to the request to the client; and
wherein the storing and routing occurs at the TCP/IP level using the TCP/IP protocol and a DMZ server does not change data of the request; and
wherein the method requires no administrative management of a server of the network after initial installation and configuration to perform the storing, checking, and providing.
17. The method of claim 16, wherein a computer program and certain data of the network server reside only in the network.
18. The method of claim 16, wherein the checking for existence of the request is performed continuously.
19. The method of claim 16, wherein the checking for existence of the request is performed periodically.
20. The method of claim 16, further comprising, in response to the checking, passing client connection information to the network server.
21. The method of claim 20, wherein the client connection information is passed to the network server via the network Controller.
22. The method of claim 16, further comprising creating a connection binder between at least one of the requests and the outbound connection.
23. The method of claim 22, further comprising, after creating the connection binder, routing the data responsive to the request to the client.
24. The method of claim 23, wherein routing the data comprises streaming the data.
US18/778,056 2012-02-19 2013-02-13 Reverse access method for securing front-end applications and others Active USRE50745E1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US18/778,056 USRE50745E1 (en) 2012-02-19 2013-02-13 Reverse access method for securing front-end applications and others

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
IL218185 2012-02-19
IL218185A IL218185B (en) 2012-02-19 2012-02-19 Internal server intrusion protection system
US14/379,305 US9935958B2 (en) 2012-02-19 2013-02-13 Reverse access method for securing front-end applications and others
US18/778,056 USRE50745E1 (en) 2012-02-19 2013-02-13 Reverse access method for securing front-end applications and others
PCT/IL2013/000017 WO2013121410A1 (en) 2012-02-19 2013-02-13 Reveres access method for securing front-end applications and others
US202016838401A 2020-04-02 2020-04-02

Publications (1)

Publication Number Publication Date
USRE50745E1 true USRE50745E1 (en) 2026-01-06

Family

ID=46467095

Family Applications (4)

Application Number Title Priority Date Filing Date
US16/838,401 Active USRE50113E1 (en) 2012-02-19 2013-02-13 Reverse access method for securing front-end applications and others
US14/379,305 Ceased US9935958B2 (en) 2012-02-19 2013-02-13 Reverse access method for securing front-end applications and others
US18/778,056 Active USRE50745E1 (en) 2012-02-19 2013-02-13 Reverse access method for securing front-end applications and others
US15/896,819 Active US10110606B2 (en) 2012-02-19 2018-02-14 Reverse access method for securing front-end applications and others

Family Applications Before (2)

Application Number Title Priority Date Filing Date
US16/838,401 Active USRE50113E1 (en) 2012-02-19 2013-02-13 Reverse access method for securing front-end applications and others
US14/379,305 Ceased US9935958B2 (en) 2012-02-19 2013-02-13 Reverse access method for securing front-end applications and others

Family Applications After (1)

Application Number Title Priority Date Filing Date
US15/896,819 Active US10110606B2 (en) 2012-02-19 2018-02-14 Reverse access method for securing front-end applications and others

Country Status (6)

Country Link
US (4) USRE50113E1 (en)
EP (1) EP2815554B1 (en)
CN (1) CN104412558B (en)
ES (1) ES2609457T3 (en)
IL (1) IL218185B (en)
WO (1) WO2013121410A1 (en)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8560604B2 (en) 2009-10-08 2013-10-15 Hola Networks Ltd. System and method for providing faster and more efficient data communication
US9241044B2 (en) 2013-08-28 2016-01-19 Hola Networks, Ltd. System and method for improving internet communication by using intermediate nodes
US11023846B2 (en) 2015-04-24 2021-06-01 United Parcel Service Of America, Inc. Location-based pick up and delivery services
US11057446B2 (en) 2015-05-14 2021-07-06 Bright Data Ltd. System and method for streaming content from multiple servers
EP3805958B1 (en) 2017-08-28 2023-12-20 Bright Data Ltd. Method for improving content fetching by selecting tunnel devices
LT3780547T (en) 2019-02-25 2023-03-10 Bright Data Ltd. SYSTEM AND METHOD FOR DOWNLOADING CONTENT USING A URL TESTING MECHANISM
WO2020202135A2 (en) 2019-04-02 2020-10-08 Luminati Networks Ltd. System and method for managing non-direct url fetching service
US11190489B2 (en) 2019-06-04 2021-11-30 OPSWAT, Inc. Methods and systems for establishing a connection between a first device and a second device across a software-defined perimeter
CN113141402B (en) * 2021-04-20 2022-11-29 中国建设银行股份有限公司 Automatic user synchronization method and device for canteen
IL309988A (en) 2021-07-26 2024-03-01 Bright Data Ltd Emulating web browser in a dedicated intermediary box
EP4418625B1 (en) 2023-02-20 2025-03-26 Barclays Execution Services Limited Message routing system

Citations (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6470386B1 (en) 1997-09-26 2002-10-22 Worldcom, Inc. Integrated proxy interface for web based telecommunications management tools
EP1324565A1 (en) * 2001-12-12 2003-07-02 Pervasive Security Systems Inc. Method and architecture for providing access to secured data from non-secured clients
US20030204613A1 (en) * 2002-04-26 2003-10-30 Hudson Michael D. System and methods of streaming media files from a dispersed peer network to maintain quality of service
US20050240994A1 (en) * 2004-04-22 2005-10-27 Sbc Knowledge Ventures, L.P. Method, system and software for maintaining network access and security
CN1731786A (en) 2004-08-04 2006-02-08 富士施乐株式会社 Network system, internal server, terminal device, storage medium and packet relay method
US20060200547A1 (en) * 2005-03-01 2006-09-07 Edwards Anthony V V Methods, devices, systems and computer program products for providing secure communications between managed devices in firewall protected areas and networks segregated therefrom
US7181493B2 (en) 2003-12-23 2007-02-20 Unisys Corporation Platform independent model-based framework for exchanging information in the justice system
US20070050843A1 (en) * 2005-03-18 2007-03-01 Lehman Brothers Inc. VoIP proxy server
US20070073869A1 (en) * 2005-08-26 2007-03-29 Hon Hai Precision Industry Co., Ltd. System and method for transmitting data
EP2031817A1 (en) 2007-08-30 2009-03-04 Software Ag Systems and/or methods for streaming reverse HTTP gateway and network including the same
US20090094691A1 (en) * 2007-10-03 2009-04-09 At&T Services Inc. Intranet client protection service
US20100131616A1 (en) * 2008-11-24 2010-05-27 Sap Ag DMZ Framework

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4639275A (en) 1982-04-22 1987-01-27 The Board Of Trustees Of The University Of Illinois Forming disordered layer by controlled diffusion in heterojunction III-V semiconductor
US4843033A (en) 1985-09-27 1989-06-27 Texas Instruments Incorporated Method for outdiffusion of zinc into III-V substrates using zinc tungsten silicide as dopant source
US4824798A (en) 1987-11-05 1989-04-25 Xerox Corporation Method of introducing impurity species into a semiconductor structure from a deposited source
US4927773A (en) 1989-06-05 1990-05-22 Santa Barbara Research Center Method of minimizing implant-related damage to a group II-VI semiconductor material
US7506058B2 (en) * 2001-12-28 2009-03-17 International Business Machines Corporation Method for transmitting information across firewalls
US20050251855A1 (en) * 2004-05-04 2005-11-10 Hob Gmbh & Co. Kg Client-server-communication system
GB0508624D0 (en) * 2005-04-28 2005-06-08 Ibm Reverse proxy system and method
US20070180512A1 (en) * 2005-10-21 2007-08-02 Hewlett-Packard Development Company, L.P. Methods of setting up and operating a reverse channel across a firewall
CA2633966C (en) * 2005-12-15 2014-04-15 Lehman Brothers Inc. System and method for secure remote desktop access
US8479275B1 (en) * 2006-02-01 2013-07-02 Cisco Technology, Inc. Secure high-throughput data-center network employing routed firewalls
CN101110693A (en) * 2006-07-17 2008-01-23 上海华虹Nec电子有限公司 Internet website security architecture system
US8413241B2 (en) * 2009-09-17 2013-04-02 Oracle America, Inc. Integrated intrusion deflection, detection and introspection
US9059962B2 (en) * 2013-03-13 2015-06-16 Route1 Inc. Secure access to applications behind firewall

Patent Citations (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6470386B1 (en) 1997-09-26 2002-10-22 Worldcom, Inc. Integrated proxy interface for web based telecommunications management tools
EP1324565A1 (en) * 2001-12-12 2003-07-02 Pervasive Security Systems Inc. Method and architecture for providing access to secured data from non-secured clients
US20170118214A1 (en) * 2001-12-12 2017-04-27 Pervasive Security Systems, Inc. Method and architecture for providing access to secured data from non-secured clients
US20030204613A1 (en) * 2002-04-26 2003-10-30 Hudson Michael D. System and methods of streaming media files from a dispersed peer network to maintain quality of service
US7181493B2 (en) 2003-12-23 2007-02-20 Unisys Corporation Platform independent model-based framework for exchanging information in the justice system
US20050240994A1 (en) * 2004-04-22 2005-10-27 Sbc Knowledge Ventures, L.P. Method, system and software for maintaining network access and security
US7707628B2 (en) 2004-08-04 2010-04-27 Fuji Xerox Co., Ltd. Network system, internal server, terminal device, storage medium and packet relay method
CN1731786A (en) 2004-08-04 2006-02-08 富士施乐株式会社 Network system, internal server, terminal device, storage medium and packet relay method
US20060031929A1 (en) 2004-08-04 2006-02-09 Fuji Xerox Co., Ltd. Network system, internal server, terminal device, storage medium and packet relay method
US20060200547A1 (en) * 2005-03-01 2006-09-07 Edwards Anthony V V Methods, devices, systems and computer program products for providing secure communications between managed devices in firewall protected areas and networks segregated therefrom
US20070050843A1 (en) * 2005-03-18 2007-03-01 Lehman Brothers Inc. VoIP proxy server
US20070073869A1 (en) * 2005-08-26 2007-03-29 Hon Hai Precision Industry Co., Ltd. System and method for transmitting data
US20090064307A1 (en) * 2007-08-30 2009-03-05 Software Ag Systems and/or methods for streaming reverse HTTP gateway, and network including the same
EP2031817A1 (en) 2007-08-30 2009-03-04 Software Ag Systems and/or methods for streaming reverse HTTP gateway and network including the same
US20090094691A1 (en) * 2007-10-03 2009-04-09 At&T Services Inc. Intranet client protection service
US20100131616A1 (en) * 2008-11-24 2010-05-27 Sap Ag DMZ Framework

Non-Patent Citations (18)

* Cited by examiner, † Cited by third party
Title
First Office Action from the Israel Patent Office for Israeli Patent Application No. 218185 dated Jul. 12, 2015.
Forrester Research, 2012, "The Complete File-Transferring Suit," 2 pages.
Fourth Office Action for Chinese Patent Application No. 2013800207104, SIPO, dated Nov. 28, 2017.
International Search Report from PCT Application No. PCT/IL2013/000017.
Second Office Action from the Israel Patent Office for Israeli Patent Application No. 218185 dated Jun. 4, 2017.
TCP/IP Networking an Example, May 25, 2002, CS 458 Slides, University of Virginia, pp. 1-12. *
The First Office Action for Chinese Application No. 201380020710.4, SIPO, dated Sep. 21, 2016.
The Second Office Action for Chinese Application No. 201380020110.4, SIPO, dated Feb. 21, 2017.
The Third Office Action for Chinese Application No. 201380020710.4, SIPO, dated Jun. 13, 2017.
First Office Action from the Israel Patent Office for Israeli Patent Application No. 218185 dated Jul. 12, 2015.
Forrester Research, 2012, "The Complete File-Transferring Suit," 2 pages.
Fourth Office Action for Chinese Patent Application No. 2013800207104, SIPO, dated Nov. 28, 2017.
International Search Report from PCT Application No. PCT/IL2013/000017.
Second Office Action from the Israel Patent Office for Israeli Patent Application No. 218185 dated Jun. 4, 2017.
TCP/IP Networking an Example, May 25, 2002, CS 458 Slides, University of Virginia, pp. 1-12. *
The First Office Action for Chinese Application No. 201380020710.4, SIPO, dated Sep. 21, 2016.
The Second Office Action for Chinese Application No. 201380020110.4, SIPO, dated Feb. 21, 2017.
The Third Office Action for Chinese Application No. 201380020710.4, SIPO, dated Jun. 13, 2017.

Also Published As

Publication number Publication date
IL218185A0 (en) 2012-06-28
US20180176225A1 (en) 2018-06-21
WO2013121410A1 (en) 2013-08-22
CN104412558A (en) 2015-03-11
EP2815554B1 (en) 2016-10-05
EP2815554A1 (en) 2014-12-24
IL218185B (en) 2018-12-31
HK1207766A1 (en) 2016-02-05
US10110606B2 (en) 2018-10-23
EP2815554A4 (en) 2015-12-23
USRE50113E1 (en) 2024-09-03
US9935958B2 (en) 2018-04-03
ES2609457T3 (en) 2017-04-20
CN104412558B (en) 2019-01-29
US20150020161A1 (en) 2015-01-15

Similar Documents

Publication Publication Date Title
US10110606B2 (en) Reverse access method for securing front-end applications and others
US12425366B2 (en) Establishing and using a tunnel from an origin server in a distributed edge compute and routing service
US11399010B1 (en) Private network request forwarding
US9954902B1 (en) Secure proxy
US8887265B2 (en) Named sockets in a firewall
US12294471B2 (en) Network layer performance and security provided by a distributed cloud computing network
US10230763B2 (en) Application layer-based single sign on
US20180159825A1 (en) Network host provided security system for local networks
US20110154477A1 (en) Dynamic content-based routing
US11838317B2 (en) Method for providing a connection between a communications service provider and an internet protocol, IP, server, providing a service, as well as a perimeter network, comprising the IP server, and an IP server providing the service
Cronje Choosing the best firewall
HK1207766B (en) Reverse access method for securing front-end applications and others

Legal Events

Date Code Title Description
FEPP Fee payment procedure

Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY

FEPP Fee payment procedure

Free format text: ENTITY STATUS SET TO SMALL (ORIGINAL EVENT CODE: SMAL); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY