Failed Security Incidents Sample Clauses

Failed Security Incidents. A failed security incident will not be subject to the terms of this Data Processing Addendum. A failed security incident is one that results in no unauthorized access or acquisition to Shared 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.
AutoNDA by SimpleDocs
Failed Security Incidents. Customer agrees that: (i) A failed Security Incident will not be subject to the terms of this Addendum. A failed Security Incident is one that results in no unauthorised access to Customer Data or to any of Tsohost’s Network, 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 (i) Tsohost’s obligation to report or respond to a Security Incident under this Section is not and will not be construed as an acknowledgement by Tsohost of any fault or liability of Tsohost with respect to the Security Incident.
Failed Security Incidents. Customer agrees that: (i) 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 FastComet's 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 unauthorized access to traffic data that does not result in access beyond IP addresses or headers) or similar incidents; and (ii) FastComet's obligation to report or respond to a Security Incident under this Section is not and will not be construed as an acknowledgment by FastComet of any fault or liability of FastComet with respect to the Security Incident.
Failed Security Incidents. Customer agrees that: i. A failed Security Incident will not be subject to the terms of this Addendum. A failed Security Incident is one that results in no unauthorized access to Customer Data or to any of Xxxx.xxx’s Network, 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 unauthorized access to traffic data that does not result in access beyond headers) or similar incidents; and ii. Xxxx.xxx’s obligation to report or respond to a Security Incident under this Section is not and will not be construed as an acknowledgement by Xxxx.xxx of any fault or liability of Xxxx.xxx with respect to the Security Incident.

Related to Failed Security Incidents

  • Security Incident Response Upon becoming aware of a Security Incident, MailChimp shall notify Customer without undue delay and shall provide timely information relating to the Security Incident as it becomes known or as is reasonably requested by Customer.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!