Information Security Requirements for Non Sample Clauses

Information Security Requirements for Non. Public Information Supplier agrees that it will protect the Non-Public Information it receives from or on behalf of the University according to applicable information security laws and regulations and leading commercially acceptable standards, including but not limited to:. • Center for Internet Security Standards for applications and operating systems - xxxxx://xxx.xxxxxxxxxx.xxx • Payment Card Industry/Data Security Standards (PCI/DSS) - xxxxx://xxx.xxxxxxxxxxxxxxxxxxxx.xxx/ • National Institute for Standards and Technology - xxxxx://xxxx.xxxx.xxx (non- exhaustive) • NIST 800-40 - Guide to Enterprise Patch Management Technologies • NIST 800-53 - Security and Privacy Controls for Information Systems and Organizations • NIST 800-171 - Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations • NIST 800-207 - Zero Trust Architecture • NIST 800-210 - General Access Control Guidance for Cloud Systems • NIST 800-52 – Guidelines for TLS Implementations • ISO/IEC 27000-series - xxxxx://xxx.xxx.xxx/isoiec-27001-information- security.html
AutoNDA by SimpleDocs
Information Security Requirements for Non. Public Information Supplier agrees that it will protect the Non-Public Information it receives from or on behalf of the University according to applicable information security laws and regulations and leading commercially acceptable standards, including but not limited to:.

Related to Information Security Requirements for Non

  • Information Security Requirements In cases where the State is not permitted to manage/modify the automation equipment (server/computer/other) that controls testing or monitoring devices, the Contractor agrees to update and provide patches for the automation equipment and any installed operating systems or applications on a quarterly basis (at minimum). The Contractor will submit a report to the State of updates installed within 30 days of the installation as well as a Plan of Actions and Milestones (POA&M) to remediate any vulnerabilities ranging from Critical to Low. The contractor will provide an upgrade path or compensatory security controls for any operating systems and applications listed as beyond “end-of-life” or EOL, within 90 days of the EOL and complete the EOL system’s upgrade within 90 days of the approved plan.

  • Electronic and Information Resources Accessibility and Security Standards a. Applicability: The following Electronic and Information Resources (“EIR”) requirements apply to the Contract because the Grantee performs services that include EIR that the System Agency's employees are required or permitted to access or members of the public are required or permitted to access. This Section does not apply to incidental uses of EIR in the performance of the Agreement, unless the Parties agree that the EIR will become property of the State of Texas or will be used by HHSC’s clients or recipients after completion of the Agreement. Nothing in this section is intended to prescribe the use of particular designs or technologies or to prevent the use of alternative technologies, provided they result in substantially equivalent or greater access to and use of a Product.

  • Information Security IET information security management practices, policies and regulatory compliance requirements are aimed at assuring the confidentiality, integrity and availability of Customer information. The UC Xxxxx Cyber-safety Policy, UC Xxxxx Security Standards Policy (PPM Section 310-22), is adopted by the campus and IET to define the responsibilities and key practices for assuring the security of UC Xxxxx computing systems and electronic data.

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

  • CERTIFICATION REGARDING USE OF CONTRACT FUNDS FOR LOBBYING This provision is applicable to all Federal-aid construction contracts and to all related subcontracts which exceed $100,000 (49 CFR 20).

  • Federal Medicaid System Security Requirements Compliance Party shall provide a security plan, risk assessment, and security controls review document within three months of the start date of this Agreement (and update it annually thereafter) in order to support audit compliance with 45 CFR 95.621 subpart F, ADP System Security Requirements and Review Process.

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