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.

Comments
Most Companies Expect To Be Hacked In The Next 12 Months
Newest First  |  Oldest First  |  Threaded View
<<   <   Page 2 / 2
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
3/17/2015 | 6:09:43 PM
Re: Good.
That may also backfire, take a look at this scenario: "if we are going to get hack regardless what we do, what is the point, let's wait and see and we can take it from there"
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
3/17/2015 | 6:06:54 PM
Re: what would happen...
If does not matter if you are a big data environment or not, data needs to be secured period. The big data itself is not the main issue.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
3/17/2015 | 6:04:35 PM
Re: what would happen...
I hear you but I do not want to see data as liability. There is a value in every piece of data we hold, it is up to us how we can put into action to drive the business.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
3/17/2015 | 6:02:21 PM
Some wants to be hacked
Some companies are actually looking forward to be hacked. It is a good deal for most small startups which want to make names, thanks to us and media and no consequence of being hacked in any way. SnapChat would not be a SnapChat if it was not hacked, they were hacked and they increased their user base.
hykerfred
50%
50%
hykerfred,
User Rank: Apprentice
3/17/2015 | 11:54:50 AM
Time to start acting
2014 was the year when the hacker side took the lead in the ongoing cyber war. New technologies and new methods are being developed on an industrial scale.

2015 must be the year when the good side wakes up and starts to do something about it. Peripheral security is not enough anymore.

We need to securely authenticate the users instead of using simple passwords, we need to protect and authenticate the data in transit, and we need to build security in the applications, not just trust the network to handle it. 
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
3/17/2015 | 11:35:05 AM
Good.
This is good news.  Top security experts advise that these days, it's not so much a matter of if you get hacked, but when.  Taking the approach of "something is going to happen" will help cut down on so-called "M&M security" (i.e., hard on the outside, soft on the inside), allowing enterprises to be better prepared and secured when a breach occurs.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
3/17/2015 | 8:49:36 AM
Re: what would happen...
Im not opposed. Especially if we fail to incorporate more effective cataloging and safeguarding procedures of big data sets.
Thomas Claburn
50%
50%
Thomas Claburn,
User Rank: Ninja
3/16/2015 | 6:01:32 PM
what would happen...
...if we started referring to Big Data as "Big Liability."
<<   <   Page 2 / 2


COVID-19: Latest Security News & Commentary
Dark Reading Staff 6/3/2020
Data Loss Spikes Under COVID-19 Lockdowns
Seth Rosenblatt, Contributing Writer,  5/28/2020
Abandoned Apps May Pose Security Risk to Mobile Devices
Robert Lemos, Contributing Writer,  5/29/2020
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
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-13777
PUBLISHED: 2020-06-04
GnuTLS 3.6.x before 3.6.14 uses incorrect cryptography for encrypting a session ticket (a loss of confidentiality in TLS 1.2, and an authentication bypass in TLS 1.3). The earliest affected version is 3.6.4 (2018-09-24) because of an error in a 2018-09-18 commit. Until the first key rotation, the TL...
CVE-2020-10548
PUBLISHED: 2020-06-04
rConfig 3.9.4 and previous versions has unauthenticated devices.inc.php SQL injection. Because, by default, nodes' passwords are stored in cleartext, this vulnerability leads to lateral movement, granting an attacker access to monitored network devices.
CVE-2020-10549
PUBLISHED: 2020-06-04
rConfig 3.9.4 and previous versions has unauthenticated snippets.inc.php SQL injection. Because, by default, nodes' passwords are stored in cleartext, this vulnerability leads to lateral movement, granting an attacker access to monitored network devices.
CVE-2020-10546
PUBLISHED: 2020-06-04
rConfig 3.9.4 and previous versions has unauthenticated compliancepolicies.inc.php SQL injection. Because, by default, nodes' passwords are stored in cleartext, this vulnerability leads to lateral movement, granting an attacker access to monitored network devices.
CVE-2020-10547
PUBLISHED: 2020-06-04
rConfig 3.9.4 and previous versions has unauthenticated compliancepolicyelements.inc.php SQL injection. Because, by default, nodes' passwords are stored in cleartext, this vulnerability leads to lateral movement, granting an attacker access to monitored network devices.