SOFTWARE INTEGRITY CONTROLS Sample Clauses

SOFTWARE INTEGRITY CONTROLS. The Contractor and the State recognize the serious threat of fraud, misuse, and destruction or theft of data or funding. These threats could be introduced when unauthorized or inappropriate modifications are made to a production system. The Contractor shall implement the following controls for the purpose of 1) The Contractor shall configure at least three software environments including a development environment, a testing environment and a production environment. 2) The Contractor shall implement a change control procedure such that activities in the development environment remain separate and distinct from the production environment. In particular the change control procedure shall incorporate at least the following: a) Segregate duties between development and testing of software changes and migration of changes to the production environment; b) Implement security controls to restrict individuals who have development or testing responsibilities from migrating changes to the production environment. c) Include a process to log and review all source control activities. 3) The Contractor shall implement a source control tool to confirm that all changes made to the production system are authorized, tested, and approved before migration to the production environment. 4) The parties acknowledge that the Contractor shall use its personnel associated with its Global Delivery Network to perform Services (“GDN Services”) under this SOW, including personnel located outside of the United States. Such GDN Services will be performed only by the Contractor’s personnel assigned and approved to work on the Project. The State and the Contractor will together determine how to provide personnel performing GDN Services with access to State email, SharePoint, test environments, and other resources as may be reasonably necessary to enable performance of the GDN Services.
Sample 1
AutoNDA by SimpleDocs
SOFTWARE INTEGRITY CONTROLS. The Contractor and the State recognize the serious threat of fraud, misuse, and destruction or theft of data or funding. These threats could be introduced when unauthorized or inappropriate modifications are made to a production system. The Contractor shall implement the following controls for the purpose of maintaining software integrity and traceability throughout the software creation life cycle, including during development, testing, and production: 1) The Contractor shall configure at least three software environments including a development environment, a testing environment and a production environment. 2) The Contractor shall implement a change control procedure such that activities in the development environment remain separate and distinct from the production environment. In particular the change control procedure shall incorporate at least the following: a) Segregate duties between development and testing of software changes and migration of changes to the production environment; b) Implement security controls to restrict individuals who have development or testing responsibilities from migrating changes to the production environment. State of California California Department of Public Health c) Include a process to log and review all source control activities. 3) The Contractor shall implement a source control tool to confirm that all changes made to the production system are authorized, tested, and approved before migration to the production environment. 4) The parties acknowledge that the Contractor shall use its personnel associated with its Global Delivery Network to perform Services (“GDN Services”) under this SOW, including personnel located outside of the United States. Such GDN Services will be performed only by the Contractor’s personnel assigned and approved to work on the Project. The State and the Contractor will together determine how to provide personnel performing GDN Services with access to State email, SharePoint, test environments, and other resources as may be reasonably necessary to enable performance of the GDN Services.
Sample 1
SOFTWARE INTEGRITY CONTROLS. Harmony and EOHHS recognize the serious threat of fraud, misuse, and destruction or theft of data or funding. These threats could be introduced when unauthorized or inappropriate modifications are made to a production system. In the event Harmony is requested to develop, test, and/or produce new software for EOHHS, Harmony shall implement the following controls for the purpose of maintaining software integrity and traceability throughout the software creation life cycle, including during development, testing, and production: 5.3.1 Harmony shall configure at least two software environments including a development/quality assurance (QA) environment and a production environment. 5.3.2 Harmony shall implement a change management procedure to ensure that activities in the development/QA environment remain separate and distinct from the production environment. In particular the change management procedure shall incorporate at least the following: 5.3.2.1 Reasonable segregation of duties and oversight controls, including, where appropriate, between development and testing of software changes and/or migration of changes to the production environment; 5.3.2.2 Segregated testing responsibilities for workers performing testing so that testers do not have access to update the production environment; 5.3.2.3 Implements security controls to provide a higher level of oversight for situations where individuals having development skills and responsibilities are appointed to implement approved changes to the production environment; 5.3.2.4 Includes a process to log and review all source control activities. 5.3.3 Harmony shall implement a source control tool to ensure that all changes made to the production system are authorized, tested, and approved before migration to the production environment. 5.3.4 Harmony shall not make any development or code changes in a production environment, except as specifically requested and authorized by EOHHS or in emergency situations. 5.3.5 With respect to EOHHS data and within the scope of this Agreement, Harmony shall implement additional internal controls as later negotiated by the Parties. 5.3.6 Harmony reserves the right, without EOHHS approval or input, to implement administrative, technical, and physical controls over non-EOHHS data, non- EOHHS-related operations, and non-EOHHS-related systems as it deems necessary in order to assure its performance under other agreement(s) and regulation(s).
Sample 1

Related to SOFTWARE INTEGRITY CONTROLS

  • Data Integrity Control Personal Data will remain intact, complete and current during processing activities.

  • Quality control system (i) The Contractor shall establish a quality control mechanism to ensure compliance with the provisions of this Agreement (the “Quality Assurance Plan” or “QAP”). (ii) The Contractor shall, within 30 (thirty) days of the Appointed Date, submit to the Authority’s Engineer its Quality Assurance Plan which shall include the following: (a) organisation, duties and responsibilities, procedures, inspections and documentation; (b) quality control mechanism including sampling and testing of Materials, test frequencies, standards, acceptance criteria, testing facilities, reporting, recording and interpretation of test results, approvals, check list for site activities, and proforma for testing and calibration in accordance with the Specifications for Road and Bridge Works issued by MORTH, relevant IRC specifications and Good Industry Practice; and (c) internal quality audit system. The Authority’s Engineer shall convey its approval to the Contractor within a period of 21 (twenty-one) days of receipt of the QAP stating the modifications, if any, required, and the Contractor shall incorporate those in the QAP to the extent required for conforming with the provisions of this Clause 11.2. (iii) The Contractor shall procure all documents, apparatus and instruments, fuel, consumables, water, electricity, labour, Materials, samples, and qualified personnel as are necessary for examining and testing the Project Assets and workmanship in accordance with the Quality Assurance Plan. (iv) The cost of testing of Construction, Materials and workmanship under this Article 11 shall be borne by the Contractor.

  • Security Controls Annually, upon Fund’s reasonable request, DST shall provide Fund’s Chief Information Security Officer or his or her designee with a summary of its corporate information security policy and an opportunity to discuss DST’s information security measures, and a high level and non-confidential summary of any penetration testing related to the provision of in-scope services . DST shall review its Security Policy annually.

  • Program Integrity The state must have processes in place to ensure that there is no duplication of federal funding for any aspect of the demonstration.

  • Data Integrity Policies and procedures to ensure the confidentiality, integrity, and availability of Customer Data or Professional Services Data and protect it from disclosure, improper alteration, or destruction.

  • Evaluation Software If the Software is an evaluation version or is provided to You for evaluation purposes, then, unless otherwise approved in writing by an authorized representative of Licensor, Your license to use the Software is limited solely for internal evaluation purposes in non-production use and in accordance with the terms of the evaluation offering under which You received the Software, and expires 90 days from installation (or such other period as may be indicated within the Software). Upon expiration of the evaluation period, You must discontinue use of the Software, return to an original state any actions performed by the Software, and delete the Software entirely from Your system and You may not download the Software again unless approved in writing by an authorized representative of Licensor. The Software may contain an automatic disabling mechanism that prevents its use after a certain period of time. RESTRICTIONS

  • Infrastructure Infrastructure serves as the foundation and building blocks of an integrated IT solution. It is the hardware which supports Application Services (C.3.2) and IT Management Services (C.3.3); the software and services which enable that hardware to function; and the hardware, software, and services which allow for secure communication and interoperability between all business and application service components. Infrastructure services facilitate the development and maintenance of critical IT infrastructures required to support Federal government business operations. This section includes the technical framework components that make up integrated IT solutions. One or any combination of these components may be used to deliver IT solutions intended to perform a wide array of functions which allow agencies to deliver services to their customers (or users), whether internal or external, in an efficient and effective manner. Infrastructure includes hardware, software, licensing, technical support, and warranty services from third party sources, as well as technological refreshment and enhancements for that hardware and software. This section is aligned with the FEA/DoDEA Technical Reference Model (TRM) which describes these components using a vocabulary that is common throughout the entire Federal government. A detailed review of the TRM is provided in Section J, Attachment 5. Infrastructure includes complete life cycle support for all hardware, software, and services represented above, including planning, analysis, research and development, design, development, integration and testing, implementation, operations and maintenance, information assurance, and final disposition of these components. The services also include administration and help desk functions necessary to support the IT infrastructure (e.g., desktop support, network administration). Infrastructure components of an integrated IT solution can be categorized as follows:

  • CONTROL SYSTEM (a) SELLER shall provide and maintain a quality control system to an industry recognized Quality Standard and in compliance with any other specific quality requirements identified in this Contract. (b) Records of all quality control inspection work by SELLER shall be kept complete and available to LOCKHEED XXXXXX and its customers.

  • Hardware and Software Requirements In order to access and retain Disclosures electronically, you must satisfy the following computer hardware and software requirements: access to the Internet; an email account and related software capable of receiving email through the Internet; a web browser which is SSL-compliant and supports secure sessions, and hardware capable of running this software.

  • Systems The details of any systems work will be determined after a thorough business analysis. System's work will be billed on a time and material basis. Investors Bank provides an allowance of 10 systems hours for data extract set up and reporting extract set up. Additional hours will be billed on a time and material basis.

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