System Security Requirements Sample Clauses

System Security Requirements. ‌ Contractor shall, in cooperation with CSD, institute policies, processes, procedures, and security controls designed to ensure the security of data and to protect information in accordance with the Information Practices Act of 1977 (Civ. Code §§ 1798 et seq.), and such other State and federal laws and regulations as may apply. The parties hereto agree to requirements, obligations, and standards in accordance with regulations set in the State Administrative Manual (XXX) and Statewide Information Management Manual (SIMM). In the event there are different system security standards that may be applied to this Article, Contractor shall endeavor to use the strictest security standard that complies with state and federal requirements.
Sample 1Sample 2See All (8)
AutoNDA by SimpleDocs
System Security Requirements. If the Contractor becomes aware of any unauthorized access to an agency’s Confidential Information or a security breach that compromises or reasonably could compromise an agency’s Confidential Information (an “incident”), the Contractor shall take appropriate immediate actions to contain the incident, in accordance with applicable law, and notify the Ordering Entity as soon as reasonably possible. The Contractor shall provide the Ordering Entity with information regarding any incident as may be reasonably requested by the Ordering Entity and that is in the Contractor’s possession, custody, or control at the time a request is received. Upon request of the Government, the Contractor will reasonably cooperate with the Government to investigate the nature and scope of any incident and to take appropriate actions to investigate and otherwise respond to the incident or associated risks. (As used in this Section, “compromise” means that the information has been exposed to any unauthorized access, inadvertent disclosure, known misuse, or known loss, alteration or destruction of Confidential Information other than as required to provide the services.)
Sample 1Sample 2Sample 3
System Security Requirements. The Alabama Department of Revenue does not prescribe the security requirements for your system. You are responsible for implementing appropriate security measures to protect taxpayers and their information in your system. You must apply security measures to protect taxpayer information in your system when it is on-line, off-line, at rest, and in transit. Unless otherwise prohibited by law, all data breaches, security incidents, or other improper disclosures of taxpayer data must be promptly reported to the Alabama Department of Revenue and Alabama Attorney General Office. Data breaches, security incidents, or other improper disclosures of taxpayer data that by law require reporting to the Alabama Attorney General Office must also be reported to the Alabama Department of Revenue.
Sample 1Sample 2
System Security Requirements. 15.1. All Services provided by Bank under this Agreement whether implemented in the state of Washington on State computer systems and networks or on Bank’s systems, must be compliant with the applicable security policy and standards of the Office of the Chief Information Officer (OCIO). The OCIO Security Policy is available at: xxxx://xxx.xx.xxx/ocio/policies/documents/141.pdf. The OCIO Security Standards are available at: xxxx://xxx.xx.xxx/ocio/policies/documents/141.10.pdf. 15.2. The Bank will be required to represent and warrant that it will comply with all applicable elements of the OCIO Security Policy and the OCIO Security Standards in its performance of any Services awarded under an Agreement. The Bank will be required to comply with ESD Security Policy and must receive annual Information Technology (IT) security awareness training either from their company, or through the LCB Annual Security Training.
Sample 1
System Security Requirements. Contractor shall utilize tamper-resistant PV module to rack fasteners for all PV module mounting. Contractor shall utilize tamper-resistant fasteners for all electrical fittings, pull boxes and other enclosures. Contractor shall supply and install Utility approved a Net Generation Output Meter (NGOM) for each PV system. Generation Meters shall use Internet Protocol (IP) communication and shall not require a custom network for connection. Generation Meters shall have the capability to store metered data including instantaneous kW, kWh, voltage, current, and phase information) in fifteen (15) minute intervals and retain such information for at least seven (7) Calendar Days. Contractor shall design, build, activate and ensure proper functioning of Data Acquisition Systems (DAS) that enable the City to track the performance of the PV Systems as well as environmental conditions through an online web-enabled graphical user interface and information displays. Contractor shall provide equipment to connect the DAS via existing Wi-Fi network or cellular data network at all locations. The means of data connection will be determined during design. The City will pay for the cost of cellular data service if needed, and the Contractor shall pay for the modem and/or other equipment needed to connect to the cellular network. The DAS(s) shall provide access to at least the following data: Instantaneous AC system output (kW) PV System production (kWh) over pre-defined intervals that may be user configured AC and DC voltage Horizontal and in-plane irradiance (at least three (3) sensors for each, at different positions in the array) Ambient and back-of-cell temperature (at least two (2) sensors for each, at different positions in the array) Inverter status flags and general system status information System availability Site Load information. Available load data for the meter the system is connected to shall be collected by the solar monitoring solution as part of the DAS. Environmental data such as temperatures, wind speed, and irradiance shall be collected via an individual weather station installed for each system at each site where PV is being installed. Data collected by the DAS shall be presented in an online web interface, accessible from any computer through the Internet with appropriate security (i.e., password-controlled access). The user interface shall allow visualization of the data at least in the following increments: 15 minutes, hour, day, week, month, and year....
Sample 1
System Security Requirements. The Alabama Department of Revenue does not prescribe the security requirements for your system. You are responsible for implementing appropriate security measures to protect taxpayers and their information in your system. You must apply security measures to protect taxpayer information in your system when it is on-line, off-line, at rest, and in transit. All e-file ATS and substitute forms tests submitted during the approval process must be created in, and originate from, the actual software.
Sample 1
System Security Requirements. COUNTY shall implement security procedures to prevent unauthorized physical access to sensitive voting equipment. The Xxxx Voting and Voter Management System shall include and support operational features to prevent both inadvertent and deliberate operations that could result in the disruption of the election process and corruption of election administrative and voting data.
Sample 1
AutoNDA by SimpleDocs
System Security Requirements. Contractor shall, in cooperation with CSD, institute measures, procedures, and protocols designed to ensure the security of data and to protect information in accordance with the Information Practices Act of 1977 (Civ. Code § 1798 et seq.), and such other State and Federal laws and regulations as may apply. In the event there are different system security standards that may be applied to this Article, Contractor shall endeavor to use the strictest security standard that complies with state and federal requirements. The parties hereto agree to the following requirements, obligations, and standards in accordance with regulations set in the State Administrative Manual (XXX) and Statewide Information Management Manual (SIMM): A. Data Protection 1. Data exchanged between CSD and Contractor must be limited to the data fields included on Data Transfer Rules documents posted at xxxxx://xxxxxxxx.xxx.xx.xxx/home/Energy/Pages/Resources.aspx. No personal financial information, e.g., credit card, bank account numbers, shall be stored or exchanged in the data exchange sessions.
Sample 1
System Security Requirements. 4.1 National and DOD security requirements 4.2 Governing security requisites 4.3 Data Security Requirements
Sample 1

Related to System Security Requirements

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

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

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

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

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

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

  • E-Verify Requirements To the extent applicable under ARIZ. REV. STAT. § 41- 4401, the Contractor and its subcontractors warrant compliance with all federal immigration laws and regulations that relate to their employees and their compliance with the E-verify requirements under ARIZ. REV. STAT. § 23-214(A). Contractor’s or its subcontractor’s failure to comply with such warranty shall be deemed a material breach of this Agreement and may result in the termination of this Agreement by the City.

  • Safety Requirements The Contractor shall comply with all Federal, State, and local safety laws and regulations applicable to the Work performed under this Agreement.

  • Residency Requirements 1. All single first-year freshmen students are required to live in University housing for at least two academic semesters. All single students who have earned less than 30 credit hours and have not resided in University housing for two academic semesters are required to live on campus for two academic semesters. This policy does not apply to single first-year students who have been out of high school for more than one year, or to single first-year freshmen who live with their parents in Miami-Dade or Broward Counties. Neither does it apply to those students who, for disciplinary or administrative reasons, may be denied the privilege of continued residency on campus. 2. Undergraduate students residing in University housing must be regularly enrolled students of the University, taking a minimum of 12 credit hours each semester. Graduate students (when housed by exception) must carry a minimum of nine credit hours per semester. To apply and sign-up for University Village apartments, students must have 45 or more completed academic credits. In order to move into University Village, students must have 60 or more completed academic credits or have completed 4 academic semesters at the University and be achieving satisfactory academic progress as defined by the University Bulletin.

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

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