# Patch Management Policy > Build a patch management policy from clauses read on 19 Nov 2026: CISA BOD 26-04 (3, 14, 60 days), Cyber Essentials v3.3 (14 days), PCI SSC (one month). ## Builder and templates - [Patch Management Policy Template Set, 10 Documents](https://patchmanagementpolicy.com/templates/index.md): Ten free patch management policy templates: a general policy, seven variants, a procedure and an exceptions clause. Each window cites its clause (19 Nov 2026). - [General Patch Management Policy Template, Full Text](https://patchmanagementpolicy.com/templates/patch-management-policy-template/index.md): Full text of a general patch management policy: nine sections, windows of 3, 14, 30, 90 and 180 days, each traced to a framework clause or marked as a default. - [Small Business Patch Management Policy Template](https://patchmanagementpolicy.com/templates/small-business/index.md): A patch policy for a company under 50 people with no security staff: one 14 day window from Cyber Essentials v3.3, monthly checks, full text, read 19 Nov 2026. - [SaaS Company Patch Management Policy Template](https://patchmanagementpolicy.com/templates/saas-company/index.md): A patch policy variant for cloud-first software companies: images rebuilt not patched, managed-service split, live patching limits, evidence. Read 19 Nov 2026. - [Enterprise Patch Management Policy Template](https://patchmanagementpolicy.com/templates/enterprise/index.md): An enterprise patch policy variant: maintenance groups, rings, delegated sign-off, inventory in several systems, windows by group importance. Read 19 Nov 2026. - [HIPAA Patch Management Policy Template](https://patchmanagementpolicy.com/templates/healthcare-hipaa/index.md): HIPAA patch policy variant: the current rule sets no deadline, the 6 Jan 2025 proposal would set 15 and 30 days; both written clearly. Read 19 Nov 2026. - [PCI DSS Patch Management Policy Template](https://patchmanagementpolicy.com/templates/payment-card-pci-dss/index.md): PCI DSS patch policy variant: critical vulnerabilities within one month of release (PCI SSC FAQ 1597, 6.3.3), plus a stricter 14 day standard. Read 19 Nov 2026. - [FedRAMP Patch Management Policy Template](https://patchmanagementpolicy.com/templates/federal-contractor-fedramp/index.md): FedRAMP patch policy variant: 2026 VDR timeframes by class, the KEV due-date rule, legacy 30, 90 and 180 days, and the mandatory date of 7 Dec 2026. - [MSP Patch Management Policy Template](https://patchmanagementpolicy.com/templates/managed-service-provider/index.md): Patch policy variant for managed service providers: client consent, per-client windows and evidence, and the EU rules that name MSPs. Read 19 Nov 2026. - [Patch Management Procedure Template, Nine Steps](https://patchmanagementpolicy.com/templates/patch-management-procedure/index.md): A patch management procedure template in nine steps: who does each, what to do and the record each step leaves, with the November 2026 cycle dates worked out. - [Patch Management Policy Exceptions Clause Template](https://patchmanagementpolicy.com/templates/patch-exceptions-clause/index.md): The exceptions clause of a patch policy in full: five grounds, seven required request fields, two signers, 90 day maximum, 30 day re-check. Read 19 Nov 2026. - [How the Patch Policy Templates Were Written](https://patchmanagementpolicy.com/templates/method/index.md): How the patch policy templates were built: 38 clause rows read on 19 Nov 2026, 5 left empty because text was unreadable, and what is the site's own drafting. - [Patch Window Table: Deadlines in 12 Frameworks](https://patchmanagementpolicy.com/patch-windows/index.md): Patch deadlines by framework in one table: CISA BOD 26-04, PCI DSS, FedRAMP, Cyber Essentials, HIPAA, NIS2, DORA. 37 rows with clause and source. - [Patch Management Policy Builder and Templates](https://patchmanagementpolicy.com/index.md): Build a patch management policy from clauses read on 19 Nov 2026: CISA BOD 26-04 (3, 14, 60 days), Cyber Essentials v3.3 (14 days), PCI SSC (one month). ## Policy sections - [Purpose and Scope of a Patch Management Policy](https://patchmanagementpolicy.com/policy-sections/purpose-and-scope/index.md): How to write the scope clause of a patch policy: Cyber Essentials names ten categories, BOD 26-04 excludes national security systems. Sample wording. - [Patch Management Roles and Responsibilities](https://patchmanagementpolicy.com/policy-sections/roles-and-responsibilities/index.md): Who owns, runs, approves, installs and escalates in a patch policy: six roles, a duty table, sample wording, and NIST's seven metric audiences. Read 19 Nov 2026 - [Asset Inventory Requirement in a Patch Policy](https://patchmanagementpolicy.com/policy-sections/asset-inventory-requirement/index.md): What the inventory clause of a patch policy must record: NIST SP 800-40r4 characteristics, why monthly scans fall short, sample wording. Read 19 Nov 2026. - [Severity and Patch Windows: What Each Framework Sets](https://patchmanagementpolicy.com/policy-sections/severity-and-patch-windows/index.md): Patch SLA wording by severity: 14 days (Cyber Essentials), 15 and 30 (HIPAA proposal), one month (PCI), BOD 26-04's 3, 14 and 60 days. Clauses read 19 Nov 2026. - [Patch Testing and Staging Policy Clause](https://patchmanagementpolicy.com/policy-sections/testing-and-staging/index.md): How to write the testing clause of a patch policy: canary rounds of a few days then weeks, rollback in writing, evidence kept. NIST and NIS2 read 19 Nov 2026 - [Patch Maintenance Window Policy Clause](https://patchmanagementpolicy.com/policy-sections/maintenance-windows/index.md): How to write the maintenance window clause of a patch policy: Patch Tuesday dates to Feb 2027, window frequency against 14 and 30 day deadlines (19 Nov 2026) - [Patch Management Metrics: What the Policy Should Report](https://patchmanagementpolicy.com/policy-sections/reporting-and-metrics/index.md): What a patch policy's reporting clause should measure: NIST's matrix of share patched by deadline, mean and median days, by asset and vulnerability tier. - [Patch Management Policy Approval and Revision](https://patchmanagementpolicy.com/policy-sections/review-and-approval/index.md): How often to revise a patch policy and what forces an earlier revision: 12 months (HIPAA proposal), annual (CIS 7.1), and dated framework changes to Dec 2026. - [Emergency Patch Policy Clause for a Patch Policy](https://patchmanagementpolicy.com/policy-sections/emergency-patch-clause/index.md): How to write the emergency clause of a patch policy: triggers, who declares, what is suspended, how it ends. KEV had 1,786 entries on 18 Nov 2026. ## Patch windows by framework - [CISA BOD 26-04 Remediation Timelines, Row by Row](https://patchmanagementpolicy.com/patch-windows/cisa-bod-26-04/index.md): CISA BOD 26-04 (10 Jun 2026) sets 3, 14 and 60 day deadlines or fix on upgrade across 16 rows. Every row, the clock and the phases, read 19 Nov 2026. - [NIST SP 800-40 Rev. 4: What It Sets for Patch Timing](https://patchmanagementpolicy.com/patch-windows/nist-sp-800-40/index.md): NIST SP 800-40 Rev. 4 (April 2022) sets no day count: it asks for maintenance groups, plans per scenario and exceptions reviewed regularly. Read 19 Nov 2026. - [CIS Control 7: Monthly Patching Safeguards 7.1 to 7.7](https://patchmanagementpolicy.com/patch-windows/cis-control-7/index.md): CIS Controls v8 Control 7 sets monthly or more frequent patching (7.3, 7.4, 7.7) and scanning cadences, with no severity tiers. Safeguards quoted, 19 Nov 2026. - [PCI DSS v4.0.1 Patching: One Month for Critical Flaws](https://patchmanagementpolicy.com/patch-windows/pci-dss/index.md): PCI DSS v4.0.1 Requirement 6.3.3 gives critical vulnerabilities one month from release; others follow the entity's risk analysis. PCI SSC sources, 19 Nov 2026. - [HIPAA Patch Rules: In Force Text and the 15/30 Day Proposal](https://patchmanagementpolicy.com/patch-windows/hipaa-security-rule/index.md): The in-force HIPAA Security Rule sets no patch deadline; the 6 Jan 2025 proposal would add 15 days (critical) and 30 days (high). Not final as of 19 Nov 2026. - [FedRAMP 2026 Patch Timeframes: 12 Hours to 192 Days](https://patchmanagementpolicy.com/patch-windows/fedramp/index.md): FedRAMP's 2026 Vulnerability Detection and Response rules set maximum timeframes from 12 hours to 192 days by Class, mandatory 7 Dec 2026. Read 19 Nov 2026. - [Cyber Essentials 14 Day Patching Rule (v3.3, April 2026)](https://patchmanagementpolicy.com/patch-windows/cyber-essentials/index.md): UK Cyber Essentials v3.3 requires updates for critical or high-risk flaws within 14 days of release, CVSS 7 or above, effective 27 Apr 2026. Read 19 Nov 2026. - [NIS2 Patch Management: Point 6.6 of Regulation 2024/2690](https://patchmanagementpolicy.com/patch-windows/nis2/index.md): NIS2 Implementing Regulation 2024/2690, point 6.6, requires patches within a reasonable time, tested first, with a documented derogation. Read 19 Nov 2026. - [DORA Patch Management: Article 10 of RTS 2024/1774](https://patchmanagementpolicy.com/patch-windows/dora/index.md): DORA's technical standard (Delegated Regulation 2024/1774, Article 10) has financial entities set their own patch deadlines and scan critical assets weekly. - [NYDFS Part 500.5: Timely Remediation, No Day Count](https://patchmanagementpolicy.com/patch-windows/nydfs-part-500/index.md): NYDFS 23 NYCRR 500.5(c), as amended effective 1 Nov 2023, requires timely remediation prioritized by risk and sets no number of days. Read 19 Nov 2026. ## Process - [Patch Management Process in 9 Steps (NIST SP 800-40r4)](https://patchmanagementpolicy.com/process/index.md): The patch management process as nine steps, from inventory to the cycle check, mapped to NIST SP 800-40 Rev. 4 sections, with the record each step leaves. - [Step 1: Patch Management Asset Inventory](https://patchmanagementpolicy.com/process/inventory/index.md): Step 1 of the patch process: what the inventory must hold per asset (NIST SP 800-40r4 section 3.2), why scan-based monthly updates fail, and the record to keep. - [Step 2: How to Track Vendor Patch Releases](https://patchmanagementpolicy.com/process/monitor-for-releases/index.md): Step 2 of the patch process: the next vendor release dates (Microsoft, Fortinet, Oracle, Android, Cisco, Kubernetes) and the CISA KEV feed, read 19 Nov 2026. - [Step 3: How to Prioritize Patches by Risk Response](https://patchmanagementpolicy.com/process/assess-and-prioritize/index.md): Step 3 of the patch process: choose accept, mitigate, transfer or avoid, then set speed with the four variables in CISA BOD 26-04. Read 19 Nov 2026. - [Step 4: Patch Testing Process with Canary Rings](https://patchmanagementpolicy.com/process/acquire-and-test/index.md): Step 4 of the patch process: validate authenticity, test with canary rings of days then weeks, and use vendor pause and preview controls. Read 19 Nov 2026. - [Step 5: Patch Approval Process and Scheduling](https://patchmanagementpolicy.com/process/approve-and-schedule/index.md): Step 5 of the patch process: change approval, maintenance window, forced install after a grace period, and the scheduling controls in Intune and Azure. - [Step 6: Patch Deployment Process and Rollback](https://patchmanagementpolicy.com/process/deploy/index.md): Step 6 of the patch process: distribute, install, restart and resolve issues in stages, with the rollback each tool really offers. Read 19 Nov 2026. - [Step 7: How to Verify Patches Are Installed](https://patchmanagementpolicy.com/process/verify/index.md): Step 7 of the patch process: confirm a patch is installed and in effect and stays installed; AWS counts INSTALLED_PENDING_REBOOT as compliant. Read 19 Nov 2026. - [Step 8: Patch Management Report Contents](https://patchmanagementpolicy.com/process/report/index.md): Step 8 of the patch process: what a patch report must contain, why NIST calls a single percentage not actionable, and a report template. Read 19 Nov 2026. - [Step 9: Patch Management Process Improvement](https://patchmanagementpolicy.com/process/review-the-cycle/index.md): Step 9 of the patch process: recheck exceptions, deadlines and groups on a stated cycle; BOD 26-04 reassesses yearly and a HIPAA proposal says 12 months. ## Patching by asset type - [Windows Patch Management Policy: Windows Rhythm](https://patchmanagementpolicy.com/patching/windows-endpoints/index.md): Windows patching: second-Tuesday release, the optional preview, out-of-band updates, Intune rings and rollback, and AWS 7-day baselines for Windows Server. - [macOS Patch Management: Three Lines at Once](https://patchmanagementpolicy.com/patching/macos/index.md): macOS patching: Apple's security releases page lists three macOS lines patched on 9 Nov 2026, plus Intune enforcement and the AWS macOS baseline. - [Linux Patch Management Policy by Distribution](https://patchmanagementpolicy.com/patching/linux-servers/index.md): Linux patching: Red Hat's four-point severity scale and errata types, Ubuntu's daily unattended upgrades, and how AWS baselines treat each distribution. - [Network Device Patch Management and Firmware](https://patchmanagementpolicy.com/patching/network-devices-and-firmware/index.md): Network device patching: Cisco's bundled advisory dates (Feb, Mar, Aug, Sep), Fortinet's second-Tuesday advisories and its severity-to-branch table. - [Third-Party Application Patching and Browsers](https://patchmanagementpolicy.com/patching/browsers-and-third-party-apps/index.md): Third-party app patching: Chrome's channels and its 17 Nov 2026 stable update, CIS safeguard 7.4 (monthly or faster), and NIST SSDF on third-party components. - [Container Image Patching: Rebuild, Do Not Patch](https://patchmanagementpolicy.com/patching/containers-and-images/index.md): Container patching: rebuild and redeploy images instead of patching running containers; Kubernetes monthly patch releases and 14-month support windows. - [Cloud Patch Management: AWS and Azure VMs](https://patchmanagementpolicy.com/patching/cloud-virtual-machines/index.md): Cloud VM patching: AWS Patch Manager methods, baselines and compliance states, Azure Update Manager schedules and limits, and shared responsibility. - [Database Patch Management: Oracle, SQL Server](https://patchmanagementpolicy.com/patching/databases/index.md): Database patching: Oracle's four Critical Patch Update dates (next 19 Jan 2027), revisions after release, PostgreSQL minor releases and SQL Server support. - [Mobile Device Patch Management: Android, iOS](https://patchmanagementpolicy.com/patching/mobile-devices/index.md): Mobile patching: Android bulletins on the first Monday with two patch levels, Apple fixes for three iOS lines on 9 Nov 2026, and Intune deferral policies. - [OT Patch Management Policy and Medical Devices](https://patchmanagementpolicy.com/patching/ot-and-medical-devices/index.md): OT and medical device patching: NIST SP 800-82r3 on testing and planned outages, FDA 30 and 60 day manufacturer timelines, routine patches not reportable. - [Patching Systems That Cannot Be Rebooted](https://patchmanagementpolicy.com/patching/systems-that-cannot-reboot/index.md): No-reboot patching: Windows Server hotpatch (4 baselines, 8 hotpatches a year), Ubuntu Livepatch, Red Hat live kernel patches and their limits. ## Guides - [What a Patch Management Policy Is and Must State](https://patchmanagementpolicy.com/guides/what-is-a-patch-management-policy/index.md): A patch management policy is the written authority for patching: scope, roles, deadlines, exceptions, revision. What NIST, DORA, NIS2 and CIS ask it to hold. - [How to Write a Patch Management Policy in 9 Sections](https://patchmanagementpolicy.com/guides/how-to-write-a-patch-management-policy/index.md): Nine sections in order, each tied to a clause read on 19 Nov 2026: NIST maintenance groups, Cyber Essentials 14 days, DORA escalation. Skeleton included. - [The Patch Management Lifecycle: Five Verbs From NIST](https://patchmanagementpolicy.com/guides/patch-management-lifecycle/index.md): NIST SP 800-40 Rev. 4 defines patch management as identify, prioritize, acquire, install, verify. Each phase, the second step, and the process page for it. - [Patch Management vs Vulnerability Management Compared](https://patchmanagementpolicy.com/guides/patch-management-vs-vulnerability-management/index.md): Patching installs a fix; vulnerability management decides what a finding needs. Differences by question, with NIST, SSDF and CIS Control 7 clauses. - [Hotfix vs Patch: What NIST's Glossary Says](https://patchmanagementpolicy.com/guides/hotfix-vs-patch/index.md): NIST's glossary calls a hotfix Microsoft's term for patch, and gives two definitions of patch. The one-line definition a policy needs. Read 19 Nov 2026. - [How Often to Patch: Cadences From the Clauses Read](https://patchmanagementpolicy.com/guides/how-often-to-patch/index.md): Monthly (CIS 7.3), 14 days of release (Cyber Essentials v3.3), one month (PCI SSC FAQ 1597), 3, 14 or 60 days (BOD 26-04). Patch Tuesday dates through Feb 2027. - [Proving Patch Compliance to an Auditor: the Evidence](https://patchmanagementpolicy.com/guides/proving-patch-compliance-to-an-auditor/index.md): What a patch compliance report must show to be checked: asset, release date, install date, severity source, exception ID. Clauses read 19 Nov 2026. - [Patch Compliance Rate: Formula, Denominators, Clocks](https://patchmanagementpolicy.com/guides/patch-compliance-rate/index.md): Patch compliance rate is assets patched within deadline over assets due. Three variants, a worked example (940 of 1,000) and why clocks differ by framework. - [Third-Party and Open Source Patching in a Policy](https://patchmanagementpolicy.com/guides/third-party-and-open-source-patching/index.md): Browsers, plug-ins, libraries and containers need their own clause. NIST SP 800-218 PW.4.4 and RV.1.1, CISA's SBOM definition and wording, read 19 Nov 2026. - [Automated Patch Management: Defaults a Policy Must Set](https://patchmanagementpolicy.com/guides/automated-patch-management/index.md): AWS, Azure and Windows Autopatch ship default approval delays and severity filters: 7 days, 30 days, 0 to 30 days. The policy lines each default touches. - [What Is Patch Management? Definition and Scale in 2026](https://patchmanagementpolicy.com/guides/what-is-patch-management/index.md): NIST defines patch management as identify, prioritize, acquire, install, verify. Scale on 19 Nov 2026: 1,786 KEV entries, 49,972 CVE records in 2025. - [Patch Management Program: Six Groups and What Proves Each](https://patchmanagementpolicy.com/guides/patch-management-program/index.md): NIST SP 800-40 Rev. 4 lists six example maintenance groups. A start-up sequence for a patch program and the record that proves each step. Read 19 Nov 2026. - [Patch management practices, each with its source](https://patchmanagementpolicy.com/guides/patch-management-practices/index.md): Ten patching practices, each with its clause and the record that proves it is done, plus AWS's approval delay range of 0 to 360 days. Read 19 Nov 2026. ## Reference - [Patch Management Policy Sections: The Nine to Include](https://patchmanagementpolicy.com/policy-sections/index.md): The nine sections a patch management policy needs, in order, with one line each, the clauses that require them and a link to the page that writes each in full. - [Patch Window Table Method: Row Rules and Read Log](https://patchmanagementpolicy.com/patch-windows/method/index.md): How each Patch Window Table row was read on 19 Nov 2026: row rules, the read log with HTTP results, what no number set means, BOD 26-04 history, CSV fields. - [Patch Management Compliance Dates: 7 Dec 2026 and Back](https://patchmanagementpolicy.com/dates-to-know/index.md): 26 dated items for patch policies, newest first: FedRAMP and BOD 26-04 on 7 Dec 2026, PCI DSS, HIPAA, DORA, NIS2 and more, each with its source. - [Patch Management Glossary: 32 Terms, Sourced](https://patchmanagementpolicy.com/glossary/index.md): 32 patch management terms defined with an example from NIST, CISA, FedRAMP, PCI SSC, Microsoft and others, each with its source and read date. - [Patch Management Tools Directory: Two Kinds, Same Fields](https://patchmanagementpolicy.com/tools/index.md): 31 patch management tools in two kinds, alphabetical, with the same fields each: what it patches, rings, reporting, price, limits. Sourced, read 19 Nov 2026. - [Patching by Asset Type: Windows to OT Windows](https://patchmanagementpolicy.com/patching/index.md): Patch windows and practice for eleven asset classes, from Windows and Linux to containers, databases, mobile and OT, each with its vendor's published rhythm. - [How the Patch Window Table Is Built and Read](https://patchmanagementpolicy.com/method/index.md): How each patch window was read on 19 Nov 2026, how sources are labeled, which texts could not be opened (PCI DSS, ISO 27001, SOC 2) and how windows are chosen. - [Patch Management Policy FAQ: 17 Questions Answered](https://patchmanagementpolicy.com/faq/index.md): Seventeen questions people ask about patching and patch policies, answered from clauses read on 19 Nov 2026: windows, lifecycle, compliance rate, software, KEV. - [Patch Management Guides: 13 Guides, Each Sourced](https://patchmanagementpolicy.com/guides/index.md): Thirteen guides on patching policy, process, windows, evidence and compliance rate. Each answers one question from clauses read on 19 Nov 2026. ## Site - [About Patch Management Policy: scope and sources](https://patchmanagementpolicy.com/about/index.md): What the site covers (policy templates, patch windows, process steps), how it is hosted, what it logs for 400 days, how to cite it. First edition 19 Nov 2026. - [Editorial Policy: sources, labels and read dates](https://patchmanagementpolicy.com/editorial-policy/index.md): How pages are sourced and labeled: primary, vendor and third-party kinds, read dates, short quotes, alphabetical vendors, corrections. Edition of 19 Nov 2026. - [Corrections Log and Open Source Gaps, Edition 1](https://patchmanagementpolicy.com/corrections/index.md): The corrections log is empty as of 19 Nov 2026. How to report an error, and the five open gaps in unread sources, such as the PCI DSS v4.0.1 text. - [Contact the Editor of Patch Management Policy](https://patchmanagementpolicy.com/contact/index.md): One address for corrections, source gaps and template questions: editor@patchmanagementpolicy.com. What to include so a clause or number can be checked fast. - [Privacy: what this site logs and for how long](https://patchmanagementpolicy.com/privacy/index.md): No cookies, no analytics, no third-party scripts. CloudFront access logs sit in a private bucket and are deleted after 400 days. The builder sends nothing. - [Terms of Use: license, citing and reliance](https://patchmanagementpolicy.com/terms/index.md): Templates and data are CC BY 4.0. The cite line, what a template is and is not, and how external links are treated. Edition of 19 Nov 2026 for this site. ## Data - [Patch Window Table, CSV](https://patchmanagementpolicy.com/data/patch-windows.csv) - [Patch Window Table, JSON](https://patchmanagementpolicy.com/data/patch-windows.json) - [Policy template clauses, CSV](https://patchmanagementpolicy.com/data/policy-templates.csv) - [Policy template clauses, JSON](https://patchmanagementpolicy.com/data/policy-templates.json)