Other incidents Sample Clauses

Other incidents. NTT will notify Client promptly if NTT becomes aware of:
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Other incidents. Security Incidents do not include any incident that results in no unauthorized access to Customer Data (as defined in the MSA) or to Khoros’s Applications, websites, or cloud servers involving pings and other broadcast attacks on firewalls or edge servers, phishing (even if successful), port scans, unsuccessful log-on attempts, denial of service attacks, packet sniffing (or other unauthorized access to traffic data that does not result in access beyond headers), or similar incidents not caused by any fault of Khoros. These incidents shall not be considered a breach of this DPA, the MSA, or SLA. Nonetheless, to the extent that a successful phishing attack leads to the compromise of Personal Data, Khoros will work with Customer to fulfil any ADPL reporting requirements.
Sample 1Sample 2
Other incidents. Vendor will notify NTT promptly if Vendor becomes aware of:
Sample 1Sample 2
Other incidents. The following matters or events are classified as Other Incidents:
Sample 1Sample 2
Other incidents. Verizon or Customer can create Other Incident tickets for service related incidents on the Serviced Devices that are not related to an Availability or Health incident. They can be logged on a 24x7 basis.
Sample 1
Other incidents. Lost or stolen patient-identifiable information (records, prescriptions). It’s not just accidents and hazards that should be reported. Errors or oversights in practice should also be reported to provide a clear record of what has occurred and how it can be prevented in the future. The incident reporting form should be completed as soon as possible after the event. An incident report should be an objective account of what happened. Ideally the person directly involved in the incident should complete the form, but any pharmacy staff member can do it. A Care Trust incident report form must be completed in addition to any internal reporting procedures within the pharmacy/company. Incident reporting and monitoring should be a supportive process and is not about “blame”.
Sample 1
Other incidents. 5) Maintenance (Scheduled and Urgent) The standard time for scheduled operations (maintenance) is from 21.00 to 06.00 hours on Saturday and Sunday and from 00.00 to 06.00 from Monday to Friday in Estonian time. Table 1. Agreed interruptions and notifications № Position Indicators Notification of the Customer Additional terms 1 Scheduled operations performance The total duration of breaks is not more than 6 hours per year. The intervals between the breaks - not less than 90 calendar days At least 48 hours before the break Time of operations is agreed with the Customer 2 Urgent operations performance The break time is equal to the actual time of work At least 12 hours before the break The estimated duration of operations is reported to the Customer The CONTRACTOR shall inform the CUSTOMER about all the interruptions in the services provision with indication of the time when the service provision will be interrupted, as well as the time of service restoration:
Sample 1
AutoNDA by SimpleDocs

Related to Other incidents

  • 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

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

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

  • Significant Incidents In addition to notifying the appropriate authorities, Grantee will submit notice to the SUD email box, XxxxxxxxxXxxxx.Xxxxxxxxx@xxxx.xxxxx.xx.xx and Substance Use Xxxxxxxx@xxxx.xxxxx.xx.xx significant incidents involving substantial disruption of Grantee’s program operation or affecting or potentially affecting the health, safety or welfare of the System Agency funded clients or participants within three (3) calendar days of discovery.

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

  • Technical or Contractual Problems Contractor shall meet with the Department's personnel, or designated representatives, to resolve technical or contractual problems occurring during the contract term or to discuss the progress made by Contractor and the Department in the performance of their respective obligations, at no additional cost to the Department. The Department may request the meetings as problems arise and will be coordinated by the Department. The Department shall provide Contractor a minimum of three full working days notice of meeting date, time, and location. Face-to-face meetings are desired; however, at Contractor's option and expense, a conference call meeting may be substituted. Contractor’s consistent failure to participate in problem resolution meetings, Contractor missing or rescheduling two consecutive meetings, or Contractor’s failure to make a good faith effort to resolve problems may result in termination of the contract.

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

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