Perimeter
1/20/2012
06:23 PM
Commentary
Commentary
Commentary
50%
50%

Breach Notification: Know The Rules

State and federal laws require notification when a breach of protected information occurs. You need to know which laws apply and how to comply

The vast majority of states and territories in the United States have rules requiring organizations managing personal information to notify affected parties if their private information has been breached.

However, the laws differ from state to state in the way they define personal information, the requirements for who needs to be notified, and how notification must take place. Add to this the fact that federal laws also require breach notification, and we see that organizations caring for personal identifying data have their work cut out for them in understanding which rules apply and how they can ensure they’ll comply in the event of a breach.

Which Rules Apply?
The key point to remember when determining which laws apply to your organization is that state laws are written to protect the residents of a state. This means you need to comply with the state laws applying to the people whose data you manage. In other words, if you have customers or employees from Massachusetts, then even though your business is located in New Hampshire, you need to comply with the Massachusetts data protection and breach notification laws.

If it seems like it a difficult task to understand and comply with upward of 50 different state and territorial laws, you get the message. It should also be clear why every year the U.S. Congress attempts to define federal data protection laws that would supersede these state laws. For better or worse, efforts at the national level have not succeeded, and we are left with the laws of the various states (in addition to the federal laws applying to financial and health information).

State breach notification laws have more in common than not. For example, these laws define personal information as a person’s first and last name, or first initial and last name, together with one or more other pieces of sensitive information. The obvious ones are Social Security number, driver’s license number, and credit card numbers. One area where differences tend to occur is banking information. For example, Massachusetts considers a bank account number (again, with a name) a piece of personal identifying information, even if there is no PIN or password that would allow a perpetrator to use the account. California, on the other hand, requires the presence of a PIN or password to make the account number a piece of protected data.

The first step in ensuring compliance with breach notification laws is knowing whose data you have. That means keeping accurate records of whose data you store, where they live, and where the data resides. Once you understand that, you can identify the laws that apply. Next, you can identify the particular pieces of information that you need to protect and understand the kind of breaches that would require you to notify the victims as well as state authorities.

In the next posting, I’ll talk about what constitutes a breach (and what doesn’t) and the mechanics of notification.

Richard Mackey is vice president of consulting at SystemExperts Corp.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading December Tech Digest
Experts weigh in on the pros and cons of end-user security training.
Flash Poll
Title Partner’s Role in Perimeter Security
Title Partner’s Role in Perimeter Security
Considering how prevalent third-party attacks are, we need to ask hard questions about how partners and suppliers are safeguarding systems and data.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-5426
Published: 2014-11-27
MatrikonOPC OPC Server for DNP3 1.2.3 and earlier allows remote attackers to cause a denial of service (unhandled exception and DNP3 process crash) via a crafted message.

CVE-2014-2037
Published: 2014-11-26
Openswan 2.6.40 allows remote attackers to cause a denial of service (NULL pointer dereference and IKE daemon restart) via IKEv2 packets that lack expected payloads. NOTE: this vulnerability exists because of an incomplete fix for CVE 2013-6466.

CVE-2014-6609
Published: 2014-11-26
The res_pjsip_pubsub module in Asterisk Open Source 12.x before 12.5.1 allows remote authenticated users to cause a denial of service (crash) via crafted headers in a SIP SUBSCRIBE request for an event package.

CVE-2014-6610
Published: 2014-11-26
Asterisk Open Source 11.x before 11.12.1 and 12.x before 12.5.1 and Certified Asterisk 11.6 before 11.6-cert6, when using the res_fax_spandsp module, allows remote authenticated users to cause a denial of service (crash) via an out of call message, which is not properly handled in the ReceiveFax dia...

CVE-2014-7141
Published: 2014-11-26
The pinger in Squid 3.x before 3.4.8 allows remote attackers to obtain sensitive information or cause a denial of service (out-of-bounds read and crash) via a crafted type in an (1) ICMP or (2) ICMP6 packet.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Now that the holiday season is about to begin both online and in stores, will this be yet another season of nonstop gifting to cybercriminals?