Hi Charris,
Charris Lappas wrote:
This is a well known issue, in short, the GW intercepts the file and send it for emulation. The endpoint client that is downloading the file believes there is a problem with the download and fails. After a couple of tries it is successful.
Even if you install the SB Agent, you will get issues, you will have both GW and Endpoint fighting to get the same file for Sandblast Analysis.
They do not fight for the analysis as processing is done sequentially because the file hits the GW first.
We have opened a TAC case, we got the same result, "works as expected!". then we opened another case in order to adjust the policy but since then nothing happened. What we have managed to do is to create a policy for computers without the Agent to have the GW inspect the file and another policy for computers with Agent to have the GW not inspect the file. It is working but you need to have a way to know which computer shave the agent and which not....
Assuming your GW is in TE background mode it will not interfere with SBA as long as the file is not malicious.
That said if you want to implement hold mode with TE for HTTP/S you must seggregate the users in policies (background and hold mode can be set per TP profile) as you described.
BTW Threat Extraction will not be a problem when we get TX inline in HTTP/S with R88.30 🙂
Regards Thomas