Comments
Sacramento Bee Databases Hit with Ransomware Attack
Newest First  |  Oldest First  |  Threaded View
alphaa10
50%
50%
alphaa10,
User Rank: Strategist
2/17/2018 | 12:23:13 AM
Re: Profound solution?
The measure announced was not to recover the lost data, but to frustrate inevitable future attempts to make the same threat, perhaps with more damage. Once a ransom demand is met, there is nothing to dissuade the same or similar groups from another attack.

Did the newspaper promise a return to paper records? Not at all, but simply a more layered and distributed system, with multiple checkpoints.

Under the circumstances, the Bee declaration helps the newspaper isolate itself from further extortion attempts.

 
BrianN060
50%
50%
BrianN060,
User Rank: Ninja
2/12/2018 | 6:07:58 PM
Looking for correlations
@DR staff: Elements of this story are repeated in any number of cybersecurity articles, surveys, reports, etc..  What I haven't seen is analysis on how specific data storage choices correlate with attack frequency, type, detection, and other characteristics and metrics. 

In this story "...its databases, both on a third-party server...", raises the above questions as regards to use of third party servers; but also leads to questions about attacks and the specifics of type, location, infrastructure, etc.., of such servers. 

Perhaps what I'm looking for is a multidimensional map showing just what particular dangers are known to inhabit various (metaphorical as well as actual), regions.  In other words, are there safer places and containers to bury your treasure? 

I realize this is far from a simple question.  For starters, a single vendor might offer several types of relational and non-relational patterns and management options; and might have options for restricting use to certain geo-located datacenters - and a single organization might use different options, from different vendors, as well as combine public-cloud with in-house storage options. 

Is anyone work on this type of multi-factor threat assessment for data storage choices? 
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
2/12/2018 | 3:14:51 PM
Profound solution?
The database data is deleted to prevent future theft.  Wow!!!!   What an idea.  Lock the barn door after the theft is done.  Brilliant.  Of course, the data is already out there so who ares about deletion.  Hey, shore up the walls would be a good idea too.  


Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The Year in Security 2018
This Dark Reading Tech Digest explores the biggest news stories of 2018 that shaped the cybersecurity landscape.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-6345
PUBLISHED: 2019-01-15
The function number_format is vulnerable to a heap overflow issue when its second argument ($dec_points) is excessively large. The internal implementation of the function will cause a string to be created with an invalid length, which can then interact poorly with other functions. This affects all s...
CVE-2018-7603
PUBLISHED: 2019-01-15
In Drupal's 3rd party module search auto complete prior to versions 7.x-4.8 there is a Cross Site Scripting vulnerability. This Search Autocomplete module enables you to autocomplete textfield using data from your website (nodes, comments, etc.). The module doesn't sufficiently filter user-entered t...
CVE-2019-3554
PUBLISHED: 2019-01-15
Wangle's AcceptRoutingHandler incorrectly casts a socket when accepting a TLS 1.3 connection, leading to a potential denial of service attack against systems accepting such connections. This affects versions of Wangle prior to v2019.01.14.00
CVE-2019-3557
PUBLISHED: 2019-01-15
The implementations of streams for bz2 and php://output improperly implemented their readImpl functions, returning -1 consistently. This behavior caused some stream functions, such as stream_get_line, to trigger an out-of-bounds read when operating on such malformed streams. The implementations were...
CVE-2019-0030
PUBLISHED: 2019-01-15
Juniper ATP uses DES and a hardcoded salt for password hashing, allowing for trivial de-hashing of the password file contents. This issue affects Juniper ATP 5.0 versions prior to 5.0.3.