Common use of SECURITY BREACH MANAGEMENT AND NOTIFICATION Clause in Contracts

SECURITY BREACH MANAGEMENT AND NOTIFICATION. 7.1 If IgnitionOne becomes aware of any accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to any Customer Personal Data transmitted, stored or otherwise Processed on IgnitionOne’s equipment or facilities (“Security Breach”), IgnitionOne will promptly notify Customer of the Security Breach and describe, to the extent possible, details of the Security Breach, including steps taken to mitigate the potential risks and steps IgnitionOne recommends Customer take to address the Security Breach. Customer agrees that an unsuccessful Security Breach attempt will not be subject to this Section. An unsuccessful Security Breach attempt is one that results in no unauthorized access to Customer Personal Data or to any of IgnitionOne’s equipment or facilities storing Customer 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, or similar incidents. 7.2 Notification(s) of Security Breaches, if any, will be delivered to one or more of Customer’s business, technical or administrative contacts by any means IgnitionOne selects, including via email. It is Customer’s sole responsibility to ensure it maintains accurate contact information on IgnitionOne’s support systems at all times. 7.3 IgnitionOne’s notification of or response to a Security Breach under this Section 7 will not be construed as an acknowledgement by IgnitionOne of any fault or liability with respect to the Security Breach.

SECURITY BREACH MANAGEMENT AND NOTIFICATION. 7.1 If IgnitionOne becomes aware of any accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to any Customer Personal Data transmitted, stored or otherwise Processed on IgnitionOne’s equipment or facilities (“Security Breach”), IgnitionOne will promptly notify Customer of the Security Breach and Breach. Notifications made pursuant to this section will describe, to the extent possible, details of the Security Breach, including steps taken to mitigate the potential risks and steps IgnitionOne recommends Customer take to address the Security Breach. . 7.2 Customer agrees that an unsuccessful Security Breach attempt will not be subject to this Section. An unsuccessful Security Breach attempt is one that results in no unauthorized access to Customer Personal Data or to any of IgnitionOne’s equipment or facilities storing Customer 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, or similar incidents. 7.2 7.3 Notification(s) of Security Breaches, if any, will be delivered to one or more of Customer’s business, technical or administrative contacts by any means IgnitionOne selects, including via email. It is Customer’s sole responsibility to ensure it maintains accurate contact information on IgnitionOne’s support systems at all times. 7.3 IgnitionOne’s notification of or response to a Security Breach under this Section 7 will not be construed as an acknowledgement by IgnitionOne of any fault or liability with respect to the Security Breach.via

SECURITY BREACH MANAGEMENT AND NOTIFICATION. 7.1 If IgnitionOne becomes aware of any accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to any Customer Agency Personal Data transmitted, stored or otherwise Processed on IgnitionOne’s equipment or facilities (“Security Breach”), IgnitionOne will promptly notify Customer Agency of the Security Breach and describe, to the extent possible, details of the Security Breach, including steps taken to mitigate the potential risks and steps IgnitionOne recommends Customer Agency take to address the Security Breach. Customer Agency agrees that an unsuccessful Security Breach attempt will not be subject to this Section. An unsuccessful Security Breach attempt is one that results in no unauthorized access to Customer Agency Personal Data or to any of IgnitionOne’s equipment or facilities storing Customer Agency 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, or similar incidents. 7.2 Notification(s) of Security Breaches, if any, will be delivered to one or more of CustomerAgency’s business, technical or administrative contacts by any means IgnitionOne selects, including via email. It is CustomerAgency’s sole responsibility to ensure it maintains accurate contact information on IgnitionOne’s support systems at all times. 7.3 IgnitionOne’s notification of or response to a Security Breach under this Section 7 will not be construed as an acknowledgement by IgnitionOne of any fault or liability with respect to the Security Breach.

SECURITY BREACH MANAGEMENT AND NOTIFICATION. 7.1 If IgnitionOne becomes aware of any accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to any Customer Personal Data transmitted, stored or otherwise Processed on IgnitionOne’s equipment or facilities (“Security Breach”), IgnitionOne will promptly notify Customer of the Security Breach and describe, to the extent possible, details of the Security Breach, including steps taken to mitigate the potential risks and steps IgnitionOne recommends Customer take to address the Security Breach. Customer agrees that an unsuccessful Security Breach attempt will not be subject to this Section. An unsuccessful Security Breach attempt is one that results in no unauthorized access to Customer Personal Data or to any of IgnitionOne’s equipment or facilities storing Customer 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, or similar incidents. 7.2 . Notification(s) of Security Breaches, if any, will be delivered to one or more of Customer’s business, technical or administrative contacts by any means IgnitionOne selects, including via email. It is Customer’s sole responsibility to ensure it maintains accurate contact information on IgnitionOne’s support systems at all times. 7.3 . IgnitionOne’s notification of or response to a Security Breach under this Section 7 will not be construed as an acknowledgement by IgnitionOne of any fault or liability with respect to the Security Breach.