Notify Appropriate Parties
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 breach involve electronic personal health records? Then
check if you’re covered by the Health Breach Notification Rule. If so,
you must notify the FTC and, in some cases, the media. Complying with the FTC’s Health Breach Notification Rule
explains who you must notify, and when. Also, check if you’re covered
by the HIPAA Breach Notification Rule. If so, you must notify the
Secretary of the U.S. Department of Health and Human Services (HHS) and,
in some cases, the media. HHS’s Breach Notification Rule explains who
you must notify, and when.
| 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 |
| 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 |
| A breach is, generally, an impermissible use or disclosure under the Privacy Rule that compromises the security or privacy of the protected health information. An impermissible use or disclosure of protected health information is presumed to be a breach unless the covered entity or business associate, as applicable, demonstrates that there is a low probability that the protected health information has been compromised based on a risk assessment of at least the following factors: The nature and extent of the protected health information involved, including the types of identifiers and the likelihood of re-identification;The unauthorized person who used the protected health information or to whom the disclosure was made;Whether the protected health information was actually acquired or viewed; andThe extent to which the risk to the protected health information has been mitigated.Covered entities and business associates, where applicable, have discretion to provide the required breach notifications following an impermissible ...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 |
|
January 2026
| 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 Notification (6)
Health Care Data (1)
ePHI Data (1)
Data Breach Reporting (6)
|
