Industry


Ads by TechWords

See your link here


Michael R. Farnum's picture
Michael R. Farnum

Hitting the Security Nerve

Fidelity sends breach notification out to Yahoo! employees

The Breach Blog is reporting that Fidelity sent out a breach notification in compliance with New Hampshire's breach notification law. Someone at Fidelity mistakenly sent out personal information (first and last name, SSN, and Yahoo! ID number) to two stock plan administrators at a different Fidelity client. The notice does not say how many people had their personal information exposed.

Like Evan Francen says in his post, this was simply a human error. The Fidelity employee either attached the wrong data to an email meant for that company, or they put the wrong email addresses on an email meant for Yahoo! It really just comes down to that. And really, how do you put technology in place to guard against this? There are plenty of products that stop data leakage, but technically this was a legit event. Without getting crazy complicated and taking the chance of getting lost in the weeds, you really cannot do a lot to keep people from sending the wrong information to an authorized email address.

A couple of other things bother me about this breach notification. One is the same issue that Evan brings up, which is whether or not the transmission was encrypted in the first place. The other company likely has the same keys as Yahoo! does since they are a client of Fidelity, and whether or not the transmission was encrypted is really immaterial to the breach. However, it would have been a good idea to state that the email was encrypted. Of course, if they had said it was, I would probably be saying they are trying to make the situation look better than it is by putting in useless information. These people just can't win with me...

The second thing that bothers me is that this excerpt:

The inadvertent recipients have deleted the e-mail and have confirmed that the file has been deleted and that the information has not been copied, printed, or downloaded. Both plan administrators signed and delivered to Fidelity SPS a statement, confirming the facts described above and promising to maintain the confidentiality of any information that may have been viewed.

Oh, that is fine and dandy. Don't have to worry about a thing now! Oh, but wait. The breach happened on Nov 12 and was reported Nov 14. So AT LEAST one day of backups occured in that period (assuming the company has a good DR plan). Have the tapes or disks or whatever system they use been purged? Have those "inadvertent recipients" gone to IT to see if their company has an email archival policy that would prohibit this from occuring? Have they checked their email security appliance or outsourcing company to see if they have purged it? There are a lot more steps here than just having the "inadvertent recipients" delete the email and sign some piece of paper. Honestly, I wouldn't sign crap until I went through all of those steps.

What People Are Saying

Too many notifications

People are receiving more data breach notifications than is wise. A minor security misstep should not warrant a data breach notification.

--Ben

How? It's Easy!

<<< Like Evan Francen says in his post, this was simply a human error. The Fidelity employee either attached the wrong data to an email meant for that company, or they put the wrong email addresses on an email meant for Yahoo! It really just comes down to that. And really, how do you put technology in place to guard against this? >>>

Are you kidding? There should be no NEED for technology to guard against this, it should be POLICY that data may not be e-mailed that contains lists of people's full names and SSN's. Was this e-mail communication encrypted? If not, it doesn't matter that it went to the wrong person... it could have been the right person and it's equally as bad from a security standpoint.

@ Brian - Good point, but...

Brian, you make a good point. It would be good not to pass SSN's and full names across email in any way. However, if there is a business need to do so and there is proper security in place, then I can't see what the problem is. Yes, I think it would be a good idea to figure out whether or not the business case can be made, but the story doesn't give enough info to discern that.

Again, security should be a business enabler, not get in the way of business.

Michael R. Farnum

Better to be despised for too anxious apprehensions than ruined by too confident a security.
Edmund Burke (1729 - 1797)