Patching Clause Samples

The Patching clause outlines the responsibilities and procedures for applying software updates, fixes, or patches to a system or application. Typically, it specifies which party is responsible for providing and installing patches, the timeframe for implementing critical updates, and any requirements for testing or notification before deployment. This clause ensures that vulnerabilities are addressed promptly, reducing security risks and maintaining the stability and reliability of the software.
POPULAR SAMPLE Copied 33 times
Patching. The Contractor must patch all Systems regularly in line with security best practices and ensure that current software, operating systems and application patching levels are maintained. The Contractor must ensure that all Systems have all patches installed on a regular schedule, within the time frame recommended by the manufacturer unless the Province otherwise consents in writing. The Contractor must ensure that vulnerabilities are remedied and patches installed on an accelerated basis for zero-day, critical and high vulnerabilities. For zero-day vulnerabilities, the Contractor must implement appropriate mitigation measures promptly on notification of the zero-day vulnerability. The Contractor must remediate zero-day, high and critical vulnerabilities through patching, decommission, or compensating controls. The Contractor must patch high vulnerabilities within 30 days or less of discovery and patch medium vulnerabilities within 90 days or less of discovery. The Contractor must ensure that a vulnerability scan is completed on components of all Systems: with any identified vulnerabilities remedied, before being placed into production; and on a regular schedule, set at a minimum of one scan per quarter, unless the Province otherwise consents in writing. The Contractor must ensure that a vulnerability scan is completed on any web applications used for Tenancy or in any other Systems: and on any major changes to such web applications, with any identified vulnerabilities remedied, before being placed into production; and on a regular schedule, set at a minimum of one scan per quarter, unless the Province otherwise consents in writing. The Contractor must ensure that all Systems servers: have antivirus and malware protection configured, active and enabled at all times; have antivirus and malware definitions updated at least once a day; and are configured to undergo a full anti-virus scan for latent infections (to detect infections missed by the real-time agent) at least once a week. The Contractor must ensure that all disposals of assets used in providing or relating to the Services are done in a secure manner that ensures that Protected Information cannot be recovered. The Contractor must have asset management and disposal Policies that are followed, and reviewed and updated regularly in line with security best practices, and that address hardware, software and other critical business assets. The Contractor must keep an asset management inventory that includes ...
Patching. The Contractor must patch all Systems regularly in line with security best practices and ensure that current software, operating systems and application patching levels are maintained.
Patching. PureCloud does not patch. The strategy is to destroy and rebuild all server instances at least every 30 days on new “gold images” that have current patch levels. Gold images are updated at least every two weeks with up-to-date security patches.
Patching. Repair surface defects such as spalls, bugholes, pitting or other voids in the surface by applying an appropriate leveler in one or multiple applications to fill the void until it is flush with the surface. Moist cure the patch when hot or dry weather conditions exist.
Patching. 14.1 The Supplier must, and must ensure that Subcontractors, treat any public releases of patches for vulnerabilities as follows: (a) the Supplier must patch any vulnerabilities classified as “critical”: (i) if it is technically feasible to do so, within 5 Working Days of the public release; or (ii) if it is technical feasible to patch the vulnerability but not technically feasible to do so as required by Paragraph 14.1(a)(i), then as soon as reasonably practicable after the public release; (b) the Supplier must patch any vulnerabilities classified as “important”: (i) if it is technically feasible to do so, within 1 month of the public release; or (ii) if it is technical feasible to patch the vulnerability but not technically feasible to do so as required by Paragraph 14.1(b)(i), then as soon as reasonably practicable after the public release; (c) the Supplier must remedy any vulnerabilities classified as “other” in the public release: (i) if it is technically feasible to do so, within 2 months of the public release; or (ii) if it is technical feasible to remedy the vulnerability but not technically feasible to do so as required by Paragraph 14.1(c)(i), then as soon as reasonably practicable after the public release; (d) where it is not technically feasible to patch the vulnerability, the Supplier must implement appropriate technical and organisational measures to mitigate the risk posed by the vulnerability.
Patching. Automatic software application updates (complete list available upon request). Patching does not include version or firmware updates unless otherwise indicated on the Sales Order.
Patching. A software patching process is in place to remedy vulnerabilities in a timely manner based on scans and assessments.
Patching. Where removals leave holes and damaged surfaces exposed in the finished work, patch and repair these holes and damaged surfaces to match adjacent finished surfaces. Where new work is to be applied to existing surfaces, perform removals and patching in a manner to produce surfaces suitable for receiving new work. Finished surfaces of patched area shall be flush with the adjacent existing surface and shall match the existing adjacent surface as closely as possible as to texture and finish.
Patching. ▇▇▇▇▇▇ maintains a vulnerability patch management process designed to identify and remediate vulnerabilities. ▇▇▇▇▇▇ regularly and periodically patches and/or takes other corrective actions to remediate known or discovered vulnerabilities to all components of the application stack in a commercially reasonable risk-based timeframe, giving greater priority to vulnerabilities with a higher severity rating.