Types of updates from Trend Micro include:
- Software upgrades: New software such as the Deep SecurityAgent and Relay.
- Security updates: Rules and malware patterns that Deep Security Agent software uses to identify potential threats. Types of security updates include:
- Pattern updates: Used by Anti-Malware.
- Rule updates: Used by:
- Intrusion Prevention
- Integrity Monitoring
- Log Inspection
(Application Control rule updates are created locally, based on your computers' software. They are not from Trend Micro.)
Trend Micro releases new rule updates every Tuesday, with additional updates as new threats are discovered. Information about the updates is available in the Trend Micro Threat Encyclopedia.
Deep Security will only inform you of minor version updates (not major) of software. For example, if you have Deep Security Agent 9.6.100, and Trend Micro releases 9.6.200, an alert will tell you that software updates are available. However, if 10.0.xxx (a major version difference) is released and you don't have any 10.0 agents, the alert will not appear (even though 10.0is newer than 9.6.100).
When deploying a new release of the Deep Security Agent:
- Deep Security Relays must be the same version or newer than all agents in your environment. The relays provided as part of Workload Security are kept up to date and compatible with the latest available agents. However, if you have deployed your own relays, always upgrade them before upgrading your agents.
- Workload Security customers can ignore the Minimum DSM Version for agents. We host and update the manager as part of the service, and it is always compatible with the latest available agents.
Both software updates and security updates are digitally signed. In addition to automatic checks, if you want to manually validate the signatures or checksums, you can use external tools such as:
- sha256sum (Linux)
- Checksum Calculator (Windows)
- jarsigner (Java Development Kit (JDK); see Check digital signatures on software packages)
When security updates are viewed or used, Workload Security validates the signature. A correct digital signature indicates that the software is authentically from Trend Micro and hasn't been corrupted or tampered with. If the digital signature is invalid, Workload Security does not use the file. A warning is also recorded in log files such as server0.log:
WARNING: ThID:85|TID:0|TNAME:Primary|UID:1|UNAME:MasterAdmin|Verifying the signature failed.
com.thirdbrigade.manager.core.general.exceptions.FileNotSignedValidationException: "corrupted_rules.zip." has not been digitally signed by Trend Micro and cannot be imported.
Deep Security Agent also validates the digital signature, compares checksums (sometimes called hashes or fingerprints) and uses other, non-disclosed integrity methods.
Software checksums (also called hashes or fingerprints) are published on the Download Center. To view the SHA-256 hash, click the + button next to the software's name.