Third-party and open source software is in scope of this policy. The owner of each product keeps a list of components and versions, checks it for publicly known vulnerabilities at least [monthly], and applies fixes within the window for the severity. A component with no available fix is handled under the exceptions clause.
Third-party patch management policy
A policy must name third-party and open source components, because operating system patching does not reach them. NIST SP 800-218 v1.1 PW.4.4 asks to verify acquired third-party and open source components "throughout their life cycles", and RV.1.1 to gather vulnerability information about them. Read 19 Nov 2026.
What the framework text asks
| Practice | Clause | Quote |
|---|---|---|
| Verify components through their life | SSDF PW.4.4 | "comply with the requirements, as defined by the organization, throughout their life cycles" |
| Check for unfixed public flaws | SSDF PW.4.4 example | "Regularly check whether there are publicly known vulnerabilities in the software modules and services that vendors have not yet fixed." |
| Gather information on components | SSDF RV.1.1 | "potential vulnerabilities in the software and third-party components that the software uses" |
| Pick a response | SSDF RV.2.2 | Decide whether each is remediated or "addressed through other means" |
Inventory first
CISA describes an SBOM as "a nested inventory, a list of ingredients that make up software components". CISA's SBOM page lists a 2026 update to the minimum elements; that guidance was not opened for this page. An SBOM answers the question a third-party clause depends on: which component, in which product, at which version.
- Browsers and plug-ins: name them as in scope and put them on the same window as the operating system. See browsers and third-party apps.
- Libraries inside your own software: belongs to the product team, not the endpoint team.
- Container base images: rebuilt, not patched in place; see containers and images.
- Components with no vendor fix: handled by the exceptions clause, with a review date.
Policy wording
The wording leaves the interval and the severity source for you. A directory of tools that patch third-party titles, with each vendor's own count, is in the tools directory; no count is given here because vendors define a title differently.
4.3 Patch windows
| Severity | Window3143090180 days |
|---|---|
| 1. Known exploited, internet-facing | 3 calendar daysApplies to: Systems reachable from the internet |
| 1. Known exploited, other | 14 calendar daysApplies to: All other systems |
| 2. Critical | 14 calendar days |
| 3. High | 30 calendar daysApplies to: All systems [set 14 if you hold Cyber Essentials] |
| 4. Medium | 90 calendar days |
| 5. Low | 180 calendar days |
| Routine baseline | Every month, or more oftenApplies to: Operating system and application updates |
No framework selected: every window above is the site template's suggested default, and the clock starts as this section states.
Sources
- NIST SP 800-218 v1.1, Secure Software Development Framework, PW.4.4, RV.1.1, RV.2.2, read 19 Nov 2026
- CISA, Software Bill of Materials, read 19 Nov 2026
Last reviewed 19 Nov 2026