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
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: Strategist
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.


97% of Americans Can't Ace a Basic Security Test
Steve Zurier, Contributing Writer,  5/20/2019
How Security Vendors Can Address the Cybersecurity Talent Shortage
Rob Rashotte, VP of Global Training and Technical Field Enablement at Fortinet,  5/24/2019
TeamViewer Admits Breach from 2016
Dark Reading Staff 5/20/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-7068
PUBLISHED: 2019-05-24
Adobe Acrobat and Reader versions 2019.010.20069 and earlier, 2019.010.20069 and earlier, 2017.011.30113 and earlier version, and 2015.006.30464 and earlier have an use after free vulnerability. Successful exploitation could lead to arbitrary code execution .
CVE-2019-7069
PUBLISHED: 2019-05-24
Adobe Acrobat and Reader versions 2019.010.20069 and earlier, 2019.010.20069 and earlier, 2017.011.30113 and earlier version, and 2015.006.30464 and earlier have a type confusion vulnerability. Successful exploitation could lead to arbitrary code execution .
CVE-2019-7070
PUBLISHED: 2019-05-24
Adobe Acrobat and Reader versions 2019.010.20069 and earlier, 2019.010.20069 and earlier, 2017.011.30113 and earlier version, and 2015.006.30464 and earlier have an use after free vulnerability. Successful exploitation could lead to arbitrary code execution .
CVE-2019-7071
PUBLISHED: 2019-05-24
Adobe Acrobat and Reader versions 2019.010.20069 and earlier, 2019.010.20069 and earlier, 2017.011.30113 and earlier version, and 2015.006.30464 and earlier have an out-of-bounds read vulnerability. Successful exploitation could lead to information disclosure.
CVE-2019-7072
PUBLISHED: 2019-05-24
Adobe Acrobat and Reader versions 2019.010.20069 and earlier, 2019.010.20069 and earlier, 2017.011.30113 and earlier version, and 2015.006.30464 and earlier have an use after free vulnerability. Successful exploitation could lead to arbitrary code execution .