Risk
1/13/2011
09:53 PM
George V. Hulme
George V. Hulme
Commentary
Connect Directly
RSS
E-Mail
50%
50%

Kudos To Tucson University Medical Center For Firing Alleged Snoops

The Tucson University Medical Center reportedly has let go three employees for accessing the medical records of those involved in the Tuscon shooting tragedy without authorization.

The Tucson University Medical Center reportedly has let go three employees for accessing the medical records of those involved in the Tuscon shooting tragedy without authorization.That's what the Arizona Daily Star is reporting in its story, 3 UMC workers fired for invading records:

The hospital said it notified families of the affected patients.

The shooting killed six people and injured 13, including U.S. Rep. Gabrielle Giffords. Giffords is in critical condition with a bullet wound to the head.

All six remaining injured patients from the shootings, including Giffords, are at UMC.

That was quick identification and resolution of the breach. I do hope that the alleged snoops didn't have their log-on credentials used by other employees.That's always a risk. However, the hospital's statement provides a good clue as to what made the quick resolution possible. Access monitoring and auditing software:

With advances in technology, ensuring patient privacy has become the focus of hospitals nationwide. UMC uses sophisticated technology to help prevent and detect inappropriate access to patient information.

That shows the importance of hospitals employing monitoring software, and having the procedures in place (and the fortitude) to act quickly. I'll bet employees at the medical center will think twice before snooping in the future.

Unfortunately, it will probably take many more such incidents before hospital workers (those who are inclined to snoop) are too concerned for the potential repercussions to do so.

Because these types of incidents seem to happen: all, of, the, time.

Recall when the University of California, Los Angeles Medical Center fired 13 (or more) employees for peeking at the star's medical records? That was way back in 2008.

In 2009, a doctor and two hospital employees were sentenced, as part of a plea agreement, to probation and thousands in fines, each. That plea agreement from the Little Rock Division of the FBI is available here.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6335
Published: 2014-08-26
The Backup-Archive client in IBM Tivoli Storage Manager (TSM) for Space Management 5.x and 6.x before 6.2.5.3, 6.3.x before 6.3.2, 6.4.x before 6.4.2, and 7.1.x before 7.1.0.3 on Linux and AIX, and 5.x and 6.x before 6.1.5.6 on Solaris and HP-UX, does not preserve file permissions across backup and ...

CVE-2014-0480
Published: 2014-08-26
The core.urlresolvers.reverse function in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not properly validate URLs, which allows remote attackers to conduct phishing attacks via a // (slash slash) in a URL, which triggers a scheme-relative URL ...

CVE-2014-0481
Published: 2014-08-26
The default configuration for the file upload handling system in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 uses a sequential file name generation process when a file with a conflicting name is uploaded, which allows remote attackers to cause a d...

CVE-2014-0482
Published: 2014-08-26
The contrib.auth.middleware.RemoteUserMiddleware middleware in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3, when using the contrib.auth.backends.RemoteUserBackend backend, allows remote authenticated users to hijack web sessions via vectors relate...

CVE-2014-0483
Published: 2014-08-26
The administrative interface (contrib.admin) in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not check if a field represents a relationship between models, which allows remote authenticated users to obtain sensitive information via a to_field ...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Three interviews on critical embedded systems and security, recorded at Black Hat 2014 in Las Vegas.