Guidance to Render Unsecured Protected Health Information Unusable, Unreadable, or Indecipherable to Unauthorized Individuals
Protected
health information (PHI) is rendered unusable, unreadable, or
indecipherable to unauthorized individuals if one or more of the
following applies:
- Electronic PHI has been encrypted as specified in the HIPAA
Security Rule by “the use of an algorithmic process to transform data
into a form in which there is a low probability of assigning meaning
without use of a confidential process or key” (45 CFR 164.304 definition
of encryption) and such confidential process or key that might enable
decryption has not been breached. To avoid a breach of the confidential
process or key, these decryption tools should be stored on a device or
at a location separate from the data they are used to encrypt or
decrypt. The encryption processes identified below have been tested by
the National Institute of Standards and Technology (NIST) and judged to
meet this standard.
- Valid encryption processes for data at rest are consistent with NIST Special Publication 800-111, Guide to Storage Encryption Technologies for End User Devices.1
- Valid encryption processes for data in motion are those which comply, as appropriate, with NIST Special Publications 800-52, Guidelines for the Selection and Use of Transport Layer Security (TLS) Implementations; 800-77, Guide to IPsec VPNs; or 800-113, Guide to SSL VPNs, or others which are Federal Information Processing Standards (FIPS) 140-2 validated.
- The media on which the PHI is stored or recorded has been destroyed in one of the following ways:
- Paper, film, or other hard copy media have been shredded or
destroyed such that the PHI cannot be read or otherwise cannot be
reconstructed. Redaction is specifically excluded as a means of data
destruction.
- Electronic media have been cleared, purged, or destroyed consistent with NIST Special Publication 800-88, Guidelines for Media Sanitization such that the PHI cannot be retrieved.
Notify individuals. If you quickly notify people that their personal information has been compromised, they can take steps to reduce the chance that their information will be misused. In deciding who to notify, and how, consider: state lawsthe nature of the compromisethe type of information takenthe likelihood of misusethe potential damage if the information is misused For example, thieves who have stolen names and Social Security numbers can use that information not only to sign up for new accounts in the victim’s name, but also to commit tax identity theft. People who are notified early can take steps to limit the damage. When notifying individuals, the FTC recommends you: Consult with your law enforcement contact about the timing of the notification so it doesn’t impede the investigation.Designate a point person within your organization for releasing information. Give the contact person the latest information about the breach, your response, and how ...read more |
In today's digital landscape, data breaches are an unfortunate reality that businesses of all sizes must contend with. A single security lapse can lead to significant financial losses, reputational damage, and legal headaches. While prevention is paramount, having a clear and well-defined data breach reporting procedure is crucial for minimizing the fallout when the inevitable happens. This article will guide you through the essential steps your business needs to take. Why a Solid Breach Reporting Procedure is Non-Negotiable Data breaches are not just a concern for large corporations; they affect small and medium-sized businesses (SMBs) just as much, if not more so. A robust reporting procedure serves multiple critical purposes: Compliance with Regulations: Various data privacy regulations, like GDPR, CCPA, and others, mandate specific reporting timelines and requirements. Failure to comply can result in hefty fines and legal action.Minimizing Damage: Swift and decisive action can significantly limit the scope ...read more |
Move quickly to secure your systems and fix vulnerabilities that may have caused the breach. The only thing worse than a data breach is multiple data breaches. Take steps so it doesn’t happen again. Secure physical areas potentially related to the breach. Lock them and change access codes, if needed. Ask your forensics experts and law enforcement when it is reasonable to resume regular operations.Mobilize your breach response team right away to prevent additional data loss. The exact steps to take depend on the nature of the breach and the structure of your business. Assemble a team of experts to conduct a comprehensive breach response. Depending on the size and nature of your company, they may include forensics, legal, information security, information technology, operations, human resources, communications, investor relations, and management. Identify a data forensics team. Consider hiring independent forensic investigators to help you determine the source and scope ...read more |
When your business experiences a data breach, notify law enforcement, other affected businesses, and affected individuals. Determine your legal requirements. All states, the District of Columbia, Puerto Rico, and the Virgin Islands have enacted legislation requiring notification of security breaches involving personal information. In addition, depending on the types of information involved in the breach, there may be other laws or regulations that apply to your situation. Check state and federal laws or regulations for any specific requirements for your business. Notify law enforcement. Call your local police department immediately. Report your situation and the potential risk for identity theft. The sooner law enforcement learns about the theft, the more effective they can be. If your local police aren’t familiar with investigating information compromises, contact the local office of the FBI or the U.S. Secret Service. For incidents involving mail theft, contact the U.S. Postal Inspection Service. Did the ...read more |
|
May 2025
Su | Mo | Tu | We | Th | Fr | Sa |
| | | | 1 | 2 | 3 |
4 | 5 | 6 | 7 | 8 | 9 | 10 |
11 | 12 | 13 | 14 | 15 | 16 | 17 |
18 | 19 | 20 | 21 | 22 | 23 | 24 |
25 | 26 | 27 | 28 | 29 | 30 | 31 |
Blog Home
Newest Blog Entries
1/21/25 Healthcare Data Breaches and Their Devastating Impact
1/21/25 Your Essential Guide to Data Breach Reporting Procedures
1/21/25 Understanding Your Obligations in Data Breach Reporting
11/16/22 Administrative Requirements and Burden of Proof
11/16/22 Notification by a Business Associat
11/16/22 Breach Notification Requirements
11/16/22 Unsecured Protected Health Information and Guidance
11/16/22 Guidance to Render Unsecured Protected Health Information Unusable, Unreadable, or Indecipherable to Unauthorized Individuals
11/16/22 Definition of Breach
11/16/22 Breach Notification Rule
11/16/22 Notify Individuals
Blog Archives
January 2025 (3) November 2022 (11)
Blog Labels
Health Care Data (1) Data Breach Notification (6) ePHI Data (1) Data Breach Reporting (6)
|