Compliance with NYS Information Security Policies and Procedures Sample Clauses

Compliance with NYS Information Security Policies and Procedures. Contractor warrants, covenants and represents that it shall comply fully with all security procedures of the State communicated to it in the performance of this Contract, including ITS Information Security policies and procedures located at xxxxx://xxx.xx.xxx/eiso/policies/security. ITS shall have the right at any time to require that the Contractor remove from interaction with ITS any Contractor representative who ITS believes is detrimental to its working relationship with the Contractor. The State will provide the Contractor with notice of its determination, and the reasons it requests the removal. If ITS signifies that a potential security violation exists with respect to the request, the Contractor shall immediately remove such individual. Contractor shall not assign the person to any aspect of the Contract or future work orders without ITS consent. Contractor shall use industry standard security measures, including standard encryption protocols, to protect and guard the availability and security of all NYS Confidential Information, and adhere to all the State’s security policies. Contractor shall be strictly prohibited from using NYS Confidential Information in any fashion other than that defined herein. There may be instances whereby ITS will communicate security procedures necessitated by ITS operations. Contractor will use reasonable efforts to implement same. In the event Contractor does not implement or communicates that it cannot or will not implement such security procedures, the Parties will reasonably work to resolve such dispute pursuant to the Contract's Dispute Resolution process. Contractor warrants that its Contractor Staff members are properly informed and trained regarding security standards andare prohibited from disclosing NYS Confidential Information to any persons without a need to know. Contractor will work cooperatively with the State so that software applications accessed by members of the public or others are accessed by the single sign-on service provided by New York State Directory Services or such other service chosen by ITS. The Contractor’s solution may be required to pass an internal NYS security review conducted by NYS prior to implementation and after any significant system modifications. This review will determine whether adequate controls are in place to protect the availability of the System and the integrity and confidentiality of the information. A significant system modification is considered any change to the un...
AutoNDA by SimpleDocs

Related to Compliance with NYS Information Security Policies and Procedures

  • Violence Policies and Procedures The Employer agrees to have in place explicit policies and procedures to deal with violence. The policy will address the prevention of violence, the management of violent situations, provision of legal counsel and support to employees who have faced violence. The policies and procedures shall be part of the employee's health and safety policy and written copies shall be provided to each employee. Prior to implementing any changes to these policies, the employer agrees to consult with the Association.

  • Policies and Procedures i) The policies and procedures of the designated employer apply to the employee while working at both sites.

  • Compliance with Policies Each Individual Limited Partner hereby agrees that he shall comply with all policies and procedures adopted by any member of the Och-Ziff Group or which Limited Partners are required to observe by law, or by any recognized stock exchange, or other regulatory body or authority.

  • Safeguarding requirements and procedures (1) The Contractor shall apply the following basic safeguarding requirements and procedures to protect covered contractor information systems. Requirements and procedures for basic safeguarding of covered contractor information systems shall include, at a minimum, the following security controls:

  • Compliance with Texas Privacy Laws and Regulations In performing their respective obligations under the Agreement, the LEA and the Provider shall comply with all Texas laws and regulations pertaining to LEA data privacy and confidentiality, including but not limited to the Texas Education Code Chapter 32, and Texas Government Code Chapter 560.

  • Provisions for Covered Entity to Inform Business Associate of Privacy Practices and Restrictions (a) Covered Entity shall notify Business Associate of any limitation(s) in the notice of privacy practices of Covered Entity under 45 CFR 164.520, to the extent that such limitation may affect Business Associate’s use or disclosure of protected health information.

  • Confidentiality and Safeguarding of University Records; Press Releases; Public Information Under this Agreement, Contractor may (1) create, (2) receive from or on behalf of University, or (3) have access to, records or record systems (collectively, University Records). Among other things, University Records may contain social security numbers, credit card numbers, or data protected or made confidential or sensitive by Applicable Laws. [Option (Include if University Records are subject to FERPA.): Additional mandatory confidentiality and security compliance requirements with respect to University Records subject to the Family Educational Rights and Privacy Act, 20 United States Code (USC) §1232g (FERPA) are addressed in Section 12.41.] [Option (Include if University is a HIPAA Covered Entity and University Records are subject to HIPAA.): Additional mandatory confidentiality and security compliance requirements with respect to University Records subject to the Health Insurance Portability and Accountability Act and 45 Code of Federal Regulations (CFR) Part 160 and subparts A and E of Part 164 (collectively, HIPAA) are addressed in Section 12.26.] Contractor represents, warrants, and agrees that it will: (1) hold University Records in strict confidence and will not use or disclose University Records except as (a) permitted or required by this Agreement, (b) required by Applicable Laws, or (c) otherwise authorized by University in writing; (2) safeguard University Records according to reasonable administrative, physical and technical standards (such as standards established by the National Institute of Standards and Technology and the Center for Internet Security [Option (Include if Section 12.39 related to Payment Card Industry Data Security Standards is not include in this Agreement.):, as well as the Payment Card Industry Data Security Standards]) that are no less rigorous than the standards by which Contractor protects its own confidential information; (3) continually monitor its operations and take any action necessary to assure that University Records are safeguarded and the confidentiality of University Records is maintained in accordance with all Applicable Laws and the terms of this Agreement; and (4) comply with University Rules regarding access to and use of University’s computer systems, including UTS165 at xxxx://xxx.xxxxxxxx.xxx/board-of-regents/policy-library/policies/uts165-information-resources-use-and-security-policy. At the request of University, Contractor agrees to provide University with a written summary of the procedures Contractor uses to safeguard and maintain the confidentiality of University Records.

  • Compliance with Privacy Laws NCPS represents and warrants that its collection, access, use, storage, disposal and disclosure of Personal Data does and will comply with all applicable federal and state privacy and data protection laws, as well as all other applicable regulations. Without limiting the foregoing, NCPS shall implement administrative, physical and technical safeguards to protect Personal Data that are no less rigorous than accepted industry, and shall ensure that all such safeguards, including the manner in which Personal Data is collected, accessed, used, stored, processed, disposed of and disclosed, comply with applicable data protection and privacy laws, as well as the terms and conditions of this Escrow Agreement. NCPS shall use and disclose Personal Data solely and exclusively for the purposes for which the Personal Data, or access to it, is provided pursuant to the terms and conditions of this Escrow Agreement, and not use, sell, rent, transfer, distribute, or otherwise disclose or make available Personal Data for NCPS’s own purposes or for the benefit of any party other than Issuer. For purposes of this section, “Personal Data” shall mean information provided to NCPS by or at the direction of the Issuer, or to which access was provided to NCPS by or at the direction of the Issuer, in the course of NCPS’s performance under this Escrow Agreement that: (i) identifies or can be used to identify an individual (also known as a “data subject”) (including, without limitation, names, signatures, addresses, telephone numbers, e-mail addresses and other unique identifiers); or (ii) can be used to authenticate an individual (including, without limitation, employee identification numbers, government-issued identification numbers, passwords or PINs, financial account numbers, credit report information, biometric or health data, answers to security questions and other personal identifiers), including the identifying information on individuals described in Section 12.

  • CONFIDENTIALITY AND PRIVACY POLICIES AND LAWS The Contractor shall comply to the extent applicable with all State and Authorized User policies regarding compliance with various confidentiality and privacy laws, rules and regulations, including but not limited to the IRS Publication 1075, Family Educational Rights and Privacy Act (FERPA), the Health Insurance and Portability Act of 1996 (HIPAA) and the Health Information Technology for Economic and Clinical Health Act (HITECH). Contractor shall cooperate in executing a written confidentiality agreement under FERPA and/or a Business Associate Agreement (HIPAA/HITECH) or other contractual provisions upon request by the State or any Authorized User.

  • Compliance with Consensus Policies and Temporary Policies Registry Operator shall comply with and implement all Consensus Policies and Temporary Policies found at <xxxx://xxx.xxxxx.xxx/general/consensus-­‐policies.htm>, as of the Effective Date and as may in the future be developed and adopted in accordance with the ICANN Bylaws, provided such future Consensus Polices and Temporary Policies are adopted in accordance with the procedure and relate to those topics and subject to those limitations set forth in Specification 1 attached hereto (“Specification 1”).

Time is Money Join Law Insider Premium to draft better contracts faster.