Management of a security incident Sample Clauses

Management of a security incident. Either party will report instances of a data breach in relation to this agreement to the other party’s contact within 12 hours of the breach being discovered. Such notification will specify: the nature of the personal data breach or suspected breach; the date and time of occurrence; the extent of the Data and Data Subjects affected or potentially affected, the likely consequences of any breach (in the case of a suspected breach, should it have occurred) for Data Subjects affected by it and any measures taken or proposed to be taken by that Party to contain the breach or suspected breach; and any other information that the other Party shall require in order to discharge its responsibilities under Data Protection Law in relation to such breach or suspected breach The parties shall co-operate fully in the management of any breach of this Data Sharing Agreement, including investigation, containment, recovery, notification and mitigation activities. No breach shall be notified to any third party, including a student, their representative, the Police Service or the Information Commissioner, without first notifying the other party.
AutoNDA by SimpleDocs
Management of a security incident. (a) Each Party shall provide the other Parties reasonable assistance in complying with all applicable requirements of the Data Protection Laws applicable to Personal Data Breaches. In particular, each Party (where relevant) shall: (i) promptly notify any relevant Party to this Agreement as soon as it becomes aware of a Personal Data Breach or a suspected Personal Data Breach which relates to Personal Data shared by such other Party under this Agreement; (ii) carry out an investigation into the Personal Data Breach or a suspected Personal Data Breach, its extent and any parties responsible for the Personal Data Breach. Such investigation should consider if the processes outlined in this Agreement have been compromised or whether this Agreement has been breached. The Party responsible for the investigation (being the Party who has experienced a Personal Data Breach) shall provide reasonable details of the Personal Data Breach to any other relevant Party notified under clause 7.3(a)(i); and (iii) where in receipt of notification in respect of an actual or suspected Personal Data Breach, provide reasonable assistance to the notifying Party in dealing with such actual / suspected Personal Data Breach in an expeditious and compliant manner. (b) If it is believed a crime has been committed, it will be reported to the relevant division who will investigate and submit a report to the Procurator Fiscal.
Management of a security incident. In the event of any potential data breaches or significant security risks affecting the shared data, the Scottish Government shall inform Clackmannanshire Council within 48 hours, and, without prejudice to any other right or remedy, Clackmannanshire Council may terminate this agreement with immediate effect by giving notice to the Scottish Government in writing. The Scottish Government operational contact will also report the security incident to the Scottish Government Data Protection and Information Asset team (DPIA) immediately after becoming aware of the incident. If the breach is a reportable breach, the Scottish Government will also notify the ICO within 72 hours of becoming aware.
Management of a security incident. Data Loss

Related to Management of a security incident

  • Security Incident “Security Incident” means the attempted or successful unauthorized access, use, disclosure, modification, or destruction of information or interference with system operations in an information system.

  • Security Incidents 11.1 Includes identification, managing and agreed reporting procedures for actual or suspected security breaches.

  • Security Incident Notification The Transfer Agent shall promptly notify the Trust but in no event later than 72 hours following discovery of any Security Incident(s). Such notification shall include the extent and nature of such intrusion, disclosure, or unauthorized access, the identity of the compromised Customer Confidential Information (to the extent it can be ascertained), how the Transfer Agent was affected by the Security Incident, and its response to such Security Incident. The Transfer Agent shall use continuous and diligent efforts to remedy the cause and the effects of such Security Incident in an expeditious manner and deliver to the Trust a root cause analysis and future incident Mitigation plan with regard to any such incident. The Transfer Agent shall reasonably cooperate with the Trust’s investigation and response to each Security Incident. If the Trust determines in its sole discretion that it may need or be required to notify any individual(s) as a result of a Security Incident, the Trust shall have the right to control all such notifications and the Transfer Agent shall bear all direct costs associated with the notification, to the extent the notification and corresponding actions are required by U.S. law, and subject to the limitation of liability set forth in the Agreement. Without limiting the foregoing, unless otherwise required by U.S. law, no such notifications shall be made by the Transfer Agent without the Trust’s prior written consent and the Trust shall, together with the Transfer Agent, determine the content and delivery of all such notifications. For the avoidance of doubt, the Transfer Agent shall be solely responsible for all costs and expenses, subject to the limitations of liability under the Agreement that the Trust and/or the Transfer Agent may incur to the extent that they are attributable to or arise from the Transfer Agent’s breach of its confidentiality obligations under the Agreement.

  • Security Incident Response Upon becoming aware of a Security Incident, MailChimp shall notify Customer without undue delay and shall provide timely information relating to the Security Incident as it becomes known or as is reasonably requested by Customer.

  • Breaches and Security Incidents During the term of the Agreement, CONTRACTOR 27 agrees to implement reasonable systems for the discovery of any Breach of unsecured DHCS PI and PII 28 or security incident. CONTRACTOR agrees to give notification of any beach of unsecured DHCS PI 29 and PII or security incident in accordance with subparagraph F, of the Business Associate Contract, 30 Exhibit B to the Agreement.

  • Security Incident Reporting A security incident occurs when CDA information assets are or reasonably believed to have been accessed, modified, destroyed, or disclosed without proper authorization, or are lost, or stolen. Subrecipient must comply with CDA’s security incident reporting procedures located at xxxxx://xxx.xxxxx.xx.xxx/ProgramsProviders/#Resources.

  • Secured Party Control Bank, Secured Party, Servicer and Company each agree that Bank will comply with instructions given to Bank by Secured Party directing disposition of funds in the Collateral Accounts (“Disposition Instructions”) without further consent by Company or Servicer. Except as otherwise required by law, Bank will not agree with any third party to comply with instructions for disposition of funds in the Collateral Accounts originated by such third party.

  • Absence of Defaults and Conflicts Resulting from Transaction The execution, delivery and performance of this Agreement, and the sale of the Securities, will not result in a breach or violation of any of the terms and provisions of, or constitute a default or a Debt Repayment Triggering Event (as defined below) under, or result in the imposition of any lien, charge or encumbrance upon any property or assets of the Company or any of its subsidiaries pursuant to, (A) the charter, by-laws or similar organizational documents of the Company or any of its subsidiaries, (B) any statute, rule, regulation or order of any governmental agency or body or any court, domestic or foreign, having jurisdiction over the Company or any of its subsidiaries or any of their properties, or (C) any agreement or instrument to which the Company or any of its subsidiaries is a party or by which the Company or any of its subsidiaries is bound or to which any of the properties of the Company or any of its subsidiaries is subject except, in the case of clauses (B) and (C) above, any breach, violation, default, lien, charge or encumbrance that would not, individually or in the aggregate, reasonably be expected to have a Material Adverse Effect; a “Debt Repayment Triggering Event” means any event or condition that gives, or with the giving of notice or lapse of time would give, the holder of any note, debenture, or other evidence of indebtedness (or any person acting on such holder’s behalf) the right to require the repurchase, redemption or repayment of all or a portion of such indebtedness by the Company or any of its subsidiaries.

  • Company Acknowledgment The Company will, at the time of the exercise of the Warrant, upon the request of the Holder hereof acknowledge in writing its continuing obligation to afford to such Holder any rights to which such Holder shall continue to be entitled after such exercise in accordance with the provisions of this Warrant. If the Holder shall fail to make any such request, such failure shall not affect the continuing obligation of the Company to afford to such Holder any such rights.

  • Error Incident An Error Incident is a single or series of NAV Errors that results from the same act, omission, or use of incorrect data. NAV Errors will be corrected as follows: · If an NAV Error is less than ½ of 1% of NAV and results in a Net Benefit, the fund will retain the benefit. · If an NAV Error is less than ½ of 1% of NAV and results in a Net Loss, the Net Loss will be paid to the fund by the party responsible for causing the NAV Error. · In the case of a Material NAV Error, shareholder transactions/accounts will be corrected/ reprocessed at the corrected (restated) NAV, subject to a $10 per-account correction minimum threshold; any residual Net Benefit after correction of shareholder accounts will be retained by the fund and any residual Net Loss (resulting from uncorrected accounts below the $10 minimum threshold) will be paid to the fund by the party responsible for causing the error. If an NAV error is not caused by either the fund accounting agent or TRP, both TRP and the fund accounting agent will provide all reasonable assistance to the fund in its attempt to recover all costs from the responsible third party. · Notwithstanding any contractual provisions to the contrary, to the extent a NAV Error was caused by the actions or omissions of the fund’s accounting agent, any Net Loss or residual Net Loss equal to $5,000 or less that results from the same Error Incident will be paid by the accounting agent. TRP will be responsible for summarizing and reporting to the funds’ Audit Committee or Trust Company’s Board (or designated committee), as applicable, all NAV Errors related to the funds/trusts in conjunction with other relevant error statistics on a quarterly basis. The report will include corrected NAV Errors as well as the aggregate effect of any uncorrected NAV Errors. The report will also include information about shareholder accounts that were corrected in the discretion of TRP in the case of an NAV Error that is not a Material NAV Error. The funds’ Audit Committee and the Trust Company’s Board shall have the authority to adjust these procedures with respect to the funds and trusts, respectively, to the extent necessary or desirable to address NAV Errors by providing notice thereof to TRP and the fund’s accounting agent.

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