Unsuccessful Security Incidents. Customer agrees that:
Unsuccessful Security Incidents. Except as noted in C. 1 (e) below, the parties acknowledge and agree that this section constitutes notice by Business Associate to Company of the ongoing existence and occurrence of attempted but Unsuccessful Security Incidents (as defined below) for which no additional notice to Company shall be required. “Unsuccessful Security Incidents” shall include, but not be limited to, pings and other broadcast attacks on Business Associate’s firewall, port scans, unsuccessful log-on attempts, denials of service and any combination of the above, so long as no such incident results in unauthorized access, use or disclosure of PHI.
Unsuccessful Security Incidents. Customer agrees that 4me assesses whether the personal data processed for the Customer is affected by a security incident. If not, this Security Incident will not be subject to this Section
Unsuccessful Security Incidents. Customer agrees that an unsuccessful Security Incident will not be subject to this Clause 3.9. An unsuccessful security incident is one that results in no unauthorized access to Personal Data or to any of Lative’s equipment or facilities storing Personal Data, and may include, without limitation, pings and other broadcast attacks on firewalls or edge servers, port scans, unsuccessful log-on attempts, denial of service attacks, packet sniffing (or other unauthorized access to traffic data that does not result in access beyond headers) or similar incidents.
Unsuccessful Security Incidents. For Unsuccessful Security Incidents, Business Associate shall provide Covered Entity, upon its written request, a report that: (i) identifies the categories of Unsuccessful Security Incidents; (ii) indicates whether Business Associate believes its (or its Business Associate Subcontractor’s) current defensive security measures are adequate to address all Unsuccessful Security Incidents, given the scope and nature of such attempts; and
Unsuccessful Security Incidents. Notwithstanding the foregoing, Business Associate shall not be required to report to Covered Entity the occurrence of an unsuccessful Security Incident; however Business Associate shall provide to Covered Entity a report of unsuccessful Security Incidents upon reasonable request. In this agreement, an unsuccessful Security Incident shall include, without limitation, activity such as pings and other broadcast attacks on Business Associate’s firewall, port scans, unsuccessful log-on attempts, denial of service, and any combination of the above, so long as such activity does not result in unauthorized access, use, acquisition, or disclosure of PHI.
Unsuccessful Security Incidents. Security Incidents that do not result in unauthorized access, use, disclosure, modification, or destruction of information or interference with system operations.
Unsuccessful Security Incidents. Customer agrees that an Unsuccessful Security Incident is not subject to the requirements of this Section 5. In addition, PayScale’s cooperation or obligation to report or respond to Security Incidents under this Addendum and the Agreement is not and will not be interpreted as an acknowledgment by PayScale of any fault or liability of PayScale with respect to a Security Incident.
Unsuccessful Security Incidents. We will have no obligation to notify you under Section 7.1 or otherwise under this DPA, the MSA of any Unsuccessful Security Incident. Top
Unsuccessful Security Incidents. WE WILL HAVE NO OBLIGATION TO NOTIFY YOU UNDER SECTION 6.1 OR OTHERWISE UNDER THIS CCPA ADDENDUM, THE MSA OF ANY UNSUCCESSFUL SECURITY INCIDENT. Top
