Administrative Requirements and Burden of Proof
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
sanctions against workforce members who do not comply with these
policies and procedures.
| Covered entities and business associates must only provide the required notifications if the breach involved unsecured protected health information. Unsecured protected health information is protected health information that has not been rendered unusable, unreadable, or indecipherable to unauthorized persons through the use of a technology or methodology specified by the Secretary in guidance. This guidance was first issued in April 2009 with a request for public comment. The guidance was reissued after consideration of public comment received and specifies encryption and destruction as the technologies and methodologies for rendering protected health information unusable, unreadable, or indecipherable to unauthorized individuals. Additionally, the guidance also applies to unsecured personal health record identifiable health information under the FTC regulations. Covered entities and business associates, as well as entities regulated by the FTC regulations, that secure information as specified by the guidance are relieved from providing notifications following the breach of such information. ...read more |
| 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 ...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 |
|
July 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)
Data Breach Reporting (6)
ePHI Data (1)
|
