- Log on to the Apex Central console.
- Go to Policies > Policy Management.
- Create or select the policy created.
- On targets, select Manage Targets and select target Apex One agents.
- Under Apex One Agent Settings, select Scan Methods.
You should see the Scan Method Selected on your current configuration.
- Log on to the Apex Central console.
- Select Policies > Policy Management.
- Select the Policy you wish to customize.
- Select Scan Methods.
- Select Either of the following:
- Conventional Scan
- Smart Scan
- Click Deploy.
For more information about the Scan Methods:
A conventional scan client stores all Apex One patterns on the endpoint and scans all files locally.
Smart Scan leverages threat signatures that are stored in the cloud. When in Smart Scan mode, the Apex One security agent first scans for security risks locally. If the client cannot determine the risk of the file during the scan, the client connects to the local Smart Scan Server. If the clients cannot connect to it, they will attempt to connect to the Trend Micro Global Smart Scan Server.
Smart Scan provides the following features and benefits:
- Provides fast, real-time security status lookup capabilities in the cloud.
- Reduces the overall time it takes to deliver protection against emerging threats.
- Reduces network bandwidth consumed during pattern updates. The bulk of pattern definition updates only needs to be delivered to the cloud and not to many endpoints.
- Reduces the cost and overhead associated with corporate-wide pattern deployments.
- Lowers kernel memory consumption on endpoints. Consumption increases minimally over time.
Trend Micro strongly recommends switching from Conventional Scanning to Smart Scanning:
- Recent statistics shows that the Smart Scan Agent pattern (OTH, which is stored locally on the actual agent that uses Smart Scanning) covers 80% of the total threats, and that the Smart Scan pattern (TBL, stored on the Scan Server) covers the other 20%.
- Aside from Smart Scan Agent pattern (icrc$oth.xxx), a local cache is used to reduce about 80% of outgoing queries. CRC cache works as a partial Smart Scan Pattern replica so that previously obtained CRC can be reused later.
In other words, the CRCs are ready to be used to protect an endpoint user and are effective on malware that have been previously detected. However, the date may vary among individual users according to their usage behavior.
| Basis of Comparison | Conventional Scan | Smart Scan |
|---|---|---|
| Availability | Available in Apex One, including all earlier OfficeScan versions | Available in Apex One, including versions of OfficeScan 10.0 to XG |
| Scanning behavior | The conventional scan client performs scanning on the local computer | The smart scan client performs scanning on the local computer. If the client cannot determine the risk of the file during the scan, the client verifies the risk by sending a scan query to a Smart Scan Server. Using advanced filtering technology, the client "caches" the scan query result. The scanning performance improves because the client does not need to send the same scan query to the Smart Scan Server. If a client cannot verify a file’s risk locally and is unable to connect to any Smart Scan Server after several attempts:
When connection to a Smart Scan Server is restored, all the files that have been flagged are re-scanned. The appropriate scan action is then performed on files that have been confirmed as infected. |
| Components in use and updated | All components are available on the update source, except the Smart Scan Agent Pattern | All components are available on the update source, except the Virus Pattern and Spyware Active-monitoring Pattern |
| Typical update source | Apex One server | Apex One server |