Reporting of Violations and Security Incidents Sample Clauses

Reporting of Violations and Security Incidents. (i) Upon becoming aware of a use or disclosure of PHI in violation of this Agreement, including any Breach or suspected Breach of Unsecured PHI, Licensed-Only Agent shall immediately report such use or disclosure to Company.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Reporting of Violations and Security Incidents. Within five (5) days of obtaining knowledge thereof, Business Associate will promptly report to Covered Entity any impermissible use or disclosure under Privacy Laws that compromises the security or privacy of the PHI (“Breach”) and any attempted or successful unauthorized access, use, disclosure, modification, or destruction of information or interference with system operations in an information system that does not compromise the security or privacy of the PHI (“Security Incidents”). Notice is hereby deemed provided, and no further notice will be given, with respect to routine unsuccessful attempts at unauthorized access to ePHI such as pings and other broadcast attacks on firewalls, denial of service attacks, failed login attempts, and port scans. Business Associate will identify and respond internally to suspected or known Security Incidents, and will mitigate, to the extent practicable, their harmful effects, document their outcomes, and provide such documentation to Covered Entity upon request. The Parties will meet and confer in good faith before notifying affected individuals and/or commencing any legal action regarding any suspected or actual Breach or Security Incident and/or breach of this BAA, so long as doing so will not constitute a violation of Privacy Laws, and shall comply with applicable Privacy Laws regarding the need for and nature of any notification. If the Parties are unable to agree during their meet and confer, Business Associate will not be responsible for any notification obligations under Privacy Laws, and specifically, without limitation, obligations under section 13402 of HITECH.
Sample 1
Reporting of Violations and Security Incidents. (i) Upon becoming aware of a use or disclosure of PHI in violation of this Agreement, including any Breach or suspected Breach of Unsecured PHI, Associate shall immediately report such use or disclosure to Company.
Sample 1
Reporting of Violations and Security Incidents. Business Associate will promptly report to Covered Entity any impermissible use or disclosure under Privacy Laws that compromises the security or privacy of the PHI (“Breach”) and any attempted or successful unauthorized access, use, disclosure, modification, or destruction of information or interference with system operations in an information system that does not compromise the security or privacy of the PHI (“Security Incidents”). Notice is hereby deemed provided, and no further notice will be given, with respect to routine unsuccessful attempts at unauthorized access to ePHI such as pings and other broadcast attacks on firewalls, denial of service attacks, failed login attempts, and port scans. Business Associate will identify and respond internally to suspected or known Security Incidents, and will mitigate, to the extent practicable, their harmful effects, document their outcomes, and provide such documentation to Covered Entity upon request. The Parties will meet and confer in good faith before notifying affected individuals and/or commencing any legal action regarding any suspected or actual Breach or Security Incident and/or breach of this BAA, and shall comply with applicable Privacy Laws regarding the need for and nature of any notification. If the Parties are unable to agree during their meet and confer, Business Associate will not be responsible for any notification obligations under Privacy Laws, and specifically, without limitation, obligations under section 13402 of HITECH.
Sample 1

Related to Reporting of Violations and Security Incidents

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

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

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

  • Reporting Incidents The Interconnection Parties shall report to each other in writing as soon as practical all accidents or occurrences resulting in injuries to any person, including death, and any property damage arising out of the Interconnection Service Agreement.

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

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

  • REPORTING OF ACCIDENTS The Contractor shall report to the Engineer details of any accident as soon as possible after its occurrence. In the case of any fatality or serious accident, the Contractor shall, in addition, notify the Engineer immediately by the quickest available means. The Contractor shall also notify the relevant authority whenever the Laws of Kenya require such a report.

  • Absence of Violations, Defaults and Conflicts Neither the Company nor any of its subsidiaries is (A) in violation of its charter, by-laws or similar organizational document, (B) in default in the performance or observance of any obligation, agreement, covenant or condition contained in any contract, indenture, mortgage, deed of trust, loan or credit agreement, note, lease or other agreement or instrument to which the Company or any of its subsidiaries is a party or by which it or any of them may be bound or to which any of the properties or assets of the Company or any subsidiary is subject (collectively, “Agreements and Instruments”), except for such defaults that would not reasonably be expected to, singly or in the aggregate, result in a Material Adverse Effect, or (C) in violation of any law, statute, rule, regulation, judgment, order, writ or decree of any arbitrator, court, governmental body, regulatory body, administrative agency or other authority, body or agency having jurisdiction over the Company or any of its subsidiaries or any of their respective properties, assets or operations (each, a “Governmental Entity”), except for such violations that would not reasonably be expected to, singly or in the aggregate, result in a Material Adverse Effect. The execution, delivery and performance of this Agreement and the consummation of the transactions contemplated herein and in the Registration Statement, the General Disclosure Package and the Prospectus (including the issuance and sale of the Securities and the use of the proceeds from the sale of the Securities as described therein under the caption “Use of Proceeds”) and compliance by the Company with its obligations hereunder have been duly authorized by all necessary corporate action and do not and will not, whether with or without the giving of notice or passage of time or both, conflict with or constitute a breach of, or default or Repayment Event (as defined below) under, or result in the creation or imposition of any lien, charge or encumbrance upon any properties or assets of the Company or any subsidiary pursuant to, the Agreements and Instruments (except for such conflicts, breaches, defaults or Repayment Events or liens, charges or encumbrances that would not reasonably be expected to, singly or in the aggregate, result in a Material Adverse Effect), nor will such action result in any violation of (x) the provisions of the charter, by-laws or similar organizational document of the Company or any of its subsidiaries or (y) any law, statute, rule, regulation, judgment, order, writ or decree of any Governmental Entity, except with respect to clause (y), such violations as would not reasonably be expected to, singly or in the aggregate, result in a Material Adverse Effect. As used herein, a “Repayment Event” means any event or condition which gives 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.

  • Security Violations and Accounts Updates Grantee will adhere to the Confidentiality Article requirements and HHS Data Usage Agreement of this contract and immediately contact System Agency if a security violation is detected, or if Grantee has any reason to suspect that the security or integrity of the CMBHS data has been or may be compromised in any way.

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