WO2005010644A2 - Systeme et procede visant a augmenter la securite d'un reseau - Google Patents

Systeme et procede visant a augmenter la securite d'un reseau Download PDF

Info

Publication number
WO2005010644A2
WO2005010644A2 PCT/SG2004/000228 SG2004000228W WO2005010644A2 WO 2005010644 A2 WO2005010644 A2 WO 2005010644A2 SG 2004000228 W SG2004000228 W SG 2004000228W WO 2005010644 A2 WO2005010644 A2 WO 2005010644A2
Authority
WO
WIPO (PCT)
Prior art keywords
application
responder
private
address
website
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/SG2004/000228
Other languages
English (en)
Other versions
WO2005010644A3 (fr
Inventor
Bandu J. Wewalaarachchi
Hari Gunasingham
Lakshita Sanjeewa Wijerathne
Viraj Sanjaya Ramanayake
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.)
Eutech Cybernetics Pte Ltd
Original Assignee
Eutech Cybernetics Pte 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
Application filed by Eutech Cybernetics Pte Ltd filed Critical Eutech Cybernetics Pte Ltd
Publication of WO2005010644A2 publication Critical patent/WO2005010644A2/fr
Publication of WO2005010644A3 publication Critical patent/WO2005010644A3/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

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/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
    • H04L63/0218—Distributed architectures, e.g. distributed firewalls

Definitions

  • This invention relates to methods and systems for increasing security over the internet. More particularly, this invention relates to a system and method for providing public access to websites while providing increased security for private databases and applications that are accessed by the website in order to respond to user inquiries.
  • the internet may be loosely described as a public network, or a collection of public networks, consisting generally of a collection of distributed IP devices, e.g. , PCs, printers, routers, servers, etc., each of which have a distinct IP address, e.g., 1.1.1.1, 1.1.1.2, ... 1.1.1.10. See, e.g., Fig. 1.
  • Private networks which themselves comprise collection of IP devices, each having a discrete IP address which theoretically may be identical to the IP address for a completely different device located on a different private network or located on a public network.
  • Private networks are often connected to the public networks through a gateway (router or proxy).
  • Devices on one private network can communicate or "address" a device on a public network through the gateway that acts as a proxy to the public network. If a device on a private network knows the IP address of device in the same private network or public network, the first device can directly address the second device using the above principle. Accordingly, in order to address a device on the internet, it is necessary to know its IP address.
  • the websites that make up much of what is considered by the public to be "the internet” reside on web servers which have addresses on a public network (a public IP address).
  • a public IP address By contrast, most users access the internet through PCs residing on a private network which provides a gateway to the public networks (these gateways are commonly referred to as Internet gateways and carry two IP addresses, one on the private network and the other on a public network).
  • these devices on private networks are described above as having IP addresses, these IP addresses are usually , private (they are not addressable by users outside of the private network on which it resides) and dynamic (the IP address for a particular device on a private network is assigned automatically by a DHCP (dynamic host configuration protocol) server in order to reduce network management overheads created by conflicting IP addresses).
  • DHCP dynamic host configuration protocol
  • Both the browser in a user's PC and a website residing on a web server have port numbers for receiving communications into the correct application that runs in the device.
  • website port numbers are public and well known.
  • the port number for websites on the http network is 80; the port number for websites on the https is 443; and the port number for websites on the FTP network is 21. Accordingly, when a user' s PC browser sends a request to a website, it uses the website's IP address together with the appropriate port to address the website and accompanies the message with the PC's temporary dynamic IP address as well as the transient port number that corresponds to the browser which generated the request.
  • the website in responding to the request, directs the response to the dynamic IP address and port number that accompanied the request. See, e.g., Fig. 2.
  • the way that PCs with dynamic IP addresses on a private network can receive information from a website web server on a public network may be described as follows: the user types into a browser application running on his PC the public IP ' address for a website web server. The user's PC then directs a request to the website . server at the specified address and well-known port number. The request generated by the user's PC includes its return address (its private dynamic address) and a "port number", which is also known as a "TCP socket," that will be open for a short specified time in order to receive the reply.
  • the TCP socket identifies the particular application on the user's computer to which the reply should be directed — any one user may have several browsers open on his PC, using each browser to communicate with different websites.
  • a device in the private network is able to address a device in the public network through a gateway (which serves as a proxy for the public network)
  • a website cannot address the PC in the private network due to the fact that private IP is not a 'global address' and it is not addressable from the public network.
  • the gateway manages a temporary network address translation table (NAT) which gets built dynamically as communication takes place.
  • NAT temporary network address translation table
  • a request from private network travels to the public network via the gateway, it forwards the request to the website with its own public IP address and a randomly picked port number as the return socket. Also, the gateway adds an entry to the NAT to map that socket to the return IP address and port number of the browser or other client application that generated the request.
  • the gateway forwards it to the client application the generated the request after performing a lookup in the NAT.
  • the gateway does not allow it by virtue of the fact that there is no address mapping in the NAT (unless it has been specifically setup to act as a reverse proxy as described below).
  • a public website can always be addressed by a client application' on a private network, while a private user's PC cannot be addressed from the Internet.
  • websites traditionally reside on "web servers" which have a static public IP address on a public network.
  • the web server may be represented on the public network by a router or "reverse proxy" which directs inquiries to the web server which may be placed on a private network. See, e.g., Fig. 3.
  • the proxy or router will map its public IP address to the private address of the web server, and redirect inquiries coming into the public IP address to the web server address.
  • This method is also known as “reverse proxy” or “IP forwarding” or “protocol tunneling” with slight variation in implementation.
  • the principle is to forward the request coming from a client application (or an Internet gateway of another private network) on the Internet to the web server.
  • Websites in contrast, by virtue of the fact that they have public addresses, are subject to unauthorized access.
  • websites typically reside on a web server and.compri.se two primary functional units: a listening unit and a responder unit.
  • the listening unit which maintains an open line of communication with the public network and receives requests for information from other devices (users) located on the public network or on private networks with access to the public network.
  • the responder unit contains the ASP pages, CGI applications, etc., in effect defining that information which is to be published or made available for publication.
  • the responder When the responder receives a request for information, the responder typically accesses, a memory, for example via a database application, conta-ining public and sensitive information. Many websites also have access to private "source data" which may be used to generate the public or sensitive information for publication to authorized users.
  • the responder unit serves as the gateway for dete ⁇ n ing which requesting devices are entitled to sensitive and/or public information in the website.
  • the responder unit is typically designed so as not to give away, or "publish,” the private source data. Rather, it only uses the private source data to generate the public and/or sensitive information which is then published to authorized users via the website.
  • network engineers design "firewalls" which will attempt to identify instances of unauthorized access to the website's data sources. This is primarily done by blocking outside users or devices from initiating TCP/IP connections into the protected network through specific ports (known as “blocking incoming ports”).
  • firewalls cannot fully close all incoming ports into the website because certain ports must remain open for the web server to function.
  • a firewall only blocks the initialization of a TCP connection (at the beginning of the TCP conversation) by inspecting traffic that targets a specific port. After the initialization, the traffic has to pass through the firewall in both directions with randomly assigned ports, and the firewall has to allow it to happen. Therefore, unlike in the case of a proxy, a firewall is unable to isolate the network from unauthorized incoming traffic. Each call comes from a 'visitor' of the Internet, which could potentially be a hacker. Summary of the Invention The present invention arises from the realization of the inventors that unauthorized users can circumvent firewall protection of a website's data sources by downloading a software file onto the website web server which replaces or modifies the existing website responder unit. See Fig. 4.
  • Such replacement responder unit would be different from the original responder unit at least to the extent that it would allow the unauthorized user unlimited access to the website's data sources.
  • the responder unit of the website which controls access to the public and sensitive information and private source data contained in the website's data sources, might be replaced by a responder unit of the unauthorized user's own design, which design could permit unrestricted access by the unauthorized user to all of the sensitive information and private source data to which the website has access.
  • the present invention relates to a system and method which prevents this and other types of unauthorized access to sensitive information and private source data is used to serve websites which are accessible to the public.
  • the website web server located on a public network having a public IP address and known port number performs only the listening function.
  • the responding function is located on a separate device on a private network with a private and dynamic IP address and having a randomly assigned port number.
  • the responder has no listening sockets (open ports expecting to receive from client application) and therefore does not listen to the public network, and therefore is not accessible to unauthorized access, much in the way that a private user's PC is not accessible to unauthorized access.
  • the web server having the listening function does not initiate connection with the device having the responding function because its private IP address is unreachable from the public network and unknown, even to the web server, and by virtue of the fact that there are no listening sockets to accept any requests.
  • the communication link between the device having the responder function and the web server having the listening function is initiated by the device having the responder function.
  • the responder establishes a single encrypted connection to the web server ⁇ with a private and dynamic IP address and port number for responsive communications.
  • Figure 2 illustrates the communication between the browsers on a private user' s PC on a private network with web servers located on a public network.
  • Figure 3 is a schematic representation of a website on a prive network represented on a public network by a router or "reverse" proxy.
  • Figure 4 is a schematic representation of a web server in which an unauthorized user has placed a substitute responder, giving that user access to sensitive information and private source data on the database
  • Figure 5 is a schematic representation of the invention showing a server having only the listening function of a website located on a public network and a separate device having the responder function located on a private network with a dynamic IP address and port number with a single encrypted connection between the responder device and a listening server which is established by the responder device.
  • FIG. 6 A is a schematic representation of a preferred embodiment of the invention.
  • Figure 6B is a schematic representation of another embodiment of the invention.
  • Figure 6C is a schematic representation of another embodiment of the invention.
  • an IP device such as a server is located on a public network, with a public IP address and known port number.
  • This device contains a listening function for a website which receives, communications and inquiries for information from other devices located on the public network or on private networks in communication with the public network. This listening function also transmit responses to the requesting devices.
  • a second IP device is located on a private network and contains the responder function of a traditional website. This sevice has a dynamic private IP address.
  • the responder function is in communication with a data source, e.g., a database.
  • the data source may contain public and sensitive information and/or private source data necessary or useful in responding to inquiries received by the listening function.
  • the responder function initiates a single connection with the listening function, transmitting its dynamic IP address and randomly assigned port number for responsive communications.
  • This line of communication may be established in much the same way that a private PC on a private network opens a line of communication with a traditional website as described above in the background of the invention.
  • This single line of communication is preferably encrypted.
  • the listening function When the listening function receives a request for information from another device on the public network or on a private network in communication with the public network, the listening function "responds" to the opening communication established by the responder using the dynamic IP address and port number transmitted by the responder in the opening communication.
  • the responder function processes the request, optionally accessing information in the data source(s), and communicates their response to the listening function, which in turn publishes the information to the requesting device using the requesting device's IP address and port number.
  • the only connection between the device having the responder function and the public network is the single encrypted connection with the listening server, established by the responder device using its dynamic IP address and randomly assigned port number.
  • FIG. 6 A shows a more preferred embodiment of the invention in which the responder unit is connected to a private network and has a private IP address and a randomly assigned port number. It can access other devices on the private network, but cannot be addressed by devices outside the private network.
  • the listener unit is connected to a public network with a public IP address and known port number.
  • the responder unit initiates communication with the listener unit via an encrypted TCP/IP - connection. Accordingly, neither the responder unit, other applications residing on the same device, or other devices to which the responder unit has access are susceptible to unauthorized access, either via the listener or via the responder' s connection to its private network.
  • Figure 6B shows another embodiment of the invention in which the responder function is moved to another public address as opposed to a private network. In this embodiment, all the "incoming ports" are closed in the firewall to protect the responder from TCP IP level attacks, and the responder device communicates with the listener device via an encrypted TCP/IP connection. Therefore, the responder unit is not susceptible to unauthorized access via the listener unit. However, the responder device is still addressable over the internet.
  • Figure 6C shows yet another embodiment of the invention in which the connection from the responder unit is not addressable via any network, public or private, and in which its connection to the listening unit is non-IP based, for example, via IPX, ethernet (below IP level), serial communication, USB or Fireware. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un serveur web de site web situé sur un réseau public et possédant une adresse IP et un numéro de port connu, ainsi qu'une fonction d'écoute des demandes de réception d'informations d'autres dispositifs situés sur le réseau public ou sur des réseaux privés avec accès au réseau public. Une fonction de réponse est exécutée par un autre dispositif sur un réseau privé possédant une adresse IP privée dynamique et un numéro de port attribué de manière aléatoire.
PCT/SG2004/000228 2003-07-31 2004-07-30 Systeme et procede visant a augmenter la securite d'un reseau Ceased WO2005010644A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
SG200304007-8 2003-07-31
SG200304007 2003-07-31

Publications (2)

Publication Number Publication Date
WO2005010644A2 true WO2005010644A2 (fr) 2005-02-03
WO2005010644A3 WO2005010644A3 (fr) 2005-12-15

Family

ID=34102175

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SG2004/000228 Ceased WO2005010644A2 (fr) 2003-07-31 2004-07-30 Systeme et procede visant a augmenter la securite d'un reseau

Country Status (1)

Country Link
WO (1) WO2005010644A2 (fr)

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5550984A (en) * 1994-12-07 1996-08-27 Matsushita Electric Corporation Of America Security system for preventing unauthorized communications between networks by translating communications received in ip protocol to non-ip protocol to remove address and routing services information
WO2002030082A2 (fr) * 2000-10-04 2002-04-11 Preventon Technologies Limited Procede et systeme destines a maitriser l'acces a des serveurs par des clients sur un reseau a protocole internet

Also Published As

Publication number Publication date
WO2005010644A3 (fr) 2005-12-15

Similar Documents

Publication Publication Date Title
US11652792B2 (en) Endpoint security domain name server agent
US7454489B2 (en) System and method for accessing clusters of servers from the internet network
US6591306B1 (en) IP network access for portable devices
US7792995B2 (en) Accessing data processing systems behind a NAT enabled network
CA2383247C (fr) Acces externe a un dispositif protege sur un reseau prive
EP0825748B1 (fr) Procédé et appareil limitant l'accès à l'information privée dans les systèmes de noms de domaines par réorientation de demandes d'interrogations
US8375434B2 (en) System for protecting identity in a network environment
US6804783B1 (en) Firewall providing enhanced network security and user transparency
US20170034174A1 (en) Method for providing access to a web server
US7925693B2 (en) NAT access control with IPSec
MX2011003649A (es) Metodo y aparato de nat transversal.
EP4167524B1 (fr) Commande de connexion de dispositif de réseau local
US8190773B2 (en) System and method for accessing a web server on a device with a dynamic IP-address residing behind a firewall
US11736516B2 (en) SSL/TLS spoofing using tags
US7715326B2 (en) Webserver alternative for increased security
WO2005010644A2 (fr) Systeme et procede visant a augmenter la securite d'un reseau
JP3575369B2 (ja) アクセスルーティング方法及びアクセス提供システム
EP4572231A1 (fr) Cybersécurité basée sur un traitement de protocole de système de nom de domaine
CA2353180C (fr) Methode et appareil pour resoudre une adresse de site web lorsque la connexion est etablie avec un reseau prive virtuel (vpn)
KR20020036994A (ko) 사설망 내부에 위치하는 웹 서버로의 접근을 지원하는사설 웹호스팅 방법 및 서비스
KR20030089305A (ko) 임베디드 장치에 대한 아이피 주소 등록 및 참조 방법과그 시스템
JP2001251367A (ja) ネットワーク通信方法および装置

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase