Welcome to our weekly roundup, where we share what you need to know about the cybersecurity news and events that happened over the past few days. This week, a new report revealed that the Equifax breach had a larger impact than previously thought. In addition, The Senate Intelligence Committee released an interim report declaring that the Department of Homeland Security had an “inadequate” response to the Russian hack of the 2016 election.
Read on to learn more.
Sales people and channel partners are integral parts of our business, and we have considered them key parts of our journey to GDPR compliance.
A new investigation revealed that millions of driver’s license numbers, phone numbers and email addresses in connection with names, dates of birth and Social Security numbers were exposed.
Email is a particularly weak link for companies because of its role as a communication tool, and the fact that it is still the number one threat vector for cybercriminal exploits.
The Senate Intelligence Committee determined that the Department of Homeland Security mounted an “inadequate” response to the Russian government-affiliated campaign in 2016.
According to the Protenus Breach Barometer, around 1.13 million patient records were compromised in 110 healthcare data breaches in the first quarter of 2018.
These regulations enshrine mandatory data breach notification in Canadian law in the form of an amendment to the Personal Information Protection and Electronic Documents Act (PIPEDA) of 2000.
After advising users to change their account passwords on May 3, Twitter recently revealed that it fixed the bug that stored passwords unmasked in an internal log and that there’s no indication of a breach.
Hackers are gaining access to cameras and recording videos, selling camera access to other parties, or even using cameras to snoop around shops and scoop credit card information from customers.
What do you think of Canada’s new data breach notification regulations? Share your thoughts in the comments below or follow me on Twitter to continue the conversation; @JonLClay.