Computer System Security Requirements Sample Clauses

Computer System Security Requirements. To the extent that Supplier electronically stores or transmits Protected Information or has access to any UC Information Resources, it will include in its written, comprehensive Information Security Plan the establishment and maintenance of a security system covering its computers, including any wireless system, that, at a minimum, and to the extent technically feasible, will have the following elements:
Sample 1Sample 2Sample 3See All (7)
AutoNDA by SimpleDocs
Computer System Security Requirements. To the extent that Contractor electronically stores or transmits Confidential Information or has access to any ETF Information Resources, it will include in its written, comprehensive Information Security Plan the establishment and maintenance of a security system covering its computers, including any wireless system, that, at a minimum, and to the extent technically feasible, will have the following elements: (1) Secure user authentication protocols including: a. Control of user IDs and other identifiers; b. A secure method of assigning and selecting passwords, or use of unique identifier technologies, such as biometrics or token devices; c. Multi-Factor Authentication (MFA);
Sample 1Sample 2Sample 3See All (4)
Computer System Security Requirements. To the extent that Contractor electronically stores or transmits Confidential Information or has access to any Department Information Resources, it will include in its written, comprehensive Information Security Plan the establishment and maintenance of a security system covering its computers, including any wireless system, that, at a minimum, and to the extent technically feasible, will have the following elements:
Sample 1
Computer System Security Requirements. Supplier shall include in its information security program a computer security system that complies with the Security Rule, including but not limited to the following elements: .Secure user authentication protocols including: 1. control of user IDs and other identifiers; 2. a reasonably secure method of assigning and selecting passwords, or use of unique identifier technologies, such as biometrics or token devices;
Sample 1
Computer System Security Requirements. To the extent that Contractor electronically stores or transmits Confidential Information or has access to any ETF Information Resources, it will include in its written, comprehensive Information Security Plan the establishment and maintenance of a security system covering its computers, including any wireless system, that, at a minimum, and to the extent technically feasible, will have the following elements: (1) Secure user authentication protocols including: a. Control of user IDs and other identifiers; b. A secure method of assigning and selecting passwords, or use of unique identifier technologies, such as biometrics or token devices; c. Multi-Factor Authentication (MFA); d. Control of data security passwords to ensure that such passwords are kept in a location and/or format that does not compromise the security of the data they protect; e. Restricting access to active users and active user accounts only; and f. Blocking access to user identification after multiple unsuccessful attempts to gain access or the limitation placed on access for the particular system. g. Periodic review of user access, access rights and audit of user accounts. (2) Secure access control measures that: a. Restrict access to records and files containing Confidential Information and systems that may have access to ETF Information Resources to those who need such information to perform their job duties; and b. Assign unique identifications plus passwords, which are not vendor supplied default passwords, to each person with computer access, which are reasonably designed to maintain the integrity of the security of the access controls. (3) Encryption of all transmitted records and files containing Confidential Information or the use of other compensating controls meeting applicable industry standards for protection of data. Contractor will inform the Department about which industry standards and other compensating controls Contractor utilizes. Contractor and the Department agree that if the Department has concerns, those concerns will be discussed and resolved pursuant to Section 13.0 (Contract Dispute Resolution) of Exhibit 6. (4) Adequate security of all networks that connect to ETF Information Resources or access Confidential Information, including wireless networks. (5) Reasonable monitoring of systems, for unauthorized use of or access to Confidential Information and ETF Information Resources. (6) Encryption of all Confidential Information stored on Contractor devices, includ...
Sample 1
Computer System Security Requirements. If Supplier or Supplier Personnel electronically stores or transmits PII or HCI, its written WISP shall include the establishment and maintenance of a security system covering its computers, including any wireless system that, at a minimum, shall have the following elements:
Sample 1

Related to Computer System Security Requirements

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

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

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

  • New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to: (1) Limit system access to the types of transactions and functions that authorized users, such as students, parents, and LEA are permitted to execute; (2) Limit unsuccessful logon attempts; (3) Employ cryptographic mechanisms to protect the confidentiality of remote access sessions; (4) Authorize wireless access prior to allowing such connections; (5) Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity; (6) Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions; (7) Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles; (8) Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services; (9) Enforce a minimum password complexity and change of characters when new passwords are created; (10) Perform maintenance on organizational systems; (11) Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance; (12) Ensure equipment removed for off-site maintenance is sanitized of any Student Data in accordance with NIST SP 800-88 Revision 1; (13) Protect (i.e., physically control and securely store) system media containing Student Data, both paper and digital; (14) Sanitize or destroy system media containing Student Data in accordance with NIST SP 800-88 Revision 1 before disposal or release for reuse; (15) Control access to media containing Student Data and maintain accountability for media during transport outside of controlled areas; (16) Periodically assess the security controls in organizational systems to determine if the controls are effective in their application and develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems; (17) Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems; (18) Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception); (19) Protect the confidentiality of Student Data at rest; (20) Identify, report, and correct system flaws in a timely manner; (21) Provide protection from malicious code (i.e. Antivirus and Antimalware) at designated locations within organizational systems; (22) Monitor system security alerts and advisories and take action in response; and (23) Update malicious code protection mechanisms when new releases are available.

  • Accessibility Requirements Under Tex. Gov’t Code Chapter 2054, Subchapter M, and implementing rules of the Texas Department of Information Resources, the System Agency must procure Products and services that comply with the Accessibility Standards when those Products are available in the commercial marketplace or when those Products are developed in response to a procurement solicitation. Accordingly, Grantee must provide electronic and information resources and associated Product documentation and technical support that comply with the Accessibility Standards.

  • City Requirements Design, construction, materials, sizing, other specifications, permitting, inspections, testing, documentation and furnishing of as-built drawings, and acceptance of completed infrastructure shall be in accordance with City Requirements. Design and construction shall be by professionals licensed in the state of North Carolina to do the relevant work. City approval of the design of the Improvements shall be required prior to construction, as set forth in City Requirements. If Developer is connecting to the County sewer system, the City may require Developer to furnish the contract providing for such connection.

  • Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.

  • Personal Property Requirements The Collateral Agent shall have received from each Loan Party (except to the extent the Administrative Agent determines that any of the following is not commercially feasible, taking into account the cost to procure and the effectiveness and enforceability under local law): (i) all certificates, agreements or instruments representing or evidencing the Pledged Equity Interests and the Pledged Intercompany Debt (each as defined in the U.S. Security Agreement) accompanied by instruments of transfer and stock powers endorsed in blank; (ii) all other certificates, agreements, including Control Agreements, or instruments necessary to perfect security interests in all Chattel Paper, all Instruments, all Deposit Accounts and all Investment Property of each Loan Party (as each such term is defined in the U.S. Security Agreement and to the extent required by the terms of the U.S. Security Agreement); (iii) UCC financing statements in appropriate form for filing under the UCC and such other documents under applicable Requirements of Law in each jurisdiction as may be necessary or appropriate to perfect the Liens created, or purported to be created, by the Security Documents; (iv) certified copies of Requests for Information (Form UCC-11), tax lien, judgment lien, bankruptcy and pending lawsuit searches or equivalent reports or lien search reports, each of a recent date listing all effective financing statements, lien notices or comparable documents that name (A) any domestic Loan Party as debtor and that are filed in those state and county jurisdictions in which any of the property of such domestic Loan Party is located and the state and county jurisdictions in which such domestic Loan Party’s principal place of business is located, and (B) any foreign Loan Party, to the extent obtainable from the District of Columbia, none of which encumber the Collateral covered or intended to be covered by the Security Documents (other than those relating to Liens acceptable to the Collateral Agent); (v) delivery of such documents and instruments and instruments as the Collateral Agent may request for filing with the United States Patent, Trademark and Copyright Offices, and the execution and/or delivery of such other security and other documents, and the taking of all actions as may be necessary or, in the reasonable opinion of the Collateral Agent, desirable, to perfect the Liens created, or purported to be created, by the Security Agreements; (vi) any documents required to be submitted to the Collateral Agent by the Loan Parties as may be necessary or desirable to perfect the security interest of the Collateral Agent pursuant to each Foreign Security Agreement; and (vii) evidence acceptable to the Collateral Agent of payment by the Loan Parties of all applicable recording taxes, fees, charges, costs and expenses required for the recording of the Security Documents.

  • Facility Requirements 1. Maintain wheelchair accessibility to program activities according to governing law, including the Americans With Disabilities Act (ADA), as applicable. 2. Provide service site(s) that will promote attainment of Contractor’s program objectives. Arrange the physical environment to support those activities. 3. Decrease program costs when possible by procuring items at no cost from County surplus stores and by accepting delivery of such items by County.

  • Changes in Equipment, Systems, Etc USBFS reserves the right to make changes from time to time, as it deems advisable, relating to its systems, programs, rules, operating schedules and equipment, so long as such changes do not adversely affect the services provided to the Trust under this Agreement.

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