Security administrators struggle to balance the mandate of providing adequate security against malware threats with the needs of end-users to work in an unfettered manner.
One of the side effects is the administrative overhead burden on the central processing unit on the endpoint. Should these administrative tasks monopolize the processing power, administrators risk having end-users simply deactivate the protection in order to carry on with their work routine.
Even if one minute a day is lost to productivity drains because of PC horsepower allocation to security scans and remediation, the cost over a year across a medium sized enterprise adds up quickly.
As an early trigger for expensive PC hardware refresh is an onslaught of help desk calls, many companies find that they can actually extend the hardware refresh cycle out another 12-24 months simply by employing a security solution that does not tax the PC as heavily.
The indirect costs associated with brand reputation, opportunity losses, etc. add untold thousands of dollars per year as well.
Further, some institutions under ‘green initiatives’ monitor power consumption related to security measures favor solutions that use less energy.
Forward-thinking security administrators target minimal intrusiveness on work activity by security measures, and nominally, that can vary from 5-10% of CPU utilization. Above that, productivity suffers, and help desk calls, end-user deactivation, and general dissatisfaction often ensue.
As such, forward-thinking enterprises are looking beyond the software license fees when evaluating security software alternatives.
This paper is oriented toward security administrators whose daily tasks include endpoint security administration and their leadership who balance organizational objectives and budgetary constraints.
It presents the results from several tests to designed to determine the impact on a computer system and the user’s ability to perform several common actions, such as copying or creating files, and their impact while detecting (Read more...)
This is a Security Bloggers Network syndicated blog post authored by The Cylance Team. Read the original post at: Cylance Blog