Unsuccessful Security Incident Sample Clauses

Unsuccessful Security Incident an attempt to gain access to your Content, Smart Data or the infrastructure and networks that provide the Services (including denial of service attacks, pings, attacks on firewalls or edge servers, port scans, unsuccessful log-on attempts, packet sniffing or other unauthorised access to traffic data) that does not result in a personal data breach in relation to your Content and/or Smart Data.
Sample 1Sample 2Sample 3See All (26)
AutoNDA by SimpleDocs
Unsuccessful Security Incident. AAI has no obligation to report or respond to an Unsuccessful Security Incident, and any response by AAI shall not be construed as an acknowledgement by AAI of any fault or liability. An “Unsuccessful Security Incident” means an incident that results in no unauthorized access to Customer Data or to any of AAI’s equipment or facilities storing Customer Data, and may include, without limitation, dropped or denied network traffic, denied access attempts to systems and applications, alerts from security devices or services, pings and other broadcast attacks on firewalls or edge servers, denial of service attacks, packet sniffing (or other unauthorized access to traffic data that does not result in access to Customer Data) or similar incidents.
Sample 1Sample 2
Unsuccessful Security Incident any attempts of bypassing the Business Associate’s security system including, but not limited to, pings, password-based attacks, unsuccessful log-on attempts and other attacks on Business Associate’s firewall, so long as no such incident results in actual or reasonably suspected unauthorized access, Use or Disclosure of PHI.
Sample 1
Unsuccessful Security Incident. “Unsuccessful Security Incident” shall mean a Security Incident that does not result in unauthorized access, use, disclosure, modification or destruction of PHI (including, for example, and not for limitation, pings on Business Associate’s firewall, port scans, attempts to log onto a system or enter a database with an invalid password or user name, denial-of-service attacks that do not result in the system being taken off-line, or malware such as worms or viruses).
Sample 1
Unsuccessful Security Incident. As used herein, the term “Unsuccessful Security Incident” means a security incident (as defined under HIPAA) that does not result in: (1) the unauthorized access, use, disclosure, modification or destruction of information; or (2) material interference with system operations in a party’s information system, including, without limitation, activity such as ping and other broadcast attacks on that party’s firewall, port scans, unsuccessful log-on attempts, denial of service and/or any combination of the foregoing, so long as no such incident results in unauthorized access, use or disclosure of electronic protected health information.
Sample 1

Related to Unsuccessful 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.

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

  • Unsuccessful E bidders deposit will be refunded to the same account from which the deposit transfers within 3 working days from the auction date.

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

  • Data Incidents Merchant must report all instances of a Data Incident (as defined in the American Express Merchant Operating Guide) immediately to ISO after discovery of the incident. Merchant must ensure data quality and that Transaction Data and customer information is processed promptly, accurately, and completely, and complies with the American Express Technical Specifications. THE FOLLOWING SERVICES ARE PROVIDED BY ISO ONLY. Bank shall not have any obligation or liability of any nature in connection with such services. PART THREE

  • Security Breach In the event that Seller discovers or is notified of a breach, potential breach of security, or security incident at Seller's Facility or of Seller's systems, Seller shall immediately (i) notify Company of such potential, suspected or actual security breach, whether or not such breach has compromised any of Company's confidential information; (ii) investigate and promptly remediate the effects of the breach, whether or not the breach was caused by Seller; (iii) cooperate with Company with respect to any such breach or unauthorized access or use; (iv) comply with all applicable privacy and data protection laws governing Company's or any other individual's or entity's data; and (v) to the extent such breach was caused by Seller, provide Company with reasonable assurances satisfactory to Company that such breach, potential breach, or security incident shall not recur. Seller shall provide documentation to Company evidencing the length and impact of the breach. Any remediation of any such breach will be at Seller's sole expense.

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