US Federal Communications Commission updates, and beefs up its data breach notification rules on 13 March 2024…the US is moving more in line with the EU and Australia continues to languish in this area
March 27, 2024
Mandatory data breach notification rules are becoming standard in most first world jurisdictions. Over time the obligations upon affected entities have tightened. That is good policy given the way that hackers operate. The US Federal Communications Commission (“FCC”) has updated Data Breach Notification Rules. These updated rules obviously do not apply in Australia. That said they are very useful to consider because they are so much more detailed and analytical than the Australian equivalents. It is a very useful resource when considering how to deal with data breaches and how to properly structure a notification.
The media release relevantly provides:
It has been sixteen years since the Federal Communications Commission last updated its policies to protect consumers from data breaches. Sixteen years! To be clear, that was before the iPhone was introduced. There were no smart phones, there was no app store, there were no blue and green bubbles for text. It was a long time ago. In the intervening years a lot has changed about when, where, and how we use our phones, and what data our providers collect about us when we do. But not the FCC’s data breach rules; they remain stuck in the analog age.
Today we fix this problem. We update our policies to protect consumers from digital age data breaches. We make clear that under the Communications Act carriers have a duty to protect the privacy and security of consumer data.
First, we modernize our data breach rules to make clear they include all personally identifiable information. In the past, these rules have only prohibited the disclosure of information about who we call and when. But consumers also deserve to know if their carrier has disclosed their social security number or financial data or other sensitive information that could put them in harm’s way. We fix that today—and it is overdue. Read the rest of this entry »