Home  Administration > Data Collector Administration > SiteScope Administration > Running SiteScope Securely > Hardening the SiteScope Platform



Hardening the SiteScope Platform

Network and system security has become increasingly important. As a system availability monitoring tool, SiteScope will necessarily have access to some system information which could be used to compromise system security if steps are not taken to secure it. This section describes several configuration and set up options that can be used to harden the SiteScope platform.

Important: In SiteScope version 8.0 and later, there are two Web servers that are active and serving two versions of the SiteScope product interface. In order to limit all access to SiteScope you must apply the applicable settings to both the SiteScope Classic Web server and the Apache Tomcat server supplied with SiteScope 8.0 and later.

Setting SiteScope User Preferences

SiteScope user profiles are used to require a username and password in order to access the SiteScope interface. After installation, SiteScope will normally be accessible to any user who has HTTP access to the server where SiteScope is running.

By default, SiteScope is installed with only one user account and this account does not have a default username or password defined for it. This is the administrator account. You should define a username and password for this account after installing and accessing the product. You can also create other user account profiles to control how other users may access the product and what actions they may perform. See the section "User Preferences" in SiteScope Help for more information on creating user accounts.

Restricting Access to SiteScope by IP Address

You can restrict access to SiteScope based on the IP address of the client requesting access to the application. This is a form of access control list. As noted, SiteScope 8.0 includes two product interfaces and two Web servers. The changes need to be applied to both interfaces in order to be effective.

To restrict access to the SiteScope Classic Web server, you enter the allowed IP addresses using the General Preferences settings. You must use the SiteScope Classic interface to enter these settings. This access control can be further enhanced by requiring that a username and password be used as well. See the online help for the General Preferences page in the SiteScope Classic interface for more information.

To restrict access to the SiteScope 8.0 interface using an IP access control list, you must edit the configuration file for the Tomcat server included with SiteScope. You can enable access control lists by adding a Valve component to the applicable section of the Tomcat server configuration file. See the Apache Jakarta Web site for documentation on Tomcat configuration. For example, see http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/valve.html.

Using Secure Socket Layer (SSL) to Access SiteScope

SiteScope can be configured to use SSL to control access to the product interface. Enabling this option will require that users are authenticated using a certificate. See Configuring SiteScope to Use SSL for more information.




Copyright 2006 Mercury Interactive Corporation