# Third-Party Application Patching and Browsers

Canonical: https://patchmanagementpolicy.com/patching/browsers-and-third-party-apps/
Last reviewed: 19 Nov 2026

## Third party application patching

Third-party applications need their own patch window because no single operating system tool covers them. Chrome shipped a desktop stable update on 17 Nov 2026, and CIS Controls v8 safeguard 7.4 asks for application updates through automated patch management “on a monthly, or more frequent, basis.” Read 19 Nov 2026.

### Browsers: a rhythm measured in days

Google's Chrome Releases blog showed a Stable Channel Update for Desktop dated Tuesday, 17 Nov 2026 ([Chrome Releases](https://chromereleases.googleblog.com/)). Google's enterprise help page describes five channels and says the Stable channel “is updated every 2 weeks for major releases,” the Extended Stable channel every 8 weeks, with Extended Stable users still receiving security fixes ([Chrome Enterprise Help](https://support.google.com/chrome/a/answer/9027636)). It advises keeping 5% of users on Beta, which gets a two-week preview. Those are Google's statements on the page as read on 19 Nov 2026; Firefox's release calendar and Adobe's security bulletin pages could not be read from this environment on that date and are not described here.

A policy for browsers should therefore state a window in days, not in months, and say whether a managed browser may auto-update outside the change window. The question of which channel a group uses is also a maintenance-group decision (see [assess and prioritize](https://patchmanagementpolicy.com/process/assess-and-prioritize/)).

### What the standards say about applications

| Source | Text | Consequence for the policy |
|---|---|---|
| CIS Controls v8, safeguard 7.4 (August 2023 guide) | “Perform application updates on enterprise assets through automated patch management on a monthly, or more frequent, basis.” | A written cadence of at most a month for applications, by automated tooling |
| NIST SP 800-218 (SSDF) PW.4.4 | Verify that acquired commercial, open-source and other third-party components comply with the organization's requirements throughout their life cycles | Components are checked over time, not once at purchase |
| NIST SP 800-218 RV.1.1 | Gather information from acquirers, users and public sources on vulnerabilities in the software and its third-party components | Monitoring includes the libraries inside products, not only the products |
| AWS Patch Manager, Windows OS-Applications baseline | For applications released by Microsoft it approves all patches, auto-approved 7 days after release or update | Microsoft applications can ride the same tool; other vendors need their own source |

Sources: CIS Controls v8 PDF, NIST SP 800-218 v1.1 PDF, AWS documentation, read 19 Nov 2026. CIS v8.1 wording was not read.

### Finding what is installed

The usual failure is the application nobody listed. NIST's inventory advice applies in full: keep a software inventory per asset down to package level, and use an SBOM from the vendor where one exists. For open source libraries inside your own software, see the [third-party and open source patching guide](https://patchmanagementpolicy.com/guides/third-party-and-open-source-patching/). The inventory step is [step 1](https://patchmanagementpolicy.com/process/inventory/).

### Testing, rollback and evidence

- Test on the pilot group in the week of release; applications with plug-ins and macros need the longest.
- Keep the previous installer version in the repository for rollback; a browser rollback also needs the profile policy to allow an older version.
- Evidence: application version per asset with date, the channel assigned to each group, and the list of unmanaged installs found and their disposition.

### Sources

- [Chrome Releases blog](https://chromereleases.googleblog.com/), read 19 Nov 2026
- [Google Chrome Enterprise Help, release channels](https://support.google.com/chrome/a/answer/9027636), read 19 Nov 2026
- [CIS Controls v8 (August 2023 guide), safeguard 7.4](https://storage.pardot.com/799323/1693938137QgfIAdmE/CIS_Controls__v8__Critical_Security_Controls__2023_08.pdf), read 19 Nov 2026
- [NIST SP 800-218 (SSDF) v1.1](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf), read 19 Nov 2026
- [AWS Systems Manager, predefined and custom patch baselines](https://docs.aws.amazon.com/systems-manager/latest/userguide/patch-manager-predefined-and-custom-patch-baselines.html), read 19 Nov 2026

Last reviewed 19 Nov 2026

### Related pages

- [Third-Party and Open Source Patching in a Policy](https://patchmanagementpolicy.com/guides/third-party-and-open-source-patching/)
- [Step 1: Patch Management Asset Inventory](https://patchmanagementpolicy.com/process/inventory/)
- [CIS Control 7: Monthly Patching Safeguards 7.1 to 7.7](https://patchmanagementpolicy.com/patch-windows/cis-control-7/)
- [Step 3: How to Prioritize Patches by Risk Response](https://patchmanagementpolicy.com/process/assess-and-prioritize/)
