Web Isolation and Opswat Metadefender Cloud Integration Hash vs. File: For cloud deployments
search cancel

Web Isolation and Opswat Metadefender Cloud Integration Hash vs. File: For cloud deployments

book

Article ID: 425845

calendar_today

Updated On:

Products

Web Isolation Cloud

Issue/Introduction

Why the Hash vs. File: For cloud deployments does not support sending the full file to MetaDefender.

Cause

Symantec AV support scanning the full file content, not just the file hash.These are internal scanning services that run within the same infrastructure and have access to the local file system. When a file needs to be scanned, the system passes the file path to these scanners, which then read and analyze the complete file content. This is different from OPSWAT Metadefender Cloud, which is an external cloud service and only receives the file hash for lookup purposes.

Resolution

Regarding the Hash vs. File: For cloud deployments, WI supports sending the file hash only. It does not support sending the full file to MetaDefender.

'n/a' Scanner Name: In WI activity logs, successful scans show the scanner as n/a by design. This is because a "success" may involve multiple configured scanners, making it impossible to attribute the result to a single engine. (Specific scanners are only identified when a file is blocked).

Additional Information

https://techdocs.broadcom.com/us/en/symantec-security-software/web-and-network-security/web-isolation/1-16/Symantec-Threat-Isolation-Overview/How-Symantec-Threat-Isolation/Third-Party-File-Sanitizer.html

Updated Tech Doc