Abstract:
An integrated series of security protocols is disclosed that protect remote user communications (22) with remote enterprise services, and simultaneously protect the enterprises services from third parties. In the first layer, an implementation of the Secure Sockets Layer (SSL) version of a HTTPS provides communications security, including authentication of the enterprise web server and the security of the transmitted data. The protocols provide for an identification of the user, and an authentication of the user to ensure the user is who he/she claims to be and a determination of entitlements that the user may avail themselves of within the enterprise system. Session security is described, particularly as to the differences between a remote user's copper wire connection to a legacy system and a user's remote connection to the enterprise system over a "stateless" public Internet (15), where each session is a single transmission, rather than an interval of time between logon and logoff, as is customary in legacy systems. Security for the enterprise network and security for the data maintained by the various enterprise applications is also described.
Abstract:
A double firewalled system is disclosed for protecting remote enterprise servers (24) that provide communication services to telecommunication network customers (10) from unauthorized third parties. A first router (29a) directs all connection requests to one or more secure web servers (24), which may utilize a load balancer (45) to efficiently distribute the session connection load among a high number of authorized client users (10). On the network side of the web servers (24), a second router (29b) directs all connection requests to a dispatcher server (26), which routes application server calls to a proxy server for the application requested. A plurality of data security protocols are also employed. The protocols provide for an identification of the user (10) to ensure the user (10) is who he/she claims to be and a determination of entitlements that the user (10) may avail themselves of within the enterprise system. Session security is described, particularly as to the differences between a remote user's copper wire connection to a legacy system and a user's remote connection to the enterprise system over a "stateless" public Internet, where each session is a single transmission, rather than an interval of time between logon and logoff, as is customary in legacy systems.