Second that... our mail server also sits behind a dedicated AV, spam, filtering 
SMTP appliance. For our end points we have several tiers. Primarily all systems 
protected with Malwarebytes Enterprise. Mobiles also have built-in AV turned on 
with our VPN endpoint client that also does web and application filtering. All 
systems have MS Firewall on by default/GPO as well as the built-in AV. Our file 
servers are covered by Malwarebytes and the McAfee AV engine and every device 
is WSUS updated regularly and end-users are tested and educated every quarter.

Troy

From: [email protected] [mailto:[email protected]] On 
Behalf Of Rick Berry
Sent: Monday, June 9, 2014 7:37 AM
To: [email protected]
Subject: [Exchange] RE: Kaspersky vs McAfee vs Symantec

One mild suggestion is that you split that thought process in two pieces, if 
not three.  Treat the endpoint PC/Server protection as a separate thing than 
the email server parts, perhaps.

Exchange malware/spam protection can be handled a billion ways, I personally 
have a preference for 'prefilters' (such as Symantec cloud, formerly 
messagelabs) where the MX records inbound (and smarthosts outbound) go through 
the cloud and never eat mine or my clients' bandwidth.  (I carry a few thousand 
seats on Symantec for a large swath of corporate/business clients).  The 
processing happens outside, I have nearly zero SPAM issues nor do I really ever 
see email-borne malware make it through (no cryptolocker payloads, no bad PDFs 
hiding in zip files, etc).  There are other cloud filtering services worthy of 
similar praise (appriver, many others).   Can't speak to the costs, but the 
real business costs of *not* doing something like that is always a much higher 
number.

Appliance-based solutions also good (barracuda, sonicwall) for email.

On-server stuff also good, I just prefer running it off server or pre-filter 
... GFI mailessentials is good, there are a billion others that are also good.

For endpoint, that's a bigger discussion, I tend to loathe McAfee, Symantec and 
Trend for endpoint (personal bias) and generally use a combination of two 
things at any given site ... typically an edge appliance that has a malware 
filter subscription as well as software on endpoints.  For small businesses, a 
typical deployment for us would be a Sonicwall TZ or NSA with their gateway 
antimalware/filtering services, which helps block nasty stuff including 
oftentimes the proclivity of users to click on something stupid.  Then we add 
on something else like NOD or Kaspersky or VIPRE, sometimes in conjunction with 
Malwarebytes paid products.  Usually it's ThreatTrack VIPRE (ex GFI) but 
nothing is perfect, and again why we like to hedge with a few layers (filter 
email, filter at firewall, filter more on client).





From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Liby Philip Mathew
Sent: Monday, June 9, 2014 9:17 AM
To: Admin Issues 
([email protected]<mailto:[email protected]>)
Subject: [Exchange] Kaspersky vs McAfee vs Symantec

Hi guys,
I have been told to identify the pros & cons of Kaspersky vs McAfee vs Symantec 
including the cost.
I am looking to protect end user PC, Server, centralized management & MS 
Exchange 2010 / 2013 AV/spam/phish/spoof etc.
What are your experiences / suggestions?
TIA


Regards
Liby Philip Mathew


Disclaimer

[The information contained in this e-mail message and any attached files are 
confidential information and intended solely for the use of the individual or 
entity to whom they are addressed. This transmission may contain information 
that is privileged, confidential or exempt from disclosure under applicable 
law. If you have received this e-mail in error, please notify the sender 
immediately and delete all copies. If you are not the intended recipient, any 
disclosure, copying, distribution, or use of the information contained herein 
is STRICTLY PROHIBITED. Path Solutions accepts no responsibility for any 
errors, omissions, computer viruses and other defects.]
P Protect our planet: Do not print this email unless necessary.


*** This message may contain confidential and proprietary RMH Group information 
and is intended only for the sole use of the recipient(s). If you are not the 
named recipient you should not read, distribute or copy this e-mail. Please 
notify the sender and destroy this e-mail and any attachments and all copies. 
***

Reply via email to