In Brief

Featured Posts

DPO Management

Public Policy

Privacy News

Home » DPO Management, Data Breaches, Enforcement, Featured Posts, Prosecutions

Blue Cross Blue Shield Breach Notification – Any delay is unreasonable!

Submitted by Steve Meltzer on November 16, 2009 – 7:00 pmComments

The Connecticut Attorney General has requested more information from Blue Cross Blue Shield in order to determine if BCBS violated Connecticut law and acted in an unfair and deceptive manner because it waited TWO MONTHS TO NOTIFY RESIDENTS OF A BREACH.

According to Hunton & Williams,

“[t]he data contained on the stolen laptop included the names, addresses and Taxpayer Identification Numbers of approximately 19,000 health care providers in Connecticut.  The breach also involved thousands of Social Security numbers (“SSNs”), since an estimated 16-22% of individual health care providers use their SSNs as Taxpayer Identification Numbers.

Attorney General Blumenthal called “one of the most sizable and significant in Connecticut’s history,” involved the theft of a laptop containing confidential unencrypted data from the car of a BCBS employee in late August.  BCBS notified affected Connecticut residents of the breach in late October.”

The Attorney General needs to decide, as an initial regulatory decision, whether, in terms of protecting the citizens of the State of Connecticut, the delay was reasonable.

The answer is rather simple, really.   The starting point for the decision needs to be that any delay is unreasonable. That is, the instant that the data was compromised, the potential for harm had begun.  BCBS needs, therefore, to justify a reasonable reason why it was putting citizens’ financial security at risk.

The only reasonable excuse, the only possible rationale that can be justified is that BCBS could not determine who should be notified.  Even then, a notification should have been forthcoming to all potential victims.

What other reasonable excuse could there possibly be?  Pray tell?

Does your organization have a data breach protocol?  Isn’t it about time?

bcbs bubble burst

Popularity: 32% [?]

Share and Enjoy:
  • RSS
  • Twitter
  • Facebook
  • LinkedIn
  • E-mail this story to a friend!
  • Print this article!
  • Digg
  • del.icio.us
  • StumbleUpon
  • FriendFeed

Related posts:

  1. Blue Cross Blue Shield in the Data Breach Crosshairs BCBS of Tennessee is reporting a breach effecting 2 million individual. BCBS...
  2. New Massachusetts Privacy Laws – Breach Notification Requirements [Updated October 15, 2009 for compliance with new amendments to the regulations]...
  3. New Hampshire’s new breach notification law effective on 01/01/2010 New Hampshire’s new breach notification law builds on the breach notification requirements...
  4. HITECH Breach Notification Interim Final Rule HHS issued regulations requiring health care providers, health plans, and other entities...
  5. CT: AG sues Health Net over data breach Following a security breach involving health information, social security numbers and bank...
  6. AU: Data breach notification legislation may be in the offing Australian businesses may soon be forced to tell their customers if their...

  • BCBS should also be taking steps to encrypt data so that protected health information is protected on media. Encrypting data on a laptop is very easy and should have been done by an organization as large at BCBS.

    Alex Zaltsman
    CEO
    http://www.experiordata.com
  • Thanks for the comment. I agree. There is no reason for unencrypted data to be "walking around." This is as true of organizations the size of BCBS as it is for much smaller organizations as well.
blog comments powered by Disqus