Fix Vulnerabilities
Think about service providers. If service providers
were involved, examine what personal information they can access and
decide if you need to change their access privileges. Also, ensure your
service providers are taking the necessary steps to make sure another
breach does not occur. If your service providers say they have remedied
vulnerabilities, verify that they really fixed things.
Check your network segmentation. When you set up
your network, you likely segmented it so that a breach on one server or
in one site could not lead to a breach on another server or site. Work
with your forensics experts to analyze whether your segmentation plan
was effective in containing the breach. If you need to make any changes,
do so now.
Work with your forensics experts. Find out if
measures such as encryption were enabled when the breach happened.
Analyze backup or preserved data. Review logs to determine who had
access to the data at the time of the breach. Also, analyze who
currently has access, determine whether that access is needed, and
restrict access if it is not. Verify the types of information
compromised, the number of people affected, and whether you have contact
information for those people. When you get the forensic reports, take
the recommended remedial measures as soon as possible.
Have a communications plan. Create a comprehensive
plan that reaches all affected audiences — employees, customers,
investors, business partners, and other stakeholders. Don’t make
misleading statements about the breach. And don’t withhold key details
that might help consumers protect themselves and their information.
Also, don’t publicly share information that might put consumers at
further risk.
Anticipate questions that people will ask. Then, put
top-tier questions and clear, plain-language answers on your website
where they are easy to find. Good communication up front can limit
customers’ concerns and frustration, saving your company time and money
later.
| 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 ...read more |
| The HIPAA Breach Notification Rule, 45 CFR §§ 164.400-414, requires HIPAA covered entities and their business associates to provide notification following a breach of unsecured protected health information. Similar breach notification provisions implemented and enforced by the Federal Trade Commission (FTC), apply to vendors of personal health records and their third party service providers, pursuant to section 13407 of the HITECH Act. ...read more |
| If a breach of unsecured protected health information occurs at or by a business associate, the business associate must notify the covered entity following the discovery of the breach. A business associate must provide notice to the covered entity without unreasonable delay and no later than 60 days from the discovery of the breach. To the extent possible, the business associate should provide the covered entity with the identification of each individual affected by the breach as well as any other available information required to be provided by the covered entity in its notification to affected individuals. ...read more |
| Covered entities and business associates, as applicable, have the burden of demonstrating that all required notifications have been provided or that a use or disclosure of unsecured protected health information did not constitute a breach. Thus, with respect to an impermissible use or disclosure, a covered entity (or business associate) should maintain documentation that all required notifications were made, or, alternatively, documentation to demonstrate that notification was not required: (1) its risk assessment demonstrating a low probability that the protected health information has been compromised by the impermissible use or disclosure; or (2) the application of any other exceptions to the definition of “breach.” Covered entities are also required to comply with certain administrative requirements with respect to breach notification. For example, covered entities must have in place written policies and procedures regarding breach notification, must train employees on these policies and procedures, and must develop and apply appropriate ...read more |
|
August 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
November 2022 (11)
January 2025 (3)
Blog Labels
Data Breach Reporting (6)
Data Breach Notification (6)
Health Care Data (1)
ePHI Data (1)
|
