Reporting Suspected Security Incidents Sample Clauses

Reporting Suspected Security Incidents. CONTRACTOR shall notify COUNTY, by telephone and e-mail or fax, within twenty-four (24) hours after discovering any suspected security incident, intrusion, loss or unauthorized use or disclosure of PSEI or PHI in violation of this Agreement or any applicable local, state or federal laws, regulations or standards.
AutoNDA by SimpleDocs
Reporting Suspected Security Incidents. CONTRACTOR shall notify COUNTY, by telephone and e-mail or fax, within twenty-four (24) hours after discovering any suspected security incident, intrusion, loss or unauthorized use or disclosure of Identifiable Information in violation of this Agreement or any applicable local, state or federal laws, regulations or standards. For purposes of this Agreement, a breach of, or security incident involving, Identifiable Information shall be treated as discovered by CONTRACTOR as of the first (1st) day on which such breach is known, or by exercising reasonable diligence would have been known, to CONTRACTOR, or any employee or agent thereof, other than the person committing the suspected breach.

Related to Reporting Suspected Security Incidents

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

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

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

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

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