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.


Higher Education: 15 Books to Help Cybersecurity Pros Be Better
Curtis Franklin Jr., Senior Editor at Dark Reading,  12/12/2018
'PowerSnitch' Hacks Androids via Power Banks
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/8/2018
Worst Password Blunders of 2018 Hit Organizations East and West
Curtis Franklin Jr., Senior Editor at Dark Reading,  12/12/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: camera, camera everywhere, not a single news to rely on
Current Issue
10 Best Practices That Could Reshape Your IT Security Department
This Dark Reading Tech Digest, explores ten best practices that could reshape IT security departments.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-14623
PUBLISHED: 2018-12-14
A SQL injection flaw was found in katello's errata-related API. An authenticated remote attacker can craft input data to force a malformed SQL query to the backend database, which will leak internal IDs. This is issue is related to an incomplete fix for CVE-2016-3072. Version 3.10 and older is vulne...
CVE-2018-18093
PUBLISHED: 2018-12-14
Improper file permissions in the installer for Intel VTune Amplifier 2018 Update 3 and before may allow unprivileged user to potentially gain privileged access via local access.
CVE-2018-18096
PUBLISHED: 2018-12-14
Improper memory handling in Intel QuickAssist Technology for Linux (all versions) may allow an authenticated user to potentially enable a denial of service via local access.
CVE-2018-18097
PUBLISHED: 2018-12-14
Improper directory permissions in Intel Solid State Drive Toolbox before 3.5.7 may allow an authenticated user to potentially enable escalation of privilege via local access.
CVE-2018-3704
PUBLISHED: 2018-12-14
Improper directory permissions in the installer for the Intel Parallel Studio before 2019 Gold may allow authenticated users to potentially enable an escalation of privilege via local access.