IMSVA 8.5 Administration Guide
IMSVA 8.5 Administration Guide
the product described herein without notice. Before installing and using the product,
please review the readme files, release notes, and/or the latest version of the applicable
documentation, which are available from the Trend Micro website at:
http://docs.trendmicro.com/en-us/enterprise/interscan-messaging-security.aspx
Trend Micro, the Trend Micro t-ball logo, Control Manager, eManager, InterScan, and
TrendLabs are trademarks or registered trademarks of Trend Micro Incorporated. All
other product or company names may be trademarks or registered trademarks of their
owners.
Copyright 2013. Trend Micro Incorporated. All rights reserved.
Document Part No.: MSEM85911/130322
Release Date: April 2013
Protected by U.S. Patent No.: Patents pending
This documentation introduces the main features of the product and/or provides
installation instructions for a production environment. Read through the documentation
before installing or using the product.
Detailed information about how to use specific features within the product may be
available in the Trend Micro Online Help and/or the Trend Micro Knowledge Base at
the Trend Micro website.
Trend Micro always seeks to improve its documentation. If you have questions,
comments, or suggestions about this or any Trend Micro document, please contact us at
docs@trendmicro.com.
Evaluate this documentation on the following site:
http://www.trendmicro.com/download/documentation/rating.asp
Table of Contents
Preface
Preface ................................................................................................................. xi
Whats New ....................................................................................................... xii
Audience ........................................................................................................... xix
InterScan Messaging Security Virtual Appliance Documentation ........... xix
Document Conventions .................................................................................. xx
Chapter 2:
Opening the IMSVA Management Console .............................................. 2-2
Viewing the Management Console Using Secure Socket Layer .............. 2-3
Setting Up a Child Device ............................................................................. 2-5
Using Smart Search ........................................................................................ 2-7
Changing the Management Console Password .......................................... 2-7
ii
Table of Contents
iii
iv
Table of Contents
vi
Table of Contents
vii
viii
Table of Contents
Appendices
Appendix A: Default Directory Locations
Default Mail Queues ..................................................................................... A-2
eManager, Virus and Program Logs ........................................................... A-4
Temporary Folder .......................................................................................... A-4
Notification Pickup Folder .......................................................................... A-4
Index
Index .............................................................................................................. IN-1
Preface
Preface
Welcome to the Trend Micro InterScan Messaging Security Virtual Appliance
Administrators Guide. This manual contains information on InterScan Messaging
Security Virtual Appliance (IMSVA) features, system requirements, as well as
instructions on installation and configuring IMSVA settings.
Refer to the IMSVA 8.5 Installation Guide for information on how to install and
upgrade IMSVA.
xi
Whats New
IMSVA 8.5 New Features
The following table provides an overview of new features available in IMSVA 8.5.
TABLE 1. IMSVA 8.5 New Features
NEW FEATURE
DESCRIPTION
Smart Scan
xii
DESCRIPTION
The Advanced Threat Scan Engine (ATSE) uses a
combination of pattern-based scanning and
aggressive heuristic scanning to detect document
exploits and other threats used in targeted attacks.
Preface
NEW FEATURE
DESCRIPTION
DESCRIPTION
Trend Micro Email Encryption integrates with IMSVA
to protect sensitive email content by encrypting
inbound and outbound email messages according to
specific policies.
IMSVA can also scan encrypted messages for
threats.
IMSVA provides reports and notifications to monitor
encrypted email traffic.
xiii
NEW FEATURE
DESCRIPTION
EUQ enhancement
xiv
DESCRIPTION
Cloud Pre-Filter
Preface
NEW FEATURE
Common Policy Objects
DESCRIPTION
Several information objects that can be used by
policies have been removed from policy creation and
given their own areas for configuration:
Address Groups
BATV Keys
Policy Notifications
Stamps
Web Reputation
BATV Support
Detection Capability
Enhancement
X-Header Support
xv
NEW FEATURE
DESCRIPTION
EUQ Enhancement
Antispoofing filter
xvi
DESCRIPTION
Preface
NEW FEATURE
DESCRIPTION
Self-contained Installation
Route Configuration
Multiple Antivirus and Malware
Policies
xvii
NEW FEATURE
Multiple Spam Prevention
Technologies
xviii
DESCRIPTION
Three layers of spam protection:
IntelliTrap
Delegated Administration
Migration
Preface
Audience
The IMSVA documentation is written for IT administrators in medium and large
enterprises. The documentation assumes that the reader has in-depth knowledge of
email messaging networks., including details related to the following:
LDAP
Database management
The documentation does not assume that the reader has any knowledge of antivirus or
antispam technology.
xix
Readme File
Contain late-breaking product information that might not be found in the
other documentation. Topics include a description of features, installation
tips, known issues, and product release history.
The Installation Guide, Administrators Guide and readme file are available at:
http://docs.trendmicro.com
Document Conventions
The documentation uses the following conventions:
TABLE 6. Document Conventions
CONVENTION
DESCRIPTION
UPPER CASE
Bold
Italics
Monospace
Note
Tip
xx
Configuration notes
Recommendations or suggestions
Preface
CONVENTION
Important
WARNING!
DESCRIPTION
Information regarding required or default configuration
settings and product limitations
Critical actions and configuration options
xxi
Part I
Getting Started
Chapter 1
About Command & Control (C&C) Contact Alert Services on page 1-17
1-1
DESCRIPTIONS
BENEFITS
1-2
Cloud-based
pre-filtering of
messages
Email
encryption
FEATURE
DESCRIPTIONS
BENEFITS
Advanced antimalware
protection
Command &
Control (C&C)
Contact Alert
Services
Regulatory
compliance
Smart Scan
GLBA
HIPAA
PCI-DSS
SB-1386
US PII
1-3
FEATURE
IntelliTrap
DESCRIPTIONS
BENEFITS
Real-time
Statistics and
Monitor
1-4
FEATURE
DESCRIPTIONS
BENEFITS
DoS attacks
Malicious
email content
Degradation of
services
Legal liability
and business
integrity
1-5
FEATURE
Mass mailing
virus
containment
DESCRIPTIONS
BENEFITS
1-6
FEATURE
DESCRIPTIONS
BENEFITS
Spam
Prevention
Solution (SPS)
Note
Activate SPS before you
configure IP Profiler and
Email reputation.
Administration and integration
LDAP and
domain-based
policies
1-7
FEATURE
BENEFITS
Web-based
management
console
End-User
Quarantine
(EUQ)
Delegated
administration
By delegating administrative
roles to different employees, you
can promote the sharing of
administrative duties.
Centralized
reporting
System
availability
monitor
1-8
DESCRIPTIONS
FEATURE
DESCRIPTIONS
BENEFITS
POP3
scanning
Integration
with Deep
Discovery
Advisor
Integration
with Trend
Micro Control
Manager
1-9
About Spyware/Grayware
Your clients are at risk from potential threats other than viruses/malware. Grayware can
negatively affect the performance of the computers on your network and introduce
significant security, confidentiality, and legal risks to your organization.
1-10
DESCRIPTION
Spyware
Adware
Dialers
Joke Programs
Hacking Tools
Password Cracking
Applications
Other
1-11
DESCRIPTION
Reduced computer
performance
Increased web
browser-related
crashes
Reduced user
efficiency
Degradation of
network bandwidth
1-12
Control Manager server: The Control Manager server is the machine upon which
the Control Manager application is installed. The web-based Control Manager
management console is hosted from this server.
Outbreak Prevention
Policy
DESCRIPTION
SUPPORTED?
No.
Yes
1-13
FEATURE
1-14
DESCRIPTION
SUPPORTED?
Yes
Single Sign-on
No.
Configuration
replication
Replicate configuration
settings from an existing
IMSVA server to a new
IMSVA server from Control
Manager.
Yes
Pattern update
Yes
Engine update
Yes
Product component
update
No.
Configuration by user
interface redirect
Yes
Renew product
registration
Yes
Customized reporting
from Control Manager
Yes
FEATURE
Control Manager agent
installation/
uninstallation
DESCRIPTION
Install or uninstall IMSVA
Control Manager agent from
Control Manager.
SUPPORTED?
No.
IMSVA Control Manager
agent is automatically
installed when you install
IMSVA. To enable/disable the
agent, do the following from
the IMSVA management
console:
1.
Go to Administration >
Connections.
2.
3.
To enable/disable the
agent, select/clear the
check box next to Enable
MCP Agent.
Event notification
Yes
Yes
1-15
1-16
1-17
With C&C Contact Alert Services, IMSVA has the ability to inspect the sender,
recipients and reply-to addresses in a message's header, as well as URLs in the message
body, to see if any of them matches known C&C objects. Administrators can configure
IMSVA to quarantine such messages and send a notification when a message is flagged.
IMSVA logs all detected email with C&C objects and the action taken on these
messages. IMSVA sends these logs to Control Manager for query purposes.
1-18
Chapter 2
This chapter explains how to log on to the management console and provides
instructions on what to do immediately after installation to get IMSVA up and running.
2-1
2.
3.
Password: imsva
What to do next
Trend Micro recommends changing the password regularly, to prevent unauthorized
access to the management console.
2-2
) icon next to
2-3
Create the Tomcat SSL certificate for the IMSVA management console, as follows:
$IMSS_HOME/UI/javaJRE/bin/keytool -genkey -alias tomcat keyalg RSA -sigalg SHA1withRSA -keystore
with a password value of changeit for both the certificate and the keystore itself
$IMSS_HOME/UI/tomcat/sslkey/.keystore -validity 3652
Create the Apache SSL certificate for the EUQ management console, as follows:
a.
b.
c.
d.
2-4
Procedure
1.
2.
After you set up a parent device (see Viewing the Management Console Using Secure
Socket Layer on page 2-3), do the following:
a.
b.
Log on to the management console. Make sure that you are logging on to the
parent device management console.
2-5
3.
4.
c.
d.
Under Add IP Address, add the IP address for the Internal Communication
Port of the child device.
Just as you did for the parent device, connect a management computer to the
child device and log on to the management console. All IMSVA devices have
the same management console logon credentials.
b.
In the Setup Wizard, configure the local system settings and then click
Next>.
c.
On the Deployment Settings screen, select Child Server and add the IP
address for the Internal Communication Port of the parent device.
d.
Click Finish.
b.
Verify that the child device appears under Managed Services and that a green
check mark ( ) appears under Connection. You can start or stop Scanner,
Policy, or EUQ services.
Note
If you enabled EUQ on the parent, it will also be enabled on the child.
5.
If you want to use EUQ on the child device, redistribute the data across the EUQ
databases:
a.
b.
2-6
c.
Click Redistribute.
Note
If you registered an EUQ-enabled child device to its parent device, add senders
to the approved senders list, and then re-distribute EUQ data. Some of the
newly added approved senders might not appear.
Trend Micro recommends the following:
After redistributing EUQ, the administrator informs all end users to verify
that the newly added approved senders are still available.
That the administrator notifies all end users not to add EUQ approved
senders list when the administrator is adding a child device and
redistributing EUQ.
Procedure
1.
2-7
2.
Specify the current password, the new password, and the new password
confirmation.
Note
A valid password can contain letters, numbers and the following characters: `~!@#$
%^&*()[]{}+-|:'<>?/,.= _.
The password must be between 4 and 32 alphanumeric characters.
3.
Click Save.
Procedure
1.
2-8
2.
Select Use a proxy server for updates to patterns, engines, licenses, Web
Reputation queries, Cloud Pre-Filter, and Trend Micro Email Encryption.
3.
4.
5.
Specify the port the proxy server uses to connect to the Internet.
6.
Specify the user name you need for administrative access to the proxy server.
7.
8.
Click Save.
2-9
IMSVA Services
The scanner and policy services must be started to start protecting your network using
IMSVA. You can, however, choose whether to install or start the EUQ service.
Policy Services: Acts as a remote store of rules for the scanner services to enhance
rule lookups.
2-10
Go to System Status.
2.
Under the Managed Services Settings section, click the Start or Stop button for the
service(s) that you would like to start or stop.
2-11
2.
Smart Scan: Smart scan leverages threat signatures that are stored in the
cloud.
When in Smart Scan mode, IMSVA uses the Smart Scan Agent Pattern to
check for security risks. The Smart Scan Agent Pattern is updated daily by
Trend Micro and delivers the same protection provided by conventional antimalware and antispyware patterns. If the Smart Scan Agent Pattern cannot
determine the reputation of a file, IMSVA queries the Smart Protection
Network to provide up-to-date protection.
2-12
3.
4.
Optional: Use an HTTP proxy server to connect to the Smart Protection Network.
Specify the following:
User name
Password
Click Save.
Note
IMSVA automatically restarts the scanner service (imssd) whenever you change your
scan method settings.
2-13
Chapter 3
3-1
Full: Users have complete access to the features and settings contained in the
menu item.
Read: Users can view features and settings contained in the menu item, but cannot
modify them.
None: Users will not see the menu item, preventing them from viewing or
configuring any of the settings in the menu item.
Procedure
1.
2.
3-2
Click Add.
3.
b.
4.
3-3
5.
3-4
Select Full, Read, or None for each of the following access areas that appear
on the IMSVA management console menu:
Summary
Cloud Pre-Filter
Policy
IP Filtering
Reports
Logs
Administration
b.
Click Save.
Note
Only the default IMSVA administrator account can add new administrator accounts.
Custom administrator accounts cannot do so even if you assign full permission to the
Administration area.
Custom administrator accounts with full administration rights can only change their
own IMSVA passwords. If you forget the default administrator account password,
contact Trend Micro technical support to reset the password.
2.
3.
4.
Click Save.
3-5
2.
Click Delete.
3.
Click OK.
Note
You can only delete custom administrator accounts, not the default IMSVA
administrator account.
3-6
Chapter 4
4-1
2.
4.
Password: imsva
4-2
Click Next.
The Local System Settings screen appears.
4-3
2.
Modify the device host name, internal communication port, IP address, and
netmask if necessary. Also, configure your network settings and set the device
system time.
Note
The local system settings take effect immediately when you click the Next > button.
If the IP address or time settings are changed, IMSVA will restart. Wait until IMSVA
is online and then log on again.
Click Next.
The Deployment Settings screen appears.
2.
Select Parent or Child. If this is the first device you are setting up, you must select
Parent. You can configure additional child devices at a later time.
To deploy the device between upstream and downstream MTAs, clear the gateway
deployment check box.
4-4
Click Next.
The SMTP Routing screen appears.
4-5
4-6
2.
Click Next.
The Notification Settings screen appears.
2.
Sender's email address: Specify the email address to appear as the sender.
SMTP server address: Specify the Fully Qualified Domain Name (FQDN)
or the IP address of the SMTP server that delivers email on the network.
4-7
3.
SMTP server port: Specify the port number that IMSVA uses to connect to
the SMTP server.
Preferred charset: IMSVA will use this setting to encode the notification
messages.
Message header: Specify the text to appear at the top of the notification.
Message footer: Specify the text to appear at the bottom of the notification.
Click Next.
The Update Source screen appears.
4-8
2.
Configure the following update settings, which will determine from where IMSVA
will receive its component updates and through which proxy (if any) IMSVA needs
to connect to access the Internet:
Proxy Settings: Select the Use a proxy server for updates to patterns,
engines, licenses, Web Reputation queries, Cloud Pre-Filter, and Trend
Micro Email Encryption check box and configure the proxy type, server
name, port, user name, and passwords.
4-9
Procedure
1.
Click Next.
The LDAP Settings screen appears.
4-10
2.
3.
Domino
4-11
OpenLDAP
b.
To enable one or both LDAP servers, select the check boxes next to Enable
LDAP 1 or Enable LDAP 2.
c.
Specify the names of the LDAP servers and the port numbers they listen on.
d.
Under LDAP cache expiration for policy services and EUQ services,
specify a number that represents the time to live next to the Time to Live in
minutes field.
e.
LDAP ADMIN
ACCOUNT
(EXAMPLES)
Without
Kerberos:
user1@domain.c
om (UPN) or
domain\user1
With Kerberos:
user1@domain.c
om
4-12
BASE
DISTINGUISHED
NAME (EXAMPLES)
dc=domain,
dc=com
AUTHENTICATION
METHOD
Simple
Advanced (with
Kerberos)
LDAP SERVER
Active Directory
Global Catalog
LDAP ADMIN
ACCOUNT
(EXAMPLES)
Without
Kerberos:
user1@domain.c
om (UPN) or
domain\user1
With Kerberos:
BASE
DISTINGUISHED
NAME (EXAMPLES)
dc=domain,
dc=com
dc=domain1,dc=c
om (if mutiple
unique domains
exist)
AUTHENTICATION
METHOD
Simple
Advanced (with
Kerberos)
user1@domain.c
om
f.
OpenLDAP
cn=manager,
dc=test1, dc=com
dc=test1, dc=com
Simple
Lotus Domino
user1/domain
Not applicable
Simple
Sun iPlanet
Directory
uid=user1,
ou=people,
dc=domain,
dc=com
dc=domain,
dc=com
Simple
If you are configuring a rule for outgoing messages, the internal address list applies
to the senders.
If you are configuring a rule for incoming messages, the internal address list applies
to the recipients.
4-13
Procedure
1.
Click Next.
The Internal Addresses screen appears.
2.
4-14
Select Enter domain from the drop-down list, specify the domain in the text
box, and then click >>.
Select Search for LDAP groups from the drop-down list. A screen for
selecting the LDAP groups appears. Specify an LDAP group name to search
in the text box and click Search. The search result appears in the list box. To
add it to the Selected list, click >>.
Click the Import button to import a text file containing a list of predefined
domains.
Note
IMSVA can only import a domain list from a text file (.txt). Ensure that the text file
contains only one domain per line. You can also use wildcard characters to specify
the domain. For example, *.com or *.example.com.
Click Next.
The TMCM Server Settings screen appears.
4-15
2.
b.
c.
d.
4-16
Under Web server authentication, specify the user name and password for
the web server if it requires authentication.
e.
f.
Specify the proxy server port number, user name, and password.
Click Next.
The Product Activation screen appears.
2.
To obtain an Activation Code, click Register Online and follow the directions at
the Trend Micro Registration website.
3.
After obtaining the applicable Activation Codes, specify the Activation Code for
each product or service to activate.
4-17
Click Next.
A Review Settings screen appears.
2.
4-18
Chapter 5
Updating Components
This chapter explains how to update IMSVA components.
Topics include:
5-1
5-2
DESCRIPTION
Advanced Threat
Scan Engine
Virus Pattern
Spyware Pattern
IntelliTrap Pattern
IntelliTrap
Exception Pattern
Antispam Engine
Antispam Pattern
URL Filtering
Engine
Updating Components
COMPONENT
DESCRIPTION
2.
3.
5-3
4.
Click Save.
If you are using the Configuration Wizard, click Next.
If you suspect that your networks security is compromised by new malware and
would like to update the components immediately.
Procedure
1.
5-4
Updating Components
2.
Under Components, verify the version numbers of the antivirus, antispyware, and
antispam components that IMSVA uses to protect your network.
3.
To update all components, select the first check box on the column header next to
the Name field. To update specific component(s), select the check box next to the
desired component.
4.
Click Update.
5-5
Procedure
1.
2.
To roll back all components to the previous versions, select the first check box on
the column header next to the Name field. To roll back specific component(s),
select the check box next to the desired component.
3.
5-6
Updating Components
The Updates screen appears with the Schedule tab selected by default.
2.
3.
4.
Minute intervals: Updates every { } minutes per hour. Select the minute
interval.
For example, if you select 15, the update is triggered four times an hour: at 00,
15, 30, 45 minutes. If you select 30, the update will be triggered twice an hour:
at 00 and 30 minutes.
5-7
For example, if you select 15, the update is triggered at 15 minutes after the
hour, every hour.
5.
Daily: Updates every day at the time you choose. Select the time of day.
Weekly: Updates once a week at the specified day and time. Select a day of
the week and the time of day.
Click Save.
2.
3.
Click Upload.
After the file finishes uploading, the package type, build number, and title appear
under Latest uploaded package.
5-8
Updating Components
Select the check boxes next to the devices to which you want to deploy the update.
2.
Click Update.
3.
Accept the license agreement. After the update is complete, a summary page
appears.
4.
Click OK.
WARNING!
During the update, do not modify any other settings. To stop the update, click
Cancel.
If a device check box is grayed out, you cannot deploy the update to the device
because the device:
Has more up-to-date files than the ones you are trying to deploy.
Is a child device and you have not yet uploaded the files to the parent device.
Under Host Name, click the name of the device you want to view.
A summary screen appears showing the updates and related log information.
2.
5-9
3.
4.
5-10
Chapter 6
6-1
6-2
With Cloud Pre-Filter, you can protect your domains against malicious messages coming
from outside your network. Cloud Pre-Filter blocks malicious messages before they
reach your network.
6-3
DESCRIPTION
The Cloud Pre-Filter account is used to manage Cloud Pre-Filter
policies. You must create one Cloud Pre-Filter account before you
use the Cloud Pre-Filter service.
IMSVA stores the account information locally after creating an
account. IMSVA uses the account information to communicate with
Cloud Pre-Filter to complete command requests, such as
managing Cloud Pre-Filter policies and retrieving message
tracking or report data.
6-4
TERM
Policy
DESCRIPTION
Cloud Pre-Filter policies apply to your domains. You can create
only one policy per domain. When the messages sent to the
domain reach Cloud Pre-Filter, Cloud Pre-Filter uses the policy for
that domain to determine how to scan the messages and how to
route the messages to the domain.
Cloud Pre-Filter rejects all messages to domains that do not exist
in the Cloud Pre-Filter policy list.
Cloud Pre-Filter service stores all policies in the cloud.
Inbound Server
6-5
2.
3.
4.
Specify your location from the Your location list. This setting specifies which of
the global Trend Micro data centers you use.
5.
Click Create.
IMSVA generates a key for the Cloud Pre-Filter account.
6-6
6.
Save this key to a secure location. IMSVA uses the key and the user name to
authenticate connection to Cloud Pre-Filter.
Tip
Trend Micro recommends saving the key file. The key file contains your account
password, data center information, and other related settings.
7.
8.
6-7
6-8
Chapter 7
7-1
Scan Technology
IMSVA allows you to select the level of malware detection appropriate for your
company's security policy by configuring the scan engine.
The following table outlines the scanning technology available in IMSVA.
TABLE 7-1. Scan Technology
SCAN TECHNOLOGY
DESCRIPTION
7-2
Important
Because ATSE identifies both known and unknown advanced threats, enabling ATSE may
increase the possibility of legitimate files being flagged as malicious. Trend Micro
recommends sending detected files to a controlled virtual environment for further
observation and analysis.
2.
7-3
3.
Click Save.
Collect, aggregate, manage, and analyze logs into a centralized storage space
Provide advanced visualization and investigation tools that monitor, explore, and
diagnose security events within the corporate network
IMSVA integrates with the Virtual Analyzer in Deep Discovery Advisor. IMSVA sends
suspicious messages, including attachments, to Virtual Analyzer for further analysis.
Virtual Analyzer performs content simulation and analysis in an isolated virtual
environment to identify characteristics commonly associated with many types of
malware.
In particular, Virtual Analyzer checks if files attached to messages contain exploit code.
Although many files include non-executable data, attackers find ways to cause such files
to exploit vulnerabilities in programs and operating systems that run them. Because of
this, sending malicious files to target users has become an effective way for attackers to
compromise systems.
For more information, see the Deep Discovery Advisor Administrators Guide.
7-4
ATSE detections are identifiable through the prefixes HEUR and EXPL. If the
detection name contains one of these prefixes, IMSVA:
Sends the entire message (including attachments) to Deep Discovery Advisor for
further analysis.
Deep Discovery Advisor assigns a risk level to each analyzed message. IMSVA queries
this risk level approximately 15 minutes after sending the message to Deep Discovery
Advisor. After receiving the risk level, IMSVA logs the detection as a Probable
advanced threat or an Analyzed advanced threat based on the risk level and the
security level that you select on the IMSVA management console.
Note
If IMSVA does not receive a risk level, or if the risk level returned is invalid, IMSVA logs
the detection as a Probable advanced threat.
The following table contains the security levels and the corresponding Deep Discovery
Advisor risk levels that trigger an action from IMSVA.
Tip
Trend Micro recommends setting the security level to Low.
7-5
SECURITY LEVEL
High
DESCRIPTION
Apply action on all messages exhibiting
any suspicious behavior
Medium
Low
RISK LEVEL
High risk
Medium risk
Low risk
High risk
Medium risk
High risk
Note
If you select the Quarantine action in a virus rule and IMSVA receives a valid risk level
from Deep Discovery Advisor, the risk level and security level determine if IMSVA
intercepts and reprocesses the message. If you select any other action, IMSVA processes
the message according to the rule configuration and logs the Deep Discovery Advisor risk
level.
7-6
2.
3.
4.
Server
Server port
API key
7-7
Proxy server
User name
Password
Note
IMSVA supports only HTTP proxies.
5.
Configure the Security Level settings for the messages that Deep Discovery
Advisor analyzes.
Note
The security level determines the Deep Discovery Advisor risk level that triggers an
action from IMSVA. For more information, see Deep Discovery Advisor Risk Levels and
IMSVA Security Level Settings on page 7-5.
The available security level settings are: High, Medium, and Low. Trend Micro
recommends setting the security level to Low.
6.
Click Save.
Note
IMSVA can notify you if Deep Discovery Advisor is unable to return a valid or complete
analysis result. For more information, see Configuring Event Criteria and Notification Message on
page 26-5.
7-8
Chapter 8
8-1
8-2
Step 1: Register IMSVA to the encryption service (See Registering for Email Encryption
on page 8-3)
Step 2: Register domains to the encryption service (See Registering Domains on page
8-5)
Step 3: Configure policies to encrypt your messages (See Adding Policies on page
17-2)
2.
8-3
3.
Click Next.
Your contact information is sent to the Trend Micro Email Encryption Server.
Note
It may take one or two working days before you receive the information to complete
domain ownership verification. If you do not receive a message within 3 working
days, contact your sales representative.
What to do next
To change your contact information, click Change on the Gateway Info tab.
Note
The Change button is not enabled until at least one domain has been registered
successfully.
Managing Domains
The Manage Domains tab enables the administrator to register new domains for use
with the IMSVA email encryption features. When a domain is registered with the
encryption service, it is permitted to obtain private keys for email addresses on that
domain. For example, you want to register mycompany.org. After the registration is
authorized and completed on the encryption service, IMSVA will be able to obtain
private keys to decrypt messages to user01@mycompany.org,
user02@mycompany.org, and so on. The security processes and checks to authorize
an IMSVA domain registration, and will include checking publicly available information
that might include contacting the domain registrant.
Note
For security reasons, the person who is the registered owner of the domain will be
contacted by the registration team to validate the IMSVA registration. Therefore, to register
a domain, you must be the owner of, or have the permission of, the owner of the domain
name.
8-4
You can remove a domain from IMSVA by selecting the [Delete] link next to the
domain. This removes the registration information from the encryption services
database and it will no longer be possible to obtain private keys for email addresses on
this domain.
Registering Domains
When registering domains to the Trend Micro Email Encryption Server, messages are
sent to the following email addresses to verify ownership of the domains:
postmaster@<domain>
webmaster@<domain>
the email address returned from a WHOIS lookup for the domain
WARNING!
The postmaster and webmaster accounts must exist and be enabled before domains can be
registered.
Trend Micro sends a message to the "Contact Information" email address to verify that
the domain exists and that the postmaster@<domain> and webmaster@<domain>
accounts exist and are enabled.
WARNING!
One of the following must respond to the verification message:
postmaster@<domain>
webmaster@<domain>
the email address returned from a WHOIS lookup for the domain
8-5
backup the database prior to re-installation, and restore it afterwards. This eliminates the
need to re-register IMSVA and the same domains after re-installation.
Note
IMSVA must be registered to the encryption service before any domains can be registered.
The default sender address for your domains will be postmaster@<domain>. You can
customize the default sender address from the Encryption Settings screen.
The default sender address is used when IMSVA tries to encrypt a message, but whose
domain is not in the Domain List. IMSVA signs these messages with the default sender
address.
2.
3.
Click Add.
4.
5.
8-6
Click Save.
A progress bar appears as the domain information is sent to the Trend Micro
Email Encryption Server. A confirmation screen appears that verifies the domain
information was received by the Trend Micro Encryption Server.
6.
Read the instructions about what to do once you receive the verification key file.
7.
Click Done.
The domains appear in the Domain list on the Domain tab and a message about
the Domain tab.
8.
If you are the registered owner of the domain, reply to the confirmation message
from the Trend Micro Encryption Server. The message is sent to
postmaster@<domain> and webmaster@<domain>. When your domains are
approved, you receive the domain ownership verification key file. You must reply
to the confirmation message to prove that you are the owner of the domain.
Note
It may take one or two working days before you receive the key file to register the
domain(s) to the encryption service. A key file is sent for each domain that is
registered.
If you do not receive a message within 3 working days, contact your sales
representative.
9.
8-7
Part II
Configuring IMSVA and Cloud
Pre-filter
Chapter 9
9-1
DESCRIPTION
The domain that will be covered by the policy. With the correct
routing settings, all messages to this domain are protected by
Cloud Pre-Filter.
Each domain must be unique, and only one policy can be applied
to a domain.
Valid Recipient
Filter settings
Destination servers
9-2
For filters that support this option, how each filtering criterion
is applied
For filters that support this option, what filter actions to perform
Destination servers are the inbound mail servers for the domain.
These servers receive messages bound for the domain after they
are processed by the Cloud Pre-Filter service.
SECTION
Approved and
blocked senders
DESCRIPTION
Note
Trend Micro recommends that you create Cloud Pre-Filter policies that mirror, but are less
aggressive than, on-premise IMSVA policies. Using duplicate policies helps protect your
business in the unlikely event that Cloud Pre-Filter becomes unavailable.
Considerations
Each policy applies to one domain only and only one policy can be created for each
domain.
Review each filter type and assess whether you want to apply it to a domain before
saving the policy. The following filters are enabled by default:
Email Reputation
Antivirus
Antispam
Tip
Trend Micro recommends that you have the antivirus and antispam filters enabled and
properly configured. Without these filters, the domain is highly vulnerable to large numbers
of unwanted mail and infected messages.
9-3
9-4
2.
Click Add.
The Step 1: Specify Domain and Destination Server screen appears.
3.
4.
9-5
5.
Specify the addresses of the domain's actual destination servers to allow Cloud PreFilter to relay messages to these servers after processing.
6.
Select one of the following from the Address Type drop-down list:
MX record: Mail exchange record Cloud Pre-Filter uses for DNS lookup
Note
A policy can only contain one address type for a destination server. An IP address
and an A record are considered to be the same type. An MX record is considered to
be a different type.
9-6
7.
8.
Provide a port number for communication between IMSVA and Trend Micro
Email Security SaaS Solutions. The default value is port 25.
9.
The Priority option specifies routing priority for the destination servers. Cloud PreFilter service will attempt to route messages to servers with higher priority values
first. The lower the number, the higher the priority.
Note
You do not need to specify a priority for an MX record destination server. The
priority for the MX record will be resolved automatically.
Valid Recipients
This feature works by comparing the list of users on your LDAP servers to a list of your
users on Cloud Pre-Filter. The Cloud Pre-Filter list of your users is generated by
synchronizing with your LDAP servers.
9-7
Use the valid recipient check to block all messages that do not have a recipient on your
domain. This prevents malicious messages and spam from reaching your network.
Tip
Trend Micro recommends enabling scheduled synchronization to ensure all valid messages
reach your network. LDAP servers must be configured before enabling the valid recipient
check and scheduled synchronization.
Procedure
1.
9-8
Click Next.
2.
9-9
The Add Approved Sender List or Add Blocked Sender List screen appears.
3.
4.
5.
6.
9-10
When using the import function, use a text file with only one full email or IP
address per line.
7.
When importing sender addresses, ensure that you select the correct import
mode. Selecting to replace addresses will delete all existing addresses from the
list.
8.
9.
Click Import.
The list displays the imported entries.
9-11
DESCRIPTION
Email Reputation enables you to take advantage of a dynamic and
constantly updated email source rating system to block spam and
other unwanted messages. Email Reputation blocks messages
from source IP addresses whose current reputation ratings are
poor.
You can choose Email Reputation Advanced or Email Reputation
Standard. Email Reputation Standard queries the standard
reputation database. Email Reputation Advanced queries the
standard reputation database as well as a dynamic database that
is updated in real time.
Antivirus
Antispam
When enabled, the antispam filter checks messages for spam and
phishing characteristics. The filter identifies messages as spam
based on the selected catch rate.
The antispam filter uses a Web Reputation and spam prevention
filter to stop spam from entering your network.
The antispam filter can use two approaches when detecting spam:
Procedure
1.
9-12
Click Next.
2.
3.
4.
Pass: Cloud Pre-Filter performs no action and sends the messages directly to
IMSVA. IMSVA then scans the messages.
Click Finish.
Cloud Pre-Filter Policy List appears with the domain appearing in the list. The
status for the filters display along with the domain.
9-13
9-14
WARNING!
You MUST configure your mail delivery (MX) records to route your email traffic through
Cloud Pre-Filter. If this step is not completed, your messages will be delivered to your local
servers, and not to Cloud Pre-Filter for scanning.
POINTS TO...
pgXXXX
sgXXXX
9-15
ADDRESS CONTAINS
POINTS TO...
The address points to your Shared Sites.
ngXXXX
Procedure
1.
Retrieve the Cloud Pre-Filter "Inbound Server Addresses" from the Domain tab
for a policy.
a.
b.
9-16
Click the name of an existing policy in the Policy List. The Edit Policy screen
appears displaying the Domain tab.
The addresses display under the Inbound Server Addresses area of the
Domain tab.
Note
The addresses differ depending on your geographic location and the choices
you made during the installation process. Consult the documentation supplied
by your DNS provider to make the changes. The process for making the
modification is different depending on the DNS service your company uses.
2.
a.
9-17
After the modifications take affect, test the message route by sending
messages from another email service provider (Windows Live Hotmail or
Gmail) to a recipient in your domain (for example your-domain.com). If you
receive the message from the other email service provider, the DNS MX
records are configured correctly.
9-18
RECOMMENDED ACTION
When Cloud Pre-Filter filters messages for all your domains:
Disable or do not activate IP Filtering
Cloud Pre-Filter uses Email Reputation to filter all messages
before they reach your network. This makes using IP Filtering
(both Email Reputation and IP Profiler) redundant.
When Cloud Pre-Filter filters messages for some of your domains:
Enable and use IP Filtering (both Email Reputation and IP
Profiler)
Cloud Pre-Filter is not using Email Reputation to scan all
messages before they reach your network. The messages from
domains that are not routed through Cloud Pre-Filter may still be
malicious.
Spam Prevention
Solution (SPS)
Trend Micro
Antivirus and
Content Filter
DKIM
9-19
SECURITY SERVICE
Transport Layer
Security (TLS)
RECOMMENDED ACTION
Cloud Pre-Filter supports TLS.
If the MTA sending messages to Cloud Pre-Filter supports TLS,
the messages are delivered using TLS.
When messages reach Cloud Pre-Filter from an inbound server
using TLS, Cloud Pre-Filter delivers the message to the destination
server using TLS. If the destination server does not support TLS,
the message is delivered over SMTP.
When messages reach Cloud Pre-Filter from an inbound server
that does not use TLS, Cloud Pre-Filter delivers the message to
the destination server over SMTP.
9-20
Chapter 10
10-1
IP Filtering Service
The IP Filtering service has two individual components: Email Reputation and IP
Profiler.
IP Profiler helps protect the mail server from attacks with smart profiles from the
Intrusion Detection Service (IDS).
Tip
Trend Micro recommends deploying IP Filtering as the first line of defense in your
messaging infrastructure.
Although most email systems have a multi-layer structure that often includes some preexisting IP blocking, spam filtering, and virus filtering, Trend Micro recommends
completely removing other IP blocking techniques from the messaging environment. IP
Filtering should act as the precursor to any application filtering you might use.
Standard: Blocks connections with a 550 level error code (connection refused).
The MTA returns this error code to the server initiating the connection because the
IP address is in the Standard Reputation database as a known spammer.
Advanced: Configure the MTA to make two DNS queries. If the MTA does not
receive a response from the first query to the standard reputation database, it
10-2
makes a second query to the dynamic reputation database. The MTA should return
a temporarily deny connection 450 level error code (server temporarily
unavailable, please retry) when a response is received from this database.
Legitimate email servers with compromised hosts temporarily sending spam may be
listed in the dynamic reputation database. If the connection request is from a legitimate
email server, it will re-queue and try sending the message later. This process will cause a
short delay in mail delivery until the listing expires but will not permanently block the
email.
Some servers may have additional options for handling questionable IP connections.
These options include throttling or routing messages for more detailed scanning.
You can find instructions for configuring the MTA or firewall on the Trend Micro
website:
https://ers.trendmicro.com/
These instructions have been provided by the vendor or manufacturer of the product
(MTA or firewall). Refer to your product manuals and/or technical support organization
for detailed configuration and setup options.
Note
Insert your Activation Code to replace the instructional text example; do not include any
dashes.
10-3
Procedure
1.
2.
3.
10-4
DESCRIPTION
ASN
ISP Name
COLUMN
4.
DESCRIPTION
Botnet Activity
Click News.
The News screen appears.
The News screen displays breaking news about new spam and new features
available for Email reputation. Click the following tabs for information:
5.
To view reports that summarize the activity between the MTA and the Email
reputation database servers, do the following:
a.
b.
10-5
6.
Percentage Queries
Botnet Report
b.
10-6
DESCRIPTION
DESCRIPTION
Configure the Approved and
Blocked senders lists.
You can define your lists by
individual IP address and Classless
Inter-Domain Routing (CIDR) by
Country, or by ISP.
10-7
POLICY
Reputation Settings
DESCRIPTION
Configure Email reputation
Standard and Advanced settings.
Standard customers will see only
the Enable Standard Settings
section.
Advanced customers will see both
the Dynamic Settings and the
Enable Standard Settings sections.
7.
To change your password, Activation Code, or to add your mail servers to Email
reputation, click Administration from the menu.
Configuring IP Filtering
To configure IP Filtering, perform the following steps:
1.
2.
3.
4.
5.
10-8
2.
Select the Enable IP Filtering check box. This will select both the Email
reputation and IP Profiler check boxes.
3.
Clear the Email reputation or IP Profiler check box if you do not require them.
4.
Click Save.
10-9
Spam
Viruses
DHA attacks
Bounced mail
WARNING!
Before enabling IP Profiler Rules, add all of your email servers IP addresses (that send
outgoing messages to IMSVA) to the IP Filtering Approved List. To configure the IP
Filtering Approved List, see Step 4: Adding IP Addresses to the Approved List on page 10-21.
10-10
2.
3.
4.
Rate (%): Specify the maximum number of allowable messages with spam
threats.
Total mails: Specify the total number of spam messages out of which the
threshold percentage is calculated.
Total mails: Specify the total number of spam messages out of which
the threshold percentage is calculated (the denominator).
Block temporarily: Block messages from the IP address and allow the
upstream MTA to try again.
Block permanently: Never allow another message from the IP address and
do not allow the upstream MTA to try again.
10-11
6.
Click Save.
Procedure
1.
2.
3.
4.
10-12
Rate (%): Type the maximum number of allowable messages with viruses
(the numerator).
Total mails: Type the total number of infected messages out of which the
threshold percentage is calculated (the denominator).
Rate (%): Type the maximum number of allowable messages with virus
threats (the numerator).
Total mails: Type the total number of virus messages out of which the
threshold percentage is calculated (the denominator).
6.
Block temporarily: Block messages from the IP address and allow the
upstream MTA to try again.
Block permanently: Never allow another message from the IP address and
do not allow the upstream MTA to try again.
Click Save.
Procedure
1.
10-13
The Rules screen appears with 4 tabs, one for each type of threat.
2.
3.
Select the Enable check box to enable blocking of directory harvest attacks.
4.
10-14
Rate (%): Type the maximum number of allowable messages with DHA
threats (the numerator).
Total mails: Type the total number of DHA messages out of which the
threshold percentage is calculated (the denominator).
Sent to more than: Type the maximum number of recipients allowed for the
threshold value.
Non-existing recipients exceeds: Type the maximum number of nonexistent recipients allowed for the threshold value. DHA attacks often include
randomly generated email addresses in the receiver list.
Note
The LDAP service must be running to determine non-existing recipients.
Rate (%): Type the maximum number of allowable messages with DHA
threats (the numerator).
Total mails: Type the total number of DHA messages out of which the
threshold percentage is calculated (the denominator).
10-15
Tip
Technically, the LDAP server is not a must-have. The DHA rule of IMSVA can also
obtain the DHA results returned from Postfix, which in turn passes these results to
FoxProxy through the LDAP server or other means. FoxProxy then analyzes the
results to determine if they are DHA attacks.
LDAP server is only one of the means by which Postfix checks if a user's mailbox
exists.
5.
6.
Block temporarily: Block messages from the IP address and allow the
upstream MTA to try again.
Block permanently: Never allow another message from the IP address and
do not allow the upstream MTA to try again.
Click Save.
2.
10-16
4.
Total mails: Specify the total number of bounced messages out of which the
threshold percentage is calculated (the denominator).
5.
Block temporarily: Block messages from the IP address and allow the
upstream MTA to try again.
10-17
6.
Block permanently: Never allow another message from the IP address and
do not allow the upstream MTA to try again.
Click Save.
10-18
2.
3.
Click a radio button next to one of the following, depending on your level of
service, and configure the settings:
Standard:
10-19
SMTP error code: Blocks any connections that have a certain SMTP
code. Specify an SMTP code.
SMTP error string: Specify the message associated with the SMTP
error code.
Advanced:
SMTP error code: Blocks any connections that have a certain SMTP
code. Specify an SMTP code.
SMTP error string: Specify the message associated with the SMTP
error code.
Note
The above SMTP error code and error string will be sent to the upstream MTA
that will then take the necessary pre-configured actions, such as recording the
error code and error string in a log file.
10-20
4.
Click Save.
2.
Click Add.
The Add IP/Domain to Approved List screen appears.
3.
4.
Specify the domain or IP address that you would like to add to the Approved List.
5.
Click Save.
10-21
2.
Click Add.
The Add IP/Domain to Blocked List screen appears.
3.
10-22
4.
5.
6.
Click Save.
The domain or IP address is added to the Blocked List.
2.
Next to Type, select the check boxes next to the type of threat that the IP
filter detected.
Next to Dates, select the date-time range within which IMSVA blocked the
sender.
Next to Logs per page, select the number of log entries to display on the
screen at a time.
3.
4.
10-23
10-24
To change the number of items that appears in the list at a time, select a new
display value from the drop-down box on the top of the table.
Chapter 11
11-1
2.
3.
Click Save.
2.
3.
4.
11-2
2.
3.
Click Save.
2.
11-3
11-4
3.
4.
Select Accept all, except the following list to configure the "deny list" or
Deny all, except the following list to configure the "permit list.
b.
Group of computers:
i.
ii.
Import from file: Click to import an IP list from a file. The following
shows sample content of an IP list text file:
192.168.1.1
192.168.2.0:255.255.255.0
192.168.3.1:255.255.255.128
192.168.4.100
192.168.5.32:255.255.255.192
2001:db8:10ff::ae:44f2:
11-5
2001:db8::/32
5.
b.
Select Only accept SMTP connection by TLS for IMSVA to only accept
secure incoming connections.
This option enables the IMSVA SMTP Server to accept messages only
through a TLS connection.
c.
Private key: The SMTP client encrypts a random number using IMSVA
SMTP server's public key and an encryption key to generate the session
keys.
IMSVA SMTP server then uses the private key to decrypt the random
number in order to establish the secure connection.This key must be
uploaded to enable a TLS connection.
11-6
d.
e.
6.
Click Save.
Email Relay
To prevent spammers from using the IMSVA MTA as a relay for spam, configure relay
control by adding the mail domains on your network to the Incoming Message
Settings list. When IMSVA receives a message, it looks at the final destination of the
message and compares it to this list. IMSVA discards the message under the following
circumstances:
2.
11-7
11-8
3.
4.
Specify the Relay Control parameters to have IMSVA reject messages matching
the selected condition.
5.
11-9
6.
7.
Host only
Specified IP addresses
Click Save.
Tip
For security reasons, Trend Micro recommends that you avoid open relay when
configuring the message rule settings. For more information on how to avoid open
relay, refer to the Online Help and the FAQ section in this manual.
11-10
domain1.com,192.168.1.1:2000
domain2.net,192.168.2.2:1029
domain3.com,smtp.domain3.com:25
domain4.com,mail.domain4.com:2000
domain5.com,[2001:db8:10ff::ae:44f2]:25
Procedure
1.
11-11
2.
3.
11-12
Click Add.
4.
5.
Click OK.
6.
Click Save.
11-13
Chapter 12
12-1
The handshake begins when Server B requests a secure connection with Server A
by sending a list of ciphers.
2.
Server A then selects one cipher presented by Server B and replies with its digital
certificate that may have been signed by a Certificate Authority (CA).
3.
Server B verifies Server A's identity with the trusted CA certificate. If the
verification fails, Server B may choose to stop the TLS handshake.
4.
Upon verifying Server As identity, Server B proceeds to generate the session keys
by encrypting a message using a public key.
5.
This message can only be decrypted using the corresponding private key. Server Bs
identity is thus authenticated when Server A is able to decrypt the message
successfully using the private key.
6.
The handshake completes and the secure connection is established after the servers
have created the material required for encryption and decryption.
12-2
IMSVA applies TLS on traffic entering IMSVA and traffic exiting IMSVA, not on
incoming or outgoing message traffic.
Use a certificate generator or key generator tool to generate a digital certificate and
public/private key pairs. Request a certificate authority to sign the certificate.
Apply for the certificate and public/private key pairs from a certificate authority.
Note
A default certificate and key file is provided with
IMSVA.
12-3
Ensure that the signed certificate contains both the private key and certificate
information.
Note
If your certificate is in PKCS12 format, convert it to the PEM format using the command:
[root@imsva85b ~]# openssl pkcs12 -in mycert.pfx -out mycert.pem
2.
3.
Under Transport Layer Security Setting, click the Browse button next to CA
certificate.
4.
5.
Click Upload.
12-4
12-5
12-6
2.
3.
Select Only accept SMTP connection by TLS for IMSVA to only accept secure
incoming connections.
This option enables the IMSVA SMTP server to accept messages only through a
TLS connection.
4.
Private key: The SMTP client encrypts a random number using the IMSVA
SMTP server's public key and an encryption key to generate the session keys.
The IMSVA SMTP server then uses the private key to decrypt the random
number in order to establish the secure connection.
This key must be uploaded to enable a TLS connection.
SMTP server certification: The IMSVA SMTP server's public key made
available to the SMTP clients for generating the session keys.
This key must be uploaded to enable a TLS connection.
5.
Click Save.
12-7
2.
3.
Click Save.
12-8
DESCRIPTIONS
none
No TLS
may
Opportunistic TLS
encrypt
Mandatory TLS
Table 12-1: Upstream TLS levels on page 12-9 lists the upstream TLS security levels in order
of increasing security. For more information on each security level, visit:
http://www.postfix.org/TLS_README.html#server_tls
LEVELS
none
No TLS
may
Opportunistic TLS
encrypt
Mandatory TLS
verify
Mandatory TLS
12-9
SECURITY LEVELS
secure
LEVELS
Secure-channel TLS
Table 12-2: Downstream TLS levels on page 12-9 lists the downstream TLS security levels in
order of increasing security. For more information on each security level, visit:
http://www.postfix.org/TLS_README.html#client_tls
2.
3.
Save your Certificate Authority (CA), IMSVA public key, and IMSVA private key
in the /opt/trend/imss/postfix/etc/postfix folder.
4.
Configure /opt/trend/imss/postfix/etc/postfix/main.cf.
12-10
5.
Contents of smtpd_tls_policy:
<IP address> encrypt
Contents of smtp_tls_policy:
example.com encrypt
6.
12-11
postmap smtpd_tls_policy
postmap smtp_tls_policy
7.
main.cf:
smtpd_tls_security_level=none
smtpd_tls_policy_maps= hash:/opt/trend/imss/postfix/etc/
postfix/smtpd_tls_policy
smtpd_tls_policy:
<IP address> may
In this example, a client whose IP address is not in the smtpd_tls_policy list will
communicate with the Postfix server without TLS. The security level can be changed
from may to encrypt as required.
Security parameters can be customized in the upstream site-specific TLS settings.
TABLE 12-3. Upstream Site-specific TLS Security Parameters
SECURITY PARAMETER
req_cert
12-12
DESCRIPTION
In mandatory TLS mode, IMSVA requires a trusted remote
SMTP client certificate to allow TLS connections to proceed. This
parameter overrides smtpd_tls_req_ccert in main.cf. In
opportunistic TLS mode, this parameter does not work.
SECURITY PARAMETER
DESCRIPTION
ciphers
protocols
exclude
Table 12-3: Upstream Site-specific TLS Security Parameters on page 12-12 lists the upstream sitespecific TLS security parameters in order of increasing security and customization. For
example:
smtpd_tls_policy:
<IP address> encrypt req_cert=yes ciphers=medium
protocols=TLSv1
This policy is set to limit communication with IMSVA through a TLS connection to:
a trusted certificate
12-13
Modify main.cf:
smtp_tls_security_level=none
smtp_tls_policy_maps= hash:/opt/trend/imss/postfix/etc/
postfix/smtp_tls_policy
Modify smtp_tls_policy:
[<IP address>]:25 may
example.com encrypt
In the example above, servers not listed in the smtp_tls_policy will communicate
with the Postfix client without TLS.
The security level can be changed from may to encrypt or verify as required.
For more information on security parameters in the downstream site-specific TLS
settings, visit the following site:
http://www.postfix.org/TLS_README.html#client_tls_policy
12-14
After the completion of this procedure, the /tmp/root_key.pem file contains the
private key encrypted with the Trend password. The /tmp/root_req.pem file contains
the self-signed certificate that must be distributed to all clients and servers. Both are
stored in the PEM-format.
12-15
WARNING!
The Organization (O) field for the CA and key owners must be the same.
12-16
After completing this procedure, the /tmp/imsva_key.pem file contains the IMSVA
(imsva.course.test) private key in PEM-format. The /tmp/imsva_req.pem file
contains the unsigned certificate (certificate request) in the PEM-format.
WARNING!
The Common Name (CN) field for the key owner must be equal to the FQDN or be the
same as the name specified in the domain-based delivery.
12-17
12-18
[root@imsva85b ~]#
2.
3.
Create the serial file with initial content in the /etc/pki/CA directory:
[root@imsva85b ~]# echo "01" > /etc/pki/CA/serial
[root@imsva85b ~]#
4.
12-19
12-20
The real Certification Authority Certificate used to sign all public keys of all clients
and servers communicating with IMSVA.
Individual certificates of all clients and servers communicating with IMSVA. In this
case, the administrator must copy all individual certificates in one file using the
following commands:
1.
For Windows:
copy client_cert1.pem + ... + client_certN.pem
ca_cert.pem
12-21
2.
For Linux:
cat client_cert1.pem ... client_certN.pem > ca_cert.pem
Configuring Postfix
The management console must be used to configure TLS support in IMSVA. It
downloads the key and certificates in the Postfix configuration directory (/opt/
trend/imss/postfix/etc/postfix) and updates the configuration for the
Upstream SMTP Server in the main.cf configuration file:
smtpd_tls_security_level = may
smtpd_tls_CAfile = /opt/trend/imss/postfix/etc/postfix/ca.pem
smtpd_tls_cert_file = /opt/trend/imss/postfix/etc/postfix/
cert.pem
smtpd_tls_key_file = /opt/trend/imss/postfix/etc/postfix/
key.pem
When the administrator enables the downstream TLS from the management console,
the Manager makes the following configuration changes in the main.cf configuration file
that affect the SMTP client:
smtp_tls_security_level = may
Converting Certificates
Outlook Express does not recognize the certificates in PEM-format, so they need to be
converted into the PKCS12-format. The example below shows how to convert the
IMSVA signed certificate needed for the Outlook Express clients that contact IMSVA
directly:
[root@imsva85b ~]# openssl pkcs12 -export -out
12-22
To see the available certificates, go to Menu > Tools > Options > Security >
Digital IDs.
2.
Click Import
3.
Search for files in the Personal Information Exchange format (*.pfx, *.p12)
4.
5.
Confirm the certificate import with an empty password to import the certificate.
2.
Click Advanced.
3.
Select the This server requires a secure connection (SSL) check box for
Downstream mail (SMTP).
12-23
4.
12-24
Apply changes.
Chapter 13
13-1
To scan POP3 traffic, configure your email clients to connect to the IMSVA server
POP3 proxy, which connects to POP3 servers to retrieve and scan messages.
You can set up the following connection types:
13-2
Generic: Allows you to access different POP3 servers using the same port,
typically 110, the default port for POP3 traffic.
Dedicated: Accesses the POP3 server using a specified port. Use these
connections when the POP3 server requires authentication using a secure logon,
such as APOP or NTLM.
POP3 Requirements
For IMSVA to scan POP3 traffic, a firewall must be installed on the network and
configured to block POP3 requests from all the computers on the network, except the
IMSVA server. This configuration ensures that all POP3 traffic passes to IMSVA
through the firewall and that IMSVA scans the POP3 data flow.
Go to System Status.
13-3
2.
3.
Click Save.
13-4
3.
4.
To accept any POP3 server requested by a user, specify the incoming IMSVA
port number, if it is different from the default port 110.
To access the POP3 server using a specific port for authentication purposes,
click Add to create a new dedicated POP3 connection. Provide the required
information and click OK.
Click Save.
13-5
2.
a.
Go to System Status.
b.
c.
Click Save.
3.
User account
13-6
Part III
IMSVA Policies
Chapter 14
Managing Policies
This chapter provides instructions for creating, modifying, and managing IMSVA
policies.
Topics include:
14-1
About Policies
IMSVA policies are rules that are applied to SMTP and POP3 messages. Create rules to
enforce your organizations antivirus and other security goals. By default, IMSVA
includes a Global Antivirus rule to help protect your network from viruses and related
Internet threats. Because an antivirus rule addresses the most critical and potentially
damaging types of messages, you should always keep it in the first position on the rule
list so IMSVA can analyze traffic for virus content first.
The antivirus rule does not protect against spam. For the best protection against spam,
configure a custom rule that includes spam in the scanning conditions, and activate the
IP Filtering product.
Note
Before creating a new policy, ensure that you have defined the internal addresses. See
Configuring Internal Addresses on page 16-2 for more information.
Antivirus: Scans messages for viruses and other malware such as spyware and
worms.
Others: Scans spam or phishing messages, message content, and other attachment
criteria.
Route: A set of sender and recipient email addresses or groups, or an LDAP user
or group to which the policy is applied. You can use the asterisk (*) to create
wildcard expressions and simplify route configuration.
Filter: A rule or set of rules that apply to a specific route, also known as scanning
conditions. IMSVA contains predefined filters that you can use to combat
14-2
Managing Policies
common virus and other threats. You can modify these predefined filters or define
your own filters.
Action: The action that IMSVA performs if the filter conditions are met.
Depending on the filter result, a filter action is performed that determines how the
message is finally processed.
14-3
2.
b.
c.
14-4
Specify a route:
All types
C&C email
Web Reputation
Attachments
Content
Compliance
Size
Other
All Groups
Chapter 15
15-1
DESCRIPTION
Address Groups
Compliance Templates
Notifications
Stamps
15-2
For example, you have identified three types of content that you do not want
transmitted through your companys email system and have defined three filters (in
parentheses) to detect these types of content:
All Executives
All HR Department
The filters that you use in the policies will be applied to these groups as follows:
ADDRESS GROUPS
FINANCIAL
JOBSEARCH
VBSCRIPT
All Executives
Not applied
Applied
Applied
All HR Department
Applied
Not applied
Applied
All IT Development
Staff
Applied
Applied
Not applied
15-3
You can create address groups before creating any policies or when specifying the route
during policy creation. You can also add an address group when modifying an existing
policy. Create address groups manually or import them from a text file that contains one
email address per line.
Tip
While address groups can be created during policy creation, Trend Micro recommends
creating address groups before you begin creating policies.
Procedure
1.
2.
Click Add.
The Add Address Group screen appears.
15-4
3.
Specify an email address and click Add. You can also use wildcard
characters to specify the email address. For example, *@hr.com.
Click Import.
The Import Address Group screen appears.
b.
Specify the file path and file name to import or click Browse and locate
the file.
c.
d.
Click Import.
Note
IMSVA can only import email addresses from a text file. Ensure that the text file
contains only one email address per line. You can also use wildcard characters to
specify the email address. For example, *@hr.com.
4.
Click Save.
The Address Groups screen appears with the new address group appearing in the
Address Groups table.
15-5
Note
IMSVA can only import email addresses from a text file. Ensure that the text file contains
only one email address per line. You can also use wildcard characters to specify the email
address. For example, *@hr.com.
Procedure
1.
2.
3.
Select Antivirus or Other from the drop-down list to create an antivirus rule or a
rule against other threats.
The Step 1: Select Recipients and Senders screen appears.
4.
15-6
5.
6.
15-7
7.
Click Import.
The Import Address Group screen appears.
b.
Specify the file path and file name to import or click Browse and locate
the file.
c.
15-8
d.
Click Import.
Note
IMSVA can only import email addresses from a text file. Ensure that the text file
contains only one email address per line. You can also use wildcard characters to
specify the email address. For example, *@hr.com.
8.
Click Save.
2.
b.
c.
Click Save.
The Address Groups screen appears.
3.
15-9
b.
Click Delete.
2.
3.
4.
15-10
5.
6.
Select the desired address group and click the Edit or Delete button accordingly.
15-11
2.
3.
Click Export.
The File Download screen appears.
4.
Click Save.
The Save As dialog box appears.
5.
6.
Click Save.
2.
3.
4.
5.
6.
Click Edit.
The Address Group screen appears.
7.
Click Export.
The File Download screen appears.
8.
Click Save.
The Save As dialog box appears.
15-12
9.
For information on creating a new rule, see Adding Policies on page 17-2.
2.
Under Content, on the Scanning Conditions screen, select the check boxes next
to the parts of a message to which you want the content conditions to apply.
3.
Click the link that specifies the part of the message to which you want to configure
content conditions.
The Keyword Expressions screen appears with two columns:
15-13
4.
If you are configuring expressions for the header, select the check boxes next to
the header items where the expression will apply.
5.
Click Add.
The screen for managing keyword expressions appears.
6.
7.
In the Available list, click the expression list you want to enable.
8.
Click >>.
The expressions appear in the Selected list.
To keep an expression list available but temporarily prevent IMSVA from using it,
click the expression in the selected list, and then click <<.
9.
Configuring an Expression
Configure keyword and regular expressions to enable IMSVA to scan message content.
You can create keywords or expressions from the Keywords & Expressions screen or
during rule creation.
Tip
While keywords or expressions can be created during policy creation, Trend Micro
recommends creating keywords or expressions before you begin creating policies.
15-14
Each keyword list has built-in conditions that determine if the content triggers a
detection. A keyword list must satisfy your chosen criteria before IMSVA subjects it to a
policy.
Expressions are a powerful string-matching tool. Ensure that you are comfortable with
expression syntax before creating expressions. Poorly written expressions can
dramatically impact performance. When creating expressions:
Note that IMSVA follows the expression formats defined in Perl Compatible
Regular Expressions (PCRE). For more information on PCRE, visit http://
www.pcre.org/.
Start with simple expressions. Modify the expressions if they are causing false
alarms or fine tune them to improve detections.
There are several criteria that you can choose from when creating expressions. An
expression must satisfy your chosen criteria before IMSVA subjects it to a policy.
2.
Click Add.
15-15
3.
4.
Next to Match, select one of the following that specifies when IMSVA takes
action:
Not the specified: Message content does not match any of the keywords or
expressions in the list.
5.
15-16
Click Add.
Specify the keywords. For a partial match, specify the keyword. To specify an
exact match, use "\s" (without the quotes) before and after the keyword.
For example:
c.
Click Save.
6.
7.
8.
a.
b.
Click Save.
The Keywords & Expressions screen appears with the new keyword or
expression appearing in the table.
2.
For information on creating a new rule, see Adding Policies on page 17-2.
Under Content on the Scanning Conditions screen, click the link that specifies
the part of the message to which you want to configure content conditions.
15-17
4.
5.
Next to Match, select one of the following that specifies when IMSVA takes
action:
6.
Any specified: Message content can match any of the expressions in the list.
All specified: Message content must match all the expressions in the list.
Not the specified: Message content must not match any of the expressions
in the list.
7.
Specify the keywords. For a partial match, just specify the keyword. To specify an
exact match, use \s before and after the keyword.
For example:
8.
9.
15-18
b.
Click Save.
10. To instruct IMSVA to consider the capitalization of message content when it uses
the filter, select the check box under Case sensitive.
11. Click Save to continue modifying or creating the policy.
Characters
REGULAR EXPRESSION
DESCRIPTION
. (dot)
\\
\a
\b
15-19
REGULAR EXPRESSION
DESCRIPTION
\n
\r
\t
\v
\n
\nn
\mnn
\xhh
15-20
MATCHES
[abc]
a, b, or c
[a-z]
a through z
[^abc]
[[:alpha:]]
DESCRIPTION
[:alpha:]
Alphabetic characters
[:digit:]
Digits
[:alnum:]
[:cntrl:]
Control character
[:blank:]
[:space:]
[:graph:]
15-21
CHARACTER CLASS
DESCRIPTION
[:print:]
[:punct:]
Punctuation characters
[:lower:]
Lowercase alphabetic
[:upper:]
Uppercase alphabetic
[:xdigit:]
Boundary Matches
EXPRESSION
DESCRIPTION
Beginning of line
End of line
Greedy Quantifiers
EXPRESSION
DESCRIPTION
R?
R*
R+
R{n}
R{n,}
R{n,m}
R is a regular expression.
15-22
Trend Micro does not recommend using ".*" in a regular expression. ".*" matches any
length of letters and the large number of matches may increase memory usage and affect
performance.
For example:
If the content is 123456abc, the regular expression ".*abc" match results are:
12345abc
23455abc
3456abc
456abc
56abc
6abc
abc
In this example, replace ".*abc" with "abc" to prevent excessive use of resources.
Logical Operators
EXPRESSION
DESCRIPTION
RS
R followed by S (concatenation)
R|S
Either R or S
R/S
(R)
Grouping R
15-23
DESCRIPTION
{D}
[0-9]
{L}
[A-Za-z]
{SP}
[(),;\.\\<>@\[\]:]
{NUMBER}
[0-9]+
{WORD}
[A-Za-z]+
{CR}
\r
{LF}
\n
{LWSP}
[ \t]
{CRLF}
(\r\n)
{WSP}
[ \t\f]+
{ALLC}
eManager also provides the following meta-symbols. The difference between shorthand
and meta-symbols is that meta-symbols can be within a bracket expression.
META-SYMBOL
DESCRIPTION
\s
[[:space:]]
\S
[^[:space:]]
\d
[[:digit:]]
15-24
META-SYMBOL
DESCRIPTION
\D
[^[:digit:]]
\w
[_[:alnum:]]
\W
[^_[:alnum:]]
DESCRIPTION
"C/C++"
"Regular\x20Expression"
"[xyz]\"foo"
Change the adjacent <space> to "\x20" for the following in a regular expression:
.AND.
.OR.
.NOT.
.WILD.
15-25
Procedure
1.
For information on creating a new rule, see Adding Policies on page 17-2.
2.
3.
4.
5.
Click >>.
The compliance templates appear in the Selected list.
6.
15-26
Procedure
1.
2.
Click Add.
The Add Compliance Template screen appears.
3.
4.
5.
6.
Expression: Select Expression, the data asset to protect, and the number of
times the data asset could appear in a message before IMSVA blocks the
message from leaving your network.
Keyword: Select Keyword and the data that you want IMSVA to prevent
leaving your network.
Click +.
The list under Digital Asset Definition increases by one entry.
15-27
7.
Specify the relationship between the new entry and existing entries using And or
Or.
8.
9.
Click Add.
The digital asset definition appears in the Compliance Template Definition list.
Predefined Expressions
IMSVA comes with a set of predefined expressions. These expressions cannot be
modified, copied, exported, or deleted
IMSVA verifies these expressions using pattern matching and mathematical equations.
After IMSVA matches potentially sensitive data with an expression, the data may also
undergo additional verification checks.
The following table lists the predefined expressions and the additional verification tasks
that IMSVA performs, if any.
TABLE 15-2. Predefined Expressions
NAME
All - Credit Card Number
15-28
ADDITIONAL VERIFICATION
IMSVA checks the prefix and further verifies it with the
Luhn checksum, a widely used algorithm for validating
identification numbers.
ADDITIONAL VERIFICATION
NAME
All - Email Address
None
None
Austria - SSN
(Sozialversicherungsnumm
er)
15-29
ADDITIONAL VERIFICATION
NAME
Date - Formats used in
Japan
yyyy/mm/dd
yy/mm/d
yy.mm.dd
Syy.m.d
yyyy-m-d
yy m d
None
Denmark - Personal ID
Number
Finland - Personal ID
Number
15-30
ADDITIONAL VERIFICATION
NAME
France - National
Insurance Number
None
Germany - Electronic
Taxpayer ID
Ireland - PPSN
Ireland - VAT
None
Japan - Address
None
Poland - National ID
Number
None
None
Taiwan - National ID
Number
15-31
ADDITIONAL VERIFICATION
NAME
UK - National Health
System Number
None
UK - National Insurance
Number
IMSVA verifies the first two digits of the data and the
expressions own checksum.
US - California ID or DL
Number
None
US - Dollar Amount
None
US - Phone Number
15-32
All: All of the keywords in the list must be present in the document.
Any: Any one of the keywords in the list must be present in the document.
Specific number: There must be at least the specified number of keywords in the
document. If there are more keywords in the document than the number specified,
a violation will trigger.
Distance Condition
Some of the lists contain a distance condition to determine if a violation is present.
Distance refers to the amount of characters between the first character of one keyword
and the first character of another keyword. Consider the following entry:
First Name:_John_ Last Name:_Smith_
The Forms - First Name, Last Name list has a distance condition of fifty (50) and
the commonly used form fields of "First Name" and "Last Name". In the example
above, a violation will trigger as the number of characters between the F in First
Name and the "L" in Last Name is equal to eighteen (18).
For an example of an entry that would not trigger a violation, consider the following:
The first name of our new employee from Switzerland is John. His last name is Smith.
In this example, the number of characters between the "f" in "first name" and the "l" in
"last name" is sixty-one (61). This exceeds the distance threshold and does not trigger a
violation.
15-33
DESCRIPTION
CONDITIONS
Adult
Specific
number: 4
Common medical
terms
Specific
number: 5
Forms - (First),
(Middle), Name
All
Distance: 50
Any
Forms - Expiration
date
Any
All
Distance: 50
Any
15-34
LIST NAME
DESCRIPTION
CONDITIONS
All
Distance: 50
All
Casesensitive
Japan - Surname in
Hiragana (match 50)
Specific
number: 50
Japan - Surname in
Kanji1 (match 10)
Specific
number: 10
Japan - Surname in
Kanji2 (match 50)
Specific
number: 50
Japan - Surname in
Kanji3 (match 100)
Specific
number: 100
Japan - Surname in
Katakana 1-byte
(match 50)
Specific
number: 50
Japan - Surname in
Katakana (match 50)
Specific
number: 50
15-35
LIST NAME
DESCRIPTION
CONDITIONS
Racism
Specific
number: 4
Specific
number: 10
Casesensitive
Specific
number: 10
Casesensitive
Specific
number: 10
Specific
number: 10
Casesensitive
Specific
number: 10
Casesensitive
Source code - C#
Source code - VB
Specific
number: 10
All
Casesensitive
15-36
LIST NAME
Weapons
DESCRIPTION
The Weapons list detects a wide variety of
words that describe implements of
violence.
CONDITIONS
Specific
number: 4
2.
For information on creating a new rule, see Adding Policies on page 17-2.
3.
Available: Notification messages available for use, but not currently in use.
15-37
4.
5.
Click >>.
The notifications appear in the Selected list.
To keep a notification available but temporarily prevent IMSVA from using it, click
the notification in the selected list, and then click <<.
6.
2.
Click Add.
The Add/Edit Policy Notification screen appears.
15-38
3.
To: Specify the receiver email addresses and select the check boxes next to
Original Mail Sender and/or Original Mail Recipient. Separate each address
with a semicolon (;).
15-39
4.
5.
To see the types of variables you can include in the message, click Variables list.
6.
b.
7.
Click Save.
2.
For information on creating a new rule, see Adding Policies on page 17-2.
Under Monitor on the Select Actions screen, click Send policy notifications.
The Notifications screen appears with two columns:
3.
Available: Notification messages available for use, but not currently in use.
15-40
4.
To: Specify the receiver email addresses and select the check boxes next to
Original Mail Sender and/or Original Mail Recipient. Separate each address
with a semicolon (;).
5.
6.
To see the types of variables you can include in the message, click Variables list.
7.
b.
8.
Click Save.
Using Stamps
To notify a recipient that IMSVA took action on a message's attachment or that the
message violated scanning conditions for rules, add a stamp to the beginning or end of
the message body.
15-41
Tip
Add stamps only for messages that the intended recipients will eventually receive. If you
are configuring a rule to delete messages that violate your scanning conditions, adding a
stamp is not necessary.
2.
For information on creating a new rule, see Adding Policies on page 17-2.
While creating or modifying a policy on the Select Actions screen, select the check
box next to Insert stamp in body or Insert stamp in clean email messages
under Modify.
Creating Stamps
Create stamps from the Stamps screen or during policy creation or modification.
Note
While stamps can be created during policy creation, Trend Micro recommends creating
stamps before you begin creating policies.
Procedure
1.
15-42
2.
3.
4.
Next to Insert at, click End of message body or Beginning of message body.
5.
Under Text, specify the message. To see the types of variables you can include in
the message, click Variables list.
6.
To prevent possible damage to Transport Neutral Encapsulation Format (TNEF)encoded messages or digitally signed messages, select Do not stamp TNEFencoded messages or digitally signed messages.
15-43
7.
2.
For information on creating a new rule, see Adding Policies on page 17-2.
Under Modify on the Select Actions screen, click Edit next to Insert stamp in
body or Insert stamp in clean email messages.
The Stamps screen appears showing the available stamps.
3.
To add a new stamp, click Add. To modify an existing stamp, click it in the list box
and then click Edit.
An edit screen appears.
4.
5.
Next to Insert at, click End of message body or Beginning of message body.
6.
Under Text, specify the message. To see the types of variables you can include in
the message, click Variables list.
7.
8.
9.
Click Done.
15-44
2.
Select the Enable the DKIM Approved List for use in policies check box.
3.
15-45
Manually:
a.
b.
Click Add.
Import a list:
Note
When importing a text file for the DKIM Approved List, only one domain should be
on each line.
a.
Click Import.
The Import DKIM Approved List appears.
b.
Specify the file path and file name or click Browse and locate the file.
c.
d.
4.
Click Import.
Click Save.
15-46
2.
For information on creating a new rule, see Adding Policies on page 17-2.
3.
Select the Enable the use of the Web Reputation Approved List check box.
4.
Click Save.
The Step 2: Select Scanning Conditions screen appears.
5.
Procedure
1.
15-47
2.
Populate the Web Reputation Approved List in one of the following ways:
Manually:
a.
b.
Click Add>>.
Import a list:
Note
When importing a text file for the Web Reputation Approved List, only one domain
should be on each line.
a.
Click Import.
The Import Web Reputation Approved List appears.
b.
Specify the file path and file name or click Browse and locate the file.
c.
d.
15-48
Click Import.
3.
Click Save.
15-49
Chapter 16
Internal Addresses
This chapter provides instructions for creating, modifying, and managing IMSVA
policies.
Topics include:
16-1
For incoming messages, specify the recipients address, which is in range of the
internal addresses. For example: internal address is imsstest.com, valid
recipients include jim@imsstest.com, bob@imsstest.com.
For outgoing messages, specify the senders address, which is in range of the
internal addresses. For example: internal address is imsstest.com, valid senders
include jim@imsstest.com, bob@imsstest.com.
For both incoming and outgoing messages, the rule applies to senders or recipients
that match the mail address.
16-2
Internal Addresses
2.
Under Internal Domains and User Groups, select one of the following from the
drop-down box:
Enter domain: Specify a domain and click >>. Do not type the "@" or user
name parts of an email address. For example, domainname or
domainname1.domainname2 are valid; user@domainname is invalid.
Note
You can use wildcards for domain names. For example, use *.domain.com to
include all sub-domains for "domain.com". However, you cannot use two
asterisks in the user name or domain name portion of the address, or use the
"@" symbol. *.*@domain.com and user@*.* are both invalid.
Search for LDAP group: A screen for searching the LDAP groups appears.
Specify an LDAP group name (not an individual LDAP user) that you want to
search in the text box and click Search. The search result appears in the list
box. To add it to the Selected list, click the LDAP group and then click >>.
For more information, see Searching for an LDAP User or Group on page 16-7
16-3
Note
When searching an LDAP group for the internal addresses, you can use
wildcards at the beginning and/or at the end of the LDAP group if you have
specified Microsoft Active Directory or Sun iPlanet Directory as the LDAP
server.
3.
To import domains from a file, click Import from File and select the file.
Tip
Import both the exact domain and all sub-domains for best results.
4.
Click Save.
2.
Click Export.
A File Download dialog box appears.
16-4
Internal Addresses
3.
Click Save.
A Save As dialog box appears.
4.
5.
Click Save.
When you configure a route or an exception for a route, choose Select address
groups under Select address.
The Address Groups screen appears.
2.
Click Add.
3.
b.
c.
Click Add.
The address appears in the list.
4.
To import an address group from a file to the IMSVA server, do the following:
a.
Click Import.
16-5
b.
Click Browse.
A dialog box appears.
c.
d.
If addresses are already in the list, choose whether to merge them or overwrite
them with the imported list.
e.
Click Import.
5.
Click Save.
6.
Email address
LDAP group
Address group
Procedure
1.
2.
Next to Filter by, select [find user or group] from the last drop-down list.
The Find Policy or User Group screen appears.
3.
4.
16-6
Email address
Internal Addresses
Address group
5.
In the text box, specify the key words for which to search.
6.
Click Select.
OpenLDAP 2.4.23
The following steps provide instructions on adding an LDAP user or group when
creating a new policy.
Procedure
1.
2.
3.
Select Antivirus or Other from the drop-down list to create an antivirus rule or a
rule against other threats, respectively.
4.
16-7
5.
16-8
Select Search for LDAP users or groups from the drop-down list.
Internal Addresses
6.
You can use the asterisk wildcard when performing a search. See .
b.
You can also search for LDAP groups when adding internal addresses. See
Configuring Internal Addresses on page 16-2.
7.
8.
IMSVA displays the LDAP user or group if a matching record exists on the LDAP
server.
9.
Select the user or group and click the Add button to add it to the recipient or
sender list.
16-9
Chapter 17
Configuring Policies
This chapter provides instructions for creating, modifying, and managing IMSVA
policies.
Topics include:
17-1
Adding Policies
Before creating a policy, ensure that you have configured the internal addresses. For
information, see Step 7: Configuring Internal Addresses on page 4-13.
Creating a policy involves the following steps:
Specifying a Route
The first step in adding a rule is configuring the following:
Route
A specific "To" and "From" combination that includes a recipient's and
sender's email addresses, LDAP users or groups, or address groups. You can
also configure exceptions to a route.
Route type
The direction of SMTP traffic, POP3 traffic, or all traffic.
Adding a Route
Procedure
1.
17-2
Configuring Policies
Click Add.
3.
Note
The Antivirus rule scans messages for viruses and other malware such as spyware
and worms.
The Other rule scans for spam or phishing messages, message content, encrypted
messages, regulatory compliance, and other attachment criteria.
17-3
4.
17-4
Select the policy route type from the drop-down list next to This rule will apply
to.
incoming messages
outgoing messages
POP3
all messages
Configuring Policies
5.
For outgoing messages, specify the senders address, which is in range of the
internal addresses.
For example: internal address is imsstest.com, valid senders include
jim@imsstest.com, bob@imsstest.com.
For both incoming and outgoing messages, the rule applies to senders or
recipients that match the mail address.
Note
1. You can use the asterisk wildcard when specifying an email address. For more
information, see Using the Asterisk Wildcard on page 20-13.
2. If you selected POP3, you cannot configure the route. The rule applies to all POP3
routes.
3. If you selected "all messages" for a rule, the rule also applies to messages from any
sender to any recipient.
6.
Click Next.
The Step 2: Select Scanning Conditions screen appears.
Editing a Route
Procedure
1.
2.
17-5
4.
Select the policy route type from the drop-down list next to This rule will apply
to.
incoming messages
outgoing messages
POP3
all messages
Note
The This rule will apply to option cannot be modified in the Global DKIM
Enforcement rule.
5.
For outgoing messages, specify the senders address, which is in range of the
internal addresses.
For example: internal address is imsstest.com, valid senders include
jim@imsstest.com, bob@imsstest.com.
17-6
For both incoming and outgoing messages, the rule applies to senders or
recipients that match the mail address.
Configuring Policies
Note
1. You can use the asterisk wildcard when specifying an email address. For more
information, see Using the Asterisk Wildcard on page 20-13.
2. If you selected POP3, you cannot configure the route. The rule applies to all POP3
routes.
3. If you selected "all messages" for a rule, the rule also applies to messages from any
sender to any recipient.
6.
Click Save.
Route Configuration
A route is a specific "To" and "From" combination that includes a recipients and
senders email addresses, LDAP users or groups, or address groups. You can also
configure exceptions to a route.
Senders and recipients must be on the Internal Addresses list if you select incoming
messages or outgoing messages when adding a new rule or modifying an existing rule:
If you are configuring an outgoing message, the Internal Address list applies to the
senders.
If you are configuring an incoming message, the Internal Address list applies to the
recipients.
Use the asterisk wildcard to include a range of email addresses. For example:
17-7
2.
Click one of the following on the Select Recipients and Senders screen:
Search for LDAP users or groups: Specify the LDAP user or group name
and click Search. The results display in the list box.
Select address groups: All existing address groups appear in the list. If there
are a large number of email addresses that you will reuse for routes in several
rules, click Add to create an address group.
3.
If you are adding an email address or email address group, click Add>. If you are
adding an LDAP or address group, click it in the list box, and then click Add>.
4.
To remove any email address or email address group from the Selected list, click
the trash can icon.
5.
Click Save.
17-8
Configuring Policies
Tip
When selecting an LDAP group as the recipients or senders, you can use wildcards at
the beginning and/or at the end of the LDAP group if you have specified Microsoft
Active Directory or Sun iPlanet Directory as the LDAP server.
To prevent virus leaks and ensure that all messages are scanned, Trend Micro
recommends that you maintain at least one antivirus rule that applies to all messages
at all times.
Select the check boxes as desired, from the Step 2: Select Scanning Conditions
screen. The categories of scanning conditions for the Antivirus and the Other rule
17-9
Antivirus rule
a.
Files to Scan: Set the default method for scanning messages and
specific file types containing viruses and other malware.
TABLE 17-1. Files to Scan
SETTING
17-10
DESCRIPTION
IntelliScan: uses
"true file type"
identification
Configuring Policies
SETTING
Specific file types
b.
c.
DESCRIPTION
Select the check box next to one of the following
types of file extensions to scan:
17-11
Other rule
a.
b.
17-12
Select one of the following next to Take rule action when, which
specifies when IMSVA can take action on a message:
Configuring Policies
This filter is not triggered if the detected email addresses are found in the
C&C Email Approved List. For more information, see Configuring the
C&C Email Approved List on page 17-15.
Note
Selecting C&C Email and the filter relation all conditions matched
(AND) disables the Spam/Phishing Email and Web Reputation
filters.
c.
Phishing email
d.
e.
MIME content type: Click the link to configure filter settings for
MIME content types.
True file type: Click the link to configure filter settings for
common executable, document, image, media, and compressed
files.
Size is {>, <, =} {size} {MB, KB, B}: Select to filter attachments
of a size that is more than, less than, or equal to a certain number
of bytes, kilobytes, or megabytes. Specify a number that represents
the file size.
17-13
f.
g.
h.
17-14
Configuring Policies
i.
DESCRIPTION
GLBA
HIPAA
PCI-DSS
SB-1386
US PII
Received time range: Click the link to select a day and time within
which a message was received.
17-15
Procedure
1.
2.
3.
4.
b.
17-16
Import email addresses from a text file on a local host to the IMSVA server.
Configuring Policies
Note
Each line in the file should contain only one email address that follows any of
the valid formats. IMSVA does not import incorrectly formatted email
addresses.
If the list already contains email addresses, choose whether to merge the new
entries or overwrite the existing ones.
5.
6.
7.
Click Save.
2.
Email body:
Attachments:
17-17
Important
Do not use the Forward command as it deletes essential information
from the message header. Instead, send the message as an attachment
(.msg or .eml).
3.
Under Spam/phishing emails on the scanning conditions selection screen for the
Other rule type, select the check box next to Spam detection settings.
2.
3.
To enable spam scanning, select the check box next to Select a spam catch rate
or specify a detection threshold.
If you do not select this check box, IMSVA will not label any messages that violate
this rule as spam. You can, however, still take actions on any senders in the
Blocked Senders list below.
4.
17-18
Select one of the following spam catch rates or specify a detection threshold.
High: Catches more spam. Select a high catch rate if too much spam is
getting through to your clients.
Low: Catches less spam. Select a low catch rate if IMSVA is tagging too many
legitimate messages as spam.
Configuring Policies
5.
Click DKIM approved list to enable or disable use of the DKIM Approved List.
IMSVA does not scan or mark messages as spam, if the messages come from
domains appearing in the DKIM approved list.
6.
Select the check boxes next to any of the following lists to enable them:
7.
17-19
Approved sender list: Prevents IMSVA from identifying messages from senders
in this list as spam.
Blocked sender list: Forces IMSVA to identify messages from senders in this list
as spam.
Select the check box next to Approved sender list or Blocked sender list.
2.
3.
4.
17-20
a.
Next to Email address, specify the address. To add multiple addresses, use
the asterisk (*) wildcard.
b.
To import an address group from a file on a local host to the IMSVA server, do
the following:
a.
Click Import.
b.
c.
Click Open.
d.
If addresses are already in the list, choose whether to merge them or overwrite
them with the imported list.
e.
Click Import.
b.
Click Save.
Configuring Policies
5.
c.
Specify a name for the file and a location to save the file.
d.
Click Save. The file saves to the location and a dialog appears.
e.
Click Close.
Click Save.
When configuring the spam scanning conditions, select the Exclude messages
matching text exemption rules check box under Text Exemption Rules.
2.
To add a new text exemption rule, click Add. To configure an existing rule, click it
in the list box, and then click Edit.
The Text Exemption Rules screen appears.
3.
Next to Name, specify a descriptive name for the text exemption rule.
4.
17-21
Note
If you select Subject, From, To, or Reply-to as the scan area and use Line
beginning to match the header, provide only the header content for Line
beginning.
Example:
a.
b.
Under Strings to match, provide a message string for Line beginning. For
example, test@trendmicro.com.
If you select All Headers as the scan area and use Line beginning to match the
header, provide the header name as well.
Example:
a.
b.
Under Strings to match, provide both the header name and a message string
for Line beginning. For example, From: test@trendmicro.com.
5.
Next to Items are case sensitive, select the check box to consider the text case as
well as the content.
6.
Under Strings to match, specify the text strings in the text boxes. Line beginning
means matching regular expressions at the beginning of a line. Line end means
matching regular expressions at the end of a line.
7.
Click Save.
17-22
Configuring Policies
For information on creating a new rule, see Adding Policies on page 17-2.
2.
Under Web Reputation on the Scanning Conditions screen, select the Web
Reputation settings check box.
3.
For information on creating a new rule, see Adding Policies on page 17-2.
2.
3.
Click Next.
The Web Reputation Settings screen appears.
4.
High: Blocks more websites embedded in messages but also increases the risk
of false positives. Select High if your users are visiting too many malicious
websites.
Low: Blocks fewer websites embedded in messages and reduces the risk of
false positives. Select Low if IMSVA is blocking too many legitimate websites.
17-23
5.
Select Enable the use of the Web Reputation Approved List to prevent
IMSVA from scanning and blocking domains included in the Web Reputation
Approved List.
6.
Optional: Select Enable detection of URLs that have not been rated by Trend
Micro to increase protection against short-lived websites.
Note
Web pages change frequently, and it is difficult to find data or follow a link after the
underlying page is modified. Such websites are usually used as vehicles for
transporting malware and carrying out phishing attacks.
7.
Click Save.
2.
17-24
For information on creating a new rule, see Adding Policies on page 17-2.
Configuring Policies
3.
Select Enable Exception List to scan email or IP address for marketing messages.
4.
b.
Import email addresses from a text file on a local host to the IMSVA server.
For details, see Importing Marketing Email Exceptions on page 17-26.
5.
6.
Click Save.
17-25
Procedure
1.
On the right pane of the Market Email Settings rule screen, click Import.
The Import Marketing Message Scanning Exception List screen appears.
2.
17-26
Configuring Policies
IPv4 addresses
123.123.123.123
62.36.52.1-255
62.36.52.0/24
IPv6 addresses
1050:0:0:0:5:600:300c:326b
ff06::c3
3.
4.
Select Merge with current list to append the addresses in the file to the
existing exceptions list.
Select Overwrite current list to replace the existing list with the addresses in
the file.
Click Import.
Under Attachment on the scanning conditions selection screen, select the check
box next to Name or extension.
2.
3.
17-27
Not the selected attachment names: IMSVA takes action on messages with
attachments that are not of the selected names.
4.
Select the check boxes next to the attachments to scan or not scan.
5.
b.
Click Import to import from an existing text file. Another window appears.
Alternatively, specify the names in the text box. Use a semicolon (;) to
separate values. You can also use an asterisk wildcard for the extension.
c.
6.
Click Save.
Under Attachment on the scanning conditions selection screen, select the check
box next to MIME content type.
2.
3.
4.
17-28
Not the selected attachment types: IMSVA takes action on messages with
attachments that are not of the selected types.
Select the check boxes next to the MIME content types to filter.
Configuring Policies
5.
To add your own MIME types, type them in the text box.
Use a semicolon (;) to separate values. You can also use an asterisk wildcard for the
MIME type.
6.
Under Attachment on the scanning conditions selection screen, select the check
box next to True file type.
2.
3.
Not the selected attachment types: IMSVA takes action on messages with
attachments that are not of the selected types.
4.
Select the check boxes next to the true file types to filter.
5.
Under Attachment on the scanning conditions screen, select the check box next
to Size is {>, <, =} {size} {MB, KB, B}.
2.
17-29
3.
4.
5.
Under Attachment on the scanning conditions screen, select the check box next
to Number is {>, <, =} {number}.
2.
3.
4.
Under Attachment on the scanning conditions screen, select the check box next
to Password protected zip files.
Under Size on the scanning conditions selection screen, select the check box next
to Message size is {>, <, =} {size} {MB or KB}.
2.
17-30
Configuring Policies
3.
4.
5.
2.
3.
Under Content, on the Step 2: Select Scanning Conditions screen, select the
check boxes next to the parts of a message to which you want the content
conditions to apply.
4.
Click the link that specifies the part of the message to which you want to configure
content conditions. The Keyword Expressions screen appears with two columns:
5.
If you are configuring expressions for the header, select the check boxes next to
the header items where the expression will apply.
6.
Click Add.
The screen for managing keyword expressions appears.
7.
8.
In the Available list, click the expression list you want to enable.
17-31
9.
Click >>.
The expressions appear in the Selected list.
To keep an expression list available but temporarily prevent IMSVA from using it,
click the expression in the selected list, and then click <<.
2.
3.
4.
5.
Number of recipients
17-32
Configuring Policies
Procedure
1.
2.
3.
For information on creating a new rule, see Adding Policies on page 17-2.
Under Other, on the Scanning Conditions screen, select the check boxes next to
the following:
Received time range: Blocks messages if they enter your network within the
specified time range.
Spoofed internal messages: Blocks all messages that do not originate from
the trusted IP address list.
Under Others on the scanning conditions selection screen, select the check box
next to Number of recipients {>, <, =} {number}.
2.
3.
17-33
4.
Under Others on the scanning conditions selection screen, select the check box
next to Received time range.
2.
3.
4.
From the time drop-down boxes, select the day, start time, and end time.
5.
Click Add.
6.
Under Others on the scanning conditions selection screen, select the check box
next to Spoofed internal messages.
2.
17-34
Configuring Policies
3.
4.
Click Save.
Specifying Actions
The main actions for both the Antivirus and Other rules are similar, although there are
minor differences in the options listed. Select the desired action(s) from the following
categories:
Intercept: Allows you to choose whether you would like IMSVA to intercept the
messages and prevent them from reaching the recipients. Choosing the intercept
option allows you to specify an action for IMSVA to take on intercepted messages.
Procedure
1.
17-35
Note
The screen that appears in this step depends on the type of rule that you are creating.
The antivirus rule contains two tabs that allow you to configure the main actions and
the actions for special viruses.
17-36
Configuring Policies
17-37
Procedure
1.
Under Intercept, click the radio button next to one of the following:
Do not intercept messages: This specific rule does not intercept messages.
If there are other rules, IMSVA will process the message. If there are no rules,
IMSVA passes the message to your network.
Quarantine: IMSVA puts the message and its attachments into the
quarantine area that you select from the drop-down box. For instructions on
creating a new quarantine area, see Configuring Quarantine and Archive Settings on
page 25-3.
Handoff: IMSVA hands off the message to a specific mail server. Select
Handoff if you have a secure messaging server on your network that can
process or handle the message. Configure the following:
Next to Port, specify the port number through which the mail server
receives email traffic.
Note
IMSVA can only track a message before it is handed off. After the handoff, the
message is not traceable anymore as it is no longer within the control of
IMSVA.
2.
Under Modify, select the check boxes next to any of the following:
17-38
Configuring Policies
3.
Insert stamp in body: Insert text at the beginning or end of the message.
From the drop-down box, select the name of the stamp to insert or click Edit
to go to the Stamps screen and manage your stamps.
Tag subject: Add text to the subject line of the message. Click Tag subject
to edit the tag.
Postpone delivery to: Delay delivery until a specified hour of the day. Select
the hour of the day and minutes from the drop-down boxes.
Encrypt message: Encrypt the message and send the message to the
recipient.
Under Monitor, select the check boxes next to any of the following:
BCC: Blind carbon copy the message to another recipient. Specify the
recipient's email address and separate multiple addresses with a semicolon (;).
Select the BCC option to prevent the intended recipients from seeing the new
recipient.
17-39
17-40
Configuring Policies
Procedure
1.
Under Intercept, select the radio button next to one of the following:
TABLE 17-3. Intercept Settings
SETTING
DESCRIPTION
Do not intercept
messages
Delete entire
message
Quarantine
Change recipient
Handoff
2.
Under Modify, select the check boxes next to any of the following:
17-41
Note
Options under If IMSVA finds a virus are only available for Antivirus rules.
If IMSVA finds a virus : Select the check box to enable actions if IMSVA
finds a virus or other malware, and then click one of the following:
TABLE 17-4. IMSVA Finds a Virus Settings
SETTING
Use ActiveAction
Attempt to clean
attachments. If
unable to clean
Delete attachments
DESCRIPTION
17-42
Insert stamp in body: Insert text at the beginning or end of the message.
From the drop-down box, select the name of the stamp to insert or click Edit
to go to the Stamps screen and manage your stamps.
Insert safe stamp for clean mails: Insert text into clean messages signifying
that the message is safe. From the drop-down box, select the name of the
stamp to insert or click Edit to go to the Stamps screen and manage your
stamps.
Configuring Policies
Note
The Insert safe stamp for clean mails option is not available on the Special
Viruses tab.
3.
Tag subject: Add text to the subject line of the message. Click Tag subject to
edit the tag.
Postpone delivery time: Delay delivery until a specified hour of the day.
Select the hour of the day and minutes from the drop-down boxes.
Under Monitor, select the check boxes next to any of the following:
BCC: Blind carbon copy the message to another recipient. Specify the
recipient's email address and separate multiple addresses with a semicolon (;).
Select the BCC option to prevent the intended recipients from seeing the new
recipient.
17-43
Mass mailing: IMSVA takes the actions specified in this section if it detects mass
mailing messages.
IntelliTrap: Allows you to specify the corresponding actions if you have selected
the IntelliTrap Setting options on the Scanning Conditions screen in step 2. See
Specifying Scanning Conditions on page 17-9.
Note
IMSVA takes the default action for messages matching the IntelliTrap conditions if
you do not select alternative actions.
17-44
Configuring Policies
the subject line. Add a tag only for messages that the intended recipients will eventually
receive. If you are configuring a rule to delete messages that violate your scanning
conditions, adding a tag is not necessary.
Procedure
1.
When you select actions, click Tag subject under Modify actions.
An edit screen appears.
2.
3.
4.
5.
To use a tag, select the check box next to Tag subject under Modify.
Finalizing a Policy
After you select actions for a rule, name and enable the rule. Also, assign an order
number that represents its position within the hierarchy of rules. IMSVA allows you to
add any notes to the rule that you think are necessary for future reference. You can also
modify this information for an existing rule.
When viewing rules, note the following:
The green check mark button indicates that the rule is active.
The red cross mark button indicates that the rule is saved but inactive.
The gray cross mark button indicates that the rule and the Activation Code for the
product are both inactive.
Note
You can enable and disable rules by clicking the buttons.
17-45
Finalizing a Rule
Procedure
1.
When creating a new policy, click Next on the Step 3: Select Actions screen.
The Step 4: Name and Order screen appears.
When finalizing an existing policy, click the name of the policy in the policy
list on the Policy > Policy List screen.
2.
3.
4.
In the Order Number field, specify the priority in which IMSVA will perform the
scan. IMSVA applies the rule to messages according to the order you specify.
17-46
Configuring Policies
5.
6.
7.
If you are creating a new policy, verify that the information on the screen is correct.
If any information about the rule is incorrect, click < Previous and make your
changes.
8.
17-47
Chapter 18
Encryption Settings
This chapter provides instructions for configuring encryption settings for IMSVA.
Topics include:
18-1
Encryption Types
There is a difference between the Encryption exception rule and the Unable to
decrypt messages policy rule.
TABLE 18-1. Encryption Types
FEATURE
DESCRIPTION
Encryption
exception
Unable to decrypt
messages
18-2
Encryption Settings
18-3
Chapter 19
Scanning Exceptions
This chapter provides instructions for managing IMSVA scanning exceptions.
19-1
For the actions specified in Scan Exceptions to take effect, verify that the Global
antivirus rule is enabled.
2.
For malformed messages, when a message triggers the scan exception, IMSVA stops
scanning and takes the corresponding actions. That means IMSVA will not trigger any
policy rules when a scan exception occurs.
For security setting violations and encryption exceptions, IMSVA will not stop scanning
after the action of the scan exception executes. IMSVA continues checking other policy
rules. IMSVA will stop scanning if it encounters a terminal scan action.
2.
To set scan exception conditions for messages based on several conditions, click
the Security settings violations link under Exception.
The Security Settings Violations screen appears.
3.
To set scan exception conditions for encrypted or decrypted messages, click the
Encryption exceptions link under Exception.
The Encryption Exceptions screen appears.
19-2
Scanning Exceptions
4.
To set an action for an exception type, click the corresponding link under Action:
2.
3.
To set limits on the types of messages IMSVA can scan, configure the following:
Total decompressed size of any single file exceeds { } MB: Specify the
maximum number of megabytes.
Click Save.
19-3
Procedure
1.
On the Scanning Exceptions screen, click the action name link under Actions
for Security settings violations.
The screen for configuring actions appears.
2.
19-4
Under Intercept, click the radio button next to one of the following:
Do not intercept messages: IMSVA does not take action on the message.
IMSVA processes the message using other rules if other rules exist.
Quarantine to: IMSVA moves the message and its attachments into the
quarantine area that you select from the drop-down box. For instructions on
creating a new quarantine area, see Configuring Quarantine and Archive Settings on
page 25-3.
Handoff: IMSVA hands off the message to a specific mail server. Select
Handoff if you have a secure messaging server on your network that can
process or handle the message. Configure the following:
Next to Port, specify the port number through which the mail server
receives email traffic.
Scanning Exceptions
Note
IMSVA can only track a message before it is handed off. After the handoff, the
message is not traceable anymore as it is no longer within the control of IMSVA.
3.
4.
Under Monitor, select the check boxes next to any of the following:
BCC: Blind carbon copy the message to another recipient. Specify the
recipient's email address and separate multiple addresses with a semicolon (;).
Select the BCC option to prevent the intended recipients from seeing the new
recipient.
Click Save.
On the Scanning Exceptions screen, click the action name link under Actions
for Malformed messages.
The screen for configuring actions appears.
2.
Under Intercept, click the radio button next to one of the following:
Do not intercept messages: IMSVA does not take action on the message.
IMSVA passes the message on for delivery.
19-5
Note
IMSVA does not scan malformed messages with other rules, even if other rules
exist.
Quarantine to: IMSVA moves the message and its attachments into the
quarantine area that you select from the drop-down box. For instructions on
creating a new quarantine area, see Configuring Quarantine and Archive Settings on
page 25-3.
Handoff: IMSVA hands off the message to a specific mail server. Select
Handoff if you have a secure messaging server on your network that can
process or handle the message. Configure the following:
Next to Port, specify the port number through which the mail server
receives email traffic.
Note
IMSVA can only track a message before it is handed off. After the handoff, the
message is not traceable as it is no longer within the control ofIMSVA.
3.
4.
19-6
Under Monitor, select the check boxes next to any of the following:
BCC: Blind carbon copy the message to another recipient. Specify the
recipient's email address and separate multiple addresses with a semicolon (;).
Select the BCC option to prevent the intended recipients from seeing the new
recipient.
Click Save.
Scanning Exceptions
2.
3.
Click Save.
The Scanning Exceptions screen reappears.
19-7
2.
3.
Under Intercept, click the radio button next to one of the following:
Quarantine to: IMSVA puts the message and its attachments into the
quarantine area that you select from the drop-down box. For instructions on
creating a new quarantine area, see Configuring Quarantine and Archive Settings on
page 25-3.
Handoff: IMSVA hands off the message to a specific mail server. Select
Handoff if you have a secure messaging server on your network that can
process or handle the message. Configure the following:
Next to Port, specify the port number through which the mail server
receives email traffic.
Note
IMSVA can only track a message before it is handed off. After the handoff, the
message is not traceable any more as it is no longer within the control of IMSVA.
4.
19-8
Under Monitor, select the check boxes next to any of the following:
BCC: Blind carbon copy the message to another recipient. Specify the
recipient's email address and separate multiple addresses with a semicolon (;).
Select the BCC option to prevent the intended recipients from seeing the new
recipient.
Scanning Exceptions
5.
Click Save.
19-9
Chapter 20
Existing Policies
This chapter provides instructions for creating, modifying, and managing InterScan
Messaging Security Virtual Appliance policies.
Topics include:
20-1
Procedure
1.
2.
3.
4.
Configure the route settings. For more information, see Specifying a Route on page
17-2.
5.
6.
And domains listed here do not pass DKIM verification. (Global DKIM
rule)
Configure the scan settings. For more information, see the following:
For Antivirus and Other rules: Specifying Scanning Conditions on page 17-9
For the Global DKIM Enforcement rule: Using the Domain List for the Global
DKIM Enforcement Rule on page 20-3
7.
8.
Configure the action settings. For more information, see Specifying Actions on page
17-35.
9.
Click Save.
20-2
Existing Policies
2.
3.
Click Edit in the And domains listed here do not pass DKIM verification row.
The Scanning Conditions screen appears.
4.
Manually:
a.
b.
Click Add.
Import a list:
Note
When importing a text file for the Domain List, only one domain should be on
each line.
20-3
a.
b.
Specify the file path and file name or click Browse and locate the file.
c.
d.
5.
Click Import.
Click Save.
Policy Example 1
Create a rule to delete attachments with specific file names or extensions and then stamp
the affected incoming message with an explanation to the recipients.
2.
Click Add.
3.
20-4
Existing Policies
4.
Next to This rule will apply to, select incoming messages from the drop-down
list.
5.
6.
Click Save.
The Step 1: Select Recipients and Senders screen re-appears.
Click Next.
The Step 2: Select Scanning Conditions screen appears.
2.
Next to Take rule action when, select any condition matched (OR).
3.
To enable the Name or extension condition, select the check box next to it.
20-5
4.
5.
6.
Click Save.
The Step 2: Select Scanning Conditions screen re-appears.
Click Next.
The Step 3: Select Actions screen appears.
2.
Under Modify, to enable the Delete attachment action, select the check box next
to it.
3.
Select Matching attachment from the drop-down list if it is not already selected.
4.
5.
If there is no suitable stamp available from the drop-down list, click Edit.
The Stamps screen appears.
20-6
Existing Policies
6.
7.
8.
Click Save.
The Stamps screen re-appears.
9.
Click Done.
The Select Actions screen re-appears.
10. Select the newly created stamp from the drop-down list.
20-7
Click Next.
The Step 4: Name and Order screen appears.
2.
3.
Click Finish.
The newly created rule will appear highlighted in the Policy List screen.
Policy Example 2
Create a rule that quarantines messages containing specific keywords in the subject or
body and then apply this rule to all recipients except administrators.
2.
Click Add.
3.
20-8
Existing Policies
Next to This rule will apply to, select incoming messages from the drop-down
list.
5.
6.
Select Anyone.
7.
Click Save.
The Step 1: Select Recipients and Senders screen re-appears.
8.
9.
20-9
13. Click Save after you finish adding all the desired recipients.
The Step 1: Select Recipients and Senders screen re-appears.
Click Next.
The Step 2: Select Scanning Conditions screen appears.
2.
Next to Take rule action when, select any condition matched (OR).
3.
To enable the Subject Keyword Expressions condition under Content, select the
check box next to it.
4.
5.
If the desired keywords are not available from the existing list, click Add to create a
new keyword list.
The New Keyword Expression screen appears.
20-10
Existing Policies
6.
7.
8.
9.
10. After you have added all the required keyword expressions, specify the List name
for the new keyword list and click Save.
The New Keyword Expression screen re-appears.
11. Select the new list and click >> to insert the list into the Selected box.
12. Click Save.
20-11
Click Next.
The Step 3: Select Actions screen appears.
2.
3.
Accept the Default Quarantine area or click the drop-down list to select the
desired quarantine area.
20-12
Existing Policies
Click Next.
The Step 4: Name and Order screen appears.
2.
3.
Click Finish.
The newly created rule will appear highlighted in the Policy list screen.
*@*.tld: Valid representation of both the name and the domain (not the TLD).
Wildcards cannot appear in a subdomain or the top-level domain. Wildcards also cannot
appear with other letters; they must appear alone. The following are invalid examples:
20-13
name.*: Valid representation of files with a specific name but with any extension.
20-14
Part IV
Monitoring the Network
Chapter 21
21-1
a.
b.
Click Save.
b.
Click Update.
21-2
b.
Click Rollback.
Click Refresh to connect to the update source and display the latest
component versions in the Availability column.
21-3
Chapter 22
22-1
Tabs: Allow administrators to create a screen that contains one or more widgets
Understanding Tabs
The IMSVA dashboard uses tabs to provide flexibility for administrators. Tabs provide a
container for widgets allowing administrators to create their own customized dashboard.
The dashboard supports up to 30 tabs per user account.
You can move widgets on tabs by dragging and dropping widgets in various locations on
the tab. The layout for a tab determines where you can move the widget.
22-2
Note
Customizing the dashboard, tabs, or widgets for one user account has no effect on the
dashboard, tabs, or widgets for a different user account. Each user account has a
completely independent dashboard, tabs, and widgets from every other user account.
Default Tabs
The default tabs replace the IMSVA Real-Time Statistics screen. All information that
was available on the IMSVA Real-Time Statistics screen is available through the widgets
on the default tabs. The dashboard provides the following default tabs:
System Overview
Message Traffic
IP Filtering
Cloud Pre-Filter
Note
Deleting the default tabs permanently removes the tabs from viewing for the user account
that removed the tabs. There is no way to recover a deleted tab. Deleting a default tab has
no impact on the dashboard for other user accounts.
DESCRIPTION
Displays the system resources used by
IMSVA on your network.
22-3
WIDGET
DESCRIPTION
Mail Queues
IMSVA Quarantine
IMSVA Archive
DESCRIPTION
IMSVA Scan
Performance
Scanning Conditions
Messages Processed
IP Filtering Tab
The IP Filtering tab contains widgets that display all the malicious messages and all the
spam blocked by IP Filtering components.
22-4
DESCRIPTION
IP Filtering
Performance
IP Filtering Type
DESCRIPTION
Cloud Pre-Filter
Violation Types
Adding Tabs
Add tabs to the dashboard to provide a customized information matrix for your IMSVA
network needs.
Procedure
1.
2.
3.
4.
22-5
Note
The number of widgets that you can add to a tab depends on the layout for the tab.
Once the tab contains the maximum number of widgets, you must remove a widget
from the tab or create a new tab for the widget.
5.
Click Save.
The empty tab appears on the dashboard.
6.
Procedure
1.
2.
3.
4.
Click Save.
Understanding Widgets
Widgets are the core components for the dashboard. Tabs provide the layout and
widgets provide the actual data for the dashboard.
22-6
Note
Customizing the dashboard, tabs, or widgets for one user account has no effect on the
dashboard, tabs, or widgets for a different user account. Each user account has a
completely independent dashboard, tabs, and widgets from every other user account.
In some widgets the total number of messages matching each scanning condition consists
of overlaps. For example, if a message matches more than one scanning condition, such as
spam and attachment, this message will be counted twice, once in the total number for
spam and a second time in the total number for attachment.
Using Widgets
Each widget provides targeted security-related information. Widgets can display this
information in one of the following ways:
Bar chart
Pie chart
Table
Click the help icon on a widget to view the following types of information:
TABLE 22-5. Widget Help
WIDGET TOPIC
DESCRIPTION
Overview
Widget Data
Configure
Edit
22-7
Configuring Widgets
Configuring a widget means modifying settings for the widget that are readily visible on
the widget. The following table lists some examples of the widget settings administrators
can modify.
TABLE 22-6. Configuring Widgets
SETTING
Range
DESCRIPTION
Modify the time range for data that
displays:
1 hour
6 hours
12 hours
24 hours
Data aggregation
Display
Bar chart
Pie chart
Table
Editing Widgets
Editing a widget means modifying settings for the widget that are not readily visible on
the widget. Click the edit icon to access these settings. Examples include:
22-8
DESCRIPTION
Title
Others
Procedure
1.
2.
Click the Edit icon on the widget. The Edit screen appears.
3.
4.
Click OK.
5.
6.
Click Save.
The widget reloads applying the new settings.
Adding Widgets
The number of widgets that you can add to a tab depends on the layout for the tab.
Once the tab contains the maximum number of widgets, you must remove a widget
from the tab or create a new tab for the widget.
22-9
Procedure
1.
2.
3.
Description
All Widgets
System
Message Traffic
IP Filtering
Cloud Pre-Filter
4.
5.
22-10
Chapter 23
Reports
This section provides information on generating one time and scheduled reports.
Topics include:
23-1
Generating Reports
Depending on your needs, you can choose to generate a one-time report on demand or
schedule a report to be run at specific intervals. IMSVA offers you the flexibility of
specifying the content for each report and the option of viewing or saving the result in
HTML or CSV format.
DESCRIPTIONS
Shows the total number and size of incoming messages.
Also shows the number of messages matching specific
scanning conditions.
23-2
DESCRIPTIONS
Spam summary
Reports
REPORT CONTENT
DESCRIPTIONS
DESCRIPTIONS
Shows the total number and size of
encrypted and decrypted messages.
DESCRIPTIONS
23-3
REPORT CONTENT
23-4
DESCRIPTIONS
Reports
REPORT CONTENT
Top 10 C&C email recipients and senders
DESCRIPTIONS
Top 10 recipients and senders of C&C
email based on the addresses used in the
SMTP session
2.
3.
To sort the table, click any of the column headings that are underlined.
If too many items appear on the list, click the arrow buttons on top of the list
to move to the next page or select a number from the drop-down box that
represents which page to view.
To change the number of items that appear in the list at a time, select a new
display value from the drop-down box at the bottom of the table.
To generate a report, click Add. The report takes several minutes to generate.
In progress appears in the Output column if the report is still generating.
4.
To view the report, click one of the following formats under Output:
CSV: Saves the report to a comma-separated value file that you can open with
a spreadsheet application.
23-5
Note
Email Encryption and compliance report content is not available unless you activate
those products. For more information on activating them, see Managing Product
Licenses on page 29-20.
5.
To delete a report, select the check box next to it and click Delete.
2.
Click Add.
The Add One-time Report screen appears.
23-6
Reports
3.
4.
Next to Dates, select the time span that the report will cover.
5.
6.
Click Save.
The report takes several minutes to generate. The message In progress appears in
the report table.
23-7
After the report generates, the hyperlinks HTML and CSV display in the report
table.
7.
8.
23-8
Reports
The Schedule Reports screen appears with the Daily tab displayed.
2.
3.
To view the report, click one of the following formats under Output:
4.
5.
CSV: Saves the report to a comma-separated value file that you can open with
a spreadsheet application.
If too many items appear on the list, click the arrow buttons on top of the list
to move to the next page.
To change the number of items that appears in the list at a time, select a new
display value from the drop-down box at the bottom of the table.
To delete a report, select the check box next to it and click Delete.
2.
Click the Settings link for one of the following report types:
23-9
Daily reports
Weekly reports
Monthly reports
23-10
Reports
3.
4.
Click Save.
The report status changes.
5.
Specify the number for each type of report that you would like to retain.
6.
Click Save.
7.
23-11
8.
23-12
After the report generates, you can click HTML or CSV to view the report.
Chapter 24
Logs
This chapter provides you with general instructions on the tasks that you need to
perform for the day-to-day maintenance of IMSVA. For more information on each field
on the management console, refer to the Online Help.
Topics include:
24-1
About Logs
Logs enable you to monitor various types of events and information flow within
IMSVA. They also serve as an important resource for troubleshooting.
To enable logs and benefit from the information, do the following:
2.
3.
Database log update interval: IMSVA updates the logs regularly at every
interval. Select a number between 1 and 60 for the interval. Selecting 60
means that IMSVA updates the logs once every hour.
Number of days to keep logs for query: Specify a value between 1 and 60
that represents the number of days IMSVA preserves the report logs in the
IMSVA admin database.
24-2
Application log detail level: The level of log detail. Select one of the
following:
Logs
Normal: The standard level of detail. This level provides the basic
information needed by an administrator for daily monitoring and
maintenance.
Debug: The most complete and verbose level of detail. Debug logs are
only recommended when troubleshooting.
Note
Diagnostic or debug logs might consume excessive IMSVA resources and could
reduce system performance.
Number of days to keep log files: Select the check box and specify a
number between 1 and 150 that represents the number of days IMSVA keeps
the local log files. To prevent IMSVA from deleting the log files, clear the
check box.
Maximum log file size for each service: Select the check box and specify a
number between 100 and 99999 that represents the size in MB for local log
files for each type of process or service. To remove any size restriction, clear
the check box.
24-3
Note
IMSVA log files are stored in the folder /opt/trend/imss/logs.
IP Profiler log files are stored in the folder /opt/trend/ipprofiler/logs.
Daily log files for each event type are created at midnight and have the suffix
"<Date>.<Count>". The <Count> suffix is incremented if there is more than
one (1) log file per day.
If the log file size exceeds the maximum log file size for each service, IMSVA
will delete the oldest file.
4.
Click Save.
Querying Logs
You can perform queries on five types of events or information:
System events: Tracks the time of system events such as user access, modification
of rules, registration of MCP agent and so on.
Policy events: Provides details on the policy rules that were triggered, the actions
taken, and the message details.
MTA events: Provides connection details of Postfix on the local computer where
the central controller is installed.
IP filtering: Provides the time when IMSVA started and stopped blocking
messages from the queried IP address.
24-4
Logs
IMSVA data only: These message tracking logs only contain data from IMSVA.
Cloud Pre-Filter + IMSVA data: These message tracking logs contain data from
the Cloud Pre-Filter and IMSVA.
Query Behavior
IMSVA provides the following log query behavior:
TABLE 24-1. General Query Information
QUERY
a@a.com
IMSVA ONLY
Only the exact match is
returned.
Result: a@a.com
za@a.com
a@a.com.us
a@a.com; b@a.com
b@a.com; a@a.com
b@a.com; a@a.com;
c@a.com
24-5
QUERY
Query conditions for
Message tracking left
blank
Subject
Message ID
Sender
Recipient
* in Subject field
IMSVA ONLY
All query conditions can be
left blank
Returns approximately
10000 query results
Returns approximately
10000 query results
*test@example.com
IMSVA ONLY
Valid Sender value in
IMSVA, though no results
will be returned.
24-6
Logs
QUERY
test@example.com
IMSVA ONLY
Returns:
Returns:
*test@example.com
IMSVA ONLY
Returns:
Returns:
Approximately 10000
results sent to all variations
of test@example.com (the
same as using
"*test@example.com*" in
IMSVA Only data)
Returns:
All variations ending with
test@example.com
test@example.com*
24-7
QUERY
*test@example.com*
IMSVA ONLY
Valid Recipient value in
IMSVA.
Returns:
All variations of
test@example.com
test@example.com;
test2@example.com
%^$&^
Result:
Tip
Combined result of
querying
test@example.com and
test2@example.com.
Use
"test@example.com"
or
"test2@example.com
"
Not supported.
User must provide a
properly formatted,
complete or partial email
address.
Note
The data <server name>[127.0.0.1], from returned queries, indicates the default
DNS server.
24-8
Logs
Procedure
1.
2.
3.
In the second drop-down box next to Type, select one of the following:
IMSVA data only: Displays all messages which are directed through IMSVA
Cloud Pre-Filter + IMSVA data: Displays all messages which are directed
through Cloud Pre-Filter and IMSVA. This includes messages which are
deleted by Cloud Pre-Filter.
4.
5.
Subject
Message ID
Sender
Recipient(s)
24-9
Note
6.
a.
b.
The Subject and Message ID fields only display when IMSVA data only is
selected.
7.
8.
24-10
Timestamp
Sender
Recipient
Subject
Source IP address
Message size
Message ID
Internal ID
Delivery IP address
Delivery feedback
Action details
To change the number of items that appears in the list at a time, select a new
display value from the drop-down box on the top of the table.
Logs
Click the action link to view detailed information about the action.
2.
3.
In the second drop-down box next to Type, select one of the following:
All events: Displays the timestamp and descriptions for all system events.
Updates: Displays the timestamp of all scan engines and pattern file updates
from the ActiveUpdate server to the IMSVA admin database.
Service status: Displays the timestamp and descriptions when the scanner
service is started or stopped.
Admin activity: Displays the timestamp and descriptions for major admin
activities such as changing IMSVA settings, admin account log on and log off.
Errors: Displays the timestamp and descriptions for all errors that IMSVA
encountered.
4.
In the third drop-down box next to Type, select the server to view.
5.
6.
7.
Click Display Log. A timestamp, component, and description appear for each
event.
8.
24-11
To change the number of items that appears in the list at a time, select a new
display value from the drop-down box on the top of the table.
2.
3.
In the second drop-down box next to Type, select one of the following items
related to the policy and the rules you configured for the policy:
All
Spyware/grayware
Spam/phish
C&C email
Web Reputation
Note
If you select Web Reputation, IMSVA displays two additional drop-down lists
that contain website content categories. Select any category name to narrow
down your log query.
24-12
Logs
4.
DKIM enforcement
Attachment
Size
Content
Compliance
Others
Scanning exceptions
Sender
Recipient(s)
Rule
Subject
Attachment(s)
Message ID
If you leave any text box blank, all results for that item appear.
5.
Click Display Log. A timestamp, action, rule, and message ID appear for each
event.
6.
Timestamp
Sender
Recipient
Subject
Original size
24-13
Violating attachments
Risk level
Rule type
C&C address
Rule(s)
Action
Message ID
Internal ID
Reason
Scanner
If both ATSE and Deep Discovery Advisor are enabled, IMSVA also displays the
following information:
7.
24-14
Risk rating: Risk level for the entire message (if received from Deep
Discovery Advisor)
To change the number of items that appears in the list at a time, select a new
display value from the drop-down box on the top of the table.
Logs
Note
2.
3.
On the second drop-down menu next to Type, select the IMSVA device to query.
4.
5.
6.
7.
To change the number of items that appears in the list at a time, select a new
display value from the Results per page drop-down box on the top of the
table.
24-15
2.
3.
In the second drop-down box next to Type, select one of the following items
related to IP Filtering:
Email reputation
DHA attack
Bounced mail
Virus
Spam
Manual: Refers to the IP addresses that you have specified in the blocked list.
All
4.
5.
6.
Click Display Log. Information appears for the time that IMSVA both started and
stopped blocking each IP address or domain.
7.
24-16
To change the number of items that appears in the list at a time, select a new
display value from the drop-down box on the top of the table.
Chapter 25
25-1
Quarantine Area: Stores messages that you would like to analyze before deciding
whether to delete or release to the intended recipient(s).
Deferred Queue: Stores messages that IMSVA is unable to deliver to the next
MTA. There are 4 values to control IMSVA (postfix) retries.
TABLE 25-1. Deferred Queue Parameters
PARAMETER
queue_run_delay
DESCRIPTION
Determines the time between deferred
queue scans by the queue manager.
This time should be less than or equal to
the minimal_backoff_time setting.
minimal_backoff_time
25-2
PARAMETER
maximal_backoff_time
DESCRIPTION
Determines the maximum time between
attempts to deliver a message. The time
between each attempt to deliver a
deferred message will grow
exponentially until it reaches the value in
this setting.
The attempted deliveries are repeated at
this value until the
maximal_queue_lifetime is reached.
maximal_queue_lifetime
queue_run_delay = 900s
minimal_backoff_time = 900s
maximal_backoff_time = 3600s
maximal_queue_lifetime = 1d
So for one deferred mail, the life time is 24 hours, the first retry attempt is after 15
minutes, the second retry is after 30 minutes, and all subsequent retries after 60
minutes. That means there are about 25 retries before the
maximal_queue_lifetime value is reached.
25-3
Procedure
1.
2.
Click the Quarantine tab (default) or Archive tab, to configure a quarantine area
or an archive area. The list of areas appears in the table below.
3.
To modify the total disk size allowed for all quarantine areas or archive areas for
each scanner service, specify the size of the area next to Disk quota (per
scanner), and then select MB or GB from the drop-down box.
4.
5.
6.
Next to Delete messages older than, specify the number of days after which
IMSVA deletes the quarantined or archived messages. The value is exclusive. For
example, if you specify 15, IMSVA deletes the quarantined messages on the 16th
day.
7.
Select Synchronize all spam and email messages, that do not violate virus,
phishing, or Web reputation rules, to the EUQ database (for this area only),
to automatically save messages to the EUQ database .
25-4
Note
After selecting Synchronize all spam and email messages, that do not violate
virus, phishing or Web reputation rules, to the EUQ database (for this area
only), a check mark appears under the EUQ column of the table on the Quarantine
and Archive Settings screen.
8.
Click Save.
The Quarantine and Archive Settings screen reappears.
9.
To view or modify a quarantine or archive area, click the name of the area and
configure the settings above.
10. To delete a quarantine or archive area, select the check box next to it and click
Delete.
11. After modifying any settings, click Save.
Tip
Trend Micro recommends quarantining messages that you think you might want to analyze
and possibly send to the intended recipient later. Create different types of quarantine areas
for different types of messages, such as messages that violate spam scanning conditions or
messages that violate message content conditions.
Managing the Quarantine from the Actions Screen of a Policy Rule on page 25-6
Managing the Quarantine from Mail Areas & Queues > Settings on page 25-7
25-5
2.
To add a new quarantine area, click Add. To modify an existing quarantine area,
click the area name and then click Edit. An edit screen appears.
3.
4.
5.
Select Synchronize all spam and email messages, that do not violate virus,
phishing, or Web reputation rules, to the EUQ database (for this area only)
to automatically save messages to the EUQ database.
Note
After selecting Synchronize all spam and email messages, that do not violate
virus, phishing or Web reputation rules, to the EUQ database (for this area
only), a check mark appears under the EUQ column of the table on the Quarantine
and Archive Settings screen.
6.
7.
8.
25-6
2.
b.
Select MB or GB.
Note
When the total disk size for all the quarantined messages exceeds the quota on a
scanner, the oldest quarantined messages are deleted first to keep the size under the
quota.
3.
To add a new quarantine area, click Add. To modify an existing quarantine area,
click the area name. An edit screen appears.
4.
5.
6.
Select Synchronize all spam and email messages, that do not violate virus,
phishing, or Web reputation rules, to the EUQ database (for this area only)
to automatically save messages to the EUQ database.
25-7
Note
After selecting Synchronize all spam and email messages, that do not violate
virus, phishing or Web reputation rules, to the EUQ database (for this area
only), a check mark appears under the EUQ column of the table on the Quarantine
and Archive Settings screen.
7.
Click Save to return to the Mail Areas & Queues Management screen.
Managing the Archive from the Actions Screen of a Policy Rule on page 25-8
Managing the Quarantine from Mail Areas & Queues > Settings on page 25-7
2.
To add a new archive area, click Add. To modify an existing archive area, click the
area name and then click Edit. An edit screen appears.
3.
4.
25-8
This number represents the number of days after which IMSVA deletes the
archived messages. The value is exclusive. For example, if you specify 15, IMSVA
deletes the archived messages on the 16th day.
5.
6.
7.
To archive messages, select the radio button next to Archive modified to under
Monitor and select the desired archive area from the drop-down box.
2.
b.
Select MB or GB.
Note
When the total disk size for all the quarantined messages exceeds the quota on a
scanner, the oldest archived messages are deleted first to keep the size under the
quota.
3.
To add a new archive area, click Add. To modify an existing archive area, click the
area name. An edit screen appears.
4.
5.
25-9
This number represents the number of days after which IMSVA deletes the
archived messages. The value is exclusive. For example, if you specify 15, IMSVA
deletes the archived messages on the 16th day.
6.
Click Save to return to the Mail Areas & Queues Management screen.
7.
Click Save.
Querying Messages
You can perform a query on quarantined, archived, postponed, or deferred messages
before deciding which action to perform. After viewing the message details, you can
choose to release or delete archived messages from IMSVA.
Tip
Trend Micro recommends quarantining items that could pose a risk to your network, such
as messages and attachments that violate antivirus rules. Before you resend any quarantined
message, make sure that it does not pose a threat to your network.
Trend Micro recommends archiving only items that you want to reference later. Quarantine
items that could pose a threat to your network, such as messages and attachments that
violated an antivirus rule.
25-10
The Mail Areas & Queues Management screen appears. The Quarantine tab
displays by default. If it does not display, click Quarantine.
2.
3.
Search: Select the quarantine area, the reason the message was quarantined,
and the scanner that scanned the message.
Sender
Subject
Recipient(s)
Attachment(s)
Rule
Message ID
Note
When querying a message containing multiple recipients or attachments, type *string*
(where string is the name of one of the recipients or attachments).
4.
Click Display Log. The results appear at the bottom of the screen showing the
timestamp, sender, recipient, subject, and reason for quarantining the message.
5.
25-11
To sort the table, click any of the column headings (except reason).
If too many items appear on the list, click the arrow buttons on top of the list
to move to the next page or select the desired page to view from the dropdown list.
To change the number of items that appears in the list at a time, select a new
display value from the drop-down list at the bottom of the table.
6.
To view details about any quarantined message, click the timestamp for the item.
The Quarantine Query screen appears showing the message and all of its details.
7.
To resend any message, click the check box next to it in the query result table, and
then click Deliver or Reprocess.
Deliver: The message is sent directly to the recipient, bypassing all rules
except virus scan rules.
Reprocess: The message only bypasses the current rule, and may be
quarantined again by other filters.
Tip
Trend Micro does not recommend resending messages that violated antivirus filters.
Doing so could put your network at risk.
8.
To delete any message, click the check box next to it in the query result table, and
then click Delete.
Note
IMSVA only records and shows the attachment names if you have specified
Attachment as a scanning condition. However, if the number of attachments in the
message exceeds the maximum number specified in condition, the attachment name
will not be shown.
25-12
2.
3.
4.
Search: Select the archive area, the reason the message was archived, and the
scanner that scans the message.
Sender
Subject
Recipient(s)
Attachment(s)
Rule
Message ID
Note
When querying a message containing multiple recipients or attachments, type *string*
(where string is the name of one of the recipients or attachments).
5.
Click Display Log. The results appear at the bottom of the screen showing the
timestamp, sender, recipient, subject, and reason for archiving the message.
6.
To sort the table, click any of the column headings (except reason).
25-13
7.
If too many items appear on the list, click the arrow buttons on top of the list
to move to the next page or select the desired page to view from the dropdown list.
To change the number of items that appears in the list at a time, select a new
display value from the drop-down list at the bottom of the table.
To view details about any archived message, click the timestamp for the item.
The Archive Query screen appears showing the message and all of its details.
8.
To delete any message, click the check box next to it in the query result table, and
then click Delete.
Note
IMSVA only records and shows names of attachments if you have specified
Attachment as a scanning condition. However, if the number of attachments in the
message exceeds the maximum number specified in condition, the attachment name
will not be shown.
2.
3.
4.
25-14
Sender
Subject
Recipient(s)
Attachment(s)
Rule
Internal ID
5.
Click Display Log. The results appear at the bottom of the screen showing the
timestamp, sender, recipient, subject, and reason for postponing the message.
6.
To sort the table, click any of the column headings (except reason).
If too many items appear on the list, click the arrow buttons on top of the list
to move to the next page or select the desired page to view from the dropdown list.
To change the number of items that appears in the list at a time, select a new
display value from the drop-down list at the bottom of the table.
7.
To view details about any postponed message, click the Timestamp for the item.
The message and all of its details appears.
8.
To resend any message, click the check box next to it in the query result table, and
then click Release.
9.
To delete any message, click the check box next to it in the query result table, and
then click Delete.
2.
25-15
3.
4.
Sender
Recipient(s)
Reason
5.
Click Display Log. The results appear at the bottom of the screen showing the
timestamp, sender, recipient, size, the reason for deferring the message, the host
(or device), and the next retry time.
6.
To sort the table, click any of the column headings (except reason).
If too many items appear on the list, click the arrow buttons on top of the list
to move to the next page or select the desired page to view from the dropdown list.
To change the number of items that appears in the list at a time, select a new
display value from the drop-down list at the bottom of the table.
7.
To view details about any postponed message, click the Timestamp for the item.
The message and all of its details appears.
8.
To resend any message, click the check box next to it in the query result table, and
then click Release.
9.
To delete any message, click the check box next to it in the query result table, and
then click Delete.
25-16
Note
If you reconfigure a device as a child device and it has deferred messages in its
deferred queue, then you register it to a parent device, you will not be able to view
any of the original deferred messages on the child device from the parent device
management console. Handle all deferred messages before changing device roles.
After you perform a query for quarantined messages, click the timestamp for the
quarantined item in the query result table. The Quarantine Query screen appears
showing the following information:
Timestamp
Sender
Reason
Recipient
Rules
Subject
Scanner
Original Size
Message ID
Internal ID
Attachments
25-17
If both ATSE and Deep Discovery Advisor are enabled, IMSVA also displays the
following information:
2.
3.
After you perform a query for archived messages, click the timestamp for the
archived item in the query result table. The Archive Query screen appears showing
the following information:
25-18
Timestamp
Sender
Reason
Recipient
Rules
Subject
Scanner
Original Size
Message ID
Internal ID
Attachments
If both ATSE and Deep Discovery Advisor are enabled, IMSVA also displays the
following information:
2.
3.
25-19
Tip
Trend Micro does not recommend saving messages or attachments that violated an
antivirus rule.
After you perform a query for postponed messages, click the timestamp for the
postponed item in the query result table. The query screen appears showing the
following information:
Timestamp
Sender
Reason
Recipient
Rules
Subject
Scanner
Original Size
Message ID
Internal ID
Attachments
25-20
If both ATSE and Deep Discovery Advisor are enabled, IMSVA also displays the
following information:
2.
3.
After you perform a query for deferred messages, click the timestamp for the
deferred item in the query result table. The query screen appears showing the
following information:
Arrival Time
Sender
Recipient
25-21
Host
Size
Postfix Queue ID
Each recipient and corresponding reason appear at the bottom of the screen.
2.
3.
To change the number of items that appears on a page at one time, select a
new display value from the Display drop-down box on the upper right of the
list.
To move to another page, select a number from the drop-down box to the
right, or click one of the arrow icons.
Delete with NDR: Delete the message and send a message to the recipient
informing them of the deferred message.
2.
25-22
25-23
3.
25-24
4.
5.
Select Allow end user to deliver quarantined mail in EUQ directly to allow
end users to deliver quarantined messages directly to the recipient. The message
bypasses all rules except virus scanning rules.
6.
Select Allow end users to retrieve quarantined email messages with alias
email addresses to allow end users to retrieve quarantined messages using alias
email addresses configured in Microsoft Exchange.
7.
Select Control the "auto add" approved Sender behavior when an end user
reprocesses a message to allow or prevent end users from adding a sender
automatically when a message is being processed.
8.
Select Enable NTLM to allow end users single sign-on access the EUQ
management console using the NTLM authentication protocol.
9.
Select Enable Kerberos to allow end users single sign-on access the EUQ
management console using Kerberos authentication protocol.
b.
Create a new user account in your domain for the host on which IMSVA is
installed.
c.
Where:
filename is where the generated keytab file will be stored. For example, C:
\test.keytab.
instance is the hostname of the computer where IMSVA is installed. For
example, imsva.test.com.
REALM is the uppercase name of the realm you want to authenticate with,
normally the same with the domain name on DNS server. For example,
TEST.COM.
25-25
d.
e.
25-26
b.
c.
d.
e.
a.
From the drop-down list, select Browse LDAP groups. The groups
appear in the table below.
b.
c.
Using EUQ
To use EUQ, you must enable and configure LDAP.
Procedure
1.
2.
Do the following:
Enable EUQ: To enable EUQ, select the check box next to Enable EndUser Quarantine, and then click Save.
Clear the EUQ database: To remove all data (including spam and approved
sender information) from all EUQ services in a group, click Remove.
Redistribute EUQ data: If there are multiple devices with EUQ enabled on
your network, you can redistribute EUQ data across all devices to improve
EUQ performance. Redistribute data after you start or stop an EUQ service
on a device or add a new device that has an EUQ service. Also redistribute
data before you use the command line interface to remove a device with an
EUQ service.
25-27
Redistributing Data
Tip
Trend Micro recommends the following:
after redistributing EUQ, the administrator informs all end users to verify that the
newly added approved senders are still available.
that the administrator notifies all end users not to add EUQ approved senders list
when the administrator is adding a child device and redistributing EUQ.
Procedure
1.
2.
Click Redistribute.
Note
If you register an EUQ-enabled child device to its parent, add senders to the
approved senders list, and then redistribute EUQ data, some of the newly added
approved senders might not appear.
25-28
Chapter 26
Notifications
This chapter provides you with general instructions on the tasks that you need to
perform for the day-to-day maintenance of IMSVA. For more information on each field
on the management console, refer to the Online Help.
Topics include:
26-1
Event Notifications
You can configure IMSVA to send an email or SNMP notification to you or specific
users upon the occurrence of the following categories of events:
System Status: Informs you when certain IMSVA performances fall below the
desired level. For example, when a scanner service stops working, or when the
number of messages in the delivery queue exceeds the desired quantity.
Scheduled Update Event: Alerts you when IMSVA is able or unable to perform a
scheduled update of the scan engine or pattern files from the update source onto
the admin database.
Scanner Update Result: Alerts you when IMSVA is unable to update the engine
or pattern files on any scanner.
Deep Discovery Advisor Settings: Alerts you when Deep Discovery Advisor
analysis is incomplete or invalid
Smart Scan Event: Alerts you when IMSVA reverts to Conventional Scan after an
unsuccessful attempt to connect to the Smart Protection Network.
Note
Component update is a two-step process:
26-2
1.
At the scheduled time, the IMSVA admin database will first check the update source
for new engine or pattern files.
2.
IMSVA scanners will then check the admin database at regular intervals for updated
components. The default interval is three minutes.
Notifications
2.
26-3
3.
4.
26-4
Sender's email address: Specify the email address to appear as the sender.
SMTP server address: Specify the Fully Qualified Domain Name (FQDN)
or the IP address of the SMTP server that delivers email on the network.
SMTP server port: Specify the port number that IMSVA uses to connect to
the SMTP server.
Preferred charset: IMSVA will use this setting to encode the notification
messages.
Message header: Specify the text to appear at the top of the notification.
Message footer: Specify the text to appear at the bottom of the notification.
Notifications
Note
SNMP Trap is the notification message sent to the Simple Network Management
Protocol (SNMP) server when events that require administrative attention occur.
5.
Click Save.
If you are using the Configuration Wizard, click Next.
26-5
2.
26-6
Service on any scanner stops for more than: Specify the number of
minutes.
Notifications
Data partition free space on any host is less than: Specify the number of
MB.
MTA queue free space on any host is less than: Specify the number of
MB.
Retry queue folder contains more messages than: Specify the number of
messages.
Note
The notifications Delivery queue contains more messages than and Retry
queue folder contains more messages thanonly function when IMSVA runs
with Postfix.
3.
Under Scheduled Update Event, click the Unsuccessful and Successful links to
edit notifications for component updates.
Scheduled Update Event is the event in which the latest engine and pattern files
from the Update Source are updated onto the IMSVA admin database.
4.
Under Scanner Update Results, click the Applying engine or pattern update
fails on any scanner link to edit the notification.
Scanner Update Results are the results of updating the latest engine and pattern
files from the IMSVA admin database onto the scanners.
5.
26-7
6.
Under Smart Scan Event, click Unable to connect to the Smart Protection
Network to edit the notification.
This notification is sent when IMSVA reverts to Conventional Scan after several
unsuccessful attempts to connect to the Smart Protection Network.
7.
Select the Email and/or SNMP check boxes according to how you would like to
receive the notification.
8.
Click Save.
EUQ Digest
The EUQ digest is a notification that IMSVA sends to inform users about messages that
were processed as spam and temporarily stored in the EUQ.
Note
IMSVA sends EUQ digests only if there are new quarantined messages since the last digest.
IMSVA does not send EUQ digests for distribution list addresses. To manage the
quarantined messages of distribution lists, users must log on to the EUQ management
console.
Total spam mail count: Number of new messages in EUQ since the last
notification
26-8
Notifications
Inline action links: Links that users can click to apply actions to quarantined
messages and to add senders to the Approved Senders list
Note
Inline action links display only if you enable this feature.
2.
3.
4.
Under Digest Schedule, click the radio button next to one of the following
frequencies:
5.
Weekly: Select the day and time of day from the drop-down boxes.
Under Digest Mail Template, specify the subject and notification content.
To see a list of variables to include in the notification, click Variables list.
6.
Select Enable inline action to allow users to apply actions from the EUQ digest.
7.
Click Save.
26-9
Release: Releases the message from quarantine. IMSVA may scan the message
again or deliver it to the original recipients.
Note
If you enabled the Control the auto-add approved Sender behavior when end
user reprocess a message feature, IMSVA automatically adds senders of released
messages to the Approved Senders list.
Add sender to Approved list: Prevents IMSVA from identifying messages from this
sender as spam.
IMSVA automatically deletes messages after a period that you specify. You can also
manually delete and release messages from the IMSVA management console. Users
cannot select actions for messages that have been deleted or released.
Important
Trend Micro does not recommend forwarding notifications. Inline action links remain
active in forwarded messages.
Editing Notifications
Procedure
1.
2.
3.
4.
26-10
Click Save.
Part V
Administering IMSVA
Chapter 27
27-1
Importing/Exporting
To back up IMSVA settings, export the settings from the management console. In the
event of system failure, you can restore the settings by importing the configuration file
that you have backed up previously. Note the following when importing/exporting
settings:
You cannot import or export the component list and child device registration
information.
When exporting/importing your settings, the database will be locked. Therefore, all
IMSVA actions that depend on database access, such as performing a mail trace,
will not function.
SMTP Routing Settings that were exported from IMSVA 8.0 or IMSS 7.1 and
subsequently imported into IMSVA 8.5, will overwrite existing settings in the
current IMSVA version.
Adjust the component list and child device registration information after import if
necessary
Back up a copy of the current configuration before each import operation, in order
to recover from mistaken import processes.
27-2
To reuse the original configuration settings from IMSS 7.1 or IMSVA 8.0 after
upgrading to IMSVA 8.5, import the configuration files that you have backed up
previously.
Start/stop any services on the device or in the group to which the device belongs.
Register/unregister any child devices into/from the group to which the device
belongs.
Procedure
1.
2.
Click Export.
3.
When the dialog box appears, click Save and save it to your computer.
4.
Start/stop any services on the device or in the group to which the device belongs.
Register/unregister any child devices into/from the group to which the device
belongs.
27-3
If the import is unsuccessful, the configuration will roll back to the original settings
before the import. If the import is unsuccessful during the import of EUQ approved list
settings, all settings rollback except for the EUQ approved list settings.
Procedure
1.
2.
3.
Verify that no services are starting or stopping. If services are starting or stopping,
wait until the operation has completed.
4.
5.
Under Import Configuration Files, click Browse... and locate the file.
6.
Click Import. The original IMSVA settings and rules, such as domain-based
delivery settings, will be deleted and replaced by the imported settings and rules. All
services on each device in the group restart to apply the imported settings and
rules. Wait until all services restart.
Note
Only services that were running while the import performs will restart.
7.
If the import is successful, you may click Download log file to view details of the
import.
27-4
Start/stop any services on the device or in the group to which the device
belongs.
Register/unregister any child devices into/from the group to which the device
belongs.
If the import is unsuccessful, the configuration will roll back to the original settings
before the import. If the import is unsuccessful during the import of EUQ
approved list settings, all settings rollback except for the EUQ approved list
settings.
Backing Up IMSVA
Trend Micro recommends exporting your settings to:
Keep a backup: In case a problem occurs with the IMSVA application file and
you need to rescue the application. Importing your configuration backup will
prevent you from having to configure all settings again.
Replicate settings across several devices: If you have several devices on your
network, you do not need to configure most settings on each of them separately.
Exporting Settings
During export, do not:
Start/stop any services on the device or in the group to which the device belongs
27-5
Register/unregister any child devices into/from the group to which the device
belongs
Procedure
1.
2.
Click Export.
3.
When the File Download dialog box appears, click Save to save the configuration
file to your computer.
27-6
4.
Start/stop any services on the device or in the group to which the device belongs.
Register/unregister any child devices into/from the group to which the device
belongs.
Procedure
1.
27-7
2.
Verify that no services are starting or stopping. If services are starting or stopping,
wait until they are stable.
3.
4.
Under Import Configuration Files, click Browse... and locate the file.
5.
Click Import.
The original settings and rules, such as domain-based delivery settings, will be
deleted and replaced by the imported settings and rules. All services on each device
in the group will be restarted to apply the imported settings and rules. Wait until all
services are restarted.
27-8
IMPORTING IMSVA
EUQ SETTINGS
Enabled
Enabled
Enabled
Disabled/Stopped
Disabled
Enabled
No settings import
Disabled
Disabled
No settings import
Replicating Settings
If you have installed multiple IMSVA scanners that do not share the same admin
database, you can use Trend Micro Control Manager to replicate settings across these
scanners without having to configure each scanner separately. If the scanners share the
same admin database, it is not necessary to replicate settings.
Do the following if you intend to replicate settings using Control Manager:
Enabling MCPAgent
IMSVA automatically installs the Trend Micro Management Communication Protocol
agent during installation. To integrate with Control Manager, provide the Control
Manager server details and enable the agent from the management console.
Procedure
1.
2.
27-9
3.
4.
5.
Click Save.
27-10
Procedure
1.
2.
Locate the source IMSVA scanner from the Product Directory tree.
3.
Mouseover Configure.
A drop-down list appears.
4.
5.
6.
27-11
Chapter 28
28-1
About EUQ
IMSVA provides web-based EUQ to improve spam management. The web-based EUQ
service allows end users to manage the spam quarantine of their personal accounts and
of distribution lists that they belong to. Messages that are determined to be spam are
quarantined. These messages are indexed into a database by the EUQ agent and are then
available for end users to review, delete, or approve for delivery.
You can specify the period to keep messages in the quarantine. IMSVA automatically
deletes messages that are not released from quarantine. Deleted messages cannot be
recovered.
EUQ Authentication
Enabling EUQ requires one of the following authentication methods:
LDAP authentication: Before enabling EUQ, configure LDAP settings using any
of the following ways:
2.
28-2
3.
4.
Enabling EUQ
Enabling EUQ requires one of the following authentication methods:
LDAP
SMTP
For details about EUQ authentication, see EUQ Authentication on page 28-2.
Procedure
1.
2.
3.
Use SMTP Server for authentication: When selected, the SMTP settings
section appears. Specify recipient domains and server addresses. For more
information, see Configuring SMTP Server Settings on page 28-5.
28-3
Note
IMSVA 8.5 supports only SMTP servers that use the plain and login
authentication mechanisms.
IMSVA 8.5 does not support secure connections when using SMTP servers for
authentication.
4.
Click Save.
Note
Your settings will not be saved automatically. To avoid losing your information, do
not navigate away from the page without clicking Save.
What to do next
The EUQ service automatically starts. To manually start the service, see Starting the
EUQ Service on page 28-7.
28-4
Verify that the newly added approved senders are still available.
Instruct end users not to add approved senders to the list while you are adding a
child device and redistributing EUQ.
2.
On the EUQ Management screen, select Use SMTP Server for EUQ
authentication.
28-5
3.
Click Add.
The SMTP Server Configuration screen appears.
4.
28-6
Note
You can use the following formats to specify domains:
company.com
*: Any domain
A domain can only be listed once. Only unique domains will be added to the
list.
Only one SMTP server can be assigned to a domain. However, more than one
domain can be mapped to an SMTP server.
5.
Click OK.
The information appears in the SMTP settings table.
Note
Deleting all domain and server information disables EUQ. Deleted items cannot be
recovered.
Go to System Status.
28-7
4.
Click Redistribute to redistribute the EUQ data among the devices in the group.
5.
Select System Status from the menu and verify that the EUQ service is active (or
inactive).
28-8
Procedure
1.
2.
28-9
28-10
3.
4.
5.
Select Allow end user to deliver quarantined mail in EUQ directly to allow
end users to deliver quarantined messages directly to the recipient. The message
bypasses all rules except virus scanning rules.
6.
Select Allow end users to retrieve quarantined email messages with alias
email addresses to allow end users to retrieve quarantined messages using alias
email addresses configured in Microsoft Exchange.
7.
Select Control the "auto-add" approved sender behavior when an end user
reprocesses a message and select a value from the drop-down list.
8.
Select Enable NTLM to allow end users single sign-on access the EUQ
management console using the NTLM authentication protocol.
28-11
9.
Select Enable Kerberos to allow end users single sign-on access to the EUQ
management console using Kerberos authentication protocol.
b.
Create a new user account in your domain for the host on which IMSVA is
installed.
c.
Where:
filename is where the generated keytab file will be stored. For example, C:
\test.keytab.
instance is the hostname of the computer where IMSVA is installed. For
example, imsva.test.com.
REALM is the uppercase name of the realm you want to authenticate with,
normally the same with the domain name on DNS server. For example,
TEST.COM.
account is the account created for IMSVA. For example, user@test.com.
password is the password of the account.
d.
e.
28-12
12. Specify a logon page message that appears on the user's browser when he/she
starts to access the quarantined messages.
13. Under Select LDAP groups, select the check box next to Enable all to allow all
LDAP group users to access quarantined spam.
14. To add individual LDAP groups, clear the Enable all check box and do either of
the following:
b.
c.
d.
e.
From the drop-down list, select Browse LDAP groups. The groups
appear in the table below.
b.
c.
28-13
An alternative to using the IP address is to use the target servers fully qualified domain
name (FQDN).
Domino: user1/domain
28-14
AUTHENTICATION TYPE
SMTP
Domino
28-15
Only one user can manage the EUQ at any given time. IMSVA forces the current user
to log off if another user:
Procedure
1.
2.
3.
4.
Click Next.
A new screen appears and the system sends a notification to the distribution list.
5.
6.
28-16
Once
Disabling EUQ
Before disabling EUQ, inform your users that they should manage their quarantined
spam.
Procedure
1.
2.
3.
Optional: Remove all EUQ data from each device to save disk space. To do so,
click Remove on the EUQ Management tab.
4.
Click Save.
28-17
Chapter 29
29-1
Full: Users have complete access to the features and settings contained in the
menu item.
Read: Users can view features and settings contained in the menu item, but cannot
modify them.
None: Users will not see the menu item, preventing them from viewing or
configuring any of the settings in the menu item.
Procedure
1.
2.
Click Add.
The Add Administrator Account screen appears with the Authentication tab
displaying.
29-2
3.
4.
b.
IMSVA Authentication: Specify the user name, new password, and the
new password confirmation.
IMSA Authentication: Specify the user name, new password, and the
new password confirmation.
29-3
5.
b.
29-4
Select Full, Read, or None for each of the following access areas that appear
on the IMSVA management console menu:
Summary
Cloud Pre-Filter
Policy
IP Filtering
Reports
Logs
Administration
Click Save.
Note
a.
Only the default IMSVA administrator account can add new administrator
accounts. Custom administrator accounts cannot do so even if you assign full
permission to the Administration area.
b.
Custom administrator accounts with full administration rights can only change
their own IMSVA passwords. If you forget the default administrator account
password, contact Trend Micro technical support to reset the password.
2.
3.
4.
Click Save.
2.
Click Delete.
29-5
3.
Click OK.
Note
You can only delete custom administrator accounts, not the default IMSVA
administrator account.
29-6
2.
3.
Protocol: Select the type of protocol the scanner uses to communicate with
the policy service (HTTP or HTTPS).
Click Save.
29-7
Synchronized column. IMSVA automatically synchronizes the accounts daily. You can
manually trigger synchronization by clicking Save & Synchronize.
Note
If more than one LDAP server is enabled, End-User Quarantine and EUQ single sign-on
cannot be enabled.
If the LDAP settings on the Administration > Connections > LDAP screen are not
configured, the following LDAP related features will not work:
Policy > [any rule] > [sender or recipient] > [search for LDAP user and
groups]
Administration > End-User Quarantine > User Quarantine Access > [select
groups from LDAP search below]
Administration > Admin Accounts > Add > [specify LDAP authentication]
2.
Click Add.
The LDAP Settings screen appears.
3.
4.
Next to LDAP server type, select the type of LDAP servers on your network:
29-8
Domino
OpenLDAP
5.
6.
7.
Next to Listening port number, specify the port number that the LDAP server
uses to listen to access requests.
8.
9.
Under LDAP cache expiration for policy services and EUQ services, specify
the Time to live in minutes.
Time To Live: Determines how long IMSVA retains the LDAP query results in
the cache. Specifying a longer duration enhances LDAP query during policy
execution. However, the policy server will be less responsive to changes in the
LDAP server. A shorter duration means that IMSVA has to perform the LDAP
query more often, thus reducing performance.
10. Under LDAP admin, specify the administrator account, the corresponding
password and the base distinguished name. Refer to the table below for assistance
on what to specify under this section according to the LDAP server type:
TABLE 29-1. LDAP Server Types
LDAP SERVER
Active Directory
LDAP ADMIN
ACCOUNT
(EXAMPLES)
Without Kerberos:
user1@domain.co
m (UPN) or
domain\user1
BASE
DISTINGUISHED
NAME (EXAMPLES)
dc=domain,
dc=com
AUTHENTICATION
METHOD
Simple
Advanced (with
Kerberos)
With Kerberos:
user1@domain.co
m
29-9
LDAP SERVER
Active Directory
Global Catalog
LDAP ADMIN
ACCOUNT
(EXAMPLES)
Without Kerberos:
user1@domain.co
m (UPN) or
domain\user1
With Kerberos:
user1@domain.co
m
BASE
DISTINGUISHED
NAME (EXAMPLES)
dc=domain,
dc=com
dc=domain1,dc=co
m (if mutiple
unique domains
exist)
AUTHENTICATION
METHOD
Simple
Advanced (with
Kerberos)
OpenLDAP
cn=manager,
dc=test1, dc=com
dc=test1, dc=com
Simple
Lotus Domino
user1/domain
Not applicable
Simple
Sun iPlanet
Directory
uid=user1,
ou=people,
dc=domain,
dc=com
dc=domain,
dc=com
Simple
Simple
29-10
Note
Only Active Directory and Active Directory Global Catalog support Kerberos
Authentication.
2.
3.
4.
Next to LDAP server type, select the type of LDAP servers on your network:
Domino
OpenLDAP
5.
6.
7.
Next to Listening port number, specify the port number that the LDAP server
uses to listen to access requests.
8.
9.
Under LDAP cache expiration for policy services and EUQ services, specify
the Time to live in minutes.
Time To Live: Determines how long IMSVA retains the LDAP query results in
the cache. Specifying a longer duration enhances LDAP query during policy
29-11
execution. However, the policy server will be less responsive to changes in the
LDAP server. A shorter duration means that IMSVA has to perform the LDAP
query more often, thus reducing performance.
10. Under LDAP admin, specify the administrator account, the corresponding
password and the base distinguished name. Refer to the table below for assistance
on what to specify under this section according to the LDAP server type:
TABLE 29-2. LDAP Server Types
LDAP SERVER
Active Directory
LDAP ADMIN
ACCOUNT
(EXAMPLES)
Without Kerberos:
user1@domain.co
m (UPN) or
domain\user1
BASE
DISTINGUISHED
NAME (EXAMPLES)
AUTHENTICATION
METHOD
dc=domain,
dc=com
Simple
dc=domain,
dc=com
Simple
Advanced (with
Kerberos)
With Kerberos:
user1@domain.co
m
Active Directory
Global Catalog
Without Kerberos:
user1@domain.co
m (UPN) or
domain\user1
With Kerberos:
user1@domain.co
m
29-12
Advanced (with
Kerberos)
OpenLDAP
cn=manager,
dc=test1, dc=com
dc=test1, dc=com
Simple
Lotus Domino
user1/domain
Not applicable
Simple
Sun iPlanet
Directory
uid=user1,
ou=people,
dc=domain,
dc=com
dc=domain,
dc=com
Simple
dc=domain1,dc=co
m (if mutiple
unique domains
exist)
Simple
2.
) or (
29-13
Procedure
1.
2.
3.
4.
b.
Specify the port IMSVA uses for incoming POP3 connections, the POP3
server IP address, and the POP3 server port number.
c.
Click OK.
d.
5.
Under Message Text, modify the message that IMSVA sends to users if messages
that they are trying to receive trigger a filter and are quarantined or deleted.
6.
Click Save.
29-14
Note
The incoming port on your scanners must be idle or the IMSVA daemon might not
function properly.
The following example shows how to configure generic POP3 settings for Outlook:
Procedure
1.
2.
3.
29-15
AUTH command. For this service, a separate port on the proxy has to be set up for each
specific POP3 server that any client might want to connect.
The following example shows how to configure dedicated POP3 settings in Microsoft
Outlook:
Procedure
1.
2.
3.
Set the POP3 port to 1100, which is the port that the IMSVA dedicated POP3
service is listening on.
Procedure
1.
2.
3.
29-16
4.
Option
Description
Server
Communication
protocol
Web server
authentication
Description
Enable proxy Select the check box to enable the proxy server.
Proxy type
Select the protocol that the proxy server uses: HTTP, SOCKS4, or
SOCKS5.
Proxy server Specify the proxy server FQDN or IP address, port number, and
the user name and password.
5.
Port
User name
Password
Click Save.
If you are using the Configuration Wizard, click Next.
If you enabled the agent, it will soon register to the Control Manager server. If you
disabled the agent, IMSVA will soon log off from the Control Manager server.
Verify the change on the Control Manager management console.
29-17
3.
2.
3.
4.
Click >>.
The address appears in the table.
5.
Click Save.
29-18
3.
4.
5.
Click Save.
29-19
2.
3.
4.
Click Save.
Cloud Pre-Filter: Provides message approved and blocked list filters and scanning
for spam, viruses, and other threats before the messages reach your network.
Trend Micro Antivirus and Content Filter: Basic scanning and filtering
functionality. You can think of this product as the IMSVA program itself.
Spam Prevention Solution (SPS): A built-in filter that helps IMSVA identify
content typically found in spam.
29-20
Trend Micro Email Encryption: Trend Micro Email Encryption integrates with
IMSVA to encrypt and decrypt messages and to block messages that cannot be
decrypted.
GLBA
HIPAA
PCI-DSS
SB-1386
US PII
You can activate IMSVA products through the management console. If a product
license expires, renew the license, obtain a new Activation Code, and specify the code
through the management console. If the product remains inactive, its features are
disabled.
29-21
Procedure
1.
Product
Version
Full: Indicates that you have purchased the full licensed product.
Status: Indicates whether the product has expired or has been activated.
2.
Click View detailed license online for the license you want to view.
3.
Click Check Status Online to check the status of your license agreement on the
Trend Micro web site.
29-22
2.
3.
4.
Click Activate.
The management console might access the Trend Micro web site to activate the
license.
If you are unable to reach the Trend Micro web site, verify your network settings
and try again.
29-23
2.
Click View detailed license online to view detailed information about the license.
3.
Click Check Status Online. The management console accesses the Trend Micro
web site to activate the license.
If you are unable to reach the Trend Micro web site, verify your network settings
and try again.
IMSVA checks the status of your license 90, 60, 30, and 0 days before the
expiration of the current license, and every day after the expiration of the current
license. Once renewed, IMSVA automatically updates the stored license
information.
Tip
You can wait for IMSVA to update the license status automatically. However, Trend
Micro recommends that you manually update it as soon as you extend the lifetime of
the Activation Code.
Activating Products
If you do not have an Activation Code, use the Registration Key that came with your
product to register online.
Activate products from one of the following screens:
29-24
2.
3.
Cloud Pre-Filter
Regulatory Compliance
Click Next.
Note
The Activation Code comes in the format: XX-XXXX-XXXXX-XXXXX-XXXXXXXXXX-XXXXX.
2.
3.
29-25
4.
Click Activate.
The management console may access the Trend Micro web site to activate the
license. If you are unable to reach the Trend Micro web site, verify your network
settings and try again.
Procedure
1.
2.
3.
Click Save.
29-26
Chapter 30
30-1
Configure initial settings, such as the device IP address and host name
Verify the computer you are using can ping IMSVAs IP address.
2.
Use an SSH client to connect to IMSVAs IP address and TCP port 22.
3.
4.
30-2
CLI Overview
After you open the CLI menu, it displays the following:
Procedure
1.
Verify the computer you are using can ping IMSVAs IP address.
2.
Use an SSH client to connect to IMSVAs IP address and TCP port 22.
3.
Password: The password used for the OS shell when installing the product
30-3
Enter CLI.
a.
Verify the computer you are using can ping IMSVAs IP address.
b.
Use a SSH client to connect to IMSVAs IP address and TCP port 22.
c.
2.
At the prompt >, type enable and press ENTER. The prompt changes from > to
#.
3.
Type the password used for the CLI when installing the product and press
ENTER.
30-4
View
Privileged
Parameters
None
Examples:
To disable the IMSVA management console on all NICs:
configure module IMSVA adminUI disable
View
Privileged
Parameters
Examples:
To enable the IMSVA management console for the NIC eth0:
configure module IMSVA adminUI enable eth0
30-5
View
Privileged
Parameters
None
Examples:
To enable the IMSVA management console for all NICs:
configure module IMSVA adminUI enable all
View
Privileged
Parameters
Examples:
To set the date to August 12, 2010 and the time to 3:40 PM:
configure system date 2010-08-12 15:40:00
View
30-6
Privileged
Parameters
Examples:
To configure the primary DNS with an IP address of 192.168.10.21:
configure network dns ipv4 192.168.10.21
To configure the primary and secondary DNS with the following values:
View
Privileged
Parameters
Examples:
30-7
To configure the primary and secondary DNS with the following values:
View
Privileged
Parameters
Examples:
To change the host name of the IMSVA device to test.imsva.com:
configure network hostname test.imsva.com
View
30-8
Privileged
Parameters
Examples:
To configure an NIC with the following values:
Interface: eth0
IP address: 192.168.10.10
View
Privileged
Parameters
Examples:
To configure an NIC with the following values:
Interface: eth0
IP address: 2001:db8::
Subnet mask: 64
30-9
View
Privileged
Parameters
None
Examples:
To change the password required to enter Privileged mode
configure system password enable
View
Privileged
Parameters
Examples:
To change the parent IP address of the current device to 192.168.10.24:
configure module IMSVA role change-parent 192.168.10.24
30-10
View
Privileged
Parameters
None
Examples:
To unregister a child IMSVA device from a parent IMSVA device:
configure module IMSVA role unregister
View
Privileged
Parameters
Example:
To add a new route entry:
configure network route ipv4 add 172.10.10.0/24 192.168.10.1 eth1
View
Privileged
30-11
Parameters
Example:
To add a new route entry:
configure network route ipv6 add 2001:db8:10ff::ae:4/64 2001:db8::1 eth1
View
Privileged
Parameter
Example:
To set the default route for an IMSVA device:
configure network route ipv4 default 192.168.10.1
View
Privileged
Parameter
Example:
30-12
View
Privileged
Parameters
Example:
To delete a route for an IMSVA device:
configure network route ipv4 del 172.10.10.0/24 192.168.10.1 eth1
View
Privileged
Parameters
30-13
Example:
To delete a route for an IMSVA device:
configure network route ipv6 del 2001:db8:10ff::ae:4/64 2001:db8::1 eth1
View
Privileged
Parameters
None
Examples:
To disable SSH on all NICs:
configure service ssh disable
View
Privileged
Parameters
Examples:
To enable SSH on NIC eth0:
configure service ssh enable eth0
30-14
View
Privileged
Parameters
None
Examples:
To enable SSH on all NICs:
configure service ssh enable all
View
Privileged
Parameters
Examples:
To configure the IMSVA device to use the time zone for the following location:
Region: America
City: New York
configure system timezone America New_York
30-15
CITY
Cairo
Harare
Nairobi
America
Anchorage
Bogota
Buenos_Aires
Caracas
Chicago
Chihuahua
Denver
Godthab
Lima
Los_Angeles
Mexico_City
New_York
Noronha
Phoenix
Santiago
St_Johns
Tegucigalpa
30-16
REGION/COUNTRY
Asia
CITY
Almaty
Baghdad
Baku
Bangkok
Calcutta
Colombo
Dhaka
Hong_Kong
Irkutsk
Jerusalem
Kabul
Karachi
Katmandu
Krasnoyarsk
Kuala_Lumpur
Kuwait
Magadan
Manila
Muscat
Rangoon
Seoul
Shanghai
Singapore
Taipei
Tehran
Tokyo
Yakutsk
30-17
REGION/COUNTRY
CITY
Atlantic
Azores
Australia
Adelaide
Brisbane
Darwin
Hobart
Melbourne
Perth
Europe
Amsterdam
Athens
Belgrade
Berlin
Brussels
Bucharest
Dublin
Moscow
Paris
Pacific
Auckland
Fiji
Guam
Honolulu
Kwajalein
Midway
30-18
REGION/COUNTRY
US
CITY
Alaska
Arizona
Central
East-Indiana
Eastern
Hawaii
Mountain
Pacific
enable
Enters privileged mode so privileged commands can be provided.
Syntax:
enable
View
Root
Parameters
None
Examples:
To enter privileged mode:
enable
exit
Exits privileged mode.
Exits the session for those not in privileged mode.
30-19
Syntax:
exit
View
Root/Privileged
Parameters
None
Examples:
To exit privileged mode or to exit the session when not in privileged mode:
exit
help
Displays the CLI help information.
Syntax:
help
View
Privileged/Root
Parameters
None
Examples:
To display the CLI help information:
help
history
Displays the current session's command line history.
Syntax:
history [limit]
View
30-20
Privileged/Root
Parameters
[limit]: Specifies the size of the history list for the current session
Specifying "0" retains all commands for the session.
Examples:
To specify six commands for the size of the history list:
history 6
logout
Logs out of the current CLI session.
Syntax:
logout
View
Root
Parameters
None
Examples:
To logout from the current session:
logout
ping
Pings a specified host.
Syntax:
ping [-c num_echos] [-i interval] <dest>
View
Root
30-21
Parameters
Examples:
To ping the IP address 192.168.1.1:
ping 192.168.1.1
ping6
Pings a specified host.
Syntax:
ping6 <host>
View
Root
Parameter
Example:
To ping the IP address 2001:db8::21:
ping6 2001:db8::21
30-22
View
Privileged
Parameters
Examples:
To delete email message D10D4478A5 from the email message queue:
start task postfix drop D10D4478A5
View
Privileged
Parameters
None
Examples:
To deliver all queued email messages:
start task postfix flush
View
Privileged
Parameters
None
30-23
Examples:
To display all postfix queued email messages:
start task postfix queue
View
Privileged
Parameters
None
Examples:
To start the postfix mail system:
start service postfix
View
Privileged
Parameters
None
Examples:
To stop the postfix mail system:
stop service postfix
30-24
reboot
Reboots the IMSVA device immediately or after a specified delay.
Syntax:
reboot [time]
View
Privileged
Parameters
Examples:
To reboot the IMSVA device immediately:
reboot
View
Privileged
Parameters
None
Examples:
To rescue the application software:
start task rescue
30-25
resolve
Resolves an IPv4 address from a hostname or resolves a hostname from an IPv4
address.
Syntax:
resolve <dest>
View
Privileged
Parameter
Examples:
To resolve the hostname from IP address 192.168.10.1:
resolve 192.168.10.1
resolve6
Resolves a hostname from an IPv6 address.
Syntax:
resolve6 <dest>
View
Privileged
Parameter
Example:
To resolve the hostname from IP address 2001:db8::21:
resolve6 2001:db8::21
30-26
service IMSVA
Starts, stops, or restarts all IMSVA application services.
Syntax:
{start | stop | restart} service IMSVA
View
Privileged
Parameters
Examples:
To start all IMSVA services:
start service IMSVA
View
Root
Parameters
None
Examples:
30-27
View
Root
Parameters
Examples:
To display the file system disk space usage of the IMSVA device:
show storage statistic
show network
Displays various IMSVA network configurations.
Syntax:
show network [arp | connections | dns | firewall | hostname | interface
| open-ports | route]
View
30-28
Root
Parameters
Examples:
To display the ARP tables:
show network arp
30-29
show kernel
Displays the IMSVA devices OS kernel information.
Syntax:
show kernel {messages | modules | parameters | iostat}
View
Root
Parameters
Examples:
To display the OS kernels messages:
show kernel messages
30-30
View
Root
Parameters
Examples:
To display the latest 25 IMSVA scanner logs:
show module IMSVA log imssd
show service
Displays the IMSVA service status.
Syntax:
show service [ntp <enabled | server-address> | ssh]
View
Root
30-31
Parameters
Examples:
To display the NTP service status:
show service ntp
show process
Displays the status of IMSVA processes currently running.
Syntax:
show process [top]
View
Root
Parameters
Examples:
To display the status of IMSVA processes currently running:
show process
30-32
View
Root
Parameters
None
Examples:
To display the role of the IMSVA device:
show module IMSVA role
show memory
Displays the IMSVA devices system memory information.
Syntax:
show memory [vm | statistic]
View
Root
Parameters
Examples:
To display IMSVA device virtual memory statistics:
show memory vm
View
Root
30-33
Parameters
None
Examples:
To display the IMSVA management console status
show module IMSVA status adminUI
show system
Displays various IMSVA system settings.
Syntax:
show system [date | timezone | uptime | version]
View
Root
Parameters
Examples:
To display the current time and date of the IMSVA device:
show system date
30-34
shutdown
Specifies shutting down the IMSVA device immediately or after a specified delay.
Syntax:
shutdown [time]
View
Privileged
Parameters
Examples:
To shut down the IMSVA device immediately:
shutdown
stop process
Stops a specific IMSVA process.
Note
Use the command show process on page 30-32 to display the <pid> for each
process.
Syntax:
stop process [core] <process name>
View
Privileged
Parameters
Examples:
30-35
traceroute
Displays the tracking route to a specified destination.
Syntax:
traceroute [-h hops] <dest>
View
Root
Parameters
Examples:
To display the route to IP address 172.10.10.1 with a maximum of 6 hops:
traceroute 172.10.10.1
traceroute6
Displays the tracking route to a specified destination.
Syntax:
traceroute6 [-h hops] <dest>
View
Root
Parameters
30-36
Examples:
To display the route to IP address 2001:db8::21 with a maximum of 6 hops:
traceroute6 2001:db8::21
30-37
Chapter 31
31-1
eth0: 192.168.10.1
eth1: 192.168.20.1
With eth0 specified as the Internal Communication Port, a child IMSVA device
registering to the parent must specify the parent IP address as 192.168.10.1.
Child devices also have an Internal Communication Port. Both parent and child
devices must communicate with each other through their Internal Communication
Port.
Note
The default Internal Communication Port for all IMSVA devices is eth0.
31-2
Determine the device settings for the new device (IP address, net mask, gateway IP
address, DNS server IP address, NTP server IP address if necessary).
2.
Procedure
1.
Navigate to Dashboard.
The Dashboard appears.
2.
Check the Mail Queues widget on the System Overview tab. Verify that there are
no messages in the delivery queue or deferred queue for the device you want to
remove. If there are messages in the delivery queue or deferred queue, wait
momentarily for IMSVA to process them.
3.
4.
Under Managed Services, stop all services on the device you want to remove.
When the services stop, the Unregister button appears.
31-3
Note
If the device was using EUQ, redistribute the data across the remaining EUQ
databases before you unregister the child device:
5.
a.
b.
Click Redistribute.
Click Unregister. The child will be automatically removed from the group.
Tip
Trend Micro recommends that you notify your users to not add members to the
EUQ approved list while you are adding a child device and redistributing EUQ data.
2.
3.
4.
5.
6.
Use the start task postfix flush command to flush postfix queue.
7.
31-4
Remove all child devices from the group (see Removing a Child Device from a Group on
page 31-3).
2.
Unregister the child from the parent by doing one of the following:
Use the management console (see Removing a Child Device from a Group on page
31-3).
b.
c.
d.
31-5
2.
Procedure
1.
2.
3.
4.
5.
Procedure
1.
31-6
2.
3.
4.
5.
Changing IP Addresses
This section explains how to change the IP address of parent and child devices.
Note
When changing IP addresses in the Command Line Interface (CLI) through Secure Shell
(SSH), do not close the SSH client until the connection times out. Otherwise, the IP
change script may not execute completely, causing inconsistencies in the settings.
2.
Connect to the parent device through an SSH connection and do the following
from the CLI:
a.
b.
c.
Connect to each child device through an SSH connection and do the following:
a.
b.
31-7
c.
d.
e.
2.
3.
On the parent device, do the following from the IMSVA management console:
a.
b.
c.
Connect to the child device through an SSH connection and do the following from
the CLI:
a.
b.
c.
d.
e.
31-8
b.
c.
31-9
Chapter 32
32-1
2.
3.
Click Upload.
32-2
After the file finishes uploading, the package type, build number, and title appear
under Latest uploaded package.
Select the check boxes next to the devices to which you want to deploy the update.
2.
Click Update.
3.
4.
5.
Navigate to Administration > Updates > System & Applications to view the
summary screen.
Note
a.
During an update, do not modify any other settings. If you are updating several
devices, you can click Cancel to stop the update of the next device.
b.
If you have applied some patches on a child device, and later unregister this
child device from the parent device, IMSVA automatically rescues the system
and application files, then re-applies the patches during unregistration. Due to
the re-application of the patches, it might take some time before the
management console for the new parent device (unregistered child device)
becomes available.
If a device check box is grayed out, you cannot deploy the files to the device
because the device:
Has more up-to-date files than the ones you are trying to deploy.
32-3
Is a child device and the patch requires you to upload the files and deploy
them to the parent first, or vice versa.
Under Host Name, click the name of the device you want to view.
A summary screen appears showing the updates and related log information.
2.
3.
Rescuing IMSVA
Rescuing IMSVA means that you reinstall the application.
32-4
WARNING!
All settings you configure through the management console are deleted when you rescue
the application. Before rescuing the application, create a backup of your settings.
Log on to the IMSVA management console as admin and export your current
settings.
2.
Enter the CLI as admin (see Entering the OS Shell on page 30-3).
3.
4.
5.
Type y to confirm. IMSVA rescue begins, and will take several minutes.
6.
After the rescue process completes, log on to the IMSVA management console and
import your saved settings.
7.
Re-activate Trend Micro Antivirus and Content Filter and Spam Prevention
Solution (SPS) using the Activation Code.
32-5
Chapter 33
33-1
Troubleshooting
For common issues that you might encounter when configuring or administering
IMSVA, see Troubleshooting Issues on page 33-2. If you have additional problems, check
the Trend Micro Knowledge Base.
For troubleshooting and FAQ information pertaining to the deployment of IMSVA,
refer to the IMSVA Installation Guide.
Troubleshooting Issues
DESCRIPTION AND RESOLUTION
ISSUE
General
Unable to access the
management console or
other components.
The target port is not in the firewall approved list. Open the
ports as shown in IMSVA Ports on page 33-15 in the
firewall.
If you are unable to access the management console, do
the following:
1.
2.
33-2
ISSUE
Unable to activate products
2.
3.
2.
33-3
ISSUE
Unable to update
components
2.
33-4
1.
2.
ISSUE
Unable to export
configuration files
2.
3.
4.
5.
Server displays as
disconnected in the System
Status screen.
33-5
ISSUE
When viewing detailed
information for quarantined
or archived messages,
attachment information is
sometimes not available
2.
3.
2.
3.
4.
Click Save.
33-6
ISSUE
Unable to access the EUQ
management console
Do the following:
Verify that you are using the correct URL and port
number.
33-7
ISSUE
Users are unable to log on
to EUQ management
console
Do the following:
1.
2.
3.
a.
b.
c.
d.
e.
Verify that users are using the correct logon name and
password.
Note
IMSVA uses LDAP2 servers as backup for LDAP 1
servers. Ensure the LDAP 1 and LDAP 2 servers
are synchronized. If a user's account exists only on
one of the LDAP servers, users will not be able to
consistently log on to the EUQ management
console.
33-8
ISSUE
Users are unable to log on
to EUQ management
console using NTLM single
sign-on (SSO)
b.
c.
2.
3.
4.
33-9
ISSUE
The EUQ digest does not
display quarantined
message information
correctly
Some quarantined
messages are not
appearing on the EUQ
management console
2.
2.
3.
33-10
ISSUE
Users are unable to log on
to the EUQ management
console using Kerberos
single sign-on (SSO)
2.
3.
4.
5.
6.
IP Filtering Issues
33-11
ISSUE
FoxProxy cannot start up
2.
Open foxproxy.ini.
3.
4.
5.
Unable to connect to
FoxProxy
FoxProxy processes
messages slowly
2.
33-12
ISSUE
Unable to view connections
that FoxProxy is blocking
Open foxproxy.ini.
2.
3.
2.
33-13
ISSUE
No IP Profiler log
information exists
foxmsg.****
foxnullmsg.****
foxreport.****
2.
3.
4.
33-14
ISSUE
IP profiler does not block IP
addresses in the Blocked
List.
IMSVA Ports
The following table outlines all ports used by IMSVA in their default configuration.
TABLE 33-1. IMSVA Ports
PORT NUMBER
CONFIGURATION LOCATION
25
110
5060
33-15
PORT NUMBER
CONFIGURATION LOCATION
8005
IMSVA management
console server (Tomcat)
management port that can
handle Tomcat
management command.
{IMVA}\UI\adminUI\conf\
server.xml: Server\port
8009
{IMSVA}\UI\euqUI\conf\
server.xml: Server\Service
\Connector (protocol=AJP
\1.3)\port
8015
{IMSVA}\UI\euqUI\conf
\server.xml:Server\port
8442
Management console
Tomcat port. This port is
used to handle requests
sent to Tomcat.
{IMSVA}\UI\adminUI\conf
\server.xml: Server\Service
\Connector\port
8445
Management console
listening port. You need to
open this port to log on to
the management console
using a web browser.
{IMSVA}\UI\php\conf
\widget.conf: Listen
\VirtualHost
8446
{IMSVA}\UI\euqUI\conf
\server.xml:Server\Service
\Connector\port
8447
{IMSVA}\UI\euqUI\conf
\EUQ.conf:Listen\VirtualHost
\ServerName
33-16
PORT NUMBER
CONFIGURATION LOCATION
10024
IMSVA scanner
reprocessing port.
Messages released from
the central quarantine area
in the admin database and
from the EUQ database will
be sent to this port for
reprocessing.
imss.ini\[Socket_3]\proxy_port
10026
IMSVA_HOME/postfix/ect/
postfix/master.cf
15505
IMSVA uses the following ports when you enable related service:
33-17
PORT NUMBER
CONFIGURATION LOCATION
389
80
443
88
53
WARNING!
Do not modify the
port number.
Log on the operating system with the root account using the SSH Client Tool.
2.
3.
33-18
Example:
./fwportconf add udp 161 or ./fwportconf del udp 161
Email Reputation
Procedure
1.
2.
3.
Add the IP addresses or domains that you do not want blocked to the Approved
List.
33-19
IP Profiler
Why is the domain name of an IP address that was added to
the blocked/approved list always N/A?
IMSVA does not determine the domain name of an IP address that was added to the
blocked/approved list (IMSVA does resolve the IP address of an added domain name).
Asterisk (*): Used as a wildcard character to search for characters. You can use
the asterisk (*) to search for email addresses or file names.
To search for email addresses, refer to the following examples:
TABLE 33-2. Search for email addresses
EXAMPLE
33-20
DESCRIPTION
*@domain.tld,
name@*.tld
EXAMPLE
*@*.tld
DESCRIPTION
Valid representation of both the name and the domain
(not the TLD).
DESCRIPTION
*.*
*.extension
name.*
End-User Quarantine
If I am using Kerberos, why are users unable to log on to the
EUQ console with a short name: domain\user_name?
Kerberos servers cannot accept user names in the format: Domain\user_name.
Kerberos requires the format:
user_name@domain.xxx
33-21
Procedure
1.
2.
Active Directory uses port 389 for LDAP query. If one item cannot be queried in one
domain controller, it uses the LDAP referral mechanism to query another domain
controller. Use port 389 if your company has only one domain or if port 3268 is
unavailable.
2.
3.
33-22
4.
2.
3.
4.
Example 1: bob@imsstest.com
Note
The logon name is not an email address (though it appears as one).
33-23
ActiveUpdate
How do I roll back a pattern file?
Click the Rollback button on the System Status screen.
Control Manager
How do I verify that IMSVA is registered to Control
Manager? Unregistered from Control Manager?
There are three ways to verify:
33-24
2.
Click Products.
The Product Directory screen appears.
3.
2.
2.
3.
33-25
LDAP
I cannot add an LDAP server using the correct admin
account. Why?
First, verify that the LDAP server can be connected to IMSVA. Next, verify the LDAP
server type and logon name format are configured correctly.
Other FAQs
How does IMSVA process a partial message?
The key BypassMessagePartial in theIMSVA configuration file imss.ini controls
how IMSVA processes partial messages.
33-26
If the key is set to yes (default setting), IMSVA will bypass partial messages.
33-27
The total size of each rule cannot exceed 640KB. The total size includes the rule route
(senders/recipients), rule filter (scanning condition), and rule action. Assuming that each
email address/LDAP account consists of 20 characters, IMSVA can support at least
10,000 senders/recipients for the rule route.
The maximum number of mail addresses for one address group is 10,000.
The maximum number of Approved/Block Senders for SPS rule is 5000.
2.
33-28
3.
4.
5.
6.
Why does the message size scan condition not work for
encrypted messages?
IMSVA treats encrypted messages as a special type of message. Most scan conditions do
not apply. IMSVA requires the use of the encrypted message scan condition to scan or
perform actions on encrypted messages.
If there is a firewall on your test segment, verify that the firewall allows access
through port 9000. Port 9000 is the default port that Cloud Pre-Filter uses to
connect to the Cloud service. Open port 9000 if the firewall does not allow
connection to the port.
If you do not use a proxy server for connection to Cloud Pre-Filter, use the
following command from IMSVA to verify that IMSVA can connect to Cloud PreFilter:
telnet ws.emailsecurity.trendmicro.com 9000
If you use a proxy server to connect to Cloud Pre-Filter, verify the proxy server
allows access through port 9000.
33-29
Support Information
Troubleshooting Resources
Before contacting technical support, consider visiting the following Trend Micro online
resources.
Trend Community
To get help, share experiences, ask questions, and discuss security concerns with other
users, enthusiasts, and security experts, go to:
http://community.trendmicro.com/
Go to http://esupport.trendmicro.com.
2.
Select a product or service from the appropriate drop-down list and specify any
other related information.
The Technical Support product page appears.
3.
33-30
4.
If no solution is found, click Submit a Support Case from the left navigation and
add any relevant details, or submit a support case here:
http://esupport.trendmicro.com/srf/SRFMain.aspx
A Trend Micro support engineer investigates the case and responds in 24 hours or
less.
Trend Micro blogs, Twitter, Facebook, YouTube, and other social media
Threat Encyclopedia
Most malware today consists of "blended threats" - two or more technologies combined
to bypass computer security protocols. Trend Micro combats this complex malware with
products that create a custom defense strategy. The Threat Encyclopedia provides a
comprehensive list of names and symptoms for various blended threats, including
known malware, spam, malicious URLs, and known vulnerabilities.
Go to http://www.trendmicro.com/vinfo to learn more about:
Malware and malicious mobile code currently active or "in the wild"
33-31
Phone
Fax
+1 (408) 257-2003
Website
http://www.trendmicro.com
Email address
support@trendmicro.com
Computer brand, model, and any additional hardware connected to the endpoint
33-32
33-33
Other Resources
In addition to solutions and support, there are many other helpful resources available
online to stay up to date, learn about innovations, and be aware of the latest security
trends.
TrendEdge
Find information about unsupported, innovative techniques, tools, and best practices
for Trend Micro products and services. The TrendEdge database contains numerous
documents covering a wide range of topics for Trend Micro partners, employees, and
other interested parties.
See the latest information added to TrendEdge at:
http://trendedge.trendmicro.com/
Download Center
From time to time, Trend Micro may release a patch for a reported known issue or an
upgrade that applies to a specific product or service. To find out whether any patches
are available, go to:
http://www.trendmicro.com/download/
If a patch has not been applied (patches are dated), open the Readme file to determine
whether it is relevant to your environment. The Readme file also contains installation
instructions.
TrendLabs
TrendLabs is a global network of research, development, and action centers committed
to 24x7 threat surveillance, attack prevention, and timely and seamless solutions delivery.
Serving as the backbone of the Trend Micro service infrastructure, TrendLabs is staffed
by a team of several hundred engineers and certified support personnel that provide a
wide range of product and technical support services.
TrendLabs monitors the worldwide threat landscape to deliver effective security
measures designed to detect, preempt, and eliminate attacks. The daily culmination of
33-34
these efforts is shared with customers through frequent virus pattern file updates and
scan engine refinements.
Learn more about TrendLabs at:
http://cloudsecurity.trendmicro.com/us/technology-innovation/experts/
index.html#trendlabs
33-35
Appendices
Appendices
Appendix A
A-1
DESCRIPTIONS
Stores malformed
messages.
queue_malform=
/opt/trend/imss/queue/
malform
queue_archive=
/opt/trend/imss/queue/
archive
queue_quarantine =
Stores quarantined
messages.
/opt/trend/imss/queue/
quarantine
A-2
queue_notify=
queue_notify_big=
/opt/trend/imss/queue/
notify
/opt/trend/imss/queue/
notifybig
queue_postpone=
queue_postpone_big=
/opt/trend/imss/queue/
postpone
/opt/trend/imss/queue/
postponebig
queue_deliver=
queue_deliver_big=
/opt/trend/imss/queue/
deliver
/opt/trend/imss/queue/
deliverbig
queue_reprocess=
queue_reprocess_big=
/opt/trend/imss/queue/
reprocess
/opt/trend/imss/queue/
reprocessbig
Stores notification
messages.
Stores postponed
messages.
queue_handoff=
queue_handoff_big=
/opt/trend/imss/queue/
handoff
/opt/trend/imss/queue/
handoffbig
queue_undeliverable=
/opt/trend/imss/queue/
undeliverable
queue_unnotify=
/opt/trend/imss/queue/
unnotify
DESCRIPTIONS
Stores messages pending
handoff.
Stores undeliverable
messages.
Stores undeliverable
notification messages.
/var/spool/postfix/
incoming
/var/spool/postfix/
active
/var/spool/postfix/
deferred
/var/spool/postfix/
corrupt
Unreadable or damaged
queue files are moved here
for inspection.
/var/spool/postfix/hold
/var/app_data/imss/
dtas_upload
A-3
and
/var/log
Temporary Folder
IMSVA stores all application-generated temporary files in the temporary folder:
/opt/trend/imss/temp/
and
/tmp
Note
This directory is not configurable.
and
/opt/trend/imss/queue/notifybig
A-4
A-5
Appendix B
IMSVA Scripts
This appendix provides you with a list of IMSVA scripts and their respective parameters
that you can invoke from the command line.
B-1
PARAMETERS
DESCRIPTION
dbctl.sh
db_maintain.sh
{vacuum|reindex|analyze|
all}
Note
Do not run this script on its own.
B-2
IMSVA Scripts
SCRIPT
PARAMETERS
DESCRIPTION
forceUpdate.sh
DBDSN username
password
foxproxyd
IP Profiler service
ibe_server.sh
imssctl.sh
imsstop.sh
imssstart.sh
openldap.sh
postfix
Postfix daemon
regippro.sh
reg / unreg
S99ADMINUI
Central Controller
S99CLEANEU
Q
S99CLEANEX
PIRE
S99CMAGENT
S99DIGEST
S99DTASAGE
NT
CMAgent service
Sends the EUQ digest message
B-3
SCRIPT
PARAMETERS
DESCRIPTION
S99EUQ
EUQ service
S99FOXDNS
Foxdns service
S99IMSS
S99MANAGER
Manager service
S99MONITOR
S99MSGTRAC
ING
S99POLICY
Policy service
S99REPORT
[option]:
-s: generates
centralized reports
(covers all one-time
and scheduled reports
configured on the
management console)
Note
Do not run this script on its own.
traffic data
log maintenance
S99SCHEDUL
ED
start / stop
S99UPDATE
B-4
IMSVA Scripts
SCRIPT
S99WRSAGEN
T
PARAMETERS
start / stop / restart
DESCRIPTION
WRS agent service
B-5
Appendix C
C-1
C-2
From the menu bar, select File > New > Virtual Machine.
2.
Under Virtual Machine Configuration, leave the Typical radio button selected.
3.
Click Next.
C-3
FIGURE C-2. Select a Name and Location for this Virtual Machine
4.
C-4
In the Name field, type an appropriate machine name and then click Next.
5.
6.
Click Next.
C-5
C-6
7.
8.
Click Next.
9.
For the guest operating system, select Linux > Other Linux (64-bit).
C-7
11. Select the number of processors for the virtual machine. IMSVA takes advantage
of the Virtual SMP, so select the maximum number of virtual processors available.
12. Click Next.
C-8
C-9
C-10
C-11
C-12
21. Specify at least 120GB of disk space. IMSVA requires at least 120GB disk space.
See for more information on disk space allocation.
Tip
Trend Micro recommends 250GB or more of disk space for message quarantine and
logging purposes.
C-13
23. Specify the advanced options if required. Usually these options do not need to be
changed.
24. Click Next.
C-14
C-15
Appendix D
D-1
Full-virtualization
Para-virtualization
Tip
Trend Micro recommends installing IMSVA in para-virtualization mode. This allows
IMSVA to achieve much higher throughput performance and supports enterprise
networking environments. IMSVA provides the necessary integrated Hyper-V drivers to
support the installation under Hyper-V as a para-virtualization virtual machine.
D-2
Note
Creating a New Virtual Machine on page D-6 only covers installing IMSVA on Hyper-V in
full-virtualization mode. Using Para-Virtualization Mode on page D-18 describes how to
convert full-virtualization to para-virtualization.
2.
D-3
A dialog box appears prompting you to select the location of the virtualization
server that you want to connect to.
3.
4.
Right-click the Windows 2008 R2 server and select Virtual Network Manager.
5.
D-4
Create a new virtual network by selecting External from the list of options and
clicking Add.
6.
From the External drop-down menu, select the physical network adaptor you
want to connect to.
Note
The physical adaptor must be connected to the network and have access to the
corporate network and the Internet.
D-5
D-6
From the Hyper-V Server Manager menu, right-click the Windows 2008 R2 server,
and select New > Virtual Machine.
2.
Click Next.
D-7
D-8
3.
In the Name field, type a meaningful machine name. If you plan to store the
virtual machine to another folder, select Store the virtual machine in a different
location and provide the correct location.
4.
Click Next.
5.
6.
Click Next.
D-9
7.
8.
Click Next.
D-10
9.
10. Specify a location to store the virtual hard disk, and click Next.
D-11
11. Keep the default setting Install an operating system later, and click Next.
D-12
12. Verify your settings and click Finish. Some manual configuration is still required.
13. Right-click your new Virtual Machine, and select Settings.
The Settings for test screen appears.
14. Click Add Hardware, and select Legacy Network Adapter.
D-13
D-14
D-15
19. Select the image file for IMSVA from the DVD Drive in the Hardware list.
20. Click OK.
D-16
D-17
D-18
Tip
Trend Micro recommends using IMSVA in Para-Virtualization Mode. This allows IMSVA
to achieve much higher throughput performance and supports enterprise networking
environments. IMSVA provides the necessary integrated Hyper-V drivers to support the
installation under Hyper-V as a para-virtualization virtual machine.
Procedure
1.
Open the CLI console and backup your current network configuration.
2.
D-19
3.
4.
Reconfigure the Virtual Network Adapter on the Virtual Machine Settings screen.
D-20
5.
Power on the virtual machine. Open the CLI console and reconfigure the network
configuration. The virtual machine is now in Para-Virtualization Mode.
D-21
2.
a.
b.
Use an SSH client to connect to IMSVA and modify the kernel boot options by
editing the GRUB configuration file (/boot/grub/grub.conf). Add the following to
the appropriate kernel line:
notsc divider=4
For example:
title IMSVA (2.6.18-128.1.OpenVA.2.0.1067)
root (hd0,0)
kernel /vmlinuz-2.6.18-128.1.OpenVA.2.0.1067
3.
4.
On another SSH session, set the hardware clock to the newly synchronized time.
$ hwclock --systohc
5.
D-22
Index
A
about IMSS appliances, 1-2
activate
IMSVA, 4-17
license, 29-23
product, 29-24
add
administrator accounts, 3-2, 29-2
address group
add, 15-5
delete, 15-9
edit, 15-9
address groups
examples of, 15-2
understand, 15-2
administrator accounts
add, 3-2, 29-2
delete, 3-5, 29-5
edit, 3-5, 29-5
manage, 3-2, 29-2
Advanced Threat Scan Engine, 7-2
adware, 1-11
antivirus rule, 17-10
APOP, 13-4
application
rescuing, 32-5
approved list
add IP addresses, 10-21
approved senders list
configure, 17-20
archive, xvii
configure settings, 25-3
archive areas
manage, 25-8
archived messages
view, 25-18
asterisk wildcard
use, 20-13
attachment size
scanning conditions, 17-29
audience, xix
B
back up
IMSVA, 27-5
blocked list
add IP addresses, 10-22
blocked senders list
configure, 17-20
bounced mail settings
configure, 10-16
C
C&C email, 17-12
centralized archive and quarantine, xvii
centralized logging, xvii
centralized policy, xvii
change
device roles, 31-5
Web console password, 2-7
child
add to group, 31-3
change to parent, 31-5
configure IP Settings, 29-18
Internal Communication Port, 31-8
remove from group, 31-3
reset when connection broken, 31-4
Cloud Pre-Filter
configure DNS MX records, 9-14
IN-1
IN-2
Index
connection settings
configure, 11-3, 29-6
Control Manager
enable agent, 27-9
replicate settings, 27-10
see Trend Micro Control Manager, 1-12
Control Manager server settings
configure, 4-15
Conventional scan, 2-12
D
dashboard
using, 22-2
database
configure maintenance schedule, 29-19
data protection
compliance templates
predefined expressions, 15-28
Deep Discovery Advisor, 7-4
default tabs, 22-3
deferred messages
view, 25-21
delete
address group, 15-9
administrator accounts, 3-5, 29-5
delivery settings
configure, 26-3
Deployment Settings
configure, 4-4
device
rescuing, 32-4
application, 32-5
device role
change child to parent, 31-5
parent to child, 31-5
device roles
change, 31-5
dialers, 1-11
Direct Harvest Attack (DHA) settings
configure, 10-13
display
domains, 10-23
suspicious IP addresses, 10-23
documentation
IMSVA related, xix
domains
display, 10-23
Email Encryption, 8-4, 8-5
E
edit
address group, 15-9
administrator accounts, 3-5, 29-5
Email Encryption
managing domains, 8-4
registering domains, 8-5
understand, 8-2
email relay, 11-7
Email reputation, xviii
Administration Console, 10-3
configure, 10-18
enable, 10-8
email threats
spam, 1-5
unproductive messages, 1-5
enable
Control Manager agent, 27-9
Email reputation, 10-8
End-User Access, 28-9
IP Profiler, 10-8
IP Profiler rules, 10-10
POP3 scanning, 13-3
encrypting messages, 18-3
Encryption settings
IN-3
configuring, 18-2
End-User Access
enable, 28-9
ERS
MTA settings, 10-2
using, 10-2
EUQ, xvii, 25-27, 28-2
authentication, 28-2
disable, 28-17
open the console, 28-13
start, 28-7
web console, 28-13
event criteria
configure, 26-5
event notifications, 26-2
export notes, 27-2
expression lists
manage, 15-13
expressions
configure, 15-14
regular, 15-19
F
FAQ
archive, 33-20
ERS, 33-19
EUQ, 33-21
IP Profiler, 33-20
quarantine, 33-20
File Reputation Services, 1-15
filtering, how it works, 1-7
filters
examples of, 15-2
G
generate
reports, 23-2
IN-4
H
hacking tools, 1-11
I
import notes, 27-2
IMSS appliances
about, 1-2
IMSVA
backing up, 27-5
rescue, 32-4
restore, 27-7
scripts, B-2
internal addresses
configure, 4-13, 16-2
Internal Communication Port
child, 31-8
parent, 31-7
IP Filtering
configure, 10-8
configure bounced mail settings, 10-16
configure Direct Harvest Attack
(DHA) settings, 10-13
configure spam settings, 10-10
configure virus settings, 10-12
IP Filtering Service
about, 10-2
IP Filtering tab, 22-4
IP Profiler, xviii
enable, 10-8
enable rules, 10-10
J
joke program, 1-11
L
LDAP settings
configure, 4-10, 29-7
Index
IN-5
example 1, 20-4
finalize, 17-45
manage, 14-1
policy, xvii
policy notification
add, 15-38
edit, 15-38
POP3 messages
scan, 13-2
POP3 scanning
enable, 13-3
POP3 settings
configure, 13-4, 29-14
postponed messages
view, 25-20
predefined expressions, 15-28
Pre-Filter, xiv
product licenses
manage, 29-20
view, 29-21
product services, 2-10
Q
quarantine, xvii
configure settings, 25-3
quarantine and archive, 25-2
quarantine areas
manage, 25-5
quarantined messages
view, 25-17
query
archive areas, 25-13
deferred messages, 25-15
IP filtering logs, 24-16
logs, 24-4
messages, 25-10
message tracking logs, 24-8
IN-6
Index
SMTP
notification server, A-5
SMTP messages
scan, 11-1
SMTP routing, 11-2
configure, 4-5, 11-2
SMTP settings
configure, 11-2
spam prevention, xviii
spam settings
configure, 10-10
spam text exemption rules
configure, 17-21
specify
actions, 17-35
route, 17-2
scanning conditions, 17-9
update source, 5-3
spyware/grayware, 1-10
adware, 1-11
dialers, 1-11
entering the network, 1-11
hacking tools, 1-11
joke program, 1-11
password cracking applications, 1-11
remote access tools, 1-11
risks and threats, 1-11
start
EUQ, 28-7
support
knowledge base, 33-30
resolve issues faster, 33-32
TrendLabs, 33-34
suspicious IP addresses
display, 10-23
system overview tab, 22-3
IN-7
System Settings
configure, 4-3
System Status screen, 21-2
T
tabs
add a tab, 22-5
Cloud Pre-Filter, 22-5
configure a tab, 22-6
default tabs, 22-3
IP Filtering, 22-4
message traffic, 22-4
system overview, 22-3
understand, 22-2
tag subject
add, 17-44
TMCM settings
configure, 29-16
transport layer, 11-6
TrendLabs, 33-34
Trend Micro Control Manager, 1-12
agent, 1-12
server, 1-12
troubleshooting, 33-2
email notifications, 33-4
EUQ quarantined messages, 33-10
EUQ web console access, 33-8
IP Filtering, 33-11
Web EUQ digest, 33-10
true file type, 17-29
U
understand
Email Encryption, 8-2
widgets, 22-6
update
application files, 5-8
IN-8
automatically, 5-6
manually, 5-4
pattern files, 5-2
scan engine, 5-2
system and application, 32-2
system files, 5-8
update source
configure, 4-8
specify, 5-3
User Quarantine Access
configure, 25-22
V
view
archived messages, 25-18
deferred messages, 25-21
postponed messages, 25-20
product licenses, 29-21
quarantined messages, 25-17
virus settings
configure, 10-12
W
Web console password
change, 2-7
Web EUQ, xvii
Web EUQ Digest
configure settings, 26-8
Web Reputation Services, 1-16
whats new, xii
widgets
add a widget, 22-9
configure a widget, 22-8
edit a widget, 22-8
understanding, 22-6
using a widget, 22-7