Cloud

6/8/2015
05:00 PM
Connect Directly
Twitter
Twitter
RSS
E-Mail
100%
0%

Quantifying Shadow Data In The Cloud

Report shows how much data users really are exposing on SaaS services.
Previous
1 of 8
Next

Cloud application security company Elastica today released a report with data collected from its insight into enterprises using its CloudSOC platform to offer insights into how users today are sharing data on the cloud.

The report was based on anonymized and aggregated data and offered insight into the types of data put on the cloud, how much risky shadow data is entrusted to SaaS application and analysis of the potential economic impact if these files are left unprotected and the organization suffers a breach.

According to the report, Elastica found millions of files exposed on the cloud to either compliance violations, intellectual property leaks, or other kinds of risk. When examining across organizations and compared with breach cost estimates, Elastica estimated that the average total economic impact of cloud exposures per business would equal $13.85 million.

Image Source: Pixabay.com

 

 

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio

Previous
1 of 8
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
chriscmw
50%
50%
chriscmw,
User Rank: Apprentice
6/8/2015 | 9:31:17 PM
Interesting data...
Thanks for collecting this data. It is very interesting to see what type of data and which sectors are the most vulnerable on the cloud. What I take away from this is that public, consumer grade cloud providers tend to be the least secure. I suppose that's hardly a surprise given that most enterprises using the cloud shy away from those sorts of providers. These security issues seem to be right up there with developing enterprise grade cloud tools for those cloud providers trying to move away from consumers to the enterprise market. It'll be interesting to see how the market responds.
Want Your Daughter to Succeed in Cyber? Call Her John
John De Santis, CEO, HyTrust,  5/16/2018
New Mexico Man Sentenced on DDoS, Gun Charges
Dark Reading Staff 5/18/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Flash Poll
[Strategic Security Report] Navigating the Threat Intelligence Maze
[Strategic Security Report] Navigating the Threat Intelligence Maze
Most enterprises are using threat intel services, but many are still figuring out how to use the data they're collecting. In this Dark Reading survey we give you a look at what they're doing today - and where they hope to go.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-11354
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, the IEEE 1905.1a dissector could crash. This was addressed in epan/dissectors/packet-ieee1905.c by making a certain correction to string handling.
CVE-2018-11355
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, the RTCP dissector could crash. This was addressed in epan/dissectors/packet-rtcp.c by avoiding a buffer overflow for packet status chunks.
CVE-2018-11356
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the DNS dissector could crash. This was addressed in epan/dissectors/packet-dns.c by avoiding a NULL pointer dereference for an empty name in an SRV record.
CVE-2018-11357
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the LTP dissector and other dissectors could consume excessive memory. This was addressed in epan/tvbuff.c by rejecting negative lengths.
CVE-2018-11358
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the Q.931 dissector could crash. This was addressed in epan/dissectors/packet-q931.c by avoiding a use-after-free after a malformed packet prevented certain cleanup.