27 April 2017

Top Security and Privacy Issues for 2017


Expansion of Breach Notification Requirements

While some companies in industries like health care are already required to notify customers and clients when they have experienced a breach, there are many industries where no such requirement exists.   Will that change in 2017?

Will Healthcare Organization Continue to Be Popular Targets

2016 continued to see healthcare organizations as popular targets for hackers and other criminals looking to steal personal information.  There were 57 breaches in November 2016 alone.  Will healthcare organizations continue to be popular targets or will hackers turn their attention elsewhere?

International Data Breaches

Between the requirements of the European Union’s General Data Regulation and new laws and rules in countries like Canada and Australia, companies with an international presence who suffer a breach will likely have to wade through confusing and conflicting requirements.

Class Actions After Breaches

The Third Circuit recently ruled that individuals who had their personal information stolen had standing to sue under the Fair Credit Reporting Act even if their identity had not been stolen and they had otherwise suffered no damages.  Courts in Michigan and elsewhere have dismissed similar lawsuits where the individuals were not able to show actual damages. However, there seems to be a trend to allow such cases to move forward.

Vulnerability of Mobile Devices

Whether it’s a phone, a car or a drone, companies are paying more attention to the vulnerability of mobile technology to hacking.  If you haven’t already seen it, the video (https://www.youtube.com/watch?v=MK0SrxBC1xs) of a Jeep being taken over remotely emphasizes how important it is to make sure mobile devices are protected and secure.

Will Ransomware Attacks Continue to Grow

Ransomware has quickly emerged as a favorite method of hackers.  2016 saw companies become popular targets of ransomware attacks, will that trend continue in 2017 and beyond?

Post authored by Tim Gutwald