Successful Security Incident Sample Clauses

Successful Security Incident. Reporting for any Security Incident involving the successful unauthorized access, use, disclosure, modification or destruction of Electronic Protected Information (collectively, a “Successful Security Incident”) shall be provided to the Plan pursuant to the standard reporting protocols of DBI (as determined by DBI), provided that: (i) the reports shall at a minimum include the date of the incident, the parties involved (if known, including the names of Individuals affected), a description of the Successful Security Incident, a description of the Electronic Protected Information involved in the incident, and any action taken to mitigate the impact of the Successful Security Incident and/or prevent its future recurrence; and (ii) the reports shall satisfy the minimum requirements for Security Incident reporting that may be required from time to time by the Secretary. In addition, Successful Security Incidents shall be reported to the Plan as soon as administratively practicable after the occurrence of the incident taking into account the severity and nature of the incident. Notwithstanding the foregoing, the Plan may request details about one or more Successful Security Incidents, and DBI shall have thirty (30) days thereafter to furnish the requested information.
Sample 1Sample 2See All (4)
AutoNDA by SimpleDocs
Successful Security Incident. “Successful Security Incident” shall mean a Security Incident that results in the unauthorized access, use, disclosure, modification or destruction of PHI.
Sample 1
Successful Security Incident. Reporting for any Security Incident involving the successful unauthorized access, use, disclosure, modification or destruction of Electronic Protected Information (collectively, a “Successful Security Incident”) shall be provided to the Plan pursuant to the standard reporting protocols of DBI (as determined by DBI); provided, that
Sample 1

Related to Successful Security Incident

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

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

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

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

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

  • Data Incidents If Apple becomes aware that Personal Data has been altered, deleted, or lost as a result of any unauthorized access to the Service (a “Data Incident”), Apple will notify Institution without undue delay if required by law, and Apple will take reasonable steps to minimize harm and secure the data. Notification of, or response to, a Data Incident by Apple will not be construed as an acknowledgment by Apple of any responsibility or liability with respect to a Data Incident. Institution is responsible for complying with applicable incident notification laws and fulfilling any third-party obligations related to Data Incident(s). Apple will not access the contents of Personal Data in order to identify information subject to any specific legal requirements.

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