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
Sample 1Sample 2
AutoNDA by SimpleDocs

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.

  • Data Security Requirements Without limiting Contractor’s obligation of confidentiality as further described in this Contract, Contractor must establish, maintain, and enforce a data privacy program and an information and cyber security program, including safety, physical, and technical security and resiliency policies and procedures, that comply with the requirements set forth in this Contract and, to the extent such programs are consistent with and not less protective than the requirements set forth in this Contract and are at least equal to applicable best industry practices and standards (NIST 800-53). Contractor also shall provide technical and organizational safeguards against accidental, unlawful, or unauthorized access or use, destruction, loss, alteration, disclosure, transfer, commingling, or processing of such information that ensure a level of security appropriate to the risks presented by the processing of County Data, Contractor personnel and/or subcontractor personnel and affiliates approved by County to perform work under this Contract may use or disclose County personal and confidential information only as permitted in this Contract. Any other use or disclosure requires express approval in writing by the County of Orange. No Contractor personnel and/or subcontractor personnel or affiliate shall duplicate, disseminate, market, sell, or disclose County personal and confidential information except as allowed in this Contract. Contractor personnel and/or subcontractor personnel or affiliate who access, disclose, market, sell, or use County personal and confidential information in a manner or for a purpose not authorized by this Contract may be subject to civil and criminal sanctions contained in applicable federal and state statutes. Contractor shall take all reasonable measures to secure and defend all locations, equipment, systems, and other materials and facilities employed in connection with the Services against hackers and others who may seek, without authorization, to disrupt, damage, modify, access, or otherwise use Contractor systems or the information found therein; and prevent County data from being commingled with or contaminated by the data of other customers or their users of the Services and unauthorized access to any of County data. Contractor shall also continuously monitor its systems for potential areas where security could be breached. In no case shall the safeguards of Contractor’s data privacy and information and cyber security program be less stringent than the safeguards used by County. Without limiting any other audit rights of County, County shall have the right to review Contractor’s data privacy and information and cyber security program prior to commencement of Services and from time to time during the term of this Contract. All data belongs to the County and shall be destroyed or returned at the end of the contract via digital wiping, degaussing, or physical shredding as directed by County.

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

  • Compliance with Audit and Reporting Requirements; Maintenance of Records A. The Grantee shall submit to an audit of funds paid through this Grant Agreement and shall make all books, accounting records and other documents available at all reasonable times during the term of this Grant Agreement and for a period of three (3) years after final payment for inspection by the State or its authorized designee. Copies shall be furnished to the State at no cost

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

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