Notification of a Security Incident Sample Clauses

Notification of a Security Incident. Contractor shall report, in writing, to the CSU any use or disclosure of CSU Protected Data not authorized by this Agreement or authorized in writing by the CSU, including any reasonable belief that an unauthorized individual has accessed CSU Protected Data. This report shall be made to the CSU’s primary contact and its designated information security officer. It shall include details relating to any known or suspected security breach of Contractor’s system or facilities which contain CSU Protected Data or any other breach of Protected Data relating to this Agreement. This report shall be made not later than within twenty-four (24) hours after discovery, if the information was, or is reasonably believed to have been, acquired by an unauthorized person.
Sample 1Sample 2
AutoNDA by SimpleDocs
Notification of a Security Incident. Upon becoming aware of a Security Incident, Company shall notify Sawgrass without undue delay and shall provide timely information relating to the Security Incident as it becomes known or as is reasonably requested by Company.
Sample 1
Notification of a Security Incident. Contractor shall report, in writing, to the CSU any use or disclosure of CSU Protected Data not authorized by this Agreement or authorized in writing by the CSU. This report shall be made to the CSU’s primary contact and its designated information security officer. It shall include details relating to any known security breach of Contractor’s system or facilities leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, CSU Protected Data transmitted, stored or otherwise processed, to the extent such data is within the control or possession of Contractor or a third party operating on Contractor’s behalf (“Security Breach”). This report shall be made not later than within twenty-four (24) hours after discovery of any Security Breach.
Sample 1
Notification of a Security Incident. For purposes of the Master Agreement a “Security Incident” shall be any event where (a) a person or device has gained unauthorized access to, or may imminently gain unauthorized access to, End User Data; or (b) any person or device has gained unauthorized access to the Data Center and such unauthorized access may, in OPAY’s reasonable judgment, materially affect End User Data. OPAY shall, within a reasonable period of time (considering the circumstances, but no later than twenty- four (24) hours) after becoming aware that (i) a Security Incident involving unauthorized access to End User Data has occurred; or (ii) OPAY has reason to believe any other Security Incident has occurred, notify Customer as provided in Section 14.9 (“Notice”) of the Master Agreement of such Security Incident, specifying the extent to which End User Data was compromised or disclosed. In the event Customer becomes aware of a Security Incident, Customer shall, within a reasonable period of time (considering the circumstances, but no later than twenty-four (24) hours) after becoming aware of such Security Incident notify OPAY as provided in Section 14.9 (“Notice”) of the Master Agreement of such Security Incident, specifying the extent to which End User Data was compromised or disclosed.
Sample 1
Notification of a Security Incident. Contractor shall report, in writing, to the CSU any use or disclosure of CSU Protected Data not authorized by this Agreement or authorized in writing by the CSU, including any reasonable belief that an unauthorized individual has accessed CSU Protected Data. This report shall be mation security officer. It shall facilities which contain CSU Protected Data or any other breach of Protected Data relating to this Agreement. This report shall be made not later than within twenty-four (24) hours after discovery, if the information was, or is reasonably believed to have been, acquired by an unauthorized person.
Sample 1

Related to Notification of a Security Incident

  • 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 “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.

  • Reporting Security Incidents The Business Associate will report to the County any Incident of which the Business Associate becomes aware that is:

  • 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.

  • Reporting Unsuccessful Security Incidents Business Associate shall provide Covered Entity upon written request a Report that: (a) identifies the categories of Unsuccessful Security Incidents; (b) indicates whether Business Associate believes its current defensive security measures are adequate to address all Unsuccessful Security Incidents, given the scope and nature of such attempts; and (c) if the security measures are not adequate, the measures Business Associate will implement to address the security inadequacies.

  • 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.

  • 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.

  • Sale of Note; Change of Loan Servicer; Notice of Grievance The Note or a partial interest in the Note (together with this Security Instrument) can be sold one or more times without prior notice to Borrower. A sale might result in a change in the entity (known as the “Loan Servicer”) that collects Periodic Payments due under the Note and this Security Instrument and performs other mortgage loan servicing obligations under the Note, this Security Instrument, and Applicable Law. There also might be one or more changes of the Loan Servicer unrelated to a sale of the Note. If there is a change of the Loan Servicer, Borrower will be given written notice of the change which will state the name and address of the new Loan Servicer, the address to which payments should be made and any other information RESPA requires in connection with a notice of transfer of servicing. If the Note is sold and thereafter the Loan is serviced by a Loan Servicer other than the purchaser of the Note, the mortgage loan servicing obligations to Borrower will remain with the Loan Servicer or be transferred to a successor Loan Servicer and are not assumed by the Note purchaser unless otherwise provided by the Note purchaser. Neither Borrower nor Lender may commence, join, or be joined to any judicial action (as either an individual litigant or the member of a class) that arises from the other party’s actions pursuant to this Security Instrument or that alleges that the other party has breached any provision of, or any duty owed by reason of, this Security Instrument, until such Borrower or Lender has notified the other party (with such notice given in compliance with the requirements of Section 15) of such alleged breach and afforded the other party hereto a reasonable period after the giving of such notice to take corrective action. If Applicable Law provides a time period which must elapse before certain action can be taken, that time period will be deemed to be reasonable for purposes of this paragraph. The notice of acceleration and opportunity to cure given to Borrower pursuant to Section 22 and the notice of acceleration given to Borrower pursuant to Section 18 shall be deemed to satisfy the notice and opportunity to take corrective action provisions of this Section 20.

  • Notification of Incidents If Contractor becomes aware of or has reasonable suspicion of a privacy incident or security incident regarding any State data, Contractor must report such incident to the State and the State Chief Information Security Officer as soon as possible, but no later than twenty-four (24) hours after such incident. The decision to notify the affected data subjects and the form of such notice following report of a privacy incident or security incident are the responsibility of the State. Notwithstanding anything to the contrary in this Contract, Contractor will indemnify, hold harmless and defend the State and its officers, and employees for and against any claims, damages, costs and expenses related to any privacy incident or security incident involving any State data. For purposes of clarification, the foregoing sentence shall in no way limit or diminish Contractor’s obligation(s) to indemnify, save, hold harmless, or defend the State under any other term of this Contract. Contractor will reasonably mitigate any harmful effects resulting from any privacy incident or security incident involving any State data.

Time is Money Join Law Insider Premium to draft better contracts faster.