Common use of Unsuccessful Security Incidents Clause in Contracts

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 an unsuccessful Security Incident will not be subject to this Clause 3.9Section 9. An unsuccessful security incident Security Incident is one that results in no unauthorized unauthorised access to Personal Customer Data or to any of Lative4me’s equipment or facilities storing Personal Customer Data, and may include, without limitation, pings and other broadcast attacks on firewalls or edge servers, port scans, unsuccessful log-on access attempts, denial of service attacks, packet sniffing (or other unauthorized unauthorised access to traffic data that does not result in access beyond headers) or similar incidents.

Unsuccessful Security Incidents. Customer agrees that an unsuccessful Security Incident will not be subject to this Clause 3.9Section 4. An unsuccessful security incident Security Incident is one that results in no unauthorized access to Personal Customer Data or to any of LativeNVIDIA’s equipment or facilities storing Personal Customer Data, and may 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.