This week the gang's all here to talk about some news happenings. Michael, James and I talk through some of the stories we've been tracking.

Have something you've been reading and want to talk about? Hit us on Twitter with hashtag #DtSR and suggest a topic/story for the next NewsCast!

 

Tennessee Amends Breach Notification Statute

• http://www.natlawreview.com/article/tennessee-amends-breach-notification-statute
• Removes the exception for encrypted data.
• Will this raise the costs to companies?  
• • Encrypted or not, will credit monitoring be the norm?
  • More lawsuits (even if the data is encrypted)
• Do we run the risk of notification overload?
• • What do people do with these notifications anyway?

FFIEC’s New Mobile Security Guidance: An Assessment

• http://www.bankinfosecurity.com/ffiecs-new-mobile-security-guidance-assessment-a-9104
• Interesting how they discuss some of the risks (SMS, mobile enabled website) but also talk about ways to mitigate the risk.

Software “glitch” kills Formula1 car mid-race

• Does not take a rocket surgeon to figure out the real-world applications here
  • Sure this time it was a 'glitch' but could just as well have been a security bug, exploited by an attacker?
• Many vehicles are now ‘smart’ and phone home, make decision and drive for you
• http://news.filehippo.com/2016/05/software-glitch-kills-formula-1-car-mid-race/

LinkedIn plays down 117 million user breach of data sale

• http://www.theregister.co.uk/2016/05/19/linkedin_breach/
• From 2012 breach... coming back to us
  
• Does this show how a breach can linger on?
• Alternate theory: attacker has been using credentials stolen, and now that they're not useful anymore he/she is dumping them to the public?