Setting Up Spyware Control For The Whole Domain - F-SECURE CLIENT SECURITY 8.00 Administrator's Manual

Hide thumbs Also See for CLIENT SECURITY 8.00:
Table of Contents

Advertisement

5.8.2

Setting up Spyware Control for the Whole Domain

The Spyware Reported by Hosts will be cleaned if you run a manual
spyware scan on the hosts, as well as when quarantined spyware is
removed periodically on the hosts.
Default Spyware Handling
If the Change spyware control to automatically quarantine all new
spyware setting is selected, all new spyware that is not explicitly allowed
by the administrator is quarantined automatically. This applies to both
real-time and manual spyware scanning. This changes the following
settings:
In the Spyware Scanning on File Access section the Action on
spyware setting is set to Remove automatically and quarantine.
In the Manual Spyware Scanning section the Action on spyware
setting is changed to Remove automatically and quarantine.
On Spyware Control page the Deny access to spyware setting is
enabled.
Click the
Change spyware scanning to automatically
quarantine all new spyware
preventing spyware from running does not interfere with ordinary,
legitimate applications in your company.
This example explains how to set up spyware control in such a way that it
is transparent to the end-users and that it protects them against spyware
and tracking cookies.
When you are setting up spyware control for the first time, you should first
use a small test environment that consists of hosts that have the
applications normally used in your company installed on them. At this
phase you can also allow certain applications, if that is necessary. After
the testing phase you can distribute the policy to the whole managed
domain.
CHAPTER 5
link when you are sure that
183

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the CLIENT SECURITY 8.00 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

This manual is also suitable for:

Client security

Table of Contents