13.1 . Security Incident. Vidello will (a) notify Customer of a Security Incident without undue delay after becoming aware of the Security Incident, and b) take reasonable steps to mitigate the effects and to minimise any damage resulting from the Security Incident.
13.2 Vidello Assistance. To assist Customer in relation to any personal data breach notifications Customer is required to make under the GDPR, Videllowill include in the notification such information about the Security Incident as Vidello is reasonably able to disclose to Customer, taking into account the nature of the Services, the information available to Vidello, and any restrictions on disclosing the information, such as confidentiality.
13.3 Unsuccessful Security Incidents. Customer agrees that:
13.3.1 an unsuccessful Security Incident will not be subject to this. An unsuccessful Security Incident is one that results in no unauthorised access to Customer Data or to any of Vidello 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
13.3.2 Vidello obligation to report or respond to a Security Incident under this Section is not and will not be construed as an acknowledgement by Vidello of any fault or liability of Vidello with respect to the Security Incident.
13.4 Communication. Notification(s) of Security Incidents, if any, will be delivered to one or more of Customer’s administrators by any means Vidello selects, including via email. It is Customer’s sole responsibility to ensure Customer’s administrators administrators maintain accurate contact information on the Vidello management console and secure transmission at all times.