How is the G-Server itself secured?
As a dedicated black box appliance that sits in the DMZ, G-Server implements a proprietary network transparency model: that is, it has no IP Address of its own. This makes it virtually impossible for hackers to detect the presence of the G-Server and thus initiate any direct attack.

How complex is the deployment process?
It is extremely simple and straightforward to install since the IP addresses that the Web servers maintain never need to be changed during deployment or later during ongoing maintenance operations. As a stealth appliance that sits on the rack—not on the Web server—there is no need for network configuration. This allows for a rapid and painless installation, with zero impact on organizational workflow.

Won’t the G-Server impact Web site performance?
The G-Server has virtually no impact on Web site performance. It is capable of supporting a wide range of Internet carriers—including T1-T3, E1-E3—without performance degradation. In fact, based on standard performance benchmarks, the G-Server latency performance ranked at the top as a leading-edge gateway product engineered for performance.

Won’t the digital signing process add to my workload and require more time to administer?
No. The G-Server’s signing process can be made completely automatic and transparent. By using the G-Server’s API, you can customize and seamlessly integrate the signing process to fit your existing content authoring workflow. Alternatively, administrators can choose to adopt the G-Server Signing GUI, which provides authorized signers with an easy-to-use, flexible signing wizard to meet their every day signing requirements.

Does the G-Server support SSL sites?
Yes. Two optional configurations are available for SSL implementation:

1. SSL termination: The SSL session is terminated on the G-Server and transferred to the Web server in clear HTTP. This configuration offloads the SSL effort from the Web server in order to improve overall performance.
2. Complete SSL: This configuration maintains SSL session encryption all the way to the Web server.

Does the G-Server support a high availability configuration?
Yes. The G-Server can be easily configured with a "hot-swap" standby G-Server that takes over immediately in the event the primary box fails. Other high availability solutions are also possible via simple integration to existing high availability network environments.

What makes the G-Server different from other security solutions?
The G-Server provides guaranteed protection regardless of the attack method or data layer, providing the last line of defense that closes all Web site security gaps. No other security solution today can sit transparently on the network and ensure that Web sites always serve genuine information, all while maintaining Web site performance.

How is the G-Server different from:

A network firewall?
While network firewalls are a necessary element in a Web site’s security architecture, they leave open the two main ports (80 and 443) that service HTTP and HTTPS traffic. Consequently, they offer little value in securing the integrity of the Web site applications and content. Not only does the G-Server protect your Web server from publishing unauthorized, altered or fraudulent information, it serves as a multi-function Port 80 and Port 443 protection appliance that quickly and efficiently authenticates incoming HTTP and HTTPS requests.

Intrusion Detection Systems (IDS)?
IDS attempt to detect malicious network activity usually through sniffing the network traffic and comparing each packet with a database of known attack signatures. However, it is usually weeks, if not months, before administrators can acquire and apply patches to known vulnerabilities. This leaves a huge window of opportunity open for hackers to take advantage before the patch can be applied. By contrast, the G-Server is an active corrective mechanism as well as a monitoring tool that delivers protection regardless of the attack method. All verification, recovery and blocking of damaged or unauthorized content is done proactively, in real-time and on-the-fly.

Application firewalls?
Application firewalls address browser and HTTP attacks that manipulate application behavior for malicious purposes. While application firewalls are designed to protect applications from possible hacking attempts on the application layer only, the G-Server delivers its static and dynamic content protection regardless of the data layer. In addition, application firewalls have no ability to protect static content and do not prevent altered content from being displayed. Further, unlike the G-Server, application firewalls need to be carefully programmed—and constantly reconfigured—to specify application procedures whenever a new page is loaded on the Web server.

GAP firewalls?
The concept of GAP technology is to create some type of physical separation between two networks. It consists of a switch that allows a computer or a resource to connect to either one network or another but not to both at the same time. The GAP appliance terminates all TCP/IP connections using a physical air gap. It can prevent some application-level attacks because only scanned data with known commands are passed to the internal system. While the technology is complementary to that of the G-Server, GAP firewalls have no ability to protect static or dynamic content and do not prevent altered content from being displayed.

Anti-virus and malware?
Protection from computer viruses and other forms of “malware” such as worm or Trojan horse attacks is important but has limitations. Most anti-virus solutions rely on signature-based technologies that must be updated constantly. These solutions, similar to IDS, are also unable to block many stylized attacks that are the most common attacks mounted against Web servers. The G-Server delivers its protection regardless of the attack method and does not rely on patch updates.

Access control?
Granting and preventing Web server access to users is an important function. However, unlike the G-Server, this process offers little or no protection against attacks that come in via HTTP and HTTPS traffic over the always-open ports 80 and 443.

Return to Top