Software Development and Maintenance Sample Clauses

Software Development and Maintenance. A. Secure Development Lifecycle i. Applies secure development lifecycle practices, including, during design, development, and test cycles. ii. Ensures that products are subject to security design review including threat considerations and data handling practices. iii. Ensures that Services are subject to a secure release review prior to promotion to production. B. Security Testing i. Performs rigorous security testing, including, as technically feasible: a. static code analysis. b. source code peer reviews . c. dynamic and interactive security testing. d. security logic, or security “QA” testing. ii. Ensures that Internet-facing applications are subject to application security assessment reviews and testing to identify common security vulnerabilities as identified by industry-recognized organizations (e.g., OWASP Top 10 Vulnerabilities, CWE/SANS Top 25 vulnerabilities). iii. For all mobile applications (i.e. running on Android, Blackberry, iOS, Windows Phone) that collect, transmit or display Protected Data, conducts an application security assessment review to identify and remediate industry-recognized vulnerabilities specific to mobile applications. iv. Does NOT use Protected Data for testing. v. Makes all reasonable effort to identify and remediate software vulnerabilities prior to release . C. Annual Penetration Testing i. Engages qualified, independent third-party penetration testers to perform annual penetration test against its Products and environments where Protected Data is hosted. ii. Requires sub-processors to perform similar penetration testing against their systems, environments, and networks. iii. Ensures remediation of all findings in a commercially reasonable period of time. D. Product Vulnerability Management i. Uses commercially reasonable efforts to regularly identify software security vulnerabilities in RingCentral Services. ii. Provides relevant updates, upgrades, and bug fixes for known software security vulnerabilities, for any software provided or in which any Protected Data is processed. iii. Ensures that all findings resulting from internal and external testing are evaluated according to industry best practices, including CVSS score and assessment of impact, likelihood and severity and are remediated following industry standard timelines.
Software Development and Maintenance. APPLIED INFORMATICS shall ensure the ongoing development and maintenance of SOFTWARE, to keep SOFTWARE in commercial-quality shape and form. This includes providing timely fixes to reported issues, as well as implementing new features, as requested by SPONSOR or other users of SOFTWARE.
Software Development and Maintenance. All Software developed by Provider under this Exhibit is subject to the terms of the Technology License Agreement.
Software Development and Maintenance. The contractor shall perform the following support services tasking for AIR 4.
Software Development and Maintenance. BMT will oversee, develop and implement any technology and software development, improvement, update, addition or other revision required by TMO under the PLBPA or any Bank Regulator, and BMT will bear any and all costs therefor. Without limiting the foregoing, BMT shall be responsible for the costs of any technology enhancement credit or reduction in any maintenance fees under the PLBPA. BMT shall be responsible for performing all software maintenance. Any and all material changes to any software of other technology supporting the Depositor Program must be preapproved in writing by Bank.
Software Development and Maintenance. ● Consultant will utilize a modified agile approach to software development and maintenance. ● Consultant will regularly scan applications with the Open Web Application Security Project’s (“OWASP”) Zed Attack Proxy (“ZAP”) tool to detect potential weaknesses in security and investigate any discovered weaknesses to identify and remediate security vulnerabilities. ● Consultant will review new software updates and system libraries monthly and assess whether these updates or patches are adequate to fix potential vulnerabilities within the software.