SecureSphere’s Modes Of Operation – Part I
In the next few days I will post a series of articles explaining SecureSphere’s different modes of operations and how it is integrated with transparent inspection technology, making it possible for SecureSphere to be deployed in minutes with no changes to the web or database server or any other aspect of the data center infrastructure. Follow the link to read more on how transparent inspection delivers multi-gigabit performance, sub-millisecond latency, and options for high availability that meet the requirements of even the most demanding application and database environments
SecureSphere can be installed in a variety of environments supporting different network environments and business requirements. In addition to the network topology used, SecureSphere policies can be deployed in different operational modes that affect the overall behavior of the installed system. This document describes SecureSphere’s different modes of operation and how they are related to Dynamic Profiling. Additional, more in-depth information is available in the SecureSphere User Guide.
Operation mode defines the behavior of SecureSphere regarding monitored traffic. There are three operation modes: active, simulation and disabled.
After the gateway appliance has been installed in the network using a certain deployment method (e.g. bridge, reverse proxy, kernel reverse proxy etc.), the administrator can define an operation mode for each and every Server Group. In other words, each Server Group can be defined with a different operation mode.