TribLIVE

| Opinion/The Review

 
Larger text Larger text Smaller text Smaller text | Order Photo Reprints

The UPMC data breach: Larger questions

Email Newsletters

Click here to sign up for one of our email newsletters.

Letters home ...

Traveling abroad for personal, educational or professional reasons?

Why not share your impressions — and those of residents of foreign countries about the United States — with Trib readers in 150 words?

The world's a big place. Bring it home with Letters Home.

Contact Colin McNickle (412-320-7836 or cmcnickle@tribweb.com).

Daily Photo Galleries

Wednesday, June 4, 2014, 9:00 p.m.
 

Serious concerns raised by UPMC's April announcement that hackers had stolen 27,000 employees' personal information from its payroll system are only heightened by word that all of UPMC's 62,000 workers could have been affected.

The question of how this could have happened in the first place looms larger. So do questions about UPMC's grasp of its own data security and its response to this hack.

After all, UPMC said it learned of the breach when employees reported fraudulent tax returns had been filed using their identities. And with federal prosecutors, the IRS, the Secret Service, the U.S. Postal Inspection Service and police investigating, UPMC now says it was informed by authorities that all employees could have been affected. Why didn't UPMC detect the breach — and realize how extensive it was — on its own?

When hackers hit health care, patient or payment records — not payroll data — usually are stolen, according to Larry Ponemon, president and founder of the Ponemon Institute, a Michigan cybercrime research organization. “Employee data,” he says, “tends to be better protected.” Why wasn't UPMC employees' payroll information “better protected”?

Those responsible for this hack must be brought to justice, of course. And UPMC, owing its employees far better payroll security, must take a more proactive approach to avoid a repeat of this data breach, which its 62,000 employees never should have had to worry about.

Subscribe today! Click here for our subscription offers.

 

 


Show commenting policy

Most-Read Editorials

  1. Greensburg Tuesday takes
  2. Pittsburgh Tuesday takes
  3. Alle-Kiski Tuesday takes
  4. The Kane case: Distractions mount
  5. Trumpeting ObamaCare: The Medicaid factor