| Description | This article describes the 'not applied' setting in the Customized Rating section for Tracer Engine Timeout. |
| Scope | FortiSandbox |
| Solution |
Sometimes, when scanning a file in a VM, tracer engine timeout can occur. In these cases, the best action to take depends on the Customized Rating configuration for Tracer engine timeout. If 'High risk' is configured for example, there is no re-scan upon a tracer engine timeout and 'High Risk' is returned.
When setting a customized rating section to 'Not Applied' for Tracer Engine Timeout, if a job fails in a VM scan (for example, tracer engine timeout), it will retry the VM scan one more time. If it fails again, the final rating will be the highest one from all the previously finished scan steps.
|
