Details
Trend Micro products support multiple types of SO, their maximum entry is as the shown table below. We have recently received reports from customers pointing out that some features are not running smoothly as expected.
Suspicious Object Type | Upper Limit |
---|---|
SO-exception | 25,000 *All SO types are counted together |
User-Defined SO (UDSO) | 10,000 per SO type |
Virtual Analyzer SO (VASO) | 25,000 per SO type |
From our investigation, we concluded that different types of SO has different limitions as the table below. We strongly recommend customers to install SPS in order to extend the maximum volume of URL SO. This can resolve the current found issue.
Type | Comment |
---|---|
URL |
|
File SHA-1 | Good to serve upper limited entries |
File CRC | Good to serve upper limited entries |
Domain/IP | Good to serve upper limited entries |
In addition, the SPS system can directly benefit other point products from Trend Micro also, for example Apex One, ScanMail, and Deep Security, which connects the whole threat defense ecosystem more swiftly.
The following instructions illustrates how to deploy SPS in detail:
Steps
- Get required information about the Suspicious Object list source:
- Open the Apex One as a Service management console.
- Go to Threat Intel > Distribution Settings.
- Click the Managed Products tab.
- Write down the following connection details:
Apex One as a Service doesn't support manually trigger Suspicious Object synchronization to the Smart Protection Servers by clicking the Sync Now button. - Subscribe to Apex One as a Service as the Suspicious Object source to synchronize suspicious objects:
- Open the Smart Protecton Server management console.
- Go to Smart Protection > Suspicious Objects.
- Type the FQDN or IP address of the suspicious object source.
- Type the API Key obtained by the suspicious object source.
- Click Subscribe.
- To immediately synchronize suspicious objects, select Synchronize and enable suspicious objects and then click Sync Now.
- Click Save.
Click the image to enlarge.
- Configure the Smart Protection Server for internal agents:
- SSO to the Apex One as a Service management console
- Go to Administration > Smart Protection > Smart Protection Sources.
- Select Internal Agent tab.
- Click Add.
- In the IP range section, specify an IP address range for internal agents.
- In the Custom Smart Protection Server List section, add the Smart Protection Server subscribed to the suspicious object source.
- Specify the Smart Protection Server’s host name or IPv4/IPv6 address.
- Select Web Reputation Services and input the port number.
- Click Add to List.
- Click Save.
- Click Save and Notify Agents.
Click the image to enlarge.