SoylentNews is people
SoylentNews
Submitted via IRC for TheMightyBuzzard
A new study reveals organizations are wasting an average of $6 million on the time to detect and contain insecure endpoints, among other staggering findings that show endpoint threats are a growing concern, companies are not efficiently protecting their proprietary data, and the cost and complexity of reducing endpoint risks are at an all-time high.
The study also revealed organizations are finding it increasingly difficult to identify dark endpoints — the rogue, out-of-compliance, or off-network devices that create blind spots and increase an organization's vulnerability to attack.
While confidence in endpoint security ranked low, the IT security professionals surveyed believe that close to 60 percent of the hours currently invested in the capture and evaluation of intelligence surrounding the true threats, to both compliance and proprietary data, can be saved each week by deploying automated solutions.
[...] "Managing endpoint security and protecting proprietary data is more than an IT issue, it's increasingly a global business performance and national security concern," said Geoff Haydon, CEO, Absolute. "This study along with recent ransomware attacks and high-profile data breaches show the danger of today's endpoint blind spots, and underscore that automation and newer approaches to endpoint security are key to safeguarding endpoints and the sensitive data on them for optimal business performance."
It can also cost you bruising about the head and face when you try to blame your admins.
Source: https://www.helpnetsecurity.com/2017/06/13/poor-endpoint-security/
(Score: 0) by Anonymous Coward on Wednesday June 28 2017, @10:05AM (1 child)
Are you going to volunteer to install/deinstall that physical jumper on hundreds of computers every time a security update is made? Note that security updates are not always related to code execution vulnerabilities; a Harvard architecture would not helped against HeartBleed, for example, where data was sent that should not have been sent. Nor would it have helped against the Debian SSH key generation bug. To just mention two prominent examples.
Oh, and it also would not help against private users doing stupid stuff. "Heck, why should I open my computer every time I want to install some software? I'll leave the jumper in, saves me work!"
Finally, there's no clear-cut distinction between code and data anyway. Think of interpreted languages: From the underlying architecture's view, the program is just data which is processed by the interpreter program.
(Score: 1) by anubi on Wednesday June 28 2017, @11:59AM
I am thinking of things like medical devices, power plants, and critical infrastructure that is not updated frequently, and when it is, it is carefully done.
Upgrading everyone's system so a new ad-server technology will work or to install new snoop technology is not my idea of anything critical.
"Prove all things; hold fast that which is good." [KJV: I Thessalonians 5:21]