Secure software lifecycle Sample Clauses

Secure software lifecycle a. Design Security Concepts: According to International Information System Security Certification Consortium (ISC)2, MDL recognizes that the following security principles have to be applied to the design of the solution: i. Defence in depth: multi-layers’ architecture (front-end/ backend/ middleware); ii. Economy of mechanisms: the software design and implementation shall be simple, in order to reduce the attack surface; iii. Least privilege: every process/service/person/entity shall be given only the minimum level of access rights; iv. Complete mediation: the solution must assure that security policies cannot be unintentionally or easily bypassed; b. A security document indicating the security configuration and implementation plan in line with the requirements defined in this Scope of Work shall be submitted as a deliverable by OEM.
Sample 1
AutoNDA by SimpleDocs

Related to Secure software lifecycle

  • Open Source Software The Software product may include certain open source components that are subject to open source licenses (“Open Source Software”), in which case, the embedded Open Source Software is owned by a third party. The Open Source Software is not subject to the terms and conditions of this XXXX. Instead, each item of Open Source Software is licensed under its applicable license terms which accompanies such Open Source Software. Nothing in this XXXX limits your rights under, nor grants you rights that supersede, the terms and conditions of any applicable license terms for the Open Source Software. Any fees charged by GC in connection with the SOFTWARE, do not apply to the Open Source Software for which fees may not be charged under the applicable license terms. The terms and conditions of the applicable license for the Open Source Software are available on the LICENSE.txt file, which is provided with the SOFTWARE.

  • Security of All Software Components Supplier will inventory all software components (including open source software) used in Deliverables, and provide such inventory to Accenture upon request. Supplier will assess whether any such components have any security defects or vulnerabilities that could lead to a Security Incident. Supplier will perform such assessment prior to providing Accenture with access to such software components and on an on-going basis thereafter during the term of the Agreement. Supplier will promptly notify Accenture of any identified security defect or vulnerability and remediate same in a timely manner. Supplier will promptly notify Accenture of its remediation plan. If remediation is not feasible in a timely manner, Supplier will replace the subject software component with a component that is not affected by a security defect or vulnerability and that does not reduce the overall functionality of the Deliverable(s).

  • Embedded Software To the extent any goods contain Embedded Software (defined below) that is not Buyer’s Property, no title to such Embedded Software shall pass to Buyer, and Supplier shall grant Buyer, its customers and all other users a non-exclusive worldwide, irrevocable, perpetual, royalty-free right to use, load, install, execute, demonstrate, market, test, resell, sublicense and distribute such Embedded Software as an integral part of such goods or for servicing the goods (the “Buyer-Required License”). If such Embedded Software or any part thereof is owned by a third party, prior to delivery, Supplier shall obtain the Buyer-Required License from such third-party owner. “Embedded Software” means software necessary for operation of goods and embedded in and delivered as an integral part of goods.

  • Third Party Software 1. The Software may contain third party software that requires and/or additional terms and conditions. Such required third party software notices and/or additional terms and conditions are located at xxxx://xxx.xxxxxxxxx.xxx/thirdparty/index.html and are made a part of and incorporated by reference into this XXXX. By accepting this XXXX, You are also accepting the additional terms and conditions, if any, set forth therein.

  • Software Upgrades All Software Releases (including all Error corrections made available pursuant to this Agreement) that RSA in its sole discretion: (a) deems to be logical improvements to the Software; (b) make generally available to all licensees of the Software; and (c) does not separately price or market.

  • Hardware and Software In order to use the Services, you must obtain and maintain, at your expense, compatible hardware and software as specified by Credit Union from time to time. Credit Union is not responsible for any third party software you may need to use the Services. Any such software is accepted by you as is and is subject to the terms and conditions of the software agreement you enter into directly with the third party software provider at time of download and installation.

  • Required hardware and software The minimum system requirements for using the DocuSign system may change over time. The current system requirements are found here: xxxxx://xxxxxxx.xxxxxxxx.xxx/guides/signer-guide- signing-system-requirements.

  • Software Updates XXXXX agrees to keep current with software licensed from Skyward and will install new versions on a timeline approved by XXXXX governance. This timeline will be communicated by NWRDC to the Districts.

  • Equipment and Software To use the Mobile Remote Deposit Services, you must obtain and maintain at your expense, compatible equipment and software that we may specify from time to time.

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

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