Change and Configuration Management Sample Clauses

Change and Configuration Management. Maintaining policies and procedures for managing changes Provider makes to production systems, applications, and databases. Such policies and procedures include: a) A process for documenting, testing and approving the patching and maintenance of the Service; b) A security patching process that requires patching systems in a timely manner based on a risk analysis; and c) A process for Provider to utilize a third party to conduct web application-level security assessments. These assessments generally include testing, where applicable, for: i) Cross-site request forgery ii) Services scanning iii) Improper input handling (e.g., cross-site scripting, SQL injection, XML injection, cross-site flashing) iv) XML and SOAP attacks v) Weak session management vi) Data validation flaws and data model constraint inconsistencies
AutoNDA by SimpleDocs
Change and Configuration Management. Apttus will maintain policies and procedures for managing changes to production systems, applications, and databases, including: (a) a process for documenting, testing and approving the promotion of changes into production; and (b) acceptance testing and approval processes specifically related to standard bug fixes, updates, and upgrades made available for the Subscription Services.
Change and Configuration Management. Data importer maintains policies and procedures for managing changes to production systems, applications, and databases processing personal data and for documenting the changes.
Change and Configuration Management. Lusha implements and maintains policies and procedures for managing changes to production systems, applications, and databases, including without limitation, processes for documenting testing and approval of changes into production, security patching, and authentication.
Change and Configuration Management. Maintaining policies and procedures for managing changes Moveworks makes to production systems, applications, and databases. Such policies and procedures include: • process for documenting, testing and approving the patching and maintenance of the Moveworks Product; • A security patching process that requires patching systems in a timely manner based on a risk analysis; and • A process for Moveworks to utilize a third party to conduct application level security assessments. These assessments generally include testing, where applicable, for: • Cross-site request forgery • Services scanning • Improper input handling (e.g. cross-site scripting, SQL injection, XML injection, cross-site flashing) • XML and SOAP attacks o Weak session management o Data validation flaws and data model constraint inconsistencies o Insufficient authentication o Insufficient authorization
Change and Configuration Management. Abnormal has implemented and will maintain processes for managing changes and updates to production systems, applications, and databases, including without limitation, processes for documenting, testing, and approval of changes into production, security patching, and authentication.
Change and Configuration Management. Apttus will maintain policies and procedures for managing changes to production systems, applications, and databases, including: (a) a process for documenting, testing and approving the promotion of changes into production; (b) acceptance testing and approval processes specifically related to standard bug fixes, updates, and upgrades made available for the Subscription Services; (c) a process for Apttus to utilize a third party to conduct web application level security assessments. These assessments generally include testing for: (i) cross-site request forgery; (ii) improper input handling (e.g. cross-site scripting, SQL injection, XML injection, cross-site flashing); and (iii) insufficient authentication and authorization.
AutoNDA by SimpleDocs
Change and Configuration Management. Apttus will maintain policies and procedures for managing changes to production systems, applications, and databases, including: a process for documenting, testing and approving the promotion of changes into production; acceptance testing and approval processes specifically related to standard bug fixes, updates, and upgrades made available for the Subscription Services; a process for Apttus to utilize a third party to conduct web application level security assessments. These assessments generally include testing for: cross-site request forgery; improper input handling (e.g. cross-site scripting, SQL injection, XML injection, cross-site flashing); and insufficient authentication and authorization.
Change and Configuration Management. Even a small-size project like OPPORTUNITY may involve the necessity to re-configure the structure, scheduling or even part of the objectives during the project duration. Shall this be required, this will be undertaken under the initiative of the Steering Committee, and the EC Project Officer will immediately be informed. These changes would have for objective to maximize the project's overall success.
Change and Configuration Management. FloQast maintains policies and procedures for managing changes to production systems, applications, and databases. Such policies and procedures include: a. A process for documenting, testing and approving the promotion of changes into production; b. A security patching process that requires patching systems in a timely manner based on a risk analysis; and c. A process for FloQast to perform security assessments of changes into production.
Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!