SECURITY POLICIES AND STANDARDS Sample Clauses

SECURITY POLICIES AND STANDARDS. 8.1 The Contractor shall, and shall procure that any Sub-contractor (as applicable) shall, comply with the Security Policies and Standards set out Annex A and B. 8.2 Notwithstanding the foregoing, the Authority’s Security Requirements applicable to the Services may be subject to change following certain events including, but not limited to, any relevant Variation in the delivery of the Services. Any change in the Authority’s Security Requirements resulting from such Variation (if any) shall be agreed by the Parties in accordance with the CAEHRS Variation Procedure. 8.3 The Contractor shall, and shall procure that any Sub-contractor (as applicable) shall, maintain appropriate records and is otherwise able to demonstrate compliance with the Security Policies and Standards.

SECURITY POLICIES AND STANDARDS. The Contractor shall, and shall procure that any Sub-contractor (as applicable) shall, comply with the Security Policies and Standards set out Annex A and B.

SECURITY POLICIES AND STANDARDS. 7.1 The Supplier shall, and shall procure that any Sub-contractor (as applicable) shall, comply with the Security Policies and Standards set out Annexes A and B. 7.2 Notwithstanding the foregoing, the Buyer’s Security Requirements applicable to the Services may be subject to change following certain events including, but not limited to, any relevant change in the delivery of the Services. Where any such change constitutes a Variation, any change in the Buyer’s Security Requirements resulting from such Variation (if any) shall be agreed by the Parties in accordance with the Variation Procedure. 7.3 The Supplier shall procure that any Sub-contractor (as applicable) shall, maintain appropriate records and is otherwise able to demonstrate compliance with the Security Policies and Standards.

SECURITY POLICIES AND STANDARDS. 7.1 The Supplier shall, and shall procure that any Sub-contractor (as applicable) shall, comply with the Buyer Security Policies and Standards set out below.

SECURITY POLICIES AND STANDARDS. 7.1 The Contractor shall, and shall procure that any Sub-contractor (as applicable) shall, comply with the Security Policies and Standards set out Annex A. 7.2 Notwithstanding the foregoing, the Authority’s Security Requirements applicable to the Services may be subject to change following certain events including, but not limited to, any relevant change in the delivery of the Services. Where any such change constitutes a Contract Change, any change in the Authority’s Security Requirements resulting from such Contract Change (if any) shall be agreed by the Parties in accordance with the Contract Change Procedure. Where any such change constitutes an Operational Change, any change in the Authority’s Security Requirements resulting from such Operational Change (if any) shall be agreed by the Parties and documented in the relevant Operational Change Confirmation. 7.3 The Contractor shall, and shall procure that any Sub-contractor (as applicable) shall, maintain appropriate records and is otherwise able to demonstrate compliance with the Security Policies and Standards. The Security Policies are published on: ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇/government/publications/dwp-procurement-security- policies-and-standards unless specified otherwise: a) Acceptable Use Policy b) Information Security Policy c) Physical Security Policy d) Information Management Policy

SECURITY POLICIES AND STANDARDS. Avaya maintains formal written information security policies and standards that: (i) define the administrative, physical, and technological controls to protect the confidentiality, integrity, and availability of Confidential Information, Avaya Products and Avaya systems (including mobile devices) used in providing services; (ii) encompass secure access, retention, and transfer of Confidential Information; (iii) provide for disciplinary or legal action in the event of violation of such policies by Authorized Personnel; (iv) prevent unauthorized access to Avaya’s customer data, customer systems, and Avaya systems, including access by former employees; and (v) employ the requirements for assessment, monitoring and auditing procedures to ensure Avaya is compliant with the applicable policies. Upon request but no more than once a year, Avaya may make, at minimum, the table of contents from its security policy and/or standards available for Customer review.

SECURITY POLICIES AND STANDARDS. All vendors agree to follow the University Information Security Policies and Standards in respect to systems and data access. These policies and standards are located at ▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇▇▇.▇▇▇

SECURITY POLICIES AND STANDARDS. 6.1 The Customer shall refrain from any actions likely to have an adverse impact on the Software, PRIMAVERA’s security systems and its connections to the Customer and the data therein, and undertakes to: (a) Promptly notify PRIMAVERA of any security incident that jeopardizes or is likely to jeopardize the confidentiality, integrity or availability of the Software, the data, or any information, or likely to affect the regular operation of the Software, further undertaking to cause any unauthorized use of the Software that it suspects or comes to its knowledge to stop; (b) Adopt any technical measures to avoid loss of data; (c) Adopt any measures required to prevent and deter any unauthorized access to the Software and provide to PRIMAVERA any information and the support required for latter to report, if it so wishes, any detected breach or unlawful access, breach of security, of privacy and of data protection rules to the proper authorities and to take legal action against any third parties based on the situations set out in the above paragraph. 6.2 PRIMAVERA shall also notify the Customer as soon as it becomes aware of any actual or threatened security failure likely to affect the Software or the Services.

SECURITY POLICIES AND STANDARDS. 7.1 The Supplier shall, and shall procure that any Sub-contractor (as applicable) shall, comply with the Security Policies and Standards set out Annex A. 7.2 Notwithstanding the foregoing, the Buyer’s Security Requirements applicable to the Services may be subject to change following certain events including, but not limited to, any relevant change in the delivery of the Services. Where any such change constitutes a Variation, any change in the Buyer’s Security Requirements resulting from such Contract Change (if any) shall be agreed by the Parties in accordance with the Variation Procedure. Where any such change constitutes a Variation, any change in the Buyer’s Security Requirements resulting from such Variation (if any) shall be agreed by the Parties in accordance with the Variation Procedure.