F-Secure Internet Security - Wersja do druku

Kod:
1. General



This document contains information about F-Secure Client Security 9.30 Beta. We strongly recommend that you read the entire document. Please refer to the online help for more information.

2. Product contents



This product enables you to install the following features:



Virus & Spyware Protection – protects your computer against viruses, trojans, spyware, rootkits and other malware

Internet Shield – consists of Firewall, Application Control, Intrusion Prevention (IPS) and Dial-up Control

E-Mail Scanning – protects you against malware spread via e-mail by detecting malicious content in e-mail traffic (IMAP4, POP3 and SMTP protocols)

Web Traffic Scanning – additional protection against malware by detecting and blocking malicious content in web traffic (HTTP protocol)

DeepGuard™ – proactive 0-hour protection technology that detects unknown threats by monitoring program behavior in real-time and stopping dangerous activities.

Browsing Protection – additional protection against web browser exploits and rogue sites

Device Control – provides the ability to control and disable hardware devices

Microsoft NAP Plug-in – enables integration with Microsoft Network Access Protection (NAP)

Cisco NAC Plug-in – enables integration with Cisco Network Admission Control.



The supported languages are: English, Czech, Danish, Dutch, Finnish, French, German, Greek, Hungarian, Italian, Japanese, Norwegian, Polish, Portuguese, Brazilian Portuguese, Slovenian, Spanish, Swedish and Turkish, Chinese (P.R.C, Taiwan, Hong Kong), Estonian, Canadian French, Latin American Spanish, Romanian, Russian.

3. Installation and system requirements



Before you install the product, we recommend that you review the sections in this topic to ensure that your network, hardware, software, and other system components meet the requirements for F-Secure Client Security 9.30 Beta.

3.1Installation keycode



This Beta build comes with the evaluation key that allows you to install and use all features of the product for 180 days. If you have a valid F-Secure license certificate and installation keycode for the previous version of F-Secure Client Security, you can enter it during local or remote installation.



Note: If you install the product with the evaluation key on top of a previous version that was installed with the full license key, the installation will fail.





3.2Stand-alone or centrally managed installations



If you plan to install the product as a standalone installation, then you should run the setup program (fscs-9.30-345-beta.exe) on your computers locally. Note that installation requires that you have local administrator rights.



Note: In this Beta, the new Device Control feature can be managed only from Policy Manager Console.



For centrally managed installations, you should import the installation JAR package (fscs-9.30-345-beta.jar) to Policy Manager Console and deploy the product remotely to selected hosts. With Policy Manager Console you can also export an MSI package that you can deploy via other central management systems.

3.3Supported platforms



This release can be installed and used on the following platforms:



· Microsoft Windows XP with SP3 (32-bit editions only)



· Microsoft Windows Vista (all 32-bit and 64-bit editions)



· Microsoft Windows Vista with SP1 or newer (all 32-bit and 64-bit editions)



· Microsoft Windows 7 (all 32-bit and 64-bit editions)



· Microsoft Windows 7 with SP1 or newer (all 32-bit and 64-bit editions)

3.4Recommended hardware requirements

Microsoft Windows 7 and Vista



· Processor: Intel Pentium 4 2GHz or higher



· Memory: 1GB or more



· Disk space: at least 1 GB (800 MB for Anti-virus for Workstations)



· Internet connection: an Internet connection is required in order to receive updates

Microsoft Windows XP SP3



· Processor: Intel Pentium III 1Gz or higher



· Memory: 512 MB or more



· Disk space: at least 1 GB (800 MB for Anti-virus for Workstations)



· Internet connection: an Internet connection is required in order to receive updates

3.5Centralized management requirements



The product can be deployed and managed with F-Secure Policy Manager 9.00 or newer. F-Secure Policy Manager 10.00 is recommended.

3.6Upgrading from previous versions



This Beta build supports upgrading from all previous Client Security 9.x versions.

4. What’s new



This section describes the new features, enhancements, and most important problems fixed in F-Secure Client Security 9.30 Beta.

4.1New features and enhancements



· Device Control – this feature provides the ability to disable and enable hardware devices on client computers (a single device or a class/subclass of devices) from Policy Manager Console.

4.2Fixed issues



The following issues have been fixed in this Beta build since the previous (9.20) release:



· The “Configure communication with Policy Manager Server” page in Policy Manager Console installation wizard is not localized.



· Copyright year in Manual Scan reports is not actual.



· F-Secure Client Security Microsoft NAP plug-in remains on the client host after uninstalling Client Security through Policy Manager Console.



· Mistakes in Japanese localization (CTS-82850).



· The Microsoft NAP plug-in requirement “Maximum number of days since the last connection to Policy Manager Server” is not working in F-Secure Client Security (CTS-82866).



· "AusweisApp" (a tool for online identification of German passports) is blocked when an F-Secure product is installed (CTS-81395).



· Size of the FSMA working set increases constantly (CTS-78978).

5. Known issues

5.1Installation, upgrade and uninstallation

“Force restart without asking the user to save open documents” checkbox in “Select restart options” window of Installation Wizard in Policy Manager Consol doesn’t work as expected on Vista and Windows 7 (CTS 81750)



Even if the checkbox is not checked, the system will restart irrespective of open, unsaved documents. User changes in such documents can be lost. To avoid this data loss, you can select the “Ask the user before restarting”.

Policies are not received immediately after reboot



In some cases, the installed client may not receive policies immediately after the reboot. The client will usually recover automatically after some time, and receive the new policy. If not, a reboot should help.

Unused databases are still visible after upgrade



When upgrading, some databases and engines used by the previous version might not be needed anymore. These are still visible in “Settings – Other settings – Downloads”, marked as “Not Installed”. This is normal, and after 7 days they will be automatically removed.

System might be slow for several minutes after the first reboot while the installation finishes



The system may start up slowly following the initial reboot after installation. This is because the installation is being finalized in the background by downloading and installing various updates, etc.



The effect is more visible after a fresh installation, where more updates need to be downloaded. If opened, the local UI will notify you of this with a blue status indicator and a “Completing Installation” status text.



Subsequent reboots are not affected.

NAP Health Validator is not removed from configured health policies during uninstallation



During uninstallation, references to F-Secure System Health Validator (SHV) are not automatically removed from health policies. Computers that have those policies in use are considered non-compliant with health policies and are quarantined. To correct broken references to F-Secure SHV, open the health policies properties from Network Policy Server console (nps.msc) and confirm the automatic update.

5.2DeepGuard

DeepGuard does not protect services in Windows 7 (CTS-65247)



When stopping a protected service from the command line or from the Services applet, DeepGuard fails to prompt about it. However, it still protects services from most malicious stop attempts. This problem only exists in the 32-bit version of Windows 7.

5.3Browsing Protection

Disabling Browser Protection requires closing open browsers to take effect



If there are open browsers and the Browsing Protection feature is disabled, the change will only affect the open browser once it has been closed and restarted.

Browsing Protection toolbar may be not be visible in Internet Explorer 7



When launching Internet Explorer 7 after a fresh installation, the Browsing Protection toolbar may not be visible on some computers. Even without the toolbar, Browsing Protection is still working. Closing and restarting Internet Explorer 7 will resolve this issue.

5.4Anti-Virus

Incorrect engine versions are shown in policy statistics



Incorrect engine versions are shown in the Status tab of Policy Manager Console (F-Secure Anti-Virus > Plug-ins table) after a clean installation. This affects scanning reports. The problem can be fixed by restarting the FSGKHS service.

5.5Dial-up control

“Disallow user changes” doesn’t work for the dial-up control table



It’s possible to modify the dial-up control table from Client Security’s local GUI even when it has the “disallow user changes” restriction set from Policy Manager.