The Apex One server downloads the following components and deploys them to agents:
Component |
Distribution |
|
---|---|---|
Conventional Scan Agents |
Smart Scan Agents |
|
Antivirus |
||
Smart Scan Agent Pattern |
No |
Yes |
Virus Pattern |
Yes |
No |
IntelliTrap Pattern |
Yes |
Yes |
IntelliTrap Exception Pattern |
Yes |
Yes |
Virus Scan Engine 32/64-bit |
Yes |
Yes |
Memory Inspection Pattern |
Yes |
Yes |
Early Launch Anti-Malware Pattern 32/64-bit |
Yes |
Yes |
Contextual Intelligence Engine 32/64-bit |
Yes |
Yes |
Contextual Intelligence Pattern |
Yes |
Yes |
Contextual Intelligence Query Handler 32/64-bit |
Yes |
Yes |
Advanced Threat Scan Engine 32/64-bit |
Yes |
Yes |
Advanced Threat Correlation Pattern |
Yes |
Yes |
Anti-spyware |
||
Spyware/Grayware Pattern |
Yes |
Yes |
Spyware Active-monitoring Pattern |
Yes |
No |
Spyware/Grayware Scan Engine 32/64-bit |
Yes |
Yes |
Damage Cleanup Services |
||
Damage Cleanup Template |
Yes |
Yes |
Damage Cleanup Engine 32/64-bit |
Yes |
Yes |
Early Boot Cleanup Driver 32/64-bit |
Yes |
Yes |
Firewall |
||
Common Firewall Pattern |
Yes |
Yes |
Behavior Monitoring Components |
||
Behavior Monitoring Detection Pattern 32/64-bit |
Yes |
Yes |
Behavior Monitoring Core Driver 32/64-bit |
Yes |
Yes |
Behavior Monitoring Core Service 32/64-bit |
Yes |
Yes |
Behavior Monitoring Configuration Pattern |
Yes |
Yes |
Policy Enforcement Pattern |
Yes |
Yes |
Digital Signature Pattern |
Yes |
Yes |
Memory Scan Trigger Pattern (32/64-bit) |
Yes |
Yes |
Program Inspection Monitoring Pattern |
Yes |
Yes |
Damage Recovery Pattern |
Yes |
Yes |
Suspicious Connections |
||
Global C&C IP List |
Yes |
Yes |
Relevance Rule Pattern |
Yes |
Yes |
Browser Exploit Solution |
||
Browser Exploit Prevention Pattern |
Yes |
Yes |
Script Analyzer Unified Pattern |
Yes |
Yes |
Update reminders and tips:
To allow the server to deploy the updated components to agents, enable automatic agent update. For details, see Security Agent Automatic Updates. If automatic agent update is disabled, the server downloads the updates but does not deploy them to the agents.
A pure IPv6 Apex One server cannot distribute updates directly to pure IPv4 agents. Similarly, a pure IPv4 Apex One server cannot distribute updates directly to pure IPv6 agents. A dual-stack proxy server that can convert IP addresses, such as DeleGate, is required to allow the Apex One server to distribute update to the agents.
Trend Micro releases pattern files regularly to keep agent protection current. Since pattern file updates are available regularly, Apex One uses a mechanism called "component duplication" that allows faster downloads of pattern files. See Apex One Server Component Duplication for more information.
If you use a proxy server to connect to the Internet, use the correct proxy settings to download updates successfully.
On the web console's Dashboard, add the Agent Updates widget to view the current versions of components and determine the number of agents with updated and outdated components.