January 2018 Security Roundup

We are kicking off a new feature on the blog, possibly also in the Digital Reflector, that summarizes the leading posts on topics of concern this month and onward. If you would like to share a link or comment, please send it through a dm (e.g. direct message) on twitter at ieeeboston

This month, we are kicking off three areas: Computer Security, Data Breaches, and Hacks Beyond Data

January 2018 Round Up – Computer Security

A non-exhaustive roundup of posts about Meltdown and Spectre, edited throughout the month.

###Wired

If you’re looking at how the problem was found, here’s a good summary of the timing of one research group’s effort to bring the problem to light: How Researchers Found a 20-Year-Old Flaw at the Same Time

 

## More Points of Reference for Meltdown and Spectre:
### Google

Reading Priveleged Memory with a Side Channel
Today’s CPU Vulnerability – What You Need to Know
Intel CEO: We will make our chips secure

### Landing Page Website Just for Information About This.

Meltdown Attack

### IEEE

A really good article on the background of the security flaws: How the Meltdown Vulnerability Fix Was Invented

### XKCD

XKCD explains, or mocks, things in a way only XKCD can do it

Behind paywalls:

#### Wall Street Journal

Businesses Rush to Contain Fallout From Major Chip Flaws – Software patches to plug holes could slow computers, experts say

## Data Breaches Disclosed this month
With all the news on Meltdown and Spectre, nevermind the Golden Globes, it’s been hard to keep up. Fortunately, the news here has been light.
Forever 21 announced a security breach closed in November 2017

##Hacks Beyond Data
When hacks go beyond just taking data, not dimishing the impact of data in the wrong hands, these hacks highlight those scenarios where the hack went beyond the safety controls to affect normal operations of an organization or enterprise.
Plant Safety Systems Hacked to Hide the infection of the Systems and here

If you find any links are suddenly broken (they worked when I wrote this), please dm the Section at Twitter

Thank you for continuing to support the IEEE. You can become a member to gain access to many more benefits.

*all trademarks mentioned are the property of their respective owners, the IEEE Boston Section does not own any trademarks mentioned in this blog post.