Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Security Management

9/7/2017
01:00 PM
Curtis Franklin
Curtis Franklin
Curt Franklin
50%
50%

SANS Study Says Reputation Is a Cyber-Casualty

The latest security study says that you've probably been attacked and your reputation has taken the biggest hit.

There is, it seems, no end to the things that can keep security professionals up at night. A new SANS study, sponsored by Infoblox and McAfee, asked about that list of things and found that ransomware, insider threats and DoS attacks were at the top.

The survey, "Sensitive Data at Risk: The SANS 2017 Data Protection Survey," gathered data from over 250 IT security administrators, engineers, developers and privacy experts in North America. It asked, broadly, about what threats the professionals worry about, how badly those threats have hurt them and what to do about all the threats in the IT landscape.

Threats
Attacks are ubiquitous. Seventy-eight percent of the respondents reported that their organizations have seen two or more incidents involving the major threats in the last 12 months. In addition to the big three threats mentioned earlier, identity spoofing, privilege elevation and identity theft were among the threats that organizations dealt with, in the 12 months covered by the survey.

While attacks were common, significant data loss due to the attacks was not. Only 12% of those answering said that they had experienced a significant breach to sensitive data in the last 12 months. Of those who did, the most common data lost was user login and password data (more than 40%) followed by privileged credentials and customer-identifiable personal information (more than 30% each). With relatively little data actually lost, were companies really damaged by these attacks? According to the survey, they were, indeed.

Pain
What kind of pain results when the loss of critical information isn't the primary damage? Three types of damage stood at the top of the list of cyber-pain inflicted:

  • Loss of customer confidence
  • Legal headaches and fees
  • Loss of brand reputation

Two of these three could be seen as problems of perception; humans have trouble getting past the rules of the jungle, in which weakness means being cut from the pack and cast out. The pain that untrusting citizens don't inflict, the legal and regulatory systems do. Put them all together and they form a block of reasons to avoid becoming a victim if at all possible.


You're invited to attend Light Reading's Virtualizing the Cable Architecture event – a free breakfast panel at SCTE/ISBE's Cable-Tec Expo on October 18 featuring Comcast's Rob Howald and Charter's John Dickinson.

It's hard to defend against something if you don't know where it's coming from and there are two big sources of the pain inflicted on organizations through their IT systems. The first, not surprisingly, is hacking. Whether it takes the form of direct hacking or malware, criminals are a problem for more than 40% of companies taking the survey.

Next up is the insider threat. Now, it's important to note that this is not accidental loss from a clumsy or inattentive employee. No, this is insiders taking direct action against the organization, a problem faced by more than 35% of companies. No other source comes close to these two -- and defense has to address each.

Treatment
So what's to be done about making things better? Step one is visibility. When the attacker knows more about your data, your applications or your network than you do, you're in a very vulnerable position.

The next step sounds the simplest: Do the things you know you need to do. Most security is common sense -- secure your assets and take care to control access to your systems -- but far too few organizations take the time and dedicate the resources to do the things that have long been known as best practices. Brush, floss, follow best security practices. These are things that you should do every day.

Related posts:

— Curtis Franklin is the editor of SecurityNow.com. Follow him on Twitter @kg4gwa.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...