Attacks/Breaches

12/29/2017
08:00 AM
Sara Peters
Sara Peters
Commentary
Connect Directly
Twitter
RSS
E-Mail vvv

17 Things We Should Have Learned in 2017 But Probably Didn't

The worm has returned and the Yahoos have all been exposed, but did 2017 teach us any genuinely new lessons we shouldn't already have known?

(Image: studiostoks, via Shutterstock)
(Image: studiostoks, via Shutterstock)

Comment  | 
Print  | 
Comments
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.
New Mexico Man Sentenced on DDoS, Gun Charges
Dark Reading Staff 5/18/2018
Cracking 2FA: How It's Done and How to Stay Safe
Kelly Sheridan, Staff Editor, Dark Reading,  5/17/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-10428
PUBLISHED: 2018-05-23
ILIAS before 5.1.26, 5.2.x before 5.2.15, and 5.3.x before 5.3.4, due to inconsistencies in parameter handling, is vulnerable to various instances of reflected cross-site-scripting.
CVE-2018-6495
PUBLISHED: 2018-05-23
Cross-Site Scripting (XSS) in Micro Focus Universal CMDB, version 10.20, 10.21, 10.22, 10.30, 10.31, 10.32, 10.33, 11.0, CMS, version 4.10, 4.11, 4.12, 4.13, 4.14, 4.15.1 and Micro Focus UCMDB Browser, version 4.10, 4.11, 4.12, 4.13, 4.14, 4.15.1. This vulnerability could be remotely exploited to al...
CVE-2018-10653
PUBLISHED: 2018-05-23
There is an XML External Entity (XXE) Processing Vulnerability in Citrix XenMobile Server 10.8 before RP2 and 10.7 before RP3.
CVE-2018-10654
PUBLISHED: 2018-05-23
There is a Hazelcast Library Java Deserialization Vulnerability in Citrix XenMobile Server 10.8 before RP2 and 10.7 before RP3.
CVE-2018-10648
PUBLISHED: 2018-05-23
There are Unauthenticated File Upload Vulnerabilities in Citrix XenMobile Server 10.8 before RP2 and 10.7 before RP3.