SurfinCheck is comprised of two main components:
The SurfinCheck Server is the component that provides protection based on the corporate security policy. It should be installed on a gateway machine since it will serve as a proxy for the client browsers. After installation, all client browsers should be configured to use SurfinCheck Server as an HTTP Proxy.
Depending on your license, Several SurfinCheck Servers may be installed, all operating from a single Corporate Security Policy and each servicing a different set of users.
SurfinCheck Server has a minimal user interface that consists of a chronological list of errors registered in real time. To setup and configure SurfinCheck, or to access the complete log of security activities, use the SurfinConsole.
The SurfinConsole is your Security Management Console. It is preferable to install SurfinConsole on a separate machine (so as not to reduce performance due to SurfinCheck Server load). SurfinConsole is the User Interface component through which the Corporate Security Policy is set, users and groups are defined, and reports are generated.
Before installing SurfinCheck it is recommended that you plan your setup, as described in the previous chapter. This will ensure that you setup SurfinCheck so that it suites the specific needs of your organization.
In addition, make sure you:
The program will install all the necessary components for SurfinCheck Server.
Note: As part of installation, SurfinCheck Server is added to the Startup folder so that it is automatically invoked upon boot-up of the machine. It is important to keep this configuration so that in the event of a system failure on the gateway machine, SurfinCheck will automatically be brought up as the operating system recovers.
Next, you will install the SurfinConsole, as described below.
To register SurfinCheck:
In order to implement a security policy for your organization, you must define all users that will be protected by SurfinCheck Server.
If you need to set up specific security policies for different departments or groups of users within your organization, you should first define those groups. If you do not need any group-specific policies, skip the next section and go to Defining Users.
Note: You can add multiple users using an IP range. This allows you to add many users at once (instead of one by one) by specifying a range of IP addresses. All IP addresses within that range will then be subject to the security policy you define. Creating an IP range also enables you to handle dynamic allocation of IP addresses-since every IP allocated within the range will be subject to the same policy.
See Chapter 4, Defining the Security Policy, for detailed information on defining a security policy settings for specific groups.
Defining a group enables you to set a specific security policy for a group of users. Once you define the group, you should add individual users beneath that group.
Note that you can also define multiple users using an IP range. See the next section for details.
To define a Group:
Note: You can create multiple levels of groups and subgroups, as in the example above.
All Users have to be deleted before you delete their group name.
In order to implement a security policy for your organization, you must define all users that will be protected by SurfinCheck Server. This is done through the SurfinConsole.
Note: If you need to define a specific security policy for different departments or groups of users within your organization, you should first define groups (see previous section) and only then add users within the groups.
To define users:
You can add multiple users using an IP Range. This can help you also to handle a dynamic allocation of IP addresses.
Note, however, that any user having an IP address within the specified range will be subject to the same security policy. A user that is within the IP range cannot be added again to a different group.
To add users using an IP range:
Once you complete installation of SurfinCheck and have defined users and groups, you should configure all browsers on end-user machines to use SurfinCheck as a proxy server for HTTP requests.
For any other Java-enabled browser, configure the browser to use the SurfinCheck server as the proxy server, clear the cache of the browser, and restart it.
At this point your setup is complete, and it is recommended that you now test your security policy for two types of applets-one that should be allowed into the network and one that should be blocked.
Open a client browser and access the installation test page: http://www.finjan.com/SurfinGateTest/
From the SurfinGate Test page, select the link of the Allowed Applet. This page contains a 'benevolent' applet that does not access the file system, the network, nor does it load any executable. By default, this applet should be allowed into the system.
If your setup is correct and you did not modify SurfinCheck's default settings, then when you access this page, the applet should be displayed in the browser without any messages.
Proceed to Step 2 by pressing the link of the Blocked
Applet. This page contains an e-mail applet that attempts to send
e-mail from the user's desktop. SurfinCheck's default policy specifies
that this type of applet should be blocked.
If your setup is correct, then SurfinCheck should block the e-mail applet, and you should see a message notifying you about the blocked applet.
You can also invoke the SurfinConsole and view its
log (click the Log icon) to examine the applet events that took
place.