Breach of Security. 6.1 Either party shall notify the other immediately upon becoming aware of any Breach of Security including, but not limited to an actual, potential or attempted breach, or threat to, the Security Plan.
Breach of Security. 5.1. Provider agrees to provide the GLO with the name and contact information for an employee of the Provider which shall serve as the GLO’s primary security contact.
Breach of Security. 6.1 Either party shall notify the other in writing in accordance with the agreed security incident management process as defined by the ISMS upon becoming aware of any Breach of Security or any potential or attempted Breach of Security.
Breach of Security. Either Party shall notify the other in accordance with the agreed security incident management process as defined by the ISMS upon becoming aware of any breach of security or any potential or attempted Breach of Security. Without prejudice to the security incident management process, upon becoming aware of any of the circumstances referred to in paragraph 102.1 of this Call Off Schedule, the Supplier shall: immediately take all reasonable steps (which shall include any action or changes reasonably required by the Customer) necessary to: minimise the extent of actual or potential harm caused by any Breach of Security; remedy such Breach of Security to the extent necessary protect the integrity of the Customer Property and/or Customer Assets to the extent within its control against any such Breach of Security or any potential or attempted Breach of Security; apply a tested mitigation against any such Breach of Security or attempted Breach of Security and provided that reasonable testing has been undertaken by the Supplier, if the mitigation adversely affects the Supplier’s ability to provide the Services so as to meet the relevant Service Level Performance Measures, the Supplier shall be granted relief against any resultant under-performance for such period as the Customer, acting reasonably, may specify by written notice to the Supplier; prevent a further Breach of Security or attempted Breach of Security in the future exploiting the same root cause failure; and supply any requested data to the Customer (or the Computer Emergency Response Team for UK Government (“GovCertUK”)) on the Customer’s request within two (2) Working Days and without charge (where such requests are reasonably related to a possible incident or compromise); and as soon as reasonably practicable provide to the Customer full details (using the reporting mechanism defined by the ISMS) of the Breach of Security or attempted Breach of Security, including a root cause analysis where required by the Customer. In the event that any action is taken in response to a Breach of Security or potential or attempted Breach of Security that demonstrates non-compliance of the ISMS with the Security Policy or the requirements of this Call Off Schedule, then any required change to the ISMS shall be at no cost to the Customer. 12/08/2013 ANNEX 1: SECURITY POLICY [ ] 12/08/2013 ANNEX 2: SECURITY MANAGEMENT PLAN [ ] [CALL OFF SCHEDULE 9: BUSINESS CONTINUITY AND DISASTER RECOVERY] [Guidance Note: See Cl...
Breach of Security. Either party shall notify the other in accordance with the agreed security incident management process (as detailed in the Security Management Plan if one exists) upon becoming aware of any Breach of Security or any potential or attempted Breach of Security. Without prejudice to the security incident management process, upon becoming aware of any of the circumstances referred to in paragraph 98.1, the Supplier shall: immediately take all reasonable steps(which shall include any action or changes reasonably required by the Customer) necessary to: minimise the extent of actual or potential harm caused by any Breach of Security; remedy such Breach of Security to the extent possible and protect the integrity of the Customer and the provision of the Goods and/or Services to the extent within its control against any such Breach of Security or attempted Breach of Security; prevent an equivalent breach in the future exploiting the same root cause failure; and as soon as reasonably practicable provide to the Customer, where the Customer so requests, full details (using the reporting mechanism defined by the Security Management Plan if one exists) of the Breach of Security or attempted Breach of Security, including a root cause analysis where required by the Customer. In the event that any action is taken in response to a Breach of Security or potential or attempted Breach of Security that demonstrates non-compliance of the Security Management Plan with the Security policy or the requirements of this Call Off Schedule, then any required change to the Security Management Plan shall be at no cost to the Customer. 12/08/2013 [LONG FORM – PARAGRAPHS 1 TO 8] DEFINITIONS In this Call Off Schedule 8, the following definitions shall apply:
Breach of Security. Any breach or violation by Contractor of any of the foregoing shall be deemed a material breach of a material obligation of Contractor under this Contract and may be deemed an incurable and material breach of a material obligation of Contractor under this Contract resulting in termination. Conduct on County Premises Contractor shall, at all times, comply with and abide by all reasonable policies and procedures of County (or that may be established thereby, from time to time) that pertain to conduct on County’s premises, possession or distribution of contraband, or the access to, and security of, the Party’s real property or facilities, to the extent that Contractor has been provided with a copy of each such policy or procedure. Contractor shall exercise due care and diligence to prevent any injury to persons or damage to property while on the other Party’s premises. The operation of vehicles by either Party’s personnel on the other Party’s property shall conform to posted and other applicable regulations and safe-driving practices. Vehicular accidents occurring on a Party’s property and involving either Party’s personnel shall be reported promptly to the appropriate Party’s personnel. Each Party covenants that at all times during the Term, it, and its employees, agents, and subcontractors shall comply with, and take no action that results in the other Party being in violation of, any applicable federal, state, and local laws, ordinances, regulations, and rules. Each Party’s personnel shall clearly identify themselves as the appropriate Party’s personnel and not as employees of the other Party. When on the other Party’s premises, each Party’s personnel shall wear and clearly display identification badges or tags, as approved by the other Party.
Breach of Security. 7.1 Either Party shall notify the other immediately upon becoming aware of any Breach of Security including, but not limited to an actual, potential or attempted breach, or threat to, the Security Plan.
Breach of Security. Any breach or violation by Contractor of any of the foregoing shall be deemed a material breach of a material obligation of Contractor under this Contract and may be deemed an incurable and material breach of a material obligation of Contractor under this Contract resulting in termination.
Breach of Security. (1) In the event of a suspected or established unauthorized disclosure, misappropriation or loss of Classified Information falling under this Agreement, the Competent Authority of the Receiver shall immediately inform the Competent Authority of the Originator in writing.
Breach of Security. 5.1. Contractor agrees to provide the GLO with the name and contact information for an employee of the Contractor which shall serve as the GLO’s primary security contact.
