BeyondTrust

Security in Context: The BeyondTrust Blog

Welcome to Security in Context

Bringing you news and commentary on solutions and strategies for protecting critical IT infrastructure in the context of your business.

Top 5 Data Breach Excuses Of 2011 (And What They Really Mean): Part 2

Posted January 4, 2012    Peter McCalister

SHUT THE DOOR AFTER THE HORSE HAS BOLTED. High Point Regional Health System, USA, September 2011

This excuse allows the breached organization to sound authoritative by providing an answer to how the breach could have been prevented to the media and public, even if it is a solution they haven’t put into practice yet. Unfortunately, the damage is already done and the misuse of privilege has caused significant enough damage to warrant the excuse being used in the first place.

High Point Regional Health System officials said they uncovered a breach involving the improper use of protected patient information by a former employee, in Fall of 2011. The former employee, who was fired after the breach came to light, had access to patients’ names, addresses, dates of birth, Social Security numbers, driver’s license numbers and insurance information.

After reassuring patients that they had apprehended the ‘bad guy’ – “We discovered it on our own and immediately took action on this employee,” said Tracie Blackmon, director of Public Relations & Marketing for the health system. “We feel confident we took the correct action once we found out about this, and that’s what’s most important — that our patients are taken care of and protected.” – High Point went on to relate the steps they had taken to close the door after the horse had bolted.

‘The health system has taken steps to prevent another breach, including a full review of the process of obtaining patient information at Premier Imaging. “Premier Imaging has stringent policies, procedures and systems in place to protect patient information and takes very seriously our obligation to safeguard the personal and health information of our patients,” said Greg Taylor, chief operating officer. “We regret this incident has occurred and are committed to preventing future occurrences.

BeyondTrust says: Sounding authoritative about the steps you are going to take, doesn’t mitigate for the fact it happened in the first place.
HiPAA regulations make quite clear the need for health organizations to:

i.) Manage network access based on the role based elevation of privilege – i.e access is granted based on what someone’s job requires them to do, rather than their position and authority within the company.
ii.) Provide audit trails of who accessed what, when, and for what purpose.

Leave a Reply

Additional articles

ovum-research

New Analyst SWOT Assessment Identifies Key Strengths of PowerBroker

Posted November 24, 2014    Scott Lang

Following on the heels of the Gartner PAM market guide and Frost & Sullivan review of Password Safe comes a new analyst review of our BeyondInsight and PowerBroker platforms, a SWOT assessment of BeyondTrust written by Ovum. Ovum’s honest and thorough review of BeyondTrust indicates that we are delivering, “…an integrated, one-stop approach to PAM….

Tags:
, , ,

Patented Windows privilege management brings you unmatched benefits

Posted November 24, 2014    Scott Lang

We are pleased to announce that BeyondTrust has been granted a new U.S. Patent (No. 8,850,549) for privilege management, validating our approach to helping our customers achieve least privilege in Windows environments. The methods and systems that we employ for controlling access to resources and privileges per process are unique to BeyondTrust PowerBroker for Windows….

Tags:
6

A Quick Look at MS14-068

Posted November 20, 2014    BeyondTrust Research Team

Microsoft recently released an out of band patch for Kerberos.  Taking a look at the Microsoft security bulletin, it seems like there is some kind of issue with Kerberos signatures related to tickets. Further information is available in the Microsoft SRD Blogpost So it looks like there is an issue with PAC signatures.  But what…

Tags:
, , , ,