Security Requirements. 11.1 The Supplier shall comply, and shall procure the compliance of the Suppliers Personnel, with the Security Policy and the Security Plan and the Supplier shall ensure that the Security Plan produced by the Supplier fully complies with the Security Policy.
Security Requirements. 7.1 The Authority will review the Contractor’s Security Plan when submitted by the Contractor in accordance with the Schedule (Security Requirements and Plan) and at least annually thereafter.
Security Requirements. A. Contractor shall, with respect to all employees of Contractor performing services hereunder:
Security Requirements. The Supplier shall comply, and shall procure the compliance of the Staff, with the Security Policy and the Security Management Plan (if any) and the Supplier shall ensure that the Security Management Plan produced by the Supplier fully complies with the Security Policy. The Customer shall notify the Supplier of any changes or proposed changes to the Security Policy. If the Supplier believes that a change or proposed change to the Security Policy will have a material and unavoidable cost implication to the provision of the Goods and/or Services it may notify the Customer. In doing so, the Supplier must support its request by providing evidence of the cause of any increased costs and the steps that it has taken to mitigate those costs. Any change to the Call Off Contract Charges shall then be subject to the Variation Procedure. Until and/or unless a change to the Call Off Contract Charges is agreed by the Customer pursuant to the Variation Procedure the Supplier shall continue to provide the Goods and/or Services in accordance with its existing obligations.
Security Requirements. 17 32.1.1 CONTRACTOR agrees to maintain the confidentiality of all COUNTY and 18 COUNTY-related records and information pursuant to all statutory laws relating to privacy and 19 confidentiality that currently exists or exists at any time during the term of this Agreement.
Security Requirements. The Contractor must maintain the most up-to-date anti-virus programs, industry-accepted firewalls and other protections on its systems and networking equipment. The Contractor certifies that all systems and networking equipment that support, interact with or store County Information meet the above standards and industry best practices for physical, network and system security requirements. Devices (laptops, mobile phones, printers, copiers, fax machines, or similar) that store County Data utilize encryption. The County’s Chief Information Security Officer or designee must approve any deviation from these standards. The downloading of County information onto devices, other portable storage media or services such as personal e-mail, Dropbox etc. is prohibited without the written authorization of the County’s Chief Information Security Officer or designee.
Security Requirements. 32.1.1 CONTRACTOR agrees to maintain the confidentiality of all COUNTY and COUNTY-related records and information pursuant to all statutory laws relating to privacy and confidentiality that currently exists or exists at any time during the term of this Contract. CONTRACTOR represents and warrants that it has implemented and will maintain during the term of this Contract administrative, physical, and technical safeguards to reasonably protect private and confidential client information, to protect against anticipated threats to the security or integrity of COUNTY data, and to protect against unauthorized physical or electronic access to or use of COUNTY data. Such safeguards and controls shall include at a minimum: Storage of confidential paper files that ensures records are secured, handled, transported, and destroyed in a manner that prevents unauthorized access. Control of access to physical and electronic records to ensure COUNTY data is accessed only by individuals with a need to know for the delivery of contract services. Control to prevent unauthorized access and to prevent CONTRACTOR employees from providing COUNTY data to unauthorized individuals. Firewall protection. Use of encryption methods of electronic COUNTY data while in transit from CONTRACTOR networks to external networks, when applicable. Measures to securely store all COUNTY data, including, but not be limited to, encryption at rest and multiple levels of authentication and measures to ensure COUNTY data shall not be altered or corrupted without COUNTY's prior written consent. CONTRACTOR further represents and warrants that it has implemented and will maintain during the term of this Contract administrative, technical, and physical safeguards and controls consistent with State and federal security requirements.
Security Requirements. A. Seller shall ensure that it is in compliance with all Federal and state employment laws and regulations governing verification of eligibility of employment for individuals hired by Seller or Seller Representatives prior to permitting such persons to perform Services.
Security Requirements. Authorized Users may have ongoing and/or periodic delivery and/or security restrictions that may affect service, particularly at correctional facilities. In addition, Contractor may be required to obtain security badges from the Authorized User for its employees. Authorized Users shall identify all such restrictions and requirements in the Project Definition, and Contractors are responsible for meeting all security requirements and shall take these restrictions into account when bidding on specific projects. All costs for meeting security requirements shall be included in the prices bid.
Security Requirements. 7.1 The Authority will review the Provider’s Security Plan when submitted by the Provider in accordance with Schedule 6 (Security Requirements and Plan) and at least annually thereafter.
