Executive Report: exclude unscannable objects from viruses
Created: 23 Dec 2009 | Updated: 04 Jan 2013 | 6 comments
Status:
In Development
If you run a executive report, unscannable objects are summarized under viruses.
Unscannable objects should not be handled as viruses. A separate listing would be much better.
A report in the current form can cause big misunderstanding...
Idea Filed Under:
Group Ownership:
Comments 6 Comments • Jump to latest comment
The things is that we are a security company, so if we can't scan it and say its clean, it is considered a virus.
True, we could categorize it differently, but as far as our products are concerned, its not clean, so its viral.
Yes, but then SBG should included Un-scannable as part of the Virus reports. There is no easy way to get reports on the various un-scannable reason codes. We use SBG outbound and un-scannable is a top issue.
Just for the report it should not be listed as virus. Simply "unscannable" as its own category for it would do it.
Consultant
PMCS.helpLine Software Gruppe
www.pmcs.de
follow us on Twitter: PMCS_NBU ; PMCS_BE ; PMCS_EV
Agreeed, with breakdown by sub-reason code.
Is it implented in the 9.0.2-9 now?
In the Symantec Messaging Gateway 10.5 release unscannable verdicts will be in a separate section to confirmed malware verdicts.
Would you like to reply?
Login or Register to post your comment.