OfficeScan Client / Server Edition 10.

5 Best Practice Guide

Alp Deveci Jill Chua-Maceda Jessie Prevost Alwin Yu US Core Team

Table of contents
1. Product Description .......................................................................... 3 2. Architecture ....................................................................................... 4 2.1. Installation ........................................................................................ 4 2.1.1. Recommended Hardware ..................................................... 4 2.1.2. Software Requirements ......................................................... 6 2.2. Operating System and Related Applications.................................... 8 2.2.1. Security Tuning .................................................................... 10 3. Sizing Summary .............................................................................. 11 3.1. Smart Protection Server Layout (Standalone) ............................... 13 3.1.1. Load Balancing .................................................................... 14 3.1.2. Deployment Recommendations .......................................... 14 3.2. Integrated Smart Protection Server Best Practices ....................... 16 3.3. Configuration .................................................................................. 17 3.3.1. Management Console ......................................................... 20 3.3.2. INI Configuration Files ......................................................... 38 3.4. Performance Tuning ....................................................................... 39 4. Backup and Disaster Recovery...................................................... 40 4.1. Officescan Server Database Files .................................................. 40 4.2. Officescan Server Configuration Files ............................................ 40 4.3. Officescan Client Configuration Settings ........................................ 41 5. Behavior Monitoring ....................................................................... 42 5.1. Behavior Monitoring Overview ....................................................... 42 5.1.1. Malware Behavior Blocking ................................................. 42 5.1.2. Event Monitoring .................................................................. 43 5.1.3. Enabling Behavior Monitoring ............................................. 46 5.2. Device Control Overview ................................................................ 46 5.2.1. Using Device Control ........................................................... 46 5.2.2. How Behavior Monitoring and Device Control Can Affect Performance 48 5.2.3. Deploying Behavior Monitoring and Device Control ............ 48 5.3 Alternative Ways to Prevent Performance Impact .......................... 50 5.3.1 Disabling Features from the Web Console........................... 51 5.3.2 Stopping the Service ............................................................ 51 6. Miscellaneous .................................................................................. 51 6.1 Product Communication Ports......................................................... 51 6.3 Update Architecture and Network Usage ........................................ 52 6.3.1 The Update Process ............................................................. 52 6.2.2 Network Usage (Bandwidth Consumption) .......................... 54 6.4 Virtual Desktop Infrastructure (VDI) ................................................ 55 6.4.1 Golden Image Preparation ................................................... 56 6.4.2 Install the VDI Support in OfficeScan server Plugin Manager56 6.5 Recommended Installation Adjustments for Special Environments 58 6.5.1 Migration of Unsupported Platforms ..................................... 58 6.5.2 Citrix Environment ................................................................ 59 6.5.2.1 Installation of Officescan Clients on Citrix Servers ........... 59 6.5.2.2 Citrix Known Issues ........................................................... 60 6.5.2.3 Citrix Exclusions ................................................................ 61 6.5.2.4 Citrix Firewall Port ............................................................. 62 6.5.3 Installation of OfficeScan Clients on Cisco Callmanager ..... 62 6.6 Recommended Scan-Exclusion List ............................................... 63 2

6.7

Some Common Server Ports .......................................................... 67

1. Product Description
There are four major components in an OfficeScan environment that need to be identified when architecting the deployment. Each component is briefly described below. A. OfficeScan Server Provides the OfficeScan management console and stores information in a local CodeBase database. Standard http / https protocols are used for communication and to provide updates to managed clients. The three basic functions of an OfficeScan server are: a. Client configuration (Privileges and Policy settings) b. Provides program, scan engine, and virus pattern file updates c. Reporting, centralized logging and quarantine B. OfficeScan Client A host reporting to a particular OfficeScan server. An OfficeScan client can be configured to get update information from an OfficeScan server, an Update Agent, or directly from the internet (Trend Micro ActiveUpdate server). An OfficeScan client can also be configured to use Integrated Smart Protection Server or Stand Alone Smart Scan instead of conventional scan. This method minimizes the amount of pattern download by relying on cloud technology. C. Update Agent A regular OfficeScan client that is designated to replicate update information from an OfficeScan server for the purposes of distributing the update information to other OfficeScan clients. Any client can be configured as an Update Agent via the OfficeScan server management console. OfficeScan client IP address ranges are then assigned to get update information from specific update agents. Update agents can push component updates, setting updates, and program/hotfix updates to clients. Older version OfficeScan clients can receive program upgrades from OfficeScan 10.5 Update Agents as long as they report to the OfficeScan 10.5 Update Agents. D. Smart Protection Server The Smart Protection Server provides the file reputation and web reputation through a local cloud service by scanning files and sending URLs to a local web rating server when using web reputation protection when users opt to employ Smart Scan technology. There are two types of Smart Protection Server: a. Integrated Smart Protection Server Installed as part of the OfficeScan server. Integrated Smart Protection Server is managed through OfficeScan management console. b. Stand Alone Smart Protection Server Installed on a VMware or Hyper-V host.

2.

Architecture

2.1. Installation
2.1.1. Recommended Hardware
Following sections show the recommended software and hardware specifications for an OfficeScan environment. For the full list of minimum system requirements, please refer to the Installation and Deployment Guide or OfficeScan Readme.

A. OfficeScan Server The recommended hardware specification for an OfficeScan server managing 5000 client workstations is: Server with at least 2GHz dual processor with 2GB of RAM: 3,000 to 5,000 clients Server with at least 3GHz dual processor with 4GB of RAM: 5,000 to 8,000 clients Note: Integrated Smart Protection Server not recommended for more than 3000 Smart Scan Clients. Stand Alone Smart Protection Server is recommended for more than 3000 clients. B. Update Agent The OfficeScan client with the best available resources at a particular site should be designated as an Update Agent. Since this client will be the one serving updates to the other clients in the remote office, this client must be reliable. This can be a domain controller on the site, a file server, print server or any type of server that is online all the time. This client should have an additional 700 MB of free disk space to store the engines and patterns, an additional 160 MB for programs/hot fix update and you also need an additional 20KB for every domain setting updates. Minimum requirements for Update Agents should follow the minimum hardware requirements of OfficeScan Clients.

C. OfficeScan Clients The minimum/recommended hardware specifications for the OfficeScan client are: Windows XP/2003 300MHz Intel Pentium processor or equivalent 256MB of RAM (512MB recommended) 350MB of available disk space

Windows XP/2003 64-bit Intel x64 processor, AMD x64 processor 256MB of RAM (512MB recommended) 350MB of available disk space

Windows Vista 1GHz Intel Pentium processor or equivalent 1GB of RAM (1.5GB of RAM recommended) 350MB of available disk space

Windows Vista 64-bit 4

Intel x64 processor, AMD x64 processor 1GHz Intel Pentium processor or equivalent 1GB of RAM (1.5GB of RAM recommended) 350MB of available disk space

Windows 7 32 bit 1GHz Intel Pentium processor or equivalent (2GHz recommended) 1GB of RAM (2GB of RAM recommended) 350MB of available disk space

Windows 7 64 bit Intel x64 processor, AMD x64 processor Minimum 2GHz Intel Pentium processor or equivalent 1.5GB of RAM 350MB of available disk space

Windows 2008 1GHz Intel Pentium processor or equivalent (2GHz recommended) 512MB of RAM (2GB of RAM recommended) 350MB of available disk space

Windows 2008 64-bit Intel x64 processor, AMD x64 processor 1.4GHz Intel Pentium processor or equivalent (2GHz recommended) 512MB of RAM (2GB of RAM recommended) 350MB of available disk space

Windows 2008 R2 64-bit 1.4GHz Intel Pentium processor or equivalent (2GHz recommended) 512MB of RAM (2GB of RAM recommended) 350MB of available disk space

D. Integrated Smart Protection Server The minimum hardware specifications for Integrated Smart Protection Server are: Minimum 1.86 GHz Intel Core2Duo 1GB of RAM (2GB recommended) 3.2GB of available disk space

E. Smart Protection Server (Standalone) The minimum hardware specifications for Standalone Smart Protection Server are: Dual 2.0 GHz Intel Core2Duo 64-bit processor supporting Intel Virtualization Technology or equivalent 1GB of RAM 5

20GB recommended for virtualization requirements if fewer than 1,000 endpoints. Add 15GB for every 1,000 endpoints

NOTE: Trend Micro Smart Protection Server automatically partitions the detected disk space as required

2.1.2. Software Requirements

A. OfficeScan Server Microsoft Windows Server 2003 (Standard, Enterprise, and Datacenter Editions) with Service Pack 2 or later, 32-bit/64-bit versions Microsoft Windows Server 2003 R2 (Standard, Enterprise, and Datacenter Editions) with Service Pack 2 or later, 32-bit/64-bit versions Microsoft Windows Storage Server 2003 (Basic, Standard, Enterprise, and Workgroup Editions) with Service Pack 2, 32-bit and 64-bit versions Microsoft Windows Storage Server 2003 R2 (Basic, Standard, Enterprise, and Workgroup Editions) with Service Pack 2, 32-bit and 64-bit versions Microsoft Windows Cluster Server 2003 Microsoft Windows Server 2008 (Standard, Enterprise, Datacenter and Web Editions) with Service Pack 1 or 2, 32-bit and 64-bit versions Windows Server 2008 R2 (Standard, Enterprise, Datacenter and Web Editions), 64-bit version Windows Storage Server 2008 (Basic Edition), 32-bit and 64-bit versions Windows Storage Server 2008 (Standard, Enterprise, and Workgroup Editions), 64-bit version Microsoft Windows HPC Server 2008

Note: OfficeScan cannot be installed if Microsoft Windows 2008 runs on the Server Core environment. OfficeScan supports server installation on guest Windows 2003/2008 operating systems hosted on the following virtualization applications: Microsoft Virtual Server 2005 R2 with Service Pack 1 VMware ESX/ESXi Server 4 (Server Edition) VMware Server 2 (Server Edition) VMware Workstation and Workstation ACE Edition 7.0 VMware vCenter4 Citrix XenServer 5.5 Microsoft Windows Server 2008 64-bit Hyper-V Microsoft Windows Server 2008 R2 64-bit Hyper-V Microsoft Hyper-V Server 2008 R2 64-bit

B. OfficeScan Clients Microsoft Windows XP Professional with Service Pack 2 or later, 32-bit/64-bit versions Microsoft Windows XP Home with Service Pack 2 or later, 32-bit version Microsoft Windows Server 2003 (Standard, Enterprise, Datacenter, and Web Editions) with Service Pack 2 or later, 32-bit/64-bit version 6

Microsoft Windows Server 2003 R2 (Standard, Enterprise, Datacenter) with Service Pack 2 or later, 32-bit/64-bit versions Microsoft Windows Storage Server 2003, 32-bit/64-bit versions Microsoft Windows Storage Server 2003 R2, 32-bit/64-bit versions Microsoft Windows Server 2008 (Standard, Enterprise, Datacenter, and Web Editions) with Service Pack 1 or 2, 32-bit/64-bit versions Windows Storage Server 2008 (Basic Edition), 32-bit and 64-bit versions Windows Storage Server 2008 (Standard, Enterprise, and Workgroup Editions), 64-bit version Microsoft Windows Server 2008 R2 (Standard, Enterprise, Datacenter, and Web Editions) 64-bit version Microsoft Windows HPC Server 2008 Windows Vista (Business, Enterprise, Ultimate, Home Premium, Home Basic) with Service Pack 1 or 2 Microsoft Windows 7 (Home Basic, Home Premium, Ultimate, Professional, Enterprise), 32bit/64-bit versions

Note: OfficeScan cannot be installed if Windows 2008 runs on the Server Core environment OfficeScan supports client installation on guest operating systems hosted on the following virtualization applications: Microsoft Virtual Server 2005 R2 with Service Pack 1 VMware ESX/ESXi Server 4 (Server Edition) VMware Server 2 (Server Edition) VMware Workstation and Workstation ACE Edition 7.0 VMware vCenter 4 Citrix XenServer 5.5 Microsoft Windows Server 2008 64-bit Hyper-V Microsoft Windows Server 2008 R2 64-bit Hyper-V Microsoft Hyper-V Server 2008 R2 64-bit

The administrator will not be able to remotely install OfficeScan client to Windows 7 x86 platforms without enabling the default administrator account. To resolve this issue: Enable the Remote Registry service on the Windows 7 machine. By default, Windows 7 machines disable this feature. Option A: Use the domain administrator account to remotely install OfficeScan 10.5 Service Pack 1 clients to Windows 7 computers. Option B: Use the default administrator account: 1. Type the "net user administrator /active: yes" command from the command console to enable the default administrator account. 2. Use the default administrator account to remotely install the OfficeScan client to the Windows 7 machine C. Smart Protection Server (Standalone) 7

Smart Protection Server has the following VMware Support requirements: VMware ESX 3.0, 3.5 or 4.0 VMware ESXi 3.5 Update 2 or 4.0 VMware Server 2.0 Windows 2008 R2 Hyper-V

NOTE: A purpose-built, hardened, and performance-tuned 64-bit Linux operating system is included with Trend Micro Smart Protection Server The following requirements are recommended for Trend Micro Smart Protection Server as a Virtual Machine under Windows 2008 R2 Hyper-V, VMware Server 2.0, VMware ESX 3.0, 3.5, 4.0 or VMWare ESXi 3.5 Update 2, 4.0 Create a new Virtual Machine with Red Hat Enterprise Linux 5 64-bit (Red Hat Enterprise Linux 4 64-bit for VMware ESX 3.0) Allocate this Virtual Machine with at least 1GB RAM and Dual 2.0 GHz CPU resources. Create a new Virtual Disk image which will be sufficient for your logging requirements. Allocate 1 physical network card for the virtual switch where Trend Micro Smart Protection Server is connected.

Account Ports

Administrator or Domain Admin account to log-in to target hosts for installation. NetBIOS (445, 137,138,139) for NT Remote Install OfficeScan client port (defined during OfficeScan server installation and is saved under Ofcscan.ini Client_LocalServer_Port parameter). OfficeScan virtual directory port as defined in Apache / IIS. This value needs to be consistent with what is defined in the OfficeScan management console [ Administration | Connection Settings | port number ].

Bandwidth Others

Approximately 50 MB (may vary depending on current virus pattern file size) Remote Registry service is enabled on target host. System partition of the target host is administratively shared (C$). Windows XP Simple File Sharing must be disabled on the client machines. SFS is a Microsoft feature that forces all network connections to login as Guest even if alternate credentials are provided. When SFS is enabled, OSCE can't login to the machine using the credentials specified, so the installation fails. SFS can be disabled via GPO or a registry hack. It can be disabled in the target machines individually under [ My Computer | Tools | Folder Options | View | Use Simple File Sharing (Recommended) ] option.

2.2. Operating System and Related Applications

A. TCP Stack
The OfficeScan server may receive and establish multiple HTTP sessions to communicate with its clients. The TCP properties of Windows can be modified to prevent delays and slowdowns caused by TCP time-wait accumulation and port exhaustion. Add or modify the following registry keys as recommended to improve TCP performance. MaxUserPort 8

Key: HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\MaxUserPort Data type: REG_DWORD Default value: 5000 Range: 5,00065,534 (port number) Purpose: Determines the highest port number TCP can assign when an application requests an available user port from the system. Trend Recommendation: 65,534 TcpTimedWaitDelay Key: HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\TcpTimedWaitDelay Data type: REG_DWORD Default value: 0xF0 (240 seconds = 4 minutes) Range: 0x1E 0x12C (30300 seconds) Purpose: This determines the time that must elapse before TCP can release a closed connection and reuse its resources. Trend Recommendation: 30 NOTE: These changes will require a reboot.

B. Microsoft IIS / Apache Web Server

The OfficeScan server uses either Apache or Windows IIS to communicate with its clients. The applications CGI timeout can be increased to allow more time for the server and client to communicate with each other. The Remote Install deployment method is dependent on this timeout as well. Copy process for the installation files over a slow link may cause installation failures.

Microsoft IIS
To modify IIS CGI settings, download and install MetaEdit or Metabase Explorer depending on the version of IIS in use. 1. Download and install a copy of MetaEdit for IIS 4 and 5 from Microsofts Support page http://support.microsoft.com/kb/301386 For IIS 6, download Metabase Explorer from http://www.microsoft.com/downloads/details.aspx?FamilyID=56fc92ee-a71a-4c73-b628ade629c89499&DisplayLang=en 2. Install MetaEdit / Metabase Explorer. 3. After installation, open [ Start | All Programs | Administrative Tools | MetaEdit <version number> ] Or [ Start | All Programs | IIS Resources | Metabase Explorer | Metabase Explorer ] 4. In the MetaEdit or Metabase Explorer console, Locate the key [ LM | W3SVC | 6033 ]. This corresponds to the CGITimeout key. 5. Double-click 6033 key to edit its properties. Set data parameter to 3600. Click OK to save changes. 6. Restart the World Wide Web Publishing Service. For Microsoft IIS 7 on Windows 2008: 1. Download and install the Microsoft Administration Pack for IIS 7.0 9

http://www.iis.net/downloads/default.aspx?tabid=34&g=6&i=1682 Or use the default IIS Manager that comes with IIS 7.0 2. 3. 4. 5. Open IIS Manager Select the Server in the Connections Tree View, then select the OfficeScan site In Features view, double-click CGI Type the appropriate time-out value in Timeout (hh:mm:ss) text box, 00:60:00, press ENTER, and click Apply.

Apache
Follow the procedure below to modify Apaches CGI timeout: 1. Open <drive>: \ Program Files \ Trend Micro \ OfficeScan \ PCCSRV \ apache2 \ conf \ httpd.conf configuration file. 2. Set Timeout 300 to Timeout 600. 3. Restart the Apache service. Note: The definition of the Apache timeout is different from the IIS CGI timeout. With IIS, a CGI timeout of 300 seconds means that the CGI (e.g. cgiremoteinstall) must finish within 300 seconds or the session is timed out. In Apache, the timeout parameter of 300 seconds means that if there is "no action" (or no next action) for 300 seconds, the session is timed out.

2.2.1. Security Tuning

The following are recommended permission settings to the OfficeScan folders and files. These are already set as default during installation:

Directory/User \PCCSRV \PCCSRV\HTTPDB \PCCSRV\Log \PCCSRV\Temp \PCCSRV\Private \PCCSRV\Download \PCCSRV\Web \PCCSRV\Web\Cgi \PCCSRV\Web_OSCE\Web_console \PCCSRV\Web_OSCE\web_console\Rem oteInstallCGI \PCCSRV\Web_OSCE\web_console\HTM L\ClientInstall \PCCSRV\Virus

Administrator Full control Full control Full control Full control Full control Full control Full control Full control Full control Full control Full control Full control

Everyone RX N/A N/A N/A N/A N/A N/A N/A RX N/A N/A N/A

User N/A N/A N/A RWXD N/A R R RX N/A RWXD RWXD RW

Syste m Full control N/A Full control N/A Full control Full control Full control N/A Full control N/A N/A N/A

Network Service N/A N/A N/A RWXD RX N/A N/A N/A N/A N/A N/A N/A

10

There are times that the permission might have been changed accidentally. To reset the permissions back to default: 1. Open command prompt 2. Browse to the OfficeScan servers PCCSRV folder (i.e drive:\Program Files\Trend Micro\OfficeScan\PCCSRV) 3. run the following command: SVRSVCSETUP.EXE -setprivilege

3. Sizing Summary
Important Note: This information can be used as a starting reference. Actual performance will vary depending on features enabled, topology, performance tweaks, and scan-exclusions as outlined throughout this best practice document.

The recommendations below can be used as a guideline to determine the location and number of OfficeScan servers needed to effectively manage your Local / Wide Area Network. 1. A single OfficeScan server is recommended to manage up to approximately 5,000 8,000 clients and Integrated Scan Server can manage 3000 smart clients. Stand Alone Scan Server is recommended for clients over 3000. 2. OfficeScan servers managing clients across the WAN is recommended to be installed on sites with the healthiest bandwidth (typically datacenters or head offices). 3. Consider installing a local OfficeScan server for sites with approximately 500 or more clients. This is recommended if WAN bandwidth is limited for a particular site. 4. An Update Agent is a regular OfficeScan client that is designated to replicate update information from an OfficeScan server for the purposes of distributing the update information to other OfficeScan clients.

11

Main Branch / Data Center (7,800 Clients)

Remote Office (1,200 Clients) OSCE Server
Control Manager

T1

OSCE Server 4,600 Clients

OSCE Server 3,200 Clients

T3 WAN CONNECTION

Remote Office (300 Clients) Update Agent

HIGH SPEED INTERNET

Branch Office (52 Clients) Update Agent VPN Users VPN Users

Sample OfficeScan Deployment Architecture

Sample Deployment Architecture

This table can be used as a template to scope the different sites and generate an architecture proposal.

LOCATION NORTH AMERICA New York New York Chicago Los Angeles Dallas San Jose Memphis Toronto Dallas

No. of CLIENTS

Office Scan INSTALLATION

1400 1000 600 500 71 52 35 1200 25

OSCE Server for North America WAN Integrated Scan Server for North America Local OSCE Server Local OSCE Server Update Agent Update Agent Update Agent Local OSCE Server Update Agent

12

San Francisco Houston EUROPE London Paris Nyon Copenhagen Milan Zurich Istanbul ASIA Hong Kong Singapore Manila Tokyo

20 15

Update Agent Update Agent

1600 360 70 25 25 20 10

OSCE Server for Europe WAN Update Agent Update Agent Update Agent Update Agent Update Agent Update Agent

800 230 60 600

OSCE Server for Asia WAN Update Agent Update Agent Local OSCE server (Japanese version)

3.1. Smart Protection Server Layout (Standalone)

Trend Micro recommends using Standalone Smart Protection Server if the number of smart clients will be more than 3000 instead of Integrated Smart Protection Server. Customers can also choose to install Standalone Smart Protection Server if they do not want to use Integrated Smart Protection Server. If there are a lot of users at each site then the load can be distributed by adding more Standalone Smart Protection Servers.

If the latency is huge between the branch office and the main office, it is recommended to install a Smart Protection Server (standalone) on the branch office. If Smart Protection Server (standalone) cannot be installed or there are no available hardwares then it would be best to switch the clients to conventional scan.

Smart Protection Server Sizing Recommendations

13

Endpoints

Recommended Smart Protection Server Platform

Approximate Server Stress Capacity* 2,500 5,000 7,500

Up to 1,000 Up to 3,000 Up to 5,000

Windows Server 2003: 4 CPU, 2 GB RAM Linux on Hyper-V VM: 2 CPU 2GB RAM VMware Server: 2 CPU, 2 GB RAM or Linux on Hyper-V VM: 4 CPU 2GB RAM

Up to 8,000 8,000 and over

Vmware ESX: 2 CPU, 2 GB RAM Vmware ESX: 4 CPU, 4 GB RAM

11,000 20,000

3.1.1. Load Balancing

Smart Protection Servers can be setup in order to achieve load balancing. Load balancing will help ensure http requests can be distributed among the Smart Protection Servers. There are two ways to achieve load balancing from OfficeScan console: 1. Random This will ensure that clients will randomly choose a Smart Protection Server from the list. 2. Based on IP range Smart clients will update from the Smart Protection Server list they have been assigned to.

` ` ` `

` ` ` `

` ` ` `
Random
Scan Server 1 SS1

Scan Server 2 SS2

Scan Source List Refer by: Random 1 - https://ss1/tmcss? 2 - https://ss2/tmcss?

OSCE

3.1.2. Deployment Recommendations

Smart Protection Server Redundancy
Smart Protection Servers should always be installed in redundant pairs to avoid WAN saturation in the event of a hardware failure 14

Full System Scans

Initial scans require more requests to the Smart Protection Server as seen in the tables below. Clients should schedule their first scheduled scan in phases, especially when their Smart Protection Server is centrally located. Running scheduled scans in batches will increase capacity and normalize iCRC network utilization.

Performance Data: 1st Scheduled Scan Only

Network Bandwidth Through Transactio put Concurrent Latency n Rate per (bytes Connection TTFB (ms) Second per Second) Network Usage Inbound/Outbound (mbps) CPU Memory Usage Usage (%) (MB) Maximum Total User Population

Platform

VMESX v3.5 with 4 vCPUs VMESX v3.5 with 2 vCPUs VM Server with 2 vCPUs VMESX v4.0 with 8 vCPUs VMESX v4.0 with 4 vCPUs VMESX v4.0 with 2 vCPUs Hyper-V with 4 vCPUs (*) Hyper-V with 2 vCPUs (*)

1G 1G 1G 1G 1G 1G 1G 1G

5,180 2,880 1,980 10,980 6,180 3,080 1,420 1,075

2,022 1,200 860 3,888 2,371 1,262 590 362

235 128 200 288 390 322 70 431

861,13 5 511,28 9 366,02 5 1,660,3 60 1,011,7 31 538,35 3 252,02 7 154,22 5

12 / 16 7/9 5/6 24/31 15/19 8/10 2/3 2/2

98.4 99.2 99.1

1,020 707 663

20,700 11,500 7,900 43,900 24,700 12,300 5,600 4,300

99.88 1,860 98.12 1,269 99.34 66.31 95.05 845 511 499

*Transaction rate: 0.5 Requests/Sec

Performance Data: Repeat Scheduled Scan or Real Time Scanning

Platform Network Bandwidth Transact Latency Concurrent ion Rate TTFB Connection per (ms) Second Throughput (bytes per Second) Network Usage Inbound/Outbound (mbps) CPU Memory Usage Usage (%) (MB) Maximum Total User Population

VMESX v3.5 with 4 CPUs VMESX v3.5 with 2 CPUs VM Server with 2 CPUs VMESX v4.0 with 8 vCPUs VMESX v4.0 with 4 vCPUs VMESX v4.0 with 2 vCPUs Hyper-V with 4 vCPUs (*) Hyper-V with 2 vCPUs (*)

1G 1G 1G 1G 1G 1G 1G 1G

4,680 2,380 1,580 10,580 5,580 2,580 1,280 1,058

1,413 797 562 2,692 1,654 854 385 224

207 123 172 97 262 64 78 311

601,629 339,137 239,216 1,149,211 70,569 364,098 164,065 95,290

13 / 18 7 / 10 5/7 26/35 16/21 8/10 2/3 1/2

98.9 98.9 99.1

1,006 664 634

93,600 47,600 31,600 211,600 111,600 51,600 25,600 21,100

99.86 1,718 98.65 1,230 96.45 63.49 91.84 782 449 500

*Transaction rate: 0.004 Requests/Sec

15

3.2. Integrated Smart Protection Server Best Practices

When opting to use the Integrated Smart Protection Server, make sure that it is actually installed and running. If Integrated Smart Protection Server is not properly installed then smart clients will be disconnected and will not be utilizing the cloud technology properly.

WARNING! If you are using Microsoft IIS as your Web Server, monitor the IIS logs generated by Integrated Smart Protection Server. With an environment of around 1000 machines, the daily log size can easily go up to 250MB. IIS doesnt delete old IIS logs by default and this can easily consume all the available free space on the OfficeScan server.
Make sure the above setting Do not save encrypted pages to disk is not enabled in IE in order to check for whether Integrated Smart Protection Server is running or not. After checking the setting above, type the URL below into your browser: https://Officescan_server:port/tmcss/?LCRC=08000000BCB3080092000080C4F01936D D430000 Once you enter you should see the following pop up which will confirm that Integrated Smart Protection Server is running.

16

Ensure that OfficeScan clients can query at least two Scan servers. This avoids the creation of single-point of failure. In order to take advantage of cloud technology fully, all clients must be online and connected to a Smart Protection Server. To add Smart Protection Servers go to [ Smart Scan | Scan Source ] then choose [ Internal Clients ] tab. Choose a standard list or a customer list based on IP address then click on Notify All Clients to push this setting. Do not use Smart Scan as the default scanning method at the root level. Always use Conventional Scan as the root level scanning method. When youre selecting OfficeScan clients to use Smart Scan, always choose a regular domain instead of a root level. If root level is selected as Smart Scan method, before a new client is installed, and if this client is placed in a domain where it uses Conventional Scan, it will download Conventional Scan components.

WARNING! When a client is switched from Smart Scan to Conventional Scan, OfficeScan client will download full pattern file if a conventional pattern file is not present or is more than 14 patterns behind.
Make sure Computer Location settings have correct settings OfficeScan clients can connect to. Computer Location setting can be reached by [ Networked Computers | Computer Location ]. The default setting is Client connection status. OfficeScan clients that can connect to the OfficeScan server or any of the reference servers are located internally, which means if these clients use smart scan, they will connect to a local Smart Protection Server. If connection cannot be established, these clients will be located externally and connect to the Trend Micro Global Smart Protection Server. If Gateway IP address setting is applied and the client computers gateway IP address matches any of the gateway IP addresses you specified on the Computer Location screen, the computers location is internal. Otherwise, the computers location is external.

3.3. Configuration
Majority of the product default configurations provide substantial security with a consideration on server/network performance. The information below are different recommendations, and can be used as an additional reference to either enhance security, or achieve better performance.

17

NOTE: Following notifications in UI shows these features are turned off by default on Windows Server platforms.

To turn on these features administrators should enable Unauthorized Change Prevention Service (TMBMSRV.EXE) and Firewall Service under Additional Service Settings for server platforms as needed. Path: Networked Computers -> Client Management -> Settings -> Additional Service Settings. WARNING: Enabling or disabling the Firewall service temporarily disconnects the clients from the network. Ensure that you change the settings only during non-critical hours to minimize network interruptions. Administrators can turn on Unauthorized Change Prevention Service on a single server platform by enabling/disabling it through Additional Service Settings. Administrators can also enable/disable Unauthorized Change Prevention Service on Workstations by selecting a root/domain/single client/multi-select client.

18

19

3.3.1. Management Console

SECURITY COMPLIANCE Compliance Assessment Compliance Report Notes and Recommendations ***Select an OfficeScan domain to run compliance report on the clients to see which clients are incompatible with server. In Scan Compliance view, specify one or both of the following: Number of days a client has not performed Scan Now or Scheduled Scan Number of hours the remote or scheduled scan task has been running Enabled ***Report can show status of OfficeScan client services, components, Scan compliance, and settings to find incompliant clients. This can be run on daily basis if needed. Trend Micro recommends enabling on-demand assessment to perform real-time queries for more accurate results. You can also disable on-demand assessment wherein OfficeScan queries the database instead of each client. This option may be quicker but produces less accurate results. a. The SMTP setting in notification page is needed for sending the scheduled compliance report to user. Follow these steps to complete the settings: Go to Notification > Administrator Notifications > General Settings page, fill in the fields SMTP server, Port number and From in Email Notification section and click Save. 2. Scan Compliance view uses the configurations that were used to do manual assessment last time.

Scheduled Compliance Report Scheduled Compliance Report

Outside Server Management

Define Active Directory Scope ***Select OUs containing less than 1000 account of computers for performance baseline then increase and decrease number of computers according to performance ***Make sure to add all OSCE server communication ports 135 ***Different port can be chosen but make sure it is a common port that will be available on all

Advanced Settings Specify Ports Declare a computer unreachable by checking port

20

Settings

SCAN METHODS

the computers Enabled ***Enable scheduled query for once a week to find out clients that do not have OfficeScan client. Notes and Recommendations ***Conventional scan leverages anti-malware and anti-spyware components stored locally on endpoints. Smart Scan now is default at the ROOT domain level. Smart Scan method should be selected at the Domain level so this way if a user installs a client it is easier to move from conventional scan to Smart scan. ***Smart Scan leverages anti-malware and anti-spyware signatures stored in-the-cloud. Notes and Recommendations

Scan Methods
Conventional Scan

Smart Scan

MANUAL SCAN SETTINGS

Virus / Malware Scan Settings Target Tab

Files to scan All Scannable Enabled ***Selecting All Scannable Files improves security by only scanning all known to potentially carry malicious code. Using this setting also allows you to utilize True File Type scanning. Enabled Enabled ***This function is not needed if the remote PC already has antivirus protection. Enabling this may cause redundant scanning and performance issues. Enabled ***Scanning within 2 layers is recommended. Increasing the level may cause performance issues. Compressed files are scanned in real-time when extracted. Enabled ***Scanning 3 layers is reasonable. Enabled ***This setting heuristically identifies malware by checking Microsoft Office files for exploit code. Enabled Enabled ***Minimizes the slowdown of PCs when a scan is initiated. It is not recommended to run manual scan during working hours due to high CPU usage. Enabled ***Refer to section 6.6 Recommended ScanExclusion List for recommendations on files

Scan Settings Scan Hidden Folders Scan Network Drive

Scan compressed files

Scan OLE objects Detect exploit code in OLE files

Virus/Malware Settings only Scan Boot Area CPU Usage Medium

Scan Exclusions Enable Scan Exclusion

21

and directories to exclude. Apply scan exclusion settings to all scan types Exclude directories where Trend Micro products are installed Action Tab Virus/Malware Use Active Action Enabled ***This setting will utilize the Trend Micro recommended settings for each type of virus/malware. Enabled ***Select Quarantine to have the ability to restore any files that are needed. Enabled Enabled Enabled Notes and Recommendations Enabled Enabled Disabled Enabled

Customize action for probable virus/malware

Back up files before cleaning Enable system clean up for probable virus/malware Spyware/Grayware Clean REAL-TIME SCAN SETTINGS Enable virus / malware scan Enable spyware / grayware scan Target Tab User Activity on Files Scan files being created/modified and retrieved

Created/modified and retrieved ***In cases where the system is heavily accessed such as File servers, it may be advisable to select Scan files being created / modified but only use this option if the server performance is affected. Enabled ***Selecting intelliscan slightly improves performance by only scanning types known to potentially carry malicious code. Using this setting also allows you to utilize True File Type scanning. Disabled Enabled ***For additional security, it is recommended that this setting be enabled. Note that in some environments, this setting may cause performance issues, please disable if issues are encountered. Enabled ***Scanning 2 layers is reasonable. Increasing the level may cause performance issues. Compressed files are scanned in real-time when extracted. Enabled ***Scanning 3 layers is reasonable.

Files to scan File types scanned by Intelliscan

Scan Settings Scan floppy disk during system shutdown Scan Network Drive

Scan Compressed Files

Scan OLE Objects

22

Detect exploit code in OLE files

Enabled ***This setting heuristically identifies malware by checking Microsoft Office files for exploit code. Enabled ***Turn off this setting on special cases if users regularly exchange/access compressed executable files in real-time. Enabled ***Refer to 6.6 Recommended ScanExclusion List for recommendations on files and directories to exclude. Disabled Enabled

Virus/Malware Scan Settings Only Enable Intellitrap

Scan Exclusion Enable Scan Exclusion

Apply scan exclusion settings to all scan types Exclude directories where Trend Micro products are installed Action Tab Virus/Malware Use Active Action

Customize action for probable virus/malware

Enabled ***This setting will utilize the Trend Micro recommended settings for each type of virus/malware. Enabled ***Select Quarantine to be able to restore any files that are needed Enabled Disabled ***Turn off this setting to avoid end users to see popup messages which can generate helpdesk calls. Disabled ***Turn off this setting to avoid end users to see popup messages which can generate helpdesk calls. Enabled Enabled Disabled ***Turn off this setting to avoid end users to see popup messages which can generate helpdesk calls. Notes and Recommendations Enabled ***Turn on Scheduled scan to scan systems on a regular basis. Enabled ***Turn on Scheduled scan to scan systems on a regular basis

Back up files before cleaning Display a notification message on the client computer when virus/malware is detected

Display a notification message on the client computer when probable virus/malware is detected

Enable system clean up for probable virus/malware Spyware Grayware Clean Display a notification message on the client computer when virus/malware is detected

SCHEDULED SCAN SETTINGS Enable Virus / Malware Scan

Enable spyware/grayware scan

Target Tab Schedule Weekly on Friday 12pm Files to scan All Scannable Files

Suggested to scan during lunch time or after office hours if machine remain turned on. Enabled ***Selecting All Scannable Files improves security by only scanning all known to

23

potentially carry malicious code. Using this setting also allows you to utilize True File Type scanning. Scan settings Scan compressed files Enabled ***Scanning 2 layers is reasonable. Increasing the level may cause performance issues. Compressed files are scanned in real-time when extracted. Enabled ***Scanning 3 layers is reasonable. Enabled ***This setting heuristically identifies malware by checking Microsoft Office files for exploit code. Enabled Enabled ***Prevent slowdown of PCs when a scheduled scan kicks off. Scan will finish longer if the setting is set to Low. Enabled ***Refer to section 6.6 Recommended ScanExclusion List for recommendations on files and directories to exclude. Disabled Enabled

Scan OLE objects Detect exploit code in OLE files

Virus/Malware Settings Only Scan Boot Area CPU Usage Medium

Scan Exclusions Enable Scan Exclusion

Apply scan exclusion settings to all scan types Exclude directories where Trend Micro products are installed Action Tab Virus/Malware Use Active Action

Customize action for probable virus/malware

Enabled ***This setting will utilize the Trend Micro recommended settings for each type of virus/malware. Enabled ***Select Quarantine to be able to restore any files that are needed Enabled Disabled ***Turn off this setting to avoid end users to see popup messages which can generate helpdesk calls. Disabled ***Turn off this setting to avoid end users to see popup messages which can generate helpdesk calls. Enabled

Back up files before cleaning Display a notification message on the client computer when virus/malware is detected

Display a notification message on the client computer when probable virus/malware is detected.

Enable system clean up for probable virus/malware Spyware/Grayware Clean Display a notification message on the client computer when virus/malware is detected SCAN NOW SETTINGS Enable Virus / Malware Scan 24

Enabled Enabled Notes and Recommendations Enabled

Enable Spyware/grayware scan Target Tab Files to Scan File Type scanned by Intelliscan

Enabled

Enabled ***Selecting Intelliscan slightly improves performance by only scanning types known to potentially carry malicious code. Using this setting also allows you to utilize True File Type scanning. Enabled ***Scanning within 2 layers is recommended. Increasing the level may cause performance issues. Compressed files are scanned in realtime when extracted. Enabled ***Scanning 3 layers is reasonable Enabled ***This setting heuristically identifies malware by checking Microsoft Office files for exploit code. Enabled Enabled ***Minimizes the slowdown of PCs when a scan is initiated. It is not recommended to run manual scan during working hours due to high CPU usage. Enabled ***Refer to section 6.6 Recommended ScanExclusion List for recommendations on files and directories to exclude. Disabled Enabled

Scan Settings Scan compressed files

Scan OLE objects Detect exploit code in OLE files

Virus/Malware Settings Only Scan Boot Area CPU Usage Medium

Scan Exclusion Enable Scan Exclusion

Apply scan exclusion settings to all scan types Exclude directories where Trend Micro products are installed Action Tab Virus/Malware Use Active Action

Customize action for probable virus/malware

Enabled ***This setting will utilize the Trend Micro recommended settings for each type of virus/malware. Enabled ***Select Quarantine to be able to restore any files that are needed Enabled Enabled Enabled Notes and Recommendations

Back up files before cleaning Enable system clean up for probable virus/malware Spyware/Grayware Clean UPDATE AGENT SETTINGS

25

Client can act as Update Agent

***Component Updates, Domain Settings, and Client programs and hotfixes should be selected to take full advantage of Update Agents to save bandwidth and to speed up deployment. Enabled Enabled Enabled Notes and Recommendations

Component Updates Domain Settings Client programs and hot fixes PRIVILEGES AND OTHER SETTINGS Privileges Tab Roaming Privileges Enable Roaming mode

Disabled ***It is highly recommended to disable this function as it will allow users to stop communication between OfficeScan server and client. This Roaming privilege allows users to isolate their systems to avoid getting notified by the server for scans or updates. This function has nothing to do with the ability to update when the machine is off the network, such as taking a laptop home. Disabled ***Enable this to allow users to configure their own scan setting. Disabled ***Enable this to allow users to configure their own scan setting. Disabled ***Enable this to allow users to configure their own scan setting. Disabled ***Enable this to allow users to stop the Scheduled scan when it is triggered. Disabled ***Enable this to allow users to stop the Scheduled scan when it is triggered. Enabled Disabled ***Enable this to allow users to configure their own firewall settings other than what is set on the OfficeScan server Disabled ***Keep this disabled unless necessary as it will increase traffic between OSCE server and Clients. Disabled

Scan Privileges Configure Manual Scan Settings

Configure Real-time Scan Settings

Configure Scheduled Scan Settings

Scheduled Scan Privileges Postpone Scheduled Scan

Skip and stop scheduled Scan

Firewall Privileges (if you have firewall activated) Display the Firewall tab on the Client console Allow users to enable/disable the firewall, Intrusion Detection System, and the firewall violation notification message Allow clients to send firewall logs to the OfficeScan server

Behavior Monitoring Privileges Display the Behavior Monitoring tab on the client console. Mail Scan Privileges Display the Mail Scan tab on the client console

Disabled ***Since most enterprise does not use POP3, this tab can be hidden to users to avoid confusion. If this setting is allowed then users

26

can install this tool using OSCE client GUI. Toolbox Privileges Display the Toolbox tab on the client console and allow users to install Check Point Secure Client Support Proxy Settings Privileges Allow the Client user to Configure proxy Settings

Disabled ****Unless Checkpoint Secure Client is used, this should be turned off to avoid confusion to users. Enabled ***Enable this to allow users to configure proxy to update from internet, otherwise this can be turned off. Enabled ***Enabled to Allow users to initiate an update manually by right clicking on the OSCE icon on their system tray. Disabled ***Leave this option disabled so users cannot turn off scheduled update. This will keep users up-to-date with the latest signature. Enabled ***Enable this to prevent users from uninstalling Officescan client from their system. Enabled ***Enable this to prevent users from unloading Officescan client from their system.

Component Update Privileges Perform Update Now

Enable Scheduled Update

Uninstallation Require a password for the user to uninstall the Officescan client Unloading Require a password for the user to unload the Officescan client

Other Settings Tab Update Settings Clients download updates from the Trend Micro ActiveUpdate Server

Enabled ***Enable this function to allow clients to update from Trend Micro Active Update servers whenever the Officescan client cannot contact the Officescan Server or the Update agents. This is especially helpful for users who travel with their laptop or bring their laptops home, keeping them up-to-date all the time. Enabled ***Aside from notification from the Officescan server for updates, this function is used to allow Officescan to check for updates on scheduled basis. Update checking is done in the background and no user intervention is required. Disabled ***Enable this function in environments where bandwidth is limited. This allows client to update their regular signatures and engines and avoid downloading hotfixes or program updates from the Officescan server.

Enable Scheduled Update

Clients can update components but not upgrade the client program or deploy hot fixes

Web Reputation Settings

27

Display a Notification when a web site is blocked

Enabled ***Turn this off to avoid getting popups when websites are blocked. Enabled ***Enable this function to avoid confusion on the users as to why a certain program wont run. Disabled

Behavior Monitoring Settings Display a notification when a program is blocked.

Scheduled Scan Settings Display a notification before a scheduled scan occurs Client Security Settings High: Restrict users from accessing OfficeScan client files and registries

Enabled ***Setting this to high prevent regular users from deleting Officescan files and registry entries. Disabled ***Enable this only when you use POP3 mail in your network. When selected, this setting enabled POP3 mail scan on the client console. Note that this setting only applies to clients with the mail scan privileges. Disabled ***In some environment where any user changes are prohibited, this function allows administrators to restrict users from accessing the Officescan Client console. Enabled

POP3 Email Scan Settings Scan POP3 email

Client Console Access Restriction Do not allow users to access the client console from the system tray or Windows Start menu

Restart Notification Display a notification message if the client computer needs to restart to finish cleaning infected files. ADDITIONAL SERVICES Unauthorized Change Prevention Service

Firewall Service

Notes and Recommendations Enabled ***Unauthorized Chang Prevention Service regulates application behavior and verifies program trustworthiness. Behavior Monitoring, Device Control, Certified Safe Software Service, and Client Self protection all require this service. If an Administrator wants to allow this service on a server then a single server must be chosen to view the option to enable this service. ***This setting will turn on the firewall service on the OfficeScan clients. WARNING: Enabling this service will temporarily disconnect the OfficeScan client from the network. Notes and Recommendations Enabled ***Enable this feature to protect clients from web threats when they are not connected to the internal network. Enabling this will provide them protection from accessing malicious

WEB REPUTATION

External clients tab

Enable Web Reputation Policy

28

sites. Enable assessment Disabled ***Administrator can enable assessment to monitor the type of detections before deploying Web Reputation. When assessment is turned on OfficeScan will not take any action. Enabled Enabled Enabled ***Depending on security requirements, you may or may not want to monitor what sites are being blocked on the client side. On the other hand, turning this on will generate traffic between server and clients. Enabled ***If there is already a web security on the gateway, this may be turned off. Disabled ***Administrator can enable assessment to monitor the type of detections before deploying Web Reputation. When assessment is turned on OfficeScan will not take any action. Enabled ***Internet traffic usage is lowest and browsing info is kept in house. Security level is always low. Enabled ***This will give the most up to date protection from Trend Micro but browsing info will be revealed to Trend Micro. Support security levels are high, medium, and low Enabled ***Internet traffic usage is lowest and browsing info is kept in house. When combine with Use only Smart Protection Servers, do not send queries to Smart Protection Network checked, Security level is always low. Enabled Enabled ***Depending on security requirements, you may or may not want to monitor what sites are being blocked on the client side. On the other hand, turning this on will generate traffic between server and clients. Notes and Recommendations Enabled ***Enable this setting to protect your clients from specific threats, threat types and threat families through behavior analysis.

Security Level Medium Untested URLs Block pages that have not been tested by Trend Micro Client Log Allow Clients to Send Logs to the Officescan Server

Internal clients tab

Enable Web Reputation Policy

Enable Assessment

Use Smart Protection Server Web Reputation Service

Use only Smart Protection Servers, do not send queries to Smart Protection Network

Security Level Low

Untested URLs Block pages that have not been tested by Trend Micro Client Log Allow Clients to Send Logs to the Officescan Server

BEHAVIOR MONITORING Enable Malware Blocking

29

Enable Event Monitoring

Enabled ***Enable this to monitor system events to filter potentially malicious actions. Refer to list below for recommended settings if this is enabled.

Policies (Under Event Monitoring if Enabled) ** The Assess action will log events that violate the policy but will not take action. To avoid interfering with normal activity, it is recommended that administrators start with this action set for all policies. This would help them define the proper action they need to take once data is available. Duplicated System File Assess Hosts File Modification Assess Suspicious Behavior Assess New Internet Explorer Plugin Assess Internet Explorer Setting Modification Assess Security Policy Modification Assess Program Library Injection Assess Shell Modification Assess New Service Assess System File Modification Assess Firewall Policy Modification Assess System Process Modification Assess New Startup Program Assess ***Enter the full path of programs you would Exceptions (Approve/Block) want to exempt from Behavior Monitoring or directly Block. DEVICE CONTROL Notes and Recommendations Enabled device control Enabled ***Enable this setting to take advantage of the Block autorun function on USB devices but leave Full Access permissions for the devices unless there is a need to control them due to virus outbreaks/data leak prevention Block autorun function on USB devices Enabled ***Enable this to prevent the potential threat autorun can cause. Device Plug-in Devices (USB) Full Access Optical Disks Full Access Floppy Disks Full Access Network Resource Full Access Notification Display a notification message on the client Enabled ***Enable this when device control access is Computer when OfficeScan detects unauthorized not set to Full Access to avoid causing Device access confusion to users as to why they cannot access their drives fully. Device Access Control Grant full access to all device types Enabled Allow to be run from devices Disabled ***Enable this feature if you plan on running devices from a certain path Exceptions (Approve/Block) ***Enter the full path of programs you would want to exempt from Behavior Monitoring or directly Block. CLIENT GROUPING Notes and Recommendations ***Only used during installation of a client NetBIOS domain 30

Active Directory domain DNS domain Custom client groups CUSTOM CLIENT GROUPS Automatic Client Grouping Schedule Domain Creation ***Can be used anytime to group clients Notes and Recommendations ***Administrators can create client grouping according to Active Directory or IP Enabled ******Performing scheduled domain creation creates a domain in the client tree. This may take a long time to complete, especially if the scope is broad. However, this does not move existing clients to this domain. Custom client grouping must be used. To move the clients, refer to manual sort client or OfficeScan can automatically move clients when the following events occur: 1. Client installation, 2. Clients reload 3. Clients change IP addresses 4. Clients enable or disable roaming mode Notes and Recommendations Enabled ***This enhances performance on scanning compressed files and prevents Officescan from taking time and resource scanning every content of a compressed file. When compressed files are extracted, realtime scan will still scan the files. 10MB Disabled ***Enable this function to allow users to rightclick on files or folders to perform a manual scan. Enabled ***Prevent Officescan database from getting corrupted. Enabled ***Prevent Officescan from interfering with the mails being processed by the Exchange server and the antivirus that scans the mail traffic. Enabled Enabled ***Turn this on with a recommended of at least 3 weeks to allow administrator to assess the detection of spyware in the network. Any detection will not have any action taken on them. This allows admin to monitor and verify if there are any false positive detections specially on home grown applications. Enabled ***Turn on to allow cookie scanning and

GLOBAL CLIENT SETTINGS Scan Settings Configure scan settings for large compressed files

Do not scan files in the compressed file if the size exceeds Add Manual Scan to the Windows shortcut menu on client computers

Exclude the OfficeScan server database folder from Real-time Scan Exclude Microsoft Exchange server folders from scanning

Virus/Malware Scan Settings only Clean/Delete infected files within compressed files Spyware/Grayware Scan Settings Only Enable Assessment Mode

Scan for Cookies

31

cleaning Count Cookie into spyware log Disabled ***Turn this off to prevent logs generated from cookie detection to overpopulate the virus log database. 10 minutes before it runs ***This setting only applies to users who have the privilege to control Scheduled scans. 1 hour ***This setting only applies to users who have the privilege to control Scheduled scans. Disable Enable ***Enable this setting (20 percent) when there is a number of laptop users in your environment to save battery life. Enable 4 hours ***If it is really needed, set this to Daily or every 4 to 8 hours to prevent clients from saturating the network by sending logs at short intervals regularly. Enabled ***This setting will let clients update the firewall driver settings during reboot. This way there will be no loss of network connectivity. This setting applies to only updates/upgrades done through OfficeScan server. 30 ***If timeout is reached, BM will allow the program. Disabled ***When enabled, the OSCE client will query the Trend Micro back-end servers via the Internet to reduce BM false alarms.

Scheduled Scan Settings Remind users of the Scheduled Scan

Postpone Scheduled Scan for up to

Automatically stop Scheduled Scan when scanning lasts more than Skip Scheduled Scan when a wireless computers battery life is less than

Resume a missed scheduled scan Firewall Log Settings (If you have firewall activated) Send firewall logs to the server every

Update the OfficeScan firewall driver only after a system reboot

Behavior Monitoring Settings Automatically allow program if client does not respond within X seconds. Enable Certified Safe Software Service

Alert Settings Show the alert icon on the Windows taskbar if the virus pattern file is not updated after X days Display a notification message if the client computer needs to restart to load a kernel mode driver

5 Enabled ***When firewall is enabled, it is suggested to have this turned on so that whenever the firewall driver is updated, the client may be notified to reboot for the update to take effect, otherwise, without reboots, the firewall may not function properly with the updated component. Enabled 1 minute 6 times 1 hour

OfficeScan Service Restart Automatically restart an OfficeScan client service if the service terminates unexpectedly Restart the service after If the first attempt to restart the service fails, retry Reset the restart failure count after 32

Client Self-protection Protect files in the OfficeScan client installation folder

Protect OfficeScan client processes

Protect OfficeScan client registry keys

Protect OfficeScan client services

Enabled ***To prevent other programs and even the user from modifying or deleting OfficeScan files, it is recommended to enable this setting. Enabled ***To prevent all attempts to terminate OSCE related processes, it is recommended to enable this setting Enabled ***To prevent other programs and even the user from modifying, deleting, or adding new entries related to the OSCE registry and subkeys, enable this setting Enabled ***To prevent OfficeScan services from being stopped. 60 ***To allow enough disk space on client side for updates Enabled ***This minimizes bandwidth usage by consolidating the logs first before sending them together to the OfficeScan server Enabled ***This allows clients to send only a single log to server on multiple detection of viruses detected on the same location, same virus for a period of time Enabled ***To allow auto detection of proxy for updates, this can be enabled Disabled ***To allow use of proxy scripts for connection, this can be enabled. Enabled ***Administrators can use this setting to let OfficeScan clients to update only patterns from the Trend Micro Active Updatesite Notes and Recommendations Enabled ***OfficeScan clients will try to communicate with reference servers to determine if their status will be online or offline if the OfficeScan server is not available. Disabled ***Gateway addresses can be entered instead of reference list to determine whether OfficeScan clients are online or offline.

Reserved Disk Space Reserve X MB of disk space for updates

Network Virus Log Consolidation Enable OfficeScan clients to consolidate network virus logs and send them to the OfficeScan server hourly.

Virus/Malware Log Bandwidth Settings Enable OfficeScan clients to create a single virus/malware log entry for reoccurring detection of the same virus/malware within an hour

Proxy Configuration Automatically detect settings

Use automatic configuration script

Updates Download only pattern files from the Activeupdate server when performing updates.

COMPUTER LOCATION Computer Location Client Connection status (edit reference server list)

Gateway IP address Mac address (optional)

33

CONNECTION VERIFICATION Scheduled Verification Enable Scheduled Verification

Notes and Recommendations Enabled Daily at 10:30am ***This allows the server to recheck the status of the clients that are in the network, it is ideal to set it to run on a schedule where most clients are already online.

SMART PROTECTION SOURCES Smart Protection Sources Internal Clients Use the standard list

Notes and Recommendations

Order

Random

Use customer lists based on client IP address

Use standard list if customer list becomes unavailable

Integrated Server

Use Integrated File Reputation Service Use Integrated Web Reputation Service Update Settings Enable scheduled updates Hourly Smart Feedback Smart Protection Network

Enabled ***Use this setting if all Smart Protection Servers are reachable through the same network connection for the entire environment. Ensure that there is a minimum of 2 Smart Protection Servers reachable for all clients. ***The setting will configure the clients to check the Scan Servers in the order specified on the liste. (Integrated Smart Protection Server will always be last) ***If all Scan Servers are equal in performance, availability and location, the random setting will allow the clients to load balance between all of the Smart Protection Servers on the list. ***Use this setting to customize which Smart Protection Server clients will use. It is recommended that each sub site will have its own Smart Protection Server. ***To help ensure full redundancy in situations where the customer Smart Protection Server list is unavailable, the client should check the standard list ***Check box should be enabled if the Integrated Smart Protection Server will be used. The Integrated Smart Protection Server should not be used to suppor more than 3000 clients in a primary role. If more than 3000 clients need to be supported a Stand-Alone Smart Protection Server should be installed in the environment and the Integrated Smart Protection Server should be used for backup purposes only. Enabled Enabled Enabled Enabled ***When enabled, Trend Micro Smart Feedback shares threat information with the Smart Protection Network, allowing Trend Micro to rapidly identify and address new

34

threats.

UPDATES SERVER Scheduled Update Enable scheduled update of the OfficeScan server Update Schedule

Notes and Recommendations

Enabled Hourly ***It is best to check on a more regular basis to get the latest updates.

NETWORKED COMPUTERS Automatic Update Event-Triggered Update Initiate component update on clients immediately after the OfficeScan server downloads a new component Include roaming client(s)

Let clients initiate component update when they restart and connect to the OfficeScan server (roaming clients are excluded)

Perform Scan Now after update (excluding roaming clients)

Enabled ***Turn this on so that the updates can be deployed immediately to the clients once the Officescan server finished updating. Disabled ***If you have the roaming privilege turned off, this is not necessary. Enabled ***There are instances where the clients are offline when the server updated from the internet. This function will allow clients to get their updates from the server when they are back online. Disabled ***It is not extremely necessary to do a full scan right after performing an update. The scheduled scan is normally sufficient. Enabled ***Depending on the number of clients that the server manages, you can set this from 2 hours to every 4 hours. This is the setting to configure clients on how often they will check for updates fro the Officescan server, the update agent or the Internet. Enabled ***Enable this if No update agents will be used Enabled ***Administrators can allow clients to get updates from OfficeScan servers if Update Agents are not available Disabled ***This setting can be turned on if bandwidth is healthy enough to provide back up updates to Update Agents Enabled ***Domain settings are small enough to allow clients to go to OfficeScan server to get updates from as long as Update Agents are not available. Disabled ***This setting should not be turned on unless OfficeScan clients are allowed to

Schedule-based Update 2 or 4 hours

Update Source Standard Update Source

Customized Update Source

Update components from the OfficeScan server if all customized sources are not available or not found

Update domain settings from the OfficeScan server if all customized sources are not available or not found

Update client programs and hot fixes from the OfficeScan server if all customized sources are not available or not found 35

Update agent: always update from standard update source (OfficeScan server)

upgrade from OfficeScan server. This might cause bandwidth problems depending on the network. Enabled ***Enable this to have update agents always update from the Officescan server

LOGS LOG MAINTENANCE Enable Scheduled Deletion

Notes and Recommendations Enable ***Enable this to maintain a manageable size of log and prevent performance issue on the OSCE server when retrieving logs. If Control Manager is used the logs are also sent to Control Manager, hence there is no need to keep 2 copies of logs. You can get reports from Control Manager. Ensure all Log types are selected. Logs Older than 7 days ***To Keep the log database small enough for efficiency. Daily @ 2am ***It is advisable to have this checked everyday. The Time suggested is 2am so that the traffic to server is low and can be purged before the system backup kicks off. Officescan Server automatically does database maintenance during midnight, so avoid scheduling during this time.

Logs to Delete

Log Deletion Schedule

NOTIFICATIONS ADMINISTRATOR NOTIFICATIONS

Notes and Recommendations

Standard Notifications
Virus/Malware Send notifications only when the action on the virus/malware is unsuccessful Spyware/Grayware Send notifications only when the action on the virus/malware is unsuccessful Enable ***Enable this to only notify when an action failed on the virus/malware. Enable ***Enable this to only notify when an action failed on the spyware/grayware. Enable ***Enable this to alert administrators when infections are starting to grow. 1 100 24 hrs Enabled ***Enable this to alert administrators when infections are starting to grow. 1 100 24 hrs

Outbreak Notifications
Virus/Malware

Unique Sources Detections Time Period Spyware/Grayware

Unique Sources Detections Time Period Firewall Violations 36

Monitor Firewall violations on networked computers

IDS Logs Firewall Logs Network Virus Logs Time Period Shared Folder Session Monitor Shared Folder session on your network

Enabled ***Enable this to alert administrators when there are suspicious firewall violations 100 100 100 1 hr Enabled ***Enable this to alert administrators of suspicious network sessions being generated. 100 3 min

Shared Folder Sessions Time Period

ADMINISTRATION User Accounts

User Roles

Notes and Recommendations ***User accounts are used to logon to OSCE web console. These accounts are assigned privileges as deemed appropriate. Use this section to add custom accounts or Active Directory accounts. ***User roles define a list of operations that a user can perform. These operations are roughly tied to the navigation menu. Use this section to assign/create/modify roles for a user or a windows group. This would give the account permission to perform operations defined in that group.

Active Directory Active Directory Integration Active Directory Domains Encrypt Active Directory Credentials

***Add Active Directory domains OfficeScan will associate with the client tree. ***Specif an ecryption key and file path to ensure an additional layer of protection for your Active Directory credentials. Enabled ***Administrators can set the scheduled synchronization daily.

Scheduled Synchronization Enable Scheduled Active Directory synchronization

Proxy Settings Internal Proxy Client Connection with the OfficeScan Server Computer Use the following proxy settings when clients connect to the OfficeScan server and the Integrated Smart Protection Server.

Disabled ***This should be disabled all the time unless the Officescan Clients require connection to an intranet proxy to communicate with the Officescan Server.

Client Connection with the Local Smart Protection Servers Use the following proxy settings when clients connect to the local Smart Protection Servers.

Disabled ***This should be disabled all the time unless the OfficeScan clients require connection to an INTRANET proxy to communicate with the local Smart Protection Server.

External Proxy 37

OfficeScan Server Computer Updates Use a proxy server for pattern, engine, and license updates

Enabled ***Enable this option and fill out the fields when a proxy server is required to download updates from the internet. Enabled ***Fill this out if the proxy server used requires authentication credentials. Enabled ***Enable this function to allow Officescan to remove old clients that are inactive for X days. Whenever these clients come back online, they will automatically be added and show up in the console. 7 days 10240MB ***Please note that the Quarantine folder on the Officescan server does not cleanup by itself. It is important to clean the folder up on a regular basis. 5 MB

Client Connection with Trend Micro Servers Specify proxy server authentication credentials the client will use to connect to the Trend Micro Global Smart Protection Server and Web reputation servers. Inactive Clients Enable automatic removal of inactive clients

Automatically remove a client if inactive for X days Quarantine Manager Quarantine folder capacity

Maximum size for a single file Web Console Settings Web Console Auto Refresh Enable Auto Refresh Web Console Timeout Setting Enable Timeout Setting Database Backup Database Backup Schedule Enable Scheduled Database Backup

Enabled ***Set it for 30 seconds Enabled ***Set it for 30 minutes

Daily @ 3AM ***Officescan Server does database maintenance usually at midnight, and it is best not to interfere with the maintenance so it is recommended either to set the time few hours before or few hours after Midnight after log purging.

NOTE: It is recommended that during a virus outbreak, to utilize the Outbreak prevention policy feature in Officescan. This feature allows you to control and contain an outbreak by blocking the ports, shared folders, and protect files that malwares are using to propagate and infect.

3.3.2. INI Configuration Files

A. OfcScan.ini

38

PARAMETER
[Global Setting] DisableTSCAtStart=1

USAGE / NOTES Add/Change value to 1 to disable the Damage Cleanup service from executing whenever the Officescan realtime scan starts up. This is helpful for systems with low resource to speed up the bootup/startup time. Enable this feature to allow Update Agents to download only one incremental file from the Officescan server and allow it to automatically generate full pattern and the rest of the incremental files. This will help minimize bandwidth usage.

[Global Setting] UADuplicationOptValue =128

B. OfcServer.ini
PARAMETER
[INI_AD_INTEGRATION_SECTION]] ApplyFQDNToResolveIPFirst=1

USAGE / NOTES For FQDN environment only when this is set to 1. Enable this option to resolve IP from FQDN. If this is set to 0, OfficeScan resolve IP from NetBIOS first and then resolve IP from FQDN. If this is set to 1, Officescan resolve IP from FQDN first and then resolve IP from NetBIOS.

[INI_AD_INTEGRATION_SECTION]] EnableQueryAllContainer=1

When this option is set to 1, it allows Active Directory Integration to query all objects including containers.

3.4. Performance Tuning

A. OfficeScan Server (ofcscan.ini) Parameters
The parameters below can be added or edited to further improve the performance of the OfficeScan server.

PARAMETER (ofcscan.ini)
Command_Handler_Maxium_Thread_Number

USAGE / NOTES This OfficeScan server parameter controls the number of threads responsible for receiving client communications. Default value is 20. Add the parameter under [INI_SERVER_SECTION] of ofcscan.ini to modify default setting. Recommended value is 20 multiplied by the number of CPUs. NOTE: the word Maxium is intentionally misspelled.

DB_MEM_OPT_MAX

Increase the server database cache to improve performance. Recommended value is at 10% of available memory.

39

Increase the number of Command Handler threads

1. Edit <drive>: \ Program Files \ Trend Micro \ OfficeScan \ PCCSRV \ ofcscan.ini 2. Add the parameter Command_Handler_Maximum_Thread_Number= under [INI_SERVER_SECTION] section and set its value to 20 x Number of CPUs. 3. Restart the OfficeScan Master Service.

Increase Database Cache to improve performance

1. Edit <drive>: \ Program Files \ Trend Micro \ OfficeScan \ PCCSRV \ ofcscan.ini 2. Locate the entry DB_MEM_OPT_MAX = 10240 and set its value to be at least 10% of available memory. 3. Restart the OfficeScan Master Service.

Verify Connection Thread Count Parameter

1. Go to the [INISERVER_SECTION] section. 2. Look for the VerifyConnectionThreadCount=16 parameter. 3. This value is dependent on the network capacity. If you have a 100 Mbps intranet, entering a value of 64 or 128 is acceptable.

4. Backup and Disaster Recovery

NOTE: Section below applies only to OfficeScan itself. Integrated Scan Server components will not be backed up.

4.1. Officescan Server Database Files

The OfficeScan server can be set to automatically backup client database information. This is configurable via the web-based management console under [ Administration | Database Backup ] section. This process copies all database files under [ <drive>: \ Program Files \ Trend Micro \ OfficeScan \ PCCSRV \ HTTPDB ] to either a local or remote location. It is recommended to do a Daily backup especially during client deployment. The schedule can be changed to Weekly after the deployment is complete. It is also recommended to configure the backup to start at 2:00 AM when client interaction is minimal and the process does not coincide with other OfficeScan scheduled tasks. It is recommended to use the Officescan builtin backup function to do the backup for the database. Using third party application to backup the database may cause system instability or database corruption.

4.2. Officescan Server Configuration Files

It is also recommended to manually backup the OfficeScan server configuration files which can be used to recover from a server disaster.

OfficeScan Server and Firewall configuration Files \ PCCSRV \ Ofcscan.ini Server configuration information 40

\ PCCSRV \ Private \ Ofcserver.ini Server and Update Source configuration \ PCCSRV \ Ous.ini Client update source configuration \ PCCSRV \ Private \ PFW folder Firewall profiles / policies \ Private \ SortingRuleStore \ SortingRule.xml \ Private \ AuthorStore folder RBA User Profile \ Private \ vdi.ini vdi settings In an event of server corruption, the OfficeScan server settings can be restored by following the procedure below.

Restoring OfficeScan Server Configuration

This procedure assumes that the OfficeScan server is being restored to the same host, using the same FQDN and IP address. 1. Stop the OfficeScan Master Service and WWW Publishing Service. 2. Restore the backup database files under [ <drive>: \ Program Files \ Trend Micro \ OfficeScan \ PCCSRV \ HTTPDB ] 3. Restore the OfficeScan server and Firewall policy configurations o \ Program Files \ Trend Micro \ OfficeScan \ PCCSRV \ Ofcscan.ini o \ Program Files \ Trend Micro \ OfficeScan \ PCCSRV \ Private \ Ofcserver.ini o \ Program Files \ Trend Micro \ OfficeScan \ PCCSRV \ Ous.ini o \ Program Files \ Trend Micro \ OfficeScan \ PCCSRV \ Private \ PFW directory o \ Private \ SortingRuleStore \ SortingRule.xml o \ Private \ AuthorStore folder RBA User Profile o \ Private \ vdi.ini 4. From the command prompt, go to \Program Files\Trend Micro\ OfficeScan folder and Run the command srvsvcsetup.exe setprivilege. 5. Restart the OfficeScan Master Service and WWW Publishing Service.

4.3. Officescan Client Configuration Settings

Saving the Client Configuration Settings
1. Log on to the Officesan Management Console 2. Go to Networked Computers | Client Management 3. To save the Global Domain settings, highlight the Officescan Server domain; To save just the domain level setting, highlight only the subdomain; To save only a specific clients setting, highlight the client. 4. Once highlighted, select Settings | Export Settings 5. Click on the Export button and save the file.

Restoring the Client Configuration Settings

1. Log on to the Officesan Management Console 2. Go to Networked Computers | Client Management 41

3. To restore the Global Domain settings, highlight the Officescan Server domain; To restore just the domain level setting, highlight only the subdomain; To restore only a specific clients setting, highlight the client. 4. Once highlighted, select Settings | Import Settings 5. Browse to the DAT file saved previously that you want to restore, then click in Import button 6. Put a check to Apply to all Domains or Apply to all computers belonging to the selected domain(s) 7. Click on the Apply to Target button

5. Behavior Monitoring
Trend Micro OfficeScan protects enterprise networks from malware, network viruses, Web-based threats, spyware, and mixed threat attacks. Behavior Monitoring and Device Control are some of the new OfficeScan features that proactively aim to prevent malware attacks. This document aims to increase knowledge about Behavior Monitoring and Device Control and help readers avoid potential issues during deployment.

5.1. Behavior Monitoring Overview

Behavior Monitoring constantly monitors endpoints for unusual modifications to the operating system or installed software. Behavior Monitoring is composed of the following sub-features: Malware Behavior Blocking Event Monitoring

5.1.1. Malware Behavior Blocking

Malware Behavior Blocking provides a necessary layer of additional threat protection from programs that exhibit malicious behavior. It observes system events over a period of time and as programs execute different combinations or sequences of actions, Malware Behavior Blocking detects known malicious behavior and blocks the associated programs. Use this feature to ensure a higher level of protection against new, unknown, and emerging threats. Note: To help ensure that this feature does not interfere with critical applications, OfficeScan leaves this feature disabled on server platforms, even when it is enabled through the console. To enable this feature on a server computer, select an individual server and go to Settings -> Additional Service to enable this option. For instructions, see the Administrators Guide. Figure 1-1: Malware Behavior Blocking setting

Tip: Before deploying Malware Behavior Blocking, Trend Micro recommends running a pilot deployment. See Deploying Behavior Monitoring and Device Control for more information. 42

5.1.2. Event Monitoring

Event Monitoring provides a more generic approach to protecting against unauthorized software and malware attacks. It uses a policy-based approach where system areas are monitored for certain changes, allowing administrators to regulate programs that cause such changes. If attempts to change the system are made, Event Monitoring will: Refer to the Event Monitoring policies and perform the configured action. Notify the user or administrator Use the Event Monitoring if you have specific system protection requirements that are above and beyond what is provided by Malware Behavior Blocking.

Figure 1-2: Event Monitoring setting

The following Event Monitoring policies define which events it checks for and how it handles each event.

43

Table 1-1: Event monitoring policies Events Duplicated System File Description Many malicious programs create copies of themselves or other malicious programs using file names used by Windows system files. This is typically done to override or replace system files, avoid detection, or discourage users from deleting the malicious files. The Hosts file matches domain names with IP addresses. Many malicious programs modify the Hosts file so that the Web browser is redirected to infected, nonexistent, or fake Web sites. Suspicious behavior can be a specific action or a series of actions that is rarely carried out by legitimate programs. Programs exhibiting suspicious behavior should be used with caution. Spyware/grayware programs often install unwanted Internet Explorer plugins, including toolbars and Browser Helper Objects. Many virus/malware programs change Internet Explorer settings, including the home page, trusted Web sites, proxy server settings, and menu extensions. Modifications in Windows Security Policy can allow unwanted applications to run and change system settings. Many malicious programs configure Windows so that all applications automatically load a program library (DLL). This allows the malicious routines in the DLL to run every time an application starts. Many malicious programs modify Windows shell settings to associate themselves to certain file types. This routine allows malicious programs to launch automatically if users open the associated files in Windows Explorer. Changes to Windows shell settings can also allow Default Action Assess

Hosts File Modification

Assess

Suspicious Behavior

Assess

New Internet Explorer Plugin

Assess

Internet Explorer Setting Modification Security Policy Modification

Assess

Assess

Program Library Injection

Assess

Shell Modification

Assess

44

Events

Description malicious programs to track the programs used and start alongside legitimate applications.

Default Action

New Service

Windows services are processes that have special functions and typically run continuously in the background with full administrative access. Malicious programs sometimes install themselves as services to stay hidden. Certain Windows system files determine system behavior, including startup programs and screensaver settings. Many malicious programs modify system files to launch automatically at startup and control system behavior. The Windows firewall policy determines the applications that have access to the network, the ports that are open for communication, and the IP addresses that can communicate with the computer. Many malicious programs modify the policy to allow themselves to access the network and the Internet. Many malicious programs perform various actions on built-in Windows processes. These actions can include terminating or modifying running processes Many malicious programs configure Windows so that all applications automatically load a program library (DLL). This allows the malicious routines in the DLL to run every time an application starts.

Assess

System File Modification

Assess

Firewall Policy Modification

Assess

System Process Modification

Assess

New Startup Program

Assess

Administrators can choose to perform one of the following actions to respond to monitored events: Assess: Always allow processes associated with an event but record this action in the logs for assessment NOTE: Use this option during initial deployment to assess the impact of enabling Behavior Monitoring features. Allow: Always allow processes associated with an event Ask When Necessary: Prompts users to allow or deny processes that may have violated Behavior Monitoring policies. If selected, a prompt asking users to allow or deny the process and add to the

45

Allowed Programs or Blocked Programs appears. If users do not respond within the time period specified in the Behavior Monitoring settings screen, OfficeScan automatically allows the process to continue. Deny: Always block processes associated with an event and record this action in the logs

5.1.3. Enabling Behavior Monitoring

Path: Networked Computers > Client Management > Settings > Behavior Monitoring Settings To enable Malware Behavior Blocking or Event Monitoring, select the following options: Enable Malware Behavior Blocking (workstation default: on; server default: off ) Enable Event Monitoring (workstation default: on; server default: off) Note: Since Malware Behavior Blocking is enabled by default, Trend Micro strongly recommends identifying system-intensive applications and adding them to the exception list before deploying OfficeScan. For more information, see How Behavior Monitoring and Device Control Can Affect Performance. Behavior Monitoring settings can be applied to specific entities in the client tree or all entities (root). If you are applying settings to the root, you need to select one of the following options: Apply to All Clients: Applies settings to all existing clients and to any new client added to an existing/future domain (domains not yet created during configuration). Apply to Future Domains Only: Applies settings only to clients added to future domains. This option will not apply settings to new clients added to an existing domain.

5.2. Device Control Overview

Device Control regulates access to external storage devices and network resources. Device Control helps prevent the propagation of malware on removable drives and network shares and, combined with file scanning, helps guard against security risks. Figure 1-3: Device Control settings

Notification messages are displayed on the endpoints when device control violations occur. Administrators can modify the default notification message. Note: To help ensure that this feature does not interfere with critical applications, OfficeScan leaves this feature disabled on server platforms, even when it is enabled through the console. To enable this feature on a server computer, select an individual server and go to Settings -> Additional Service to enable this option. For instructions, refer to the Administrators Guide.

5.2.1. Using Device Control

Path: Networked Computers > Client Management > Settings > Device Control

46

To configure Device Control: 1. Select the Enable device control option. 2. Choose whether to block or allow the AutoRun function (autorun.inf) on USB devices connected to the computer. 3. Select the permissions for each device type. Table 1-2: Device permissions

Permissions

Files on the Device Operations allowed: Copy, Move, Open, Save, Delete, Execute

Incoming Files

Full access

Operations allowed: Save, Move, Copy This means that a file can be saved, moved, and copied to the device. Operations allowed: Save, Move, Copy

Read and write only

Operations allowed: Copy, Move, Open, Save, Delete Operation blocked: Execute

Read and execute only

Operations allowed: Copy, Open, Execute Operations blocked: Save, Move, Delete

Operations blocked: Save, Move, Copy

Read only

Operations allowed: Copy, Open Operations blocked: Save, Move, Delete, Execute

Operations blocked: Save, Move, Copy

No access

Any attempt to access the device or network resource is automatically blocked.

Operations blocked: Save, Move, Copy

Note: The antivirus feature in OfficeScan complements Device Control. For example, if Device Cont rol allows a file to open from a regulated device but OfficeScan detects that the file is infected, a scan action will still be performed on the file to eliminate the malware. 47

4. Select whether to display a notification message on the client computer when OfficeScan detects unauthorized device access. 5. If you selected domain(s) or client(s) on the client tree, click Save to apply settings to the domain(s) or client(s). If you selected the root icon , choose from the following options: Apply to All Clients: Applies settings to all existing clients and to any new client added to an existing/future domain. Future domains are domains not yet created at the time you configure the settings. Apply to Future Domains Only: Applies settings only to clients added to future domains. This option will not apply settings to new clients added to an existing domain.

5.2.2. How Behavior Monitoring and Device Control Can Affect Performance
The Behavior Monitoring and Device Control features both use the Trend Micro Unauthorized Change Prevention Service (running under the process name TMBMSRV.EXE). These features use TMBMSRV.EXE to monitor for system events and check these events against rules to determine whether certain application activities are unwanted. TMBMSRV.EXE delivers highly beneficial behavior-based security functionality, particularly the capability to check applications for suspicious behavior (Behavior Monitoring) and control access to storage devices (Device Control). Its monitoring mechanism, however, can strain system resources, especially when the computer is running applications that cause numerous system events. To prevent impacting system performance, Trend Micro recommends configuring OfficeScan so that these system-intensive applications are not monitored by TMBMSRV.EXE.

5.2.3. Deploying Behavior Monitoring and Device Control

Running TMBMSRV.EXE and system-intensive applications on the same computer can affect system performance and disrupt critical applications. It is for this reason that a properly managed deployment of Behavior Monitoring and Device Control is recommended. To ensure smooth deployment of OfficeScan with Behavior Monitoring and Device Control: Set up and deploy a pilot environment. Identify system-intensive applications. Add system-intensive applications to the Behavior Monitoring exception list.

Step 1: Preparing a Pilot Environment

Before performing a full-scale deployment, conduct a pilot deployment in a controlled environment. A pilot deployment provides opportunity to determine how features work and, most importantly, how Behavior Monitoring and Device Control can affect your endpoints. The pilot process should result in: A better understanding of the implications of deploying the new Behavior Monitoring and Device Control features. A better understanding of applications that may conflict with these features. A list of applications that can be added to the Behavior Monitoring exception list.

48

When setting up the pilot environment: Prepare an environment that matches the production environment as closely as possible. Ensure that the following are included in the pilot environment: o Business applications o Custom applications o All network applications used by groups or individuals (such as payroll, inventory, accounting, and database applications) Deploy the OfficeScan clients into the pilot environment with the features that you intend to enable. For example, Behavior Monitoring and Device Control may both be enabled. Allow the pilot environment to run for a reasonable amount of time (give sufficient soak time) with the standard applications running and with average daily use.

Step 2: Identifying System Intensive Applications

Trend Micro provides a standalone performance tuning tool to help identify applications that could potentially cause a performance impact. The TMPerfTool tool, available from Trend Micro technical Support, should be run on a standard workstation image and/or a few target workstations during the pilot process to preempt performance issues in the actual deployment of Behavioral Monitoring and Device Control. To identify system intensive applications: 1. Unzip the TMPerfTool.zip file. 2. Place the TMPerfTool.exe file in the OfficeScan default installation folder (%ProgramDir%/Trend Micro/OfficeScan Client) or in the same folder as the TMBMCLI.dll file. 3. Double-click TMPerfTool.exe. 4. Click Analyze when the system or applications start to slow down. If a red highlighted row appears, it means that the TMPerfTool found the system-intensive process. 5. Select the highlighted row and click Exclude. 6. After excluding the process, verify if the system or application performance improves. If the performance improves, select the process row again and click Include. If the performance drops again, it means you found a system-intensive application. Perform the following: a) Note the name of the application. b) Click Stop. c) Click Report and save the .xml file in your specified folder. d) Review the applications that have been identified as conflicting and add the applications to the Behavior Monitoring exception list.

Step 3: Adding System-Intensive Applications to the Behavior Monitoring Exception List

The Behavior Monitoring exception list is a user-configurable list of approved and blocked programs that are not monitored by Behavior Monitoring and Device Control. These features automatically allow approved programs to continueapproved programs are still checked by other OfficeScan features. Blocked programs are never allowed to run. Trend Micro strongly recommends adding system-intensive applications to the Behavior Monitoring exception list to reduce the likelihood of performance issues from occurring. System-intensive applications can cause TMBMSRV.EXE (the service used by both Behavior Monitoring and Device Control) to consume very high amounts of CPU resources and disrupt critical applications.

49

Figure 1-4: Adding programs to the exception list

To add programs to the exception list: Path: Networked Computers > Client Management > Setti ngs > Behavior Monitoring Settings 1. Type the full path of the program under Exceptions. Note: Separate multiple entries with semicolons (;). The exception list supports wildcards and UNC paths. 2. Click Approved Programs or Blocked Programs Note: All exceptions apply to both Behavior Monitoring and Device Control. Add only verified programs to the Approved Programs list to ensure network security. 3. If you selected domain(s) or client(s) on the client tree, click Save to apply settings to the domain(s) or client(s). If you selected the root icon , choose from the following options: 1. Apply to All Clients: Applies settings to all existing clients and to any new client added to an existing/future domain. Future domains are domains not yet created at the time you configure the settings. 2. Apply to Future Domains Only: Applies settings only to clients added to future domains. This option will not apply settings to new clients added to an existing domain.

5.3 Alternative Ways to Prevent Performance Impact

To prevent TMBMSRV.EXE from affecting performance, you can disable the service itself or disable both Behavior Monitoring and Device Control. Warning: Disabling the Behavior Monitoring, Device Control, and other features may put your network at risk from new and suspicious attacks. Perform these actions only as a last resort. You can disable Behavior Monitoring and Device Control from the Web console or from the registry.

50

5.3.1

Disabling Features from the Web Console

Behavior Monitoring Path: Networked Computers > Client Management > Settings > Behavior Monitoring Settings To disable Behavior Monitoring, deselect the following options: Enable Malware Behavior Blocking Enable Event Monitoring If you selected domain(s) or client(s) on the client tree, click Save to apply settings to those domain(s) or client(s). If you selected the root icon , choose from the following options: Apply to All Clients Apply to Future Domains Only Device Control Path: Networked Computers > Client Management > Settings > Device Control To disable Device Control, deselect Enable Device Control. If you selected domain(s) or client(s) on the client tree, click Save to apply settings to the domain(s) or client(s). If you selected the root icon , choose from the following options: Apply to All Clients Apply to Future Domains Only

5.3.2

Stopping the Service

Disable Behavior Monitoring and Device Control by stopping the Trend Micro Unauthorized Change Prevention Service (TMBMSRV.EXE). Perform this task directly on each endpoint. Note: Starting and stopping services directly overrides settings on the console. However, these changes will not take effect if the Client Self-Protection feature is enabled. Disable Client Self-Protection before starting or stopping OfficeScan services. See the Administrators Guide for more information.

To stop the service: 1. Open the Services console. Click Start > Run. Type SERVICES.MSC and click Open. 2. In the Services console, stop Trend Micro Unauthorized Change Prevention Service.

6. Miscellaneous
6.1 Product Communication Ports

51

Port Number 1 Server Port Configurable in ofcscan.ini Master_DomainPort parameter. Default value is 8080.

Protocol HTTP

Traffic Direction Client to OSCE Server

Description The IIS / Apache web server listening port for the OfficeScan virtual directory. This is where clients download pattern file updates, and upload logs, quarantined files and status information. The virtual directory port setting must be consistent with the ofcscan.ini Master_DomainPort parameter.

Client Port

Configurable during installation. Stored in ofcscan.ini Client_LocalServer_ Port parameter Configurable during installation. Stored in ofcscan.ini Client_LocalServer_ Port parameter 80,8080, 443

HTTP

OSCE Server to Client

OfficeScan client listening port where CGI commands such as update notifications and configuration changes are received from the OSCE server. Update Agent hosts also use the Client Port to reply to download requests for scan engine and pattern file updates pulled by peer OSCE clients. This will be used for notification for updates from Control Manager as well as sending back status/virus events from Officescan Server to Control Manager Integrated Smart Protection Server ports on IIS. Scan server uses this port to receive queries from OfficeScan clients as part of cloud technology. When using OfficeScan virtual site, the scan server uses port 4345 if the OfficeScan management console uses HTTP. If HTTPS functionality is used, the scan server uses 4343. Integrated Smart Protection Server ports on Apache. Scan server uses this port to receive queries from OfficeScan clients as part of cloud technology. Integrated Web Reputation Service port on IIS. Local Web Reputation Service uses this port to receive queries from OfficeScan clients as part of cloud technology.

Client Port (Update Agent)

HTTP

Client to Update Agent

Control Manager Agent (MCP Agent)

HTTP/HTTPS

Bidirectional between Officescan Server and Control Manager Bidrectional

Integrated Smart Protection Server

8082, 4345

HTTP/HTTPS

Integrated Smart Protection Server Integrated Web Reputation Service

4343, 4345

HTTP/HTTPS

Bidrectional

5274

HTTP

Bidrectional

6.3 Update Architecture and Network Usage

6.3.1 The Update Process
OfficeScan Server
The process starts with the OfficeScan server downloading update packages. The server can be configured to get updates from several locations: o Trend Micros Active Update Server (Internet) Default method. It uses standard HTTP GET request to download update packages from the Internet. This only

52

requires the HTTP port (80) to be open from the OfficeScan server to the Internet. This can be triggered manually or on scheduled basis (Hourly, Daily, Weekly, or Monthly). Recommended setting is Hourly. o Trend Micro Control Manager (TMCM) server Control Manager notifies the OfficeScan server when an update is available for download. OfficeScan will then check its Update Source [ Updates | Server Update | Update Source ] setting to know where it should download the package via HTTP. By default, the Update Source is set to the Internet (Trends Active Update server). This can be pointed to the Control Manager server if desired (i.e. http://<server fqdn or ip address>/tvcsdownload/activeupdate). Custom Update Source (Other update source). Similar to the Internet update method except that the admin re-creates an Active Update (web) server and sets the OfficeScan server to point to the HTTP location (i.e. http://<server fqdn or ip address>/activeupdate). Control Manager and peer OfficeScan servers can service such request.

Update Agent
When the update package has been downloaded, the OfficeScan server notifies its Update Agents first that a new package is available. The Update Agents would then compare version information and download the package from its designated OfficeScan server as needed. The OfficeScan server waits for an acknowledgement command for the verification or download/update process to complete. If no acknowledgement is received, the OfficeScan server will wait to reach a timeout value before notifying the rest of its clients. Default timeout is 10 minutes and is configurable in Timeout for update agent parameter using SvrTune.exe [ Tools | Administrative Tools | Server Tuner ]. All communications are done through CGI commands via HTTP protocol. The OfficeScan server listens on its web server management port (typically 80 or 8080) while the Update Agents listen on its preconfigured port (randomly generated or manually defined during the OfficeScan server installation).

OfficeScan Client
Once the Update Agent notification process is completed, the OfficeScan server notifies the rest of its clients. Notification process is done by batches. The number by batch is configurable in Maximum Client Connections using SvrTune.exe [ Tools | Administrative Tools | Server Tuner ] utility. Once notified, clients would check for updates in the order below. OfficeScan Client Update Source Order 1. Update Agent 2. OfficeScan Server 3. Trend Micros Active Update Server (Internet) Privileges can be set to allow clients to update from the OfficeScan server when its Update Agent is unavailable. This setting is global and can be enabled under [ Updates | Client Deployment | Update Source | Update from OfficeScan server if all customized sources are not available or not found ]. NOTE: SvrTune.exe only controls the number of clients notified by the OfficeScan server at a given time after OfficeScan server completed an update. When OfficeScan clients are the ones who initiated the update, for example via Scheduled Update, the OfficeScan server will handle the client update request and the ones it cannot is queued in IIS for later processing. (IIS can process concurrently 256 cgi requests at a time, this is the default configuration.) Individual or group of clients (OfficeScan Domain) can also be given privileges to download updates directly from the Internet. Highlight the client or Domain from the [ Clients ] main window and enable the option under [ Clients | Client Privileges/Settings | Update Settings | Download from the Trend Micro ActiveUpdate Server ]. 53

Integrated Smart Protection Server

o Trend Micros Active Update Server (Internet) Default method. It uses standard HTTP GET request to download update packages from the Internet. This only requires the HTTP port (80) to be open from the OfficeScan server to the Internet. This can be triggered manually or on scheduled basis (Hourly or every 15 minutes). Recommended setting is Hourly. Trend Micro Control Manager (TMCM) server Control Manager notifies the OfficeScan server when an update is available for download. OfficeScan will then check its Update Source [ Updates | Server Update | Update Source ] setting to know where it should download the package via HTTP. By default, the Update Source is set to the Internet (Trends Active Update server). This can be pointed to the Control Manager server if desired (i.e. http://<server fqdn or ip address>/tvcsdownload/activeupdate). NOTE: Before connecting OfficeScan 10.5 to TMCM 3.5 or 5.0 make sure following hotfixes are installed on TMCM to support Smart Scan. TMCM 5.0 Patch 3 + Hotfix 1740 TMCM 3.5 Patch 6+ Hotfix 1599 o Custom Update Source (Other update source). Similar to the Internet update method except that the admin re-creates an Active Update (web) server and sets the OfficeScan server to point to the HTTP location (i.e. http://<server fqdn or ip address>/officescan/download). Control Manager and peer OfficeScan servers can service such request.

6.2.2

Network Usage (Bandwidth Consumption)

OfficeScan generates network traffic when the server and client communicate with each other. Server initiated communications are mainly CGI commands sent through HTTP protocol and are only a few kilobytes in size. The clients, on the other hand, generate traffic as they upload information and pull component updates. Below is a summary of the different types of communications within OfficeScan. Server Initiated Traffic Notification on configuration changes Notification on component updates

Client Initiated Traffic Client start-up information Uploading virus,event, firewall and web reputation logs Infected files to be quarantined on the OfficeScan server (network usage depends on quarantined file size) Downloading program and pattern file updates

Probably the most significant data transfer is when a client performs a pattern file update. To reduce network traffic generated during this process, OfficeScan uses a feature called incremental updates. Instead of downloading the full pattern each and every time, only the differences (deltas) are downloaded for up to 14 previous versions for virus definitions and 7 previous versions for spyware, network, and damage cleanup patterns. These new patterns are merged with the old pattern file as they are received by the OfficeScan client. An incremental pattern may range from 1 kilobyte to several megabytes (i.e. 3 MB) depending on version increment (how far the delta is to the latest version). To further save WAN bandwidth, specific clients can be promoted as an Update Agent to service peer clients. This implies that each client wont have to individually pull incremental updates from the OfficeScan server. The Update Agent host replicates the complete engine and pattern packages (full 54

version and increments). The engine and pattern packages are downloaded every time an update is available. To verify the latest size, simply log in to the OfficeScan server and view the size property of the folders below: <drive>: \ Program Files \ Trend Micro \ OfficeScan \ PCCSRV \ Download \ Engine <drive>: \ Program Files \ Trend Micro \ OfficeScan \ PCCSRV \ Download \ Pattern The Engine and Pattern subfolders in the OfficeScan server are copied over to the Update Agent host under <drive> : \ Program Files \ Trend Micro \ OfficeScan Client \ ActiveUpdate folder.

For locations with limited bandwidth connectivity, an ini flag (UADuplicationOptValue) can be enabled in the OfficeScan server to change the behavior of the Update Agent. Instead of downloading the complete engine and pattern packages, only the latest increment (one version older) is downloaded. The Update Agent then generates its own full pattern file as well as the 7 incremental files.

Enabling Smart Duplicate for Update Agents

1. Edit <drive>: \ Program Files \ Trend Micro \ OfficeScan \ PCCSRV \ ofcscan.ini 2. Locate the parameter UADuplicationOptValue and set value to 128. 3. Save changes on the INI file. 4. Log on to the Management Console Clients | Global Client Settings 5. Click on Save button. NOTE: To disable Smart Duplicate if bandwidth is not an issue, configure the parameter as follows: UADuplicationOptValue=64

Sample computation of bandwidth usage: Given: An incremental update is 300Kb A full compressed pattern is 45MB

For an Update Agent using regular incremental updates, it downloads the full pattern file and 7 incremental files from the Officesan server Total size downloaded = 7x(300kb incremental) + 45Mb full Pattern = 2.1MB + 45Mb = 47.1Mb

For an Update Agent configured for Smart Duplicate, it downloads only one incremental the full pattern file and generates its own full pattern and incremental, therefore Total size download = 300Kb Saves you 46.8Mb of transfer over the WAN link.

6.4 Virtual Desktop Infrastructure (VDI)

OfficeScan 10.5 supports two types of VDI environment: Citrix XenDesktop 4 and VMWare View 4. Following two features have been added: VM Awareness to avoid all VM clients in the same physical machine to do on-demand scan or component update at the same time.

55

Whitelist Cache Mechanism to reduce scan time of on-demand scan.

6.4.1

Golden Image Preparation

1. Copy the TcacheGen.exe utility to the Golden Image. 2. Use TcacheGen to create a whitelist of files and folders in the Golden Image. The tool will scan files and folders in the Golden Image and add them into the OfficeScan Whitelist to reduce scanning load on the machine. 3. Use TcacheGen to clear the GUID key found in the OfficeScan Client Registry Hive: HKEY_Local_Machine\Software\TrendMicro\Pc-cillinNTCorp\CurrentVersion\GUID 4. Set the value of VDIEnabled=1 in OfficeScan registry hive: HKEY_Local_Machine\Software\TrendMicro\Pc-cillinNTCorp\CurrentVersion\MISC.\ 5. Proceed to complete the Golden Image creation.

When deploying VDI, the following tasks need to be completed on the Golden Image.

6.4.2

Install the VDI Support in OfficeScan server Plugin Manager

1. Open the OfficeScan Console >> Plug-in Manager. Download and install the VDI Support component. 2. Click on the Manage Program button to configure VDI Support.

3. Choose between VMWare vCenter Server on Citrix XenServer 4. Enter the server connection information.

5.

Click the save button.

6. Check the vdi_list.ini to confirm the setting is applied correctly. 7. Adjust the VDI parameters depending on the actual need. 56

We can control 2 very resource intensive actions from the OfficeScan Client namely On-demand Scan and Component Updates. VDI.ini parameters description and their recommended values are: Parameter Name Cache_Time_Seconds Description This is the VDI client cache used by the OfficeScan server. When VDI client performs a scan/update, OfficeScan server uses the cache information to respond. After the default value of 300 seconds, OfficeScan server will query XenServer/vCenter to update cache information. When OfficeScan server tries to query XenServer/vCenter to get updated cache information but couldnt (Failed), within 30 secs, OfficeScan server will use old cache to respond to clients request and will not try the query again within the elapse time. The number of VDI Client tasks controlled by OfficeScan server, currently we have 2 types, (00) is for on-demand scan and (01) is for update. Within 300 seconds, if the ondemand scan client didnt respond to the OfficeScan server, the OfficeScan server considers the scan task completed and will allow the next client to run on-demand scan. Only one client can run ondemand scan at the same time. If the MaxConcurrentGuests value is reached, other requesting VDI clients need to wait 10 secs and then 10+10 secs, 10+10+10 secs, till it reaches MaxWaitingTime value. Used by BaseWaitingTime to determine how long VDI Client should wait before trying to contact the OfficeScan server Name of the VDI Client Task Within 600 seconds, if the updating client didnt respond to the OfficeScan server, the Value 300

Cache_Time_Error_Seconds

30

Controller_Counts

Controller_00_MaxRunningSeconds

300

Controller_00_MaxConcurrentGuests

Controller_00_BaseWaitingTime

10

Controller_00_MaxWaitingTime

30

Controller_00_TaskName Controller_01_MaxRunningSeconds

ODScan 600

57

Controller_01_MaxConcurrentGuests Controller_01_TaskName

OfficeScan server considers the update task completed and will allow the next client to perform an update Only three clients can perform an update at the same time. Name of the VDI Client Task

3 PatternUpdate

6.4.3

Performance Related Items

To mitigate performance issue, you should comply with the best practices below when running OfficeScan 10.5 client in VDI environment. 1. Suggest to first set scan mode to smart scan, and then deploy OfficeScan client to VDI 2. Do not switch between conventional scan and smart scan on VDI guest environment. This is because scan type change will trigger full pattern update immediately on the guest environment causing Disk I/O congestion if occurring on multiple VM images at the same time. 3. When Smart Protection Server is offline, OfficeScan clients will add files into a queue list (suspicious list). When the Smart Protection Server comes back online, all the machines will perform a scan base on this list and can cause performance issue. Make sure to have a backup Smart Protection Server to ensure the Smart Scanning is available at all times. 4. Pattern Update rollback is very Disk I/O intensive and should be done as seldom as possible. 5. Take special caution deploying program updates or hotfix to VDI Clients. Deploy to a few machines at a time to minimize performance impact. 6. AEGIS is should be disabled in VDI environment and this should be done when golden image is prepared. This can help improve performance in VDI environment. 7. Enable/Disable firewall should not be performed on all clients at the same time; otherwise it will have heavy disk I/O usage.

8. If many clients are enabled to act as update agent at the same time then this will have heavy disk I/O and CPU, and will need long time to enable. It is recommended to avoid enabling many clients to act as update agents at the same time.

6.5 Recommended Installation Adjustments for Special Environments

6.5.1 Migration of Unsupported Platforms
In OfficeScan 8.0/10.0, there are several OS platforms that were dropped. Among these platforms are the Windows 95/98/ME, Windows NT and IA64 architecture. After an upgrade of previous versions of Officescan server to version 10.5, the Officescan clients that are unsupported will not appear in the management console. The Officescan server will generate a list of these clients into a file C:\Program Files\Trend Micro\Officescan\PCCSRV\Private\unsupCln.txt. To continue updating and managing these clients, a tool (clientmover.exe) has been provided to migrate the clients to a version of Officescan server that supports these clients. In order to migrate: 1. Setup an older version of Officescan server i.e. version 7.3 2. From the OfficeScan 10.5 server, in the command prompt, go to C:\Program Files\Trend Micro\Officescan\PCCSRV\Admin\Utility\Clientmover folder

58

3. Run the tool with the following parameters: ClientMover.exe [/P:ExportDataPath] [/S:ServerIP:port] [/N] [/V] Where: /P is the path of the unsupported client list generated by the OfficeScan 10.5 server. /S is the older version of Officescan server that these clients will be moved to and the server port. /N allows you to notify and then move the clients to the previous version of the OfficeScan server /V verifies if the tool successfully moved the clients. /F force the notification or verification without checking the current client status. Example: ClientMover /P:C:\Program Files\Trend Micro\OfficeScan\PCCSRV\Private\unsupcln.txt /S:10.20.30.40:8080 /N /V 4. The result of the move will be logged into a file under C:\Program Files\TrendMicro\OfficeScan\PCCSRV\Private\. The log file name is in the following format: unsupcln.txt.log.{date_time} Example: unsupcln.txt.log.20061201_162502

6.5.2 Citrix Environment 6.5.2.1 Installation of Officescan Clients on Citrix Servers

b. Installation of Officescan Clients on Citrix servers may need some special configuration due to the architectural limitation of Officescan Clients. This includes the issue wherein a session of a Citrix client generates a PCCNTMON.exe process created on the Citrix Server. If there are 500 Citrix clients connected, there may be 500 PCCNTMON.exe process running. This may use up the Citrix Server resource. In the previous version of Officescan, tweaks on ini file and registry is needed to workaround the issue. For this version, you just need to do the following: 1. Login to the Officescan Server Management console 2. Go to Networked computers| Client Management 3. From the Client tree, expand the domain and highlight the Citrix Servers (hold down CTRL key to select multiple servers) 4. On the top menu, select Settings | Privileges and Other Settings | Other Settings 5. Put a check mark on Do not allow users to access the client console from the system tray or Windows Start menu 6. Click on Save button

Note: The only minimal side effect for this configuration is that there will be no popup messages that will come up on the Citrix Servers whenever a virus/malware, spyware/grayware, or web threats are detected

59

c.

When the OfficeScan client is installed to a Citrix server, Citrix clients currently connected to the Citrix server may become disconnected.

To address this issue, do the following before installing the client: 1. Open Registry Editor on the Citrix server. Important: Always back up the whole registry before making any modifications. Incorrect changes to the registry can cause serious system problems. 2. Go to HKLM\SOFTWARE\TrendMicro\NSC\TmProxy\WhiteList 3. Click Edit > New > Key and name the key IIS. 4. Under this new key, create the following value: Type: String value Name: ProcessImageName Value: w3wp.exe

6.5.2.2

Citrix Known Issues

A. Unsupported Citrix Features and Functions

1. The OfficeScan client on the Citrix server cannot be published. To allow users to access the OfficeScan client, publish the Citrix Server desktop through the Citrix Access Management Console (CMC). When published, users need to: a. Launch the desktop from the Citrix client Web interface. b. In the Citrix desktop session, open the OfficeScan client program from Start > Programs > Trend Micro OfficeScan Client > OfficeScan Client. c. Launch the OfficeScan client console from the system tray icon. 2. The OfficeScan client cannot be streamed because the OfficeScan client profile created by Citrix Streaming Profiler does not function correctly during streaming. This means that some functions may appear to execute properly from the client console but may actually not run anything in the backend. Other programs published and streamed on the Citrix server are expected to work properly.

B. Scanning
1. A drive or folder on a computer running Windows 2003 contains a file infected with virus/malware and the drive or folder is mapped to the Citrix server. When the infected file is opened during a Citrix client session, Real-time Scan may be unable to detect the virus/malware on the file if the mapped drive has the same drive name, for example (C, in a multi-user environment. To resolve this issue: d. Open Registry Editor. Important: Always back up the whole registry before making any modifications. Incorrect changes to the registry can cause serious system problems.

e. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TmPreFilter and add the following value: Type: Multi-string value (REG_MULTI_SZ)

60

Name: DependOnService Value: Cdm

f.

Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TmFilter\Param eters and add the following value:

Type: DWORD value (REG_DWORD) Name: CitrixOn2003Support Value: Any number except zero

If you are using remote desktop, add the following value to the same key: Type: DWORD value (REG_DWORD) Name: MsRemoteDesktopSupport Value: Any number except zero

g. Restart the machine for the changes to take effect.

h. When the OfficeScan client detects a security risk during a particular user session, the notification message for the security risk displays on all active user sessions. Warn users about this limitation or disable the notification if you do not want the notifications displaying on all user sessions. Security risk can be any of the following: Virus/Malware Spyware/Grayware Firewall policy violation Web Reputation policy violation

i. Updates
When manual update is in progress in one Citrix client session, other active sessions cannot launch manual update. Trend Micro recommends disabling manual update from the OfficeScan server Web console so users cannot run manual update. Aside from manual update, clients get updated through scheduled update or event-triggered update.

6.5.2.3

Citrix Exclusions

Refer to section 6.6 Recommended Scan-Exclusion List for recommendations on files and directories to exclude.

61

6.5.2.4

Citrix Firewall Port

Refer to section 6.7 Some Server Common Ports for recommendations on Citrix ports to open.

6.5.3 Installation of OfficeScan Clients on Cisco Callmanager

The following are needed to be configured as recommended to support Cisco Callmanager: 2. Configure Real-time Scan Settings a. Login to the OfficeScan Management console b. Go to Networked Computers| Client Management c. From the Client tree, expand the domain and highlight the Cisco Callmanager Clients

d. On the top menu, select Settings | Real-time Scan Settings e. Under the Scan Settings in the Target tab, configure Do not scan compressed files if the number of compression layers exceeds to scan only 1 layer f. In the Action tab, uncheck the following: Display a notification message on the client computer when virus/malware is detected Display a notification message on the client computer when spyware/grayware is detected g. Click on Save button

3. Configure Client Privileges and Settings a. Login to the OfficeScan Management console b. Go to Networked Computers| Client Management c. From the Client tree, expand the domain and highlight the Cisco Callmanager Clients

d. On the top menu, select Settings | Privileges and Other Settings e. Uncheck the following: Display the Mail Scan tab on the client console and allow users to install/upgrade Outlook mail scan Display the Toolbox tab on the client console and allow users to install Check Point SecureClient Support f. Click on Save button

4. Configure Scan Exclusions a. Login to the OfficeScan Management console b. Go to Networked Computers| Client Management c. From the Client tree, expand the domain and highlight the Cisco Callmanager Clients

d. On the top menu, select Settings | Real-time Scan Settings e. Under the Scan Exclusion in the Target tab, enable the following: 62

Enable scan exclusion Apply scan exclusion settings to all scan types f. Add the following folders to the Scan Exclusion List (Directories) Drive:\Program Files\Call Manager Drive:\Program Files\Call Manager Serviceability Drive:\Program Files\Call Manager Attendant g. Click on Save button

5. Configure Update Settings a. Login to the OfficeScan Management console b. Go to Updates | Networked Computers | Automatic Update c. Uncheck Perform Scan Now after update (excluding roaming clients)

d. Click on Save button

6. Turn off Scheduled Scan for Virus/Malware and Spyware/Grayware a. Login to the OfficeScan Management console b. Go to Networked Computers | Client Management c. From the Client tree, expand the domain and highlight the Cisco Callmanager Clients

d. On the top menu, select Settings | Scheduled Scan Settings e. Under the Virus/Malware Scan tab, uncheck Enable virus/malware scan f. Under the Spyware/Grayware Scan tab, uncheck Enable spyware/grayware scan

g. Click on Save button

7. Turn off/disable OfficeScan Firewall As much as possible, do not activate firewall on the OfficeScan server when Callmanager will be managed. If already activated and OSCE clients are installed, you need to disable the firewall from the Product Registration Page, then reinstall the OfficeScan clients installed on the Callmanager servers

6.6 Recommended Scan-Exclusion List

Database and encrypted type files should generally be excluded from scanning to avoid performance and functionality issues. Below are exclusions to consider depending on the type of machine you are installing the OfficeScan client on. General Exclusions for all Windows platforms Pagefile.sys *.pst %systemroot%\System32\Spool (replace %systemroot% with actual directory) %systemroot%\SoftwareDistribution\Datastore (replace %systemroot% with actual directory) %allusersprofile%\NTUser.pol %Systemroot%\system32\GroupPolicy\registry.pol

63

Microsoft Active Directory Domain Controller <drive>: \ WINNT \ SYSVOL <drive>: \ WINNT \ NTDS <drive>: \ WINNT \ ntfrs <drive>: \ WINNT \ system32 \ dhcp <drive> : \ WINNT \ system32 \ dns Microsoft IIS Server Web Server log files should be excluded from scanning. By default, IIS logs are saved in <drive>: \ WINNT \ system32 \ LogFiles <drive>: \ WINNT \ system32 \ IIS Temporary Compressed Files Microsoft IIS 7.0 Server Web Server log files should be excluded from scanning. By default, IIS logs are saved in <drive>:\inetpub\logs\ Domino Data Directory The data directory is used to store Domino email messages. Repeated scanning of this folder while it is being updated with new messages is not an efficient way to scan locally stored email. Use virus scanning applications like ScanMail for Domino to handle email viruses. By default, the Domino data directory for a non-partitioned installation is <drive>: \ Lotus \ Domino \ Data. Cisco CallManager Drive:\Program Files\Call Manager Drive:\Program Files\Call Manager Serviceability Drive:\Program Files\Call Manager Attendant

Microsoft SQL Server Because scanning may hinder performance, large databases should not be scanned. Since Microsoft SQL Server databases are dynamic, exclude the directory and backup folders from the scan list. If it is necessary to scan database files, a scheduled task can be created to scan them during off-peak hours. <drive>: \ Program Files \ Microsoft SQL Server \ MSSQL \ Data <drive: \ WINNT \ Cluster (if using SQL Clustering) Q:\ (if using SQL Clustering) C:\Program Files\Microsoft SQL Server\MSSQL.X\OLAP\Data File extensions to exclude: .mdf, .ldf, .ndf, .bak, .tm Cluster Servers Q:\ (Quorum drive) C:\Windows\Cluster

Microsoft SharePoint Portal Server <drive>: \ Program Files \ SharePoint Portal Server <drive>: \ Program Files \ Common Files \ Microsoft Shared \ Web Storage System <drive>: \ Windows \ Temp \ Frontpagetempdir M:\ Microsoft SharePoint Servers Foundation 2010 Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions 64

Drive:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files Drive:\Users\ServiceAccount\AppData\Local\Temp Drive:\Users\Default\AppData\Local\Temp Drive:\Users\the account that the search service is running as\AppData\Local\Temp Drive:\WINDOWS\system32\LogFiles Drive:\Windows\Syswow64\LogFiles Microsoft SharePoint Server 3.0 / 2007 / 2010 Drive:\Program Files\Microsoft Office Servers Drive:\Program Files\Common Files\Microsoft Shared\Web Service Extensions Drive:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config Drive:\Windows\Temp\WebTempDir Drive:\Documents and Settings\the account that the search service is running as\Local Settings\Temp\ Drive:\WINDOWS\system32\LogFiles Reference: http://support.microsoft.com/kb/952167 Microsoft Systems Management Server (SMS) SMS \ Inboxes \ SMS_Executive Thread Name SMS_CCM \ ServiceData

Microsoft Operations Manager Server (MOM) <drive>: \ Documents and Settings \ All Users \ Application Data \ Microsoft \ Microsoft Operations Manager <drive>: \ Program Files \ Microsoft Operations Manager 2005

Microsoft Internet Security and Acceleration Server (ISA) <drive>: \ Program Files \ Microsoft ISA Server \ ISALogs <drive>: \ Program Files \ Microsoft SQL Server \ MSSQL$MSFW \ Data

Microsoft Windows System Update Server (WSUS) <drive:> \ WSUS <drive:> \ WsusDatabase

VMWare Other file extension types that should be added to the exclusion list include large flat and designed files, such as VMWare disk partition. Scanning VMWare partitions while attempting to access them can affect session loading performance and the ability interact with the virtual machine. Exclusions can be configured for the directory(ies) that contain the Virtual Machines, or by excluding *.vmdk and *.vmem files.

Microsoft Exchange Server Exclude the directory or partition where MS Exchange stores its mailbox. Use virus scanning applications like ScanMail for Exchange to handle email viruses. Installable File System (IFS) drive M must also be excluded to prevent the corruption of the Exchange Information Store.

65

Exchange 5.5 o <drive>: \ EXCHSRVR \ IMCData o <drive>: \ EXCHSRVR \ MDBData

Exchange 2000 o <drive>: \ EXCHSRVR \ MDBData o <drive>: \ EXCHSRVR \ MTAData o <drive>: \ EXCHSRVR \ Mailroot o <drive>: \ EXCHSRVR \ SrsData o <drive>: \ WINNT \ system32 \ InetSrv

Exchange 2003 o <drive>: \ EXCHSRVR \ MDBData o <drive>: \ EXCHSRVR \ MTAData o <drive>: \ EXCHSRVR \ Mailroot o <drive>: \ EXCHSRVR \ SrsData o <drive>: \ WINNT \ system32 \ InetSrv o <drive>: \ EXCHSRVR \ MdbDataUtility

Exchange 2007 See http://technet.microsoft.com/en-us/library/bb332342.aspx exclusions required for the various Exchange 2007 roles

Mapped Drives / Shared Folders This option is best disabled. If it is enabled, it may create unnecessary network traffic when the end users access remote paths or mapped network drives. It can severely impact the users experience. Consider disabling this function if all workstations have OfficeScan client installed, and updated to the latest virus signature.

Volume Shadow Copies Backup process takes longer to finish when real-time scan is enabled. There are also instances when real-time scan detects an infected file in the volume shadow copy but cannot enforce the scan action because volume shadow copies have read-only access. It is also advisable to apply the latest Microsoft patches for the Volume Shadow Copies service: http://support.microsoft.com/kb/833167

Citrix Exclusions On Citrix systems following extensions have been causing performance problems. Exclude these file extensions to avoid any performance problems. *.LOG, *.DAT, *.TMP, *.POL, *.PF Novell Zenworks C:\Program Files\Novell\Zenworks Exclude the following files: NalView.exe, Rmenf.exe, ZenNotifyIcon.exe, ZenUserDaemon.exe, casa.msi, dluenf.dll, fileInfo.db, lcredmgr.dll, objInfo.db Exclude the following extensions: .APPSTATE, .LOG, .TMP, .ZC Other Trend Micro Products 66

Make sure the check box for Exclude from scanning the directories where Trend Micro products are installed is enabled in OfficeScans Exclusion List settings. Additional References: Microsoft Operating Systems: http://support.microsoft.com/kb/822158/ Microsoft SQL Server: http://support.microsoft.com/kb/309422 Microsoft Exchange 2003: http://support.microsoft.com/kb/823166 Microsoft Exchange 2000 : http://support.microsoft.com/kb/328841 Microsoft Exchange 2000/2003 : http://support.microsoft.com/kb/245822 Microsoft Exchange 2007 : http://technet.microsoft.com/en-us/library/bb332342.aspx Microsoft Sharepoint Portal Server : http://support.microsoft.com/kb/320111 Microsoft Systems Management Server : http://support.microsoft.com/kb/327453 Microsoft IIS : http ://support.microsoft.com/kb/817442 Domain Controllers: http://support.microsoft.com/kb/822158/en-us

6.7 Some Common Server Ports

Application FTP Telnet SMTP WINS Replication DNS Web server Kerberos Authentication POP3 Windows Time Synchronization Protocol NTP RPC NetBIOS Name, Netlogon and Browsing NetBIOS Session IMAP4 IMAP3 LDAP SSL (Secure Sockets Layer) Web server Server message block (SMB) for Netlogon, LDAP conversion, and Microsoft Distributed File System (DFS) discovery SQL Server PPTP Global Catalog LDAP Remote Desktop (Terminal Services) Citrix Server Ports 21 23 25 42 53 80 88 110 123 135 137,138 139 143 220 389 443 445 1433 1723 3268 3389 1494,2598 Protocol TCP TCP TCP TCP TCP/UDP TCP TCP/UDP TCP UDP TCP TCP UDP TCP TCP TCP/UDP TCP TCP TCP TCP TCP/UDP TCP TCP

Note: It is advisable to disable the firewall of the OSCE clients that are installed on the server platform.

67

Document Revision History

Date 8/16/2010 Revision Document created Editor Alp Deveci, Jill ChuaMaceda, Jessie Prevost, Alwin Yu Alp Deveci

9/9/2010

Edited and removed settings that changed since Beta

68