Intrusion Defense Firewall 1.2 User's Guide - Trend Micro? Online ...

Encrypting IDF Server to DB
Communication
Communication between the IDF Server Plug-in and the database is not encrypted by default. This is for
performance reasons and because the channel between the Server Plug-in and the database may already
be secure (either they are running on the same Computer or they are connected by crossover cable, a
private network segment, or tunneling via IPSec).
However, if the communication channel between the IDF Server Plug-in and the database is not secure,
you should encrypt the communications between them. Do this by editing the dsm.properties file
located in \IDF Server Plug-in\webclient\webapps\ROOT\WEB-INF\
MS SQL Server
Add the following line to dsm.properties:
database.SqlServer.ssl=require
Save and close the file. Stop and restart the Server Plug-in service.
Oracle Database
Add the following lines to dsm.properties:
database.Oracle.oracle.net.encryption_types_client=(3DES168)
database.Oracle.oracle.net.encryption_client=REQUIRED
database.Oracle.oracle.net.crypto_checksum_types_client=(MD5)
database.Oracle.oracle.net.crypto_checksum_client=REQUIRED
Save and close the file. Stop and restart the IDF Server Plug-in service.
Note that Oracle Database must be configured to accept encrypted communication. Consult your
Oracle Database documentation for instructions.
Running a Client Plug-in on the Database Server
Encryption should be enabled if you are using a Client Plug-in to protect the database. When you carry out
a Security Update, the IDF Server Plug-in stores new DPI Rules in the database. The rule names
themselves will almost certainly generate false positives as they get parsed by the Client Plug-in if the
data is not encrypted.
© Copyright 2010 Trend Micro Inc. www.trendmicro.com
All rights reserved. - 136 -