Database Security
Authentication
Privacy
Compliance
Identity & Access Management
Security Monitoring
Advanced Threats
Insider Threats
Vulnerability Management
Comments
17 Things We Should Have Learned in 2017 But Probably Didn't
Newest First  |  Oldest First  |  Threaded View
REISEN1955
50%
50%
REISEN1955,
 User Rank: Ninja
1/3/2018 | 10:59:13 AM
Re: Excellent Post!
In 1996 I became an official Netware CNE - now an antique of course but even back then, we were taught the value of BACKUPS and RESTORE points.  Many of these 17 points are NOT NEW by any means.  Some directly threat information has to be new of course, but it amazes me that firms always "discover" something new when dealing with Ransomware or power outage.  (When Delta crashed last year, it was due to a lack of power backups in the data centers.  Oh I remember those huge HEAVY APC boxes.  This is basic stuff!!! )  And yet it is always disclosed as something new.

I still have a collection of 3.5 disks containing 1990 backup data from my old 486 system.  Having reliable backups (ransomware) is NOTHING NEW.  

 

"Those who do not learn history are doomed to repeat it"
sngs7dan
50%
50%
sngs7dan,
 User Rank: Strategist
1/2/2018 | 10:33:44 AM
Which English?
You wrote in your first point: "... covering everything from how much they refinanced their home for to whether they prefer ..."

Really? is 'for to' in a programming language? Where was/is your editor?

On a more content related level- don't you get tired of having to say the same thing over and over? If they're not listening, why keep saying it the same way?

Until someone is personally affected by a breach, the big numbers are just numbers that do not require action on their part. When they realize they're wrong, it's already too late!

Personally, I've been breached so many times (OPM, Yahoo, Equifax, etc.), these actions feel like trying to close the barn door after the horses are stolen.

We need an alternative to using the Social Security Number and to de-escelate it from PII and regard it as the 'publicly available' information it already is. The U.S. needs to stop being the wild west cowboy and grow up into a recognition that corporations do not recognize 'individual responsibility'. Laws need to be revised accordingly.

In order to revise the laws, we need a massive turnover in Congress. In order to have a massive turnover in Congress, we need a new grass roots effort much more mainstream and more potent than the Tea Party has been for the Republicans.

Sorry, just finished my coffee. I'll wake up now.
enhayden1321
50%
50%
enhayden1321,
 User Rank: Apprentice
1/2/2018 | 10:32:12 AM
Excellent Post!
Many thanks to Sarah for her excellent summary of the security issues experienced in 2017! Your review as well as your suggested priorities for 2018 are a worthwhile read for every Security Professional and executive.


Google Engineering Lead on Lessons Learned From Chrome's HTTPS Push
Kelly Sheridan, Staff Editor, Dark Reading,  8/8/2018
White Hat to Black Hat: What Motivates the Switch to Cybercrime
Kelly Sheridan, Staff Editor, Dark Reading,  8/8/2018
PGA of America Struck By Ransomware
Dark Reading Staff 8/9/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Now about that mortgage refinance offer from Wells Fargo .....
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-6970
PUBLISHED: 2018-08-13
VMware Horizon 6 (6.x.x before 6.2.7), Horizon 7 (7.x.x before 7.5.1), and Horizon Client (4.x.x and prior before 4.8.1) contain an out-of-bounds read vulnerability in the Message Framework library. Successfully exploiting this issue may allow a less-privileged user to leak information from a privil...
CVE-2018-14781
PUBLISHED: 2018-08-13
Medtronic MMT 508 MiniMed insulin pump, 522 / MMT - 722 Paradigm REAL-TIME, 523 / MMT - 723 Paradigm Revel, 523K / MMT - 723K Paradigm Revel, and 551 / MMT - 751 MiniMed 530G The models identified above, when paired with a remote controller and having the "easy bolus" and "remote bolu...
CVE-2018-15123
PUBLISHED: 2018-08-13
Insecure configuration storage in Zipato Zipabox Smart Home Controller BOARD REV - 1 with System Version -118 allows remote attacker perform new attack vectors and take under control device and smart home.
CVE-2018-15124
PUBLISHED: 2018-08-13
Weak hashing algorithm in Zipato Zipabox Smart Home Controller BOARD REV - 1 with System Version -118 allows unauthenticated attacker extract clear text passwords and get root access on the device.
CVE-2018-15125
PUBLISHED: 2018-08-13
Sensitive Information Disclosure in Zipato Zipabox Smart Home Controller allows remote attacker get sensitive information that expands attack surface.