The 10 Most Common Security Incident Response Mistakes (Part II)

June 24, 2011
Picking up where I left off in my last posting, here are five more common mistakes that health care organizations make in responding to data security

Picking up where I left off in my last posting, here are five more common mistakes that health care organizations make in responding to data security breaches:

6. Failing to train your personnel to spot a security breach. When a laptop is stolen that contains Social Security numbers or other personal information, it is a significant event that must be promptly reported to an organization's compliance and legal departments. If rank and file employees don't recognize a security breach when they see one, then the best security incident response plan will be ineffective.

7. Failing to follow proper computer forensic procedures. Before starting an investigation and reviewing systems directly, consider whether you're applying appropriate forensic procedures that might preserve evidence. By first making a forensic image, you preserve everything (including the metadata), so that you can return to that snapshot at any time. Such measures may permit an organization to identify a hacker's IP address.

8. Inadequate management of vendor relationships. A company that entrusts its personal information to a vendor should bind that vendor to reasonable privacy and security representations. For example, if a vendor is responsible for a breach, it should be required to notify its customer of the event within a relatively short time frame.

9. Failing to notify appropriate regulatory agencies. Even though it may not be required, health care organizations should consider whether relevant regulatory agencies, such as a state Department of Insurance regulating an HMO or insurer, would be offended if they read about a security breach in the paper. An increasingly wide range of health care regulatory agencies have asserted their jurisdiction to conduct investigations related to health care security breaches.

10. Failing to coordinate effectively with law enforcement authorities. Most state security breach notification laws permit you to delay notification if it would impede a criminal investigation. Carefully consider the appropriateness of notifying law enforcement, as well as which agency might most aggressively pursue the case, whether it's the local police department, the FBI or a local high tech crimes task force. But don't delay notification based upon a half-hearted investigation by the local PD into a routine laptop theft!

Sponsored Recommendations

How Digital Co-Pilots for patients help navigate care journeys to lower costs, increase profits, and improve patient outcomes

Discover how digital care journey platforms act as 'co-pilots' for patients, improving outcomes and reducing costs, while boosting profitability and patient satisfaction in this...

5 Strategies to Enhance Population Health with the ACG System

Explore five key ACG System features designed to amplify your population health program. Learn how to apply insights for targeted, effective care, improve overall health outcomes...

A 4-step plan for denial prevention

Denial prevention is a top priority in today’s revenue cycle. It’s also one area where most organizations fall behind. The good news? The technology and tactics to prevent denials...

Healthcare Industry Predictions 2024 and Beyond

The next five years are all about mastering generative AI — is the healthcare industry ready?