SECURITY BREACH MANAGEMENT AND NOTIFICATION. Conga maintains security incident management policies and procedures and shall, to the extent permitted by law, promptly notify You of any actual or reasonably suspected unauthorized disclosure of Personal Data, by Conga or its Sub-processors of which Conga becomes aware (a “Security Breach”). To the extent such Security Breach is caused by a violation of the requirements of this DPA by Conga, Conga shall make reasonable efforts to identify and remediate the cause of such Security Breach.
SECURITY BREACH MANAGEMENT AND NOTIFICATION. 7.1 If Bluecore becomes aware of a Security Breach, Bluecore will promptly notify Customer of the Security 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 Bluecore 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 Bluecore’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.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 Bluecore selects, including via email. It is Customer’s sole responsibility to ensure it maintains accurate contact information on Bluecore’s support systems at all times.
7.4 Bluecore’s notification of or response to a Security Breach under this Section 7 will not be construed as an acknowledgement by Bluecore of any fault or liability with respect to the Security Breach.
7.5 Bluecore shall implement reasonable technical and organizational Security Measures to provide a level of security appropriate to the risk in respect to the Customer Personal Data. As technical and organizational measures are subject to technological development, Bluecore is entitled to implement alternative measures provided they do not fall short of the level of data protection set out by the Data Protection Laws.
SECURITY BREACH MANAGEMENT AND NOTIFICATION. 7.1 CA will promptly notify Customer, without undue delay, after CA becomes aware of any accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or unlawful access to any Customer’s Personal Data that is transmitted, stored or otherwise Processed by CA or its Subprocessors of which CA becomes aware (“Security Breach”). CA will use reasonable efforts to identify the cause of such Security Breach and shall promptly and without undue delay: (a) investigate the Security Breach and provide Customer with information about the Security Breach, including if applicable, such information a Data Processor must provide to a Data Controller under Article 33(3) of the GDPR to the extent such information is reasonably available; and (b) take reasonable steps to mitigate the effects and to minimize any damage resulting from the Security Breach to the extent the remediation is within CA’s reasonable control. The obligations herein shall not apply to any breach that is caused by Customer or it Authorized Users. Notification will be delivered to Customer in accordance with Section 7.3 below.
7.2 CA’s obligation to report or respond to a Security Breach under this Section is not and will not be construed as an acknowledgement by CA of any fault or liability with respect to the Security Breach.
SECURITY BREACH MANAGEMENT AND NOTIFICATION. Conga maintains security incident management policies and procedures and shall, to the extent permitted by law, without undue delay, and in any event within 48 hours of becoming aware, notify Customer of any actual or reasonably suspected unauthorized access, use, modification, or disclosure of Personal Data in connection with the Processing of that Personal Data by Conga or Conga’s Sub-processors (a “Security Breach”). Such notice will include all available details required under Data Protection Laws and Regulations to enable Customer to comply with its notification obligations to regulatory authorities or to Data Subjects affected by the Security Breach. Conga shall make all reasonable efforts to identify and take all reasonable steps to remediate the cause of such Security Breach.
SECURITY BREACH MANAGEMENT AND NOTIFICATION. 7.1 ZeeMee will promptly notify College, without undue delay, after ZeeMee becomes aware of any accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or unlawful access to any College’s Personal Data that is transmitted, stored or otherwise Processed by ZeeMee or its Subprocessors of which ZeeMee becomes aware (“Security Breach”). ZeeMee will use reasonable efforts to identify the cause of such Security Breach and shall promptly and without undue delay: (a) investigate the Security Breach and provide College with information about the Security Breach, including if applicable, such information a Data Processor must provide to a Data Controller under Article 33(3) of the GDPR to the extent such information is reasonably available; and (b) take reasonable steps to mitigate the effects and to minimize any damage resulting from the Security Breach to the extent the remediation is within ZeeMee’s reasonable control. The obligations herein shall not apply to any breach that is caused by College or it Authorized Users. Notification will be delivered to College in accordance with Section 7.3 below.
7.2 ZeeMee’s obligation to report or respond to a Security Breach under this Section is not and will not be construed as an acknowledgement by ZeeMee of any fault or liability with respect to the Security Breach.
SECURITY BREACH MANAGEMENT AND NOTIFICATION. Xactly maintains security incident management policies and procedures and shall, to the extent permitted by law, notify Customer’s designated contact as set forth by Customer in the signature block below, without undue delay (and in any event within 72 hours of confirmation), of any breach of security leading to the actual or reasonably suspected unauthorized disclosure of Personal Data by Xactly or its Sub-processors of which Xactly becomes aware (a “Security Breach”). Any such notification is not an acknowledgement of fault or responsibility. To the extent such Security Breach is caused by a violation of the requirements of this DPA by Xactly, Xactly shall make reasonable efforts to identify and remediate the cause of such Security Breach. Xactly will reasonably assist the Customer to comply with its reporting obligations under applicable Data Protection Laws and Regulations in connection with the Security Breach, including by providing at least the following information to the extent available:
a) a description of the nature of the Security Breach including where possible, the categories and approximate number of Data Subjects concerned and the categories and approximate number of Personal Data records concerned;
b) the name and contact details of the data protection officer or other contact point where more information can be obtained;
c) a description of the likely consequences of the Security Breach;
d) a description of the measures taken or proposed to be taken to address the Security Breach, including, where appropriate, measures to mitigate its possible adverse effects. In case of a Security Breach and prior to making any required public statement or required notice, Customer agrees to timely provide Xactly with a draft for discussion on the content of its intended required public statements or required notices for the affected Data Subjects and/or required notices to the relevant Regulators regarding the Security Breach to the extent such public statements or notices identify Xactly by name or relate to Xactly's multi- tenant cloud software and/or Services. This draft shall be discussed in a timely fashion and in good faith between the parties. Notwithstanding the preceding sentence, Customer shall not be required to prejudice its obligations under Data Protection Laws and Regulations.
SECURITY BREACH MANAGEMENT AND NOTIFICATION. FF maintains security incident management policies and procedures and shall notify Customer without undue delay after becoming aware of the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Data, including Personal Data, transmitted, stored or otherwise Processed by FF or its Sub-processors of which FF becomes aware (a “Customer Data Incident”). FF shall make reasonable endeavours to identify the cause of such Customer Data Incident and take those steps as FF deems necessary and reasonable in order to remediate the cause of such a Customer Data Incident to the extent the remediation is within FF’s reasonable control. The obligations herein shall not apply to incidents that are caused by Customer or Customer’s Users.
SECURITY BREACH MANAGEMENT AND NOTIFICATION. 7.1 Service Provider shall, in accordance with the EU Rules, notify the Customer and/or the supervisory authority as soon as any Personal Data Breach with respect to the Personal Data occurs, but no later than 48 hours from the discovery of such a Personal Data Breach. Service Provider’s notification of or response to a Personal Data Breach under this Section 7.1 will not be construed as an acknowledgement by Service Provider of any fault or liability with respect to the Personal Data Breach.
7.2 Service Provider will use reasonable efforts to identity the cause of such Personal Data Breach and shall promptly and without undue delay: (a) investigate the Personal Data Breach and provide Customer with information about the Personal Data Breach, including if applicable, such information a Data Processor must provide to a Data Controller under Article 33(3) of the GDPR to the extent such information is reasonably available; and (b) take reasonable steps to mitigate the effects and to minimize any damage resulting from the Personal Data Breach to the extent the remediation is within Service Provider’s reasonable control The obligations herein shall not apply to any breach that is caused by Customer or authorized users. Notification will be delivered to Customer in accordance with Section 7.3 below.
7.3 Notification(s) of Personal Data Breaches, if any, will be delivered to one or more of Customer’s business, technical or administrative contacts by any means Service Provider selects, including via email. It is Customer’s sole responsibility to ensure it maintains accurate contact information on Service Provider’s support systems at all times.
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 Agency Personal Data transmitted, stored or otherwise Processed on IgnitionOne’s equipment or facilities (“Security Breach”), IgnitionOne will promptly notify 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 Agency take to address the Security Breach. 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 Agency Personal Data or to any of IgnitionOne’s equipment or facilities storing 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 Agency’s business, technical or administrative contacts by any means IgnitionOne selects, including via email. It is Agency’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. IIJ maintains security incident management policies and procedures and shall, notify Customer without undue delay after becoming aware of the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Data, including Personal Data, transmitted, stored or otherwise Processed by IIJ or its Sub-processors of which IIJ becomes aware (a “Customer Data Incident”). IIJ shall make reasonable efforts to identify the cause of such Customer Data Incident and take those steps as IIJ deems necessary and reasonable in order to remediate the cause of such a Customer Data Incident to the extent the remediation is within IIJ’s reasonable control. The obligations herein shall not apply to incidents that are caused by Customer or Customer’s Users. IIJ will not contact data subject directly, unless the controller is unable to do so itself, requests IIJ’s assistance in notifying the data subject and IIJ has the reasonable means to make a notification on the controller’s behalf.
