|
INTEGRATION OF COMPONENTS
Endpoint security suites should integrate disparate components into a coherent, manageable whole. Most of the vendors have worked hard to integrate various aspects of their solution, with high marks going to eEye, McAfee, Sophos and Symantec.
[IMAGE] [IMAGE] [IMAGE] ENDPOINTS | Integration
[IMAGE] [IMAGE] [IMAGE] [IMAGE]
[IMAGE]
[IMAGE]
[IMAGE]
The good news
Most of the vendors have worked hard to integrate various aspects of their solution, with high marks going to eEye, McAfee, Sophos and Symantec.
The bad news
CA was never one for deep integration of components in its antimalware solutions.
[IMAGE]
[IMAGE]
The IBM ISS product has good integration, but often looked like it was packaged around complementing another vendor's antivirus and antispyware, rather than providing a whole solution. This approach make...
To continue reading for free, register below or login
To read more you must become a member of SearchSecurity.com

s sense given that IBM ISS HIPS capability has been an added defensive layer to complement traditional antivirus/antispyware products. IBM ISS has licensed BitDefender's antivirus/antispyware technology, but the management GUI still appears as though it is merely grafted in.
Trend Micro's antivirus/antispyware integration is decent, but integrating the personal firewall and HIPS, licensed from Third Brigade, needs some work. These components are a plug-in inside the management GUI, with a separate set of configuration screens that don't have the same look and feel of the configuration of antivirus and antispyware. Further, on the client side, antivirus and antispyware is a completely separate program from the HIPS software.
CA was never one for deep integration of components in its antimalware solutions. Its endpoint security product continues to separate management of antivirus and antispyware on different screens, but at least they both are available in one GUI application. CA's HIPS, on the other hand, is a separately purchased product. It is installed and managed using its own GUI and a separate client package is installed on protected workstations.
|
 |
|