Unsuccessful Security Incidents. Customer agrees that:
(i) an unsuccessful Security Incident will not be subject to this Section 9. An unsuccessful Security Incident is one that results in no unauthorised access to Customer Data or to any of AWS’s equipment or facilities storing Customer 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 unauthorised access to traffic data that does not result in access beyond headers) or similar incidents; and
(ii) AWS’s obligation to report or respond to a Security Incident under this Section 9 is not and will not be construed as an acknowledgement by AWS of any fault or liability of AWS with respect to the Security Incident.
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. 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 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. Customer agrees that:
a. An unsuccessful Security Incident will not be subject to this Section 10. An unsuccessful Security Incident is one that results in no unauthorized access to Customer Data or to any of ZEIT’s equipment or facilities storing Customer Data, and may include, without limitation, pings and other broadcast attacks on firewalls or edge servers, port scans, unsuccessful login 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; and
b. ZEIT’s obligation to report or respond to a Security Incident under this Section 10 is not and will not be construed as an acknowledgement by ZEIT of any fault or liability of ZEIT with respect to the Security Incident.
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. Customer agrees that:
8.3.1. an unsuccessful Security Incident will not be subject to this Section 8. An unsuccessful Security Incident is one that results in no unauthorised access to Customer Data or to any of MBBM VAS’s equipment or facilities storing Customer Data, and could 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 unauthorised access to traffic data that does not result in access beyond headers) or similar incidents; and
8.3.2. MBBM VAS’s obligation to report or respond to a Security Incident under this Section 8 is not and will not be construed as an acknowledgement by MBBM VAS of any fault or liability of MBBM VAS with respect to the Security Incident.
Unsuccessful Security Incidents. Customer agrees that:
(i) an unsuccessful Security Incident will not be subject to this Section 10.2. An unsusccessful Security Incident is one that results in no unauthorized access to Customer Data or to any of Mirantis’ or its subcontractors’ equipment or facilities storing Customer Data, and could 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; and
(ii) Mirantis’ obligation to report or respond to a Security Incident under this Section 10 is not and will not be construed as an acknowledgement by Mirantis of any fault or liability of Mirantis with respect to the Security Incident.
Unsuccessful Security Incidents. The parties agree that this section satisfies any notices necessary by Business Associate to Covered Entity of the ongoing existence and occurrence of attempted, but Unsuccessful Security Incidents (as defined in Section 1.)
Unsuccessful Security Incidents. Business Associate is not required to report attempted Security Incidents that fail to be successful and consequently fail to result in the unauthorized use or disclosure of EPHI, such as pings and other broadcast attacks on the Business Associate’s firewall, port scans, unsuccessful log-on attempts, and denials of service occur.
