The CAS here is integrated with a ProxySG and I would like to know what factor can influence and slow down the CAS processing time (file size, file type, etc.).
See the the snippet below, for the Content Analysis File Scanning Workflow.
For every other product use detail, for Symantec CAS, reference has been made to the resource doc. with the URL below.
With Content Analysis integrated with ProxySG, if scans take too long, and even impacts users' browsing time, this would, most likely, be caused by Content Analysis attempting to virus scan infinite streams. To avoid this problem, Symantec recommends that customers enable:
Also, if you have configured the ICAP REQMOD service for DLP on the appliance, review these policy best practices to ensure high volumes of requests to the DLP do not affect performance. See the Tech. doc. with the URL below.
With the ICAP response modification enabled (anti-virus enabled), and the ProxySG seems to slow down, and the slowness seems to increase over time up to a point where the ProxySG no longer serves objects, please refer to the Tech. Article with the URL below, for the possible causes and possible causes/resolutions.
Note 1: The customer is able to set the maximum scan file size. An individual file size cannot exceed the configured size (1–5120 MB). This limitation also applies to each file within an archive. The default maximum file size is 100 MB. See the Tech. doc. with the URL below, for more details.
Note 2: You can configure how Content Analysis reacts when specific file extensions or file types are sent over ICAP from a ProxySG appliance. Global file extension and file type policies apply to all analysis engines (AV scanning, predictive analysis). If you employ Symantec, Kaspersky, or Sophos AV engines, you can configure additional Ignore, Scan, and Block policy. Please refer to the Tech. doc. with the URL below, for more details on defining file type policy.