Security Breach Notifications. Notice must be given by the Subrecipient to anyone whose PSCI could have been breached in accordance with HIPAA, the Information Practices Act of 1977, and State policy.
Security Breach Notifications. Notice must be given by the Subrecipient to anyone whose confidential, sensitive and/or personal identifying information could have been breached in accordance with HIPAA, the Information Practices Act of 1977, and State policy.
Security Breach Notifications. TCP will promptly report to Client any unauthorized access to Client Data within TCP’s or its Subprocessors’ systems upon discovery and in accordance with applicable data breach notification laws. TCP will use diligent efforts to promptly remedy any breach of security that permitted such unauthorized access. TCP’s notification of or response to any security incident under this Section 3.2 shall not be construed as an acknowledgment by TCP of any fault or liability with respect to such security incident.
Security Breach Notifications. If Lative becomes aware of a Security Incident for which notification to Customer is required under applicable Data Protection Laws, Lative will, without undue delay: (a)notify Customer of the Security Incident:
Security Breach Notifications. Within thirty (30) days of discovering an unauthorized release, disclosure or acquisition of Customer Data (“Security Breach”), ALI will notify Customer in writing that a Security Breach has occurred. XXX will investigate the causes and consequences of the Security Breach and will attempt to minimize the risk of any further unauthorized releases, disclosures, or acquisitions. If Customer elects to or is required to notify individuals whose data was or may have been involved in the Security Breach, Customer will be solely responsible for making such notifications. For Review
Security Breach Notifications. 1NCE shall inform the Customer without undue delay of any disruptions, breaches of data pro- tection regulations or agreed stipulations through 1NCE or the persons employed by it as well as of any suspected data protection breaches or irregularities in the processing of personal data after becoming aware of the Se- curity Incident. Furthermore, 1NCE shall take reasonable steps to mitigate the effects and to minimize any damage resulting from the Secu- rity Incident. This applies in particular with re- gard to potential notification obligations of the Customer in accordance with Art. 33 and Art. 34 GDPR. 1NCE undertakes to appropriately sup- port the Customer, if necessary, in its duties ac- cording to Art. 33 and 34 GDPR (Art. 28 para. 3 sentence 2 lit. f GDPR). Notifications according to Art. 33 or 34 GDPR for the Customer may only be carried out by 1NCE after prior instruction in accordance with this DPA. The Customer agrees that an unsuccessful Security Incident will not be subject to this Section. An unsuccessful Security Incident is one that results in no unauthorized access to Customer Data or to any of 1NCE equipment or facilities storing Customer Data, and may include, without limitation, pings and other broadcast attacks on firewalls or servers, port scans, unsuccessful log-on attempts, denial of service attacks, packet sniffing (or other unau- thorized access to traffic data that does not re- xxxx in access beyond headers) or similar inci- dents. In addition, the Customer agrees 1NCE’s obligation to report or respond to a Security In- cident under this Section is not and will not be construed as an acknowledgement by 1NCE of any fault or liability of 1NCE with respect to the Security Incident.
Security Breach Notifications. Equinix will contact Customer via phone or email of any actual or attempted unauthorized access of Customer's Licensed Space (i.e., private cage or cabinet) ("Security Breach") In the provision of Licensed Space and Services, Equinix does not manage nor monitor Customer's Equipment and does not monitor any Cross Connects. Customer is solely responsible for monitoring Customer's Equipment and its network traffic.
Security Breach Notifications. Equinix will contact Customer via phone or email of any actual or attempted unauthorized access of Customer’s Licensed Space (i.e., private cage or cabinet) (“Breach”) within twenty-four (24) hours of discovery, or as soon as is practical given the circumstances. In the provision of Licensed Space and Services, Equinix does not manage nor monitor Customer’s Equipment and does not monitor any Cross Connects. Customer is solely responsible for monitoring Customer’s Equipment and its network traffic.
Security Breach Notifications. Humanity will promptly report to Client any unauthorized access to Client Data within Humanity’s or its Subprocessors’ systems upon discovery and in accordance with applicable data breach notification laws. Humanity will use diligent efforts to promptly remedy any breach of security that permitted such unauthorized access. Humanity’s notification of or response to any security incident under this Section 4.2 shall not be construed as an acknowledgment by Humanity of any fault or liability with respect to such security incident.
Security Breach Notifications. If either party discovers that there has been an unauthorized release, disclosure, or acquisition of Customer Data or unauthorized access to the Service (a “Security Breach”), the party discovering the Security Breach will inform the other party in writing within twenty-four (24) hours of discovering the Security Breach. The parties will investigate the causes and consequences of the Security Breach and will attempt to minimize the risk of any further unauthorized releases, disclosures, or acquisitions. Each party agrees to provide reasonable and expeditious assistance to the other party in investigating a Security Xxxxxx. If Customer elects to or is required by law any governmental agencies or individuals whose data was or may have been involved in the Security Breach, Customer will be solely responsible for making such notifications.