Updating means downloading antivirus and anti-spam components from the update source to InterScan™ Messaging Security Appliance (IMSA). To automate the update process, configure the update schedule.
To help protect your network, IMSA uses the following components:
Scan engine—Scans for viruses and Trojans.
Virus pattern—Identifies virus signatures—unique patterns of bits and bytes that signal the presence of a virus.
Spyware/grayware pattern—Identifies unique patterns of bits and bytes that signal the presence of certain types of potentially undesirable files and programs, such as adware and spyware.
IntelliTrap pattern—Identifies real-time compressed executable file types that commonly hide viruses and other potential threats.
IntelliTrap exceptions—Provides a list of real-time compressed executable file types that are commonly not associated with viruses and other potential threats.
Anti-spam engine—Scans for spam.
Spam pattern—Identifies spam content.
To verify if IMSA has the latest components, perform a manual update. For instructions, see Updating Manually.
You can configure an update schedule or download components manually. Configuring the update schedule, which is enabled by default, relieves you of the task of keeping IMSA up-to-date. However, if you think that a virus or Internet threat has infected computers in the network, you can immediately update your components manually.
|
Trend Micro can update components several times daily. For a reliable level of protection, configure the update schedule to download components hourly (the default selection.) |
If there is a proxy server between IMSA and the Internet, you must configure proxy server settings or IMSA will not be able to connect to the update source.
By default, IMSA downloads components from the Trend Micro ActiveUpdate server, which is the only source for up-to-date components. However, if you are using Trend Micro Control Manager (TMCM) to manage IMSA, you can update the components from the TMCM server. See your TMCM documentation for details on how a TMCM server can act as an update source.
See also: