Breach of Data Security Sample Clauses

Breach of Data Security. Contractor, upon the discovery or notification of a breach of security that results in the unauthorized release, disclosure, or acquisition of data, or the suspicion that such a breach may have occurred, must disclose to the District as soon as possible, but no later than twenty-four (24) hours, all information necessary to fulfill the requirements of Minnesota Statute section 13.055.
AutoNDA by SimpleDocs
Breach of Data Security. In the event of any actual or threatened breach of the security of Customer Data, including breach of the firewall referenced in Section 11.7 below, Service Provider will fully cooperate with Customer to secure the Customer Data. Service Provider agrees to notify Customer in writing immediately upon becoming aware of such breach and take appropriate action to remedy the situation.
Breach of Data Security. In addition to the indemnification obligations set forth in Sections 24.1 and 24.2 above, the parties hereby agree as follows: (a) Customer shall indemnify, defend and hold harmless Service Provider, its Affiliates and its and their respective officers, directors, employees, managers, partners or agents against and from any Damages actually incurred or suffered by Service Provider arising out of or in connection with Customer’s use of Customer Data and/or Customer’s breach of its obligations under Section 11 of this Agreement, except for such Damages caused by the gross negligence or willful misconduct of Service Provider or its affiliates or its or their respective officers, directors, employees, managers, partners or agents. Such Damages may include, without limitation, (i) the actual verifiable cost, if any, of notification of all persons affected by such breach of Section 11; and (ii) the actual verifiable cost, if any, to mitigate the effect of any such breach of Section 11. (b) Service Provider shall indemnify, defend and hold harmless Customer, its Affiliates and its and their respective officers, directors, employees, managers, partners or agents against and from any Damages actually incurred or suffered by Customer arising out of or in connection with Service Provider’s use of Customer Data and/or Service Provider’s breach of its obligations under Section 11 of this Agreement, except for such Damages caused by the gross negligence or willful misconduct of Customer or its affiliates or its or their respective officers, directors, employees, managers, partners or agents. Such Damages shall include, without limitation, (i) the actual verifiable cost, if any, of notification of all persons affected by such breach of Section 11; and (ii) the actual verifiable cost, if any, to mitigate the effect of any such breach of Section 11.
Breach of Data Security. Pursuant to ***, Silver Spring shall *** Customer *** Silver Spring’s *** of any *** Silver Spring’s data security that *** of any *** Customer. In such instance, in addition to Silver Spring’s ***, or ***, Silver Spring agrees to *** any *** or *** and to *** and *** the Customer in ***.
Breach of Data Security. 8.1 The Processor must notify the Controller of personal data security breaches, operational malfunctions or suspected security breaches relating to the processing of personal data without undue delay and within 24 hours after the security breach has been discovered, unless the Processor is able to demonstrate that the data security breach is unlikely to result in a risk to the rights and freedoms of data subjects. The notification in clause 8.1 must (if relevant) contain: 8.2.1 a description of the data security breach including the categories and approximate amount of data and data subjects concerned, 8.2.2 a description of the likely consequences of the data security breach, 8.2.3 a description of the measures taken or proposed to be taken by the Controller to address the data security breach, including, where appropriate, measures to mitigate its possible adverse effects. Where and in so far as it is not possible to provide the information at the same time, the information may be provided in phases without undue further delay. 8.2 The Processor shall document any data security breaches. The documentation shall only include information necessary for the Controller to verify compliance with the applicable data protection law to the relevant supervisory authority. 8.3 The Controller is responsible for notifying the relevant supervisory authority about the data security breach.
Breach of Data Security. 9.1 The Processor must notify the Controller of personal data security breaches, operational malfunctions or suspected security breaches relating to the processing of personal data without undue delay and within 24 hours after the security breach has been discovered, unless the Processor is able to demonstrate that the data security breach is unlikely to result in a risk to the rights and freedoms of data subjects. 9.2 The notification in clause 9.1 must (if relevant) contain: 9.2.1 a description of the data security breach including the categories and approximate amount of data and data subjects concerned, 9.2.2 the name and contact details of the Processor’s data protection officer, 9.2.3 a description of the likely consequences of the data security breach, 9.2.4 a description of the measures taken or proposed to be taken by the Controller to address the data security breach, including, where appropriate, measures to mitigate its possible adverse effects. Where and in so far as it is not possible to provide the information at the same time, the information may be provided in phases without undue further delay. 9.3 The Processor shall document any data security breaches. The documentation shall only include information necessary for the Controller to verify compliance with the applicable data protection law to the relevant supervisory authority. 9.4 The Controller is responsible for notifying the relevant supervisory authority about the data security breach.
Breach of Data Security. In the event KHE discovers or is notified of a breach of security adversely impacting the security of Purdue Parties’ Data (or KHE systems containing Purdue Parties’ Data) which has been given to KHE or a KHE subcontractor (or to which either has access), from which Services are provided, if legally permissible, KHE shall notify the Purdue Parties of any of the following events as soon as practicable, and in any event within five (5) business days, after the event: a. breaches and compromises of Purdue Parties’ Data, which notice will be provided telephonically and/or by email until confirmation of receipt is received; and b. any law enforcement or administrative investigation or inquiry into suspected misuse or abuse of Purdue Parties’ Data on KHE’s systems or network.
AutoNDA by SimpleDocs

Related to Breach of Data Security

  • FALSE STATEMENTS; BREACH OF REPRESENTATIONS The Parties acknowledge that this Agreement has been negotiated, and is being executed, in reliance upon the information contained in the Application, and any supplements or amendments thereto, without which the Comptroller would not have approved this Agreement and the District would not have executed this Agreement. By signature to this Agreement, the Applicant: A. represents and warrants that all information, facts, and representations contained in the Application are true and correct to the best of its knowledge; B. agrees and acknowledges that the Application and all related attachments and schedules are included by reference in this Agreement as if fully set forth herein; and C. acknowledges that if the Applicant submitted its Application with a false statement, signs this Agreement with a false statement, or submits a report with a false statement, or it is subsequently determined that the Applicant has violated any of the representations, warranties, guarantees, certifications, or affirmations included in the Application or this Agreement, the Applicant shall have materially breached this Agreement and the Agreement shall be invalid and void except for the enforcement of the provisions required by Section 9.2 of this Agreement.

  • Breach of Confidentiality Contractor acknowledges that there can be no adequate remedy at law for any breach of Contractor’s obligations hereunder, that any such breach will likely result in irreparable harm, and therefore, that upon any breach or threatened breach of the confidentiality obligations, the Court shall be entitled to appropriate equitable relief, without the requirement of posting a bond, in addition to its other remedies at law. INDEMNIFICATION

  • Breach of Agreement Failure by the party to comply with or perform any agreement or obligation (other than an obligation to make any payment under this Agreement or delivery under Section 2(a)(i) or 2(e) or to give notice of a Termination Event or any agreement or obligation under Section 4(a)(i), 4(a)(iii) or 4(d)) to be complied with or performed by the party in accordance with this Agreement if such failure is not remedied on or before the thirtieth day after notice of such failure is given to the party;

  • Breach of Representation Any representation or warranty made or deemed made by any Borrower or any Guarantor in this Agreement, any Other Document or any related agreement or in any certificate, document or financial or other statement furnished at any time in connection herewith or therewith shall prove to have been misleading in any material respect on the date when made or deemed to have been made;

  • Breach of Contract The failure of the Contractor to comply with any of the provisions, covenants or conditions of this Contract shall be a material breach of this Contract. In such event the County may, and in addition to any other remedies available at law, in equity, or otherwise specified in this Contract: a) Terminate the Contract immediately, pursuant to Section K herein; b) Afford the Contractor written notice of the breach and ten (10) calendar days or such shorter time that may be specified in this Contract within which to cure the breach; c) Discontinue payment to the Contactor for and during the period in which the Contractor is in breach; and d) Offset against any monies billed by the Contractor but yet unpaid by the County those monies disallowed pursuant to the above.

  • Breach of Covenant The Borrower breaches any material covenant or other term or condition of this Note or the Purchase Agreement in any material respect and such breach, if subject to cure, continues for a period of thirty (30) days after the occurrence thereof.

  • Breach of Representation or Warranty Any representation or warranty made or deemed made by Borrower to Lender herein or in any of the other Loan Documents or in any statement, certificate or financial statements at any time given by Borrower pursuant to any of the Loan Documents shall be false or misleading in any material respect on the date as of which made.

  • Breach of Obligations The Parties acknowledge that a breach of any of the obligations contained herein would result in injuries. The Parties further acknowledge that the amount of the liquidated damages or the method of calculating the liquidated damages specified in this Agreement is a genuine and reasonable pre-estimate of the damages that may be suffered by the non-defaulting party in each case specified under this Agreement.

  • Breach of Covenants If the Company breaches any of the covenants set forth in this Section 4, and in addition to any other remedies available to the Buyer pursuant to this Agreement, it will be considered an event of default under Section 3.4 of the Note.

  • Breach of Security 6.1 Either party shall notify the other immediately upon becoming aware of any Breach of Security including, but not limited to an actual, potential or attempted breach, or threat to, the Security Plan. 6.2 Upon becoming aware of any of the circumstances referred to in paragraph 6.1, the Contractor shall; a) immediately take all reasonable steps necessary to; (i) remedy such breach or protect the Contractor ICT System against any such potential or attempted breach or threat; and (ii) prevent an equivalent breach in the future. Such steps shall include any action or changes reasonably required by the Authority. In the event that such action is taken in response to a breach that is determined by the Authority acting reasonably not to be covered by the obligations of the Contractor under this Contract, then the Contractor shall be entitled to refer the matter to the change control procedure in clause F3 (Variation). b) as soon as reasonably practicable provide to the Authority full details (using such reporting mechanism as may be specified by the Authority from time to time) of such actual, potential or attempted breach and of the steps taken in respect thereof.

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