xyberShield Integrates Easily
As a SaaS solution, xyberShield fits seamlessly with your existing architecture:
- Works with your website wherever it is hosted
- Does not affect the operation or performance of applications on your website, or of Google Analytics or other third-party tools
- Works with applications of any kind, as long as they’re delivered via HTTP protocol
- Does not interfere with any indexing services
- Is not dependent on the type of web server - xyberShield works with many web servers including Apache, IIS, Sun, nginx, Google and jigsaw
xyberShield Script Installed on each Web Server
Every organization will have a network firewall to restrict outside access to their internal network. However, the network firewall allows traffic through Port 80 (http:) or Port 443 (https:), usually with minimal or no inspection at the application layer. In a basic implementation, the xyberShield script is installed behind the network firewall and load balancers on the logical layer of the web server. For a load-balanced environment, the xyberShield script needs to be installed on every web server behind the load balancer.
The xyberShield script is installed at the top level of the domain for each application on a web server. The script works at the session level, monitoring each session, regardless of which web server handles the request or the number of web servers running your site. Because xyberShield examines website traffic only after the SSL module has decrypted it, you don’t need to change your existing SSL certificate or even provide it to xyberShield.
The script continually monitors web traffic between the web server and any active client browser sessions. It is in constant communication with xyberShield’s Global Security Platform, where all threat analysis is performed. The xyberShield script sends session information to the nearest data center for analysis, which scores a session’s threat potential in real time.