Security Breaches and Incidents Sample Clauses

Security Breaches and Incidents. A security breach means the negligent or intentional transgression or failure to comply with physical security measures. Examples but not limited thereto- fence tampering/ penetration, unauthorised access, discharge of a firearm, activation of alarm, non-compliance to security systems and systems technology, tampering with systems, accidents, injuries, damage to equipment, non- compliance with rules, procedures and directives, non- conforming behaviour;  Report without delay (OB…..)  Alert authorities/ Eskom management
AutoNDA by SimpleDocs
Security Breaches and Incidents. ‌ 19.1 The Data Processor shall comply with its obligations as listed in Article 108 (1) and (2) DPA 2018 :- (1) If a controller becomes aware of a serious personal data breach in relation to personal data for which the controller is responsible, the controller must notify the Commissioner of the breach without undue delay. (2) Where the notification to the Commissioner is not made within 72 hours, the notification must be accompanied by reasons for the delay.” 19.2 For the purposes of this section, a personal data breach is serious if the breach seriously interferes with the rights and freedoms of a data subject, as defined in Article 108 (7) DPA 2018. 19.3 In compliance with Article 108 (5) DPA 2018 “If a processor becomes aware of a personal data breach (in relation to data processed by the processor), the processor must notify the controller without undue delay.” 19.3.1 the Data Processor agrees to notify the Data Controller within 72 hours of becoming aware of any incident or breach of its security obligations in accordance the DPA 2018, where; 19.3.2 the incident or breach might result in the unauthorised access, unauthorised disclosure, misuse, loss, theft, or accidental or unlawful destruction, alteration and/or loss of any Personal Data disclosed by the Data Controller. 19.4 Notice to the Data Controller of a Data Security incident or Data Breach, shall be delivered in writing, to the e-mail address supplied by the Data Controller. 19.5 In the event of a Data Security incident or Data Breach, the Data Processor shall promptly take adequate remedial measures to mitigate the effects and to minimise any damage resulting from the Data Security incident or Data Breach, and; 19.6 The Data Processor shall provide such information, in relation to the Data Security incident or Data Breach, to the Data Controller. 19.7 The Data Processor shall fully cooperate with the Data Controller to develop and execute a response that shall address the Data Security incident or Data Breach, and; 19.8 the Data Processor shall cooperate with the Data Controller to adequately inform any Data Subject or other person affected by the data incident or Data Breach. 19.9 Please see the Data Breach Policy of the Data Processor listed in Appendix 1 of this Agreement.
Security Breaches and Incidents 

Related to Security Breaches and Incidents

  • Security Breaches In order to protect your security, it is your sole responsibility to ensure that all usernames and passwords used to access the Website are kept secure and confidential. You must immediately notify us of any unauthorized use of your account, including the unauthorized use of your password, or any other breach of security. We will investigate any breach of security on the Website that we determine in our sole discretion to be serious in nature, but we will not be held responsible or liable in any manner for breaches of security or any unauthorized access to your account however arising.

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

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

  • Error Incident An Error Incident is a single or series of NAV Errors that results from the same act, omission, or use of incorrect data. NAV Errors will be corrected as follows: · If an NAV Error is less than ½ of 1% of NAV and results in a Net Benefit, the fund will retain the benefit. · If an NAV Error is less than ½ of 1% of NAV and results in a Net Loss, the Net Loss will be paid to the fund by the party responsible for causing the NAV Error. · In the case of a Material NAV Error, shareholder transactions/accounts will be corrected/ reprocessed at the corrected (restated) NAV, subject to a $10 per-account correction minimum threshold; any residual Net Benefit after correction of shareholder accounts will be retained by the fund and any residual Net Loss (resulting from uncorrected accounts below the $10 minimum threshold) will be paid to the fund by the party responsible for causing the error. If an NAV error is not caused by either the fund accounting agent or TRP, both TRP and the fund accounting agent will provide all reasonable assistance to the fund in its attempt to recover all costs from the responsible third party. · Notwithstanding any contractual provisions to the contrary, to the extent a NAV Error was caused by the actions or omissions of the fund’s accounting agent, any Net Loss or residual Net Loss equal to $5,000 or less that results from the same Error Incident will be paid by the accounting agent. TRP will be responsible for summarizing and reporting to the funds’ Audit Committee or Trust Company’s Board (or designated committee), as applicable, all NAV Errors related to the funds/trusts in conjunction with other relevant error statistics on a quarterly basis. The report will include corrected NAV Errors as well as the aggregate effect of any uncorrected NAV Errors. The report will also include information about shareholder accounts that were corrected in the discretion of TRP in the case of an NAV Error that is not a Material NAV Error. The funds’ Audit Committee and the Trust Company’s Board shall have the authority to adjust these procedures with respect to the funds and trusts, respectively, to the extent necessary or desirable to address NAV Errors by providing notice thereof to TRP and the fund’s accounting agent.

  • Accidents and Dangerous Occurrences The Hirer must report all accidents involving injury to the public to a member of the Village Hall management committee as soon as possible and complete the relevant section in the Village Hall’s accident book. Any failure of equipment belonging to the Village Hall or brought in by the Hirer must also be reported as soon as possible. Certain types of accident or injury must be reported on a special form to the local authority. The Hall Secretary will give assistance in completing this form. This is in accordance with the Reporting of Injuries, Diseases and Dangerous Occurrences Regulations 1995 (RIDDOR).

  • Notification of Anticipatory Breach Vendor agrees that should it, for any reason, not be able to provide or maintain appropriate safeguards to fulfill its obligations under this Section, it will immediately inform Citizens in writing of such inability and such inability on Vendor’s part will serve as justification for Citizens’ termination of this Agreement, at Citizens’ sole election, at any time after the inability becomes known to Citizens.

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

  • Data Breaches 4.1 The Data Processor does not guarantee that its security measures will be effective under all conditions. If the Data Processor discovers a data breach within the meaning of Article

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