{
  "name": "Policy Template Set, clauses",
  "edition": "2026-11-19",
  "license": "CC BY 4.0",
  "license_url": "https://creativecommons.org/licenses/by/4.0/",
  "cite": "Patch Management Policy, Policy Template Set, edition 19 Nov 2026, https://patchmanagementpolicy.com/templates/",
  "fields": [
    "template",
    "template_title",
    "template_url",
    "section",
    "section_title",
    "clause",
    "text"
  ],
  "rows": [
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "",
      "section_title": "",
      "clause": "",
      "text": "Owner: [Role, e.g. Head of IT]. Approved by: [Name, role]. Version: [1.0]. Effective: [date]. Next review: [date, no later than 12 months after approval]."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "1",
      "section_title": "Purpose and scope",
      "clause": "1.1",
      "text": "This policy sets how [Company name] finds, tests, installs and verifies security patches and updates, so that known vulnerabilities in its systems are fixed inside the windows in section 4."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "1",
      "section_title": "Purpose and scope",
      "clause": "1.2",
      "text": "It covers every operating system, firmware, application, library, container image and cloud service that [Company name] owns, operates or administers, including systems run by a third party where [Company name] controls the patch schedule. Exclusions: [list each, with reason and approver]. An exclusion not listed here is not valid."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "1",
      "section_title": "Purpose and scope",
      "clause": "1.3",
      "text": "Software that no longer receives vendor security updates is removed from service or isolated and recorded under Annex A. It is not kept in service by default."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "2",
      "section_title": "Roles and responsibilities",
      "clause": "2.1",
      "text": "Policy owner ([role]): owns this policy, approves the windows, reports to [executive sponsor]."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "2",
      "section_title": "Roles and responsibilities",
      "clause": "2.2",
      "text": "Patch coordinator ([role]): runs the monthly cycle, keeps the schedule and the evidence."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "2",
      "section_title": "Roles and responsibilities",
      "clause": "2.3",
      "text": "System owners ([role per system]): approve outage time and accept test results for their maintenance group."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "2",
      "section_title": "Roles and responsibilities",
      "clause": "2.4",
      "text": "Platform administrators ([role]): deploy, verify and roll back."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "2",
      "section_title": "Roles and responsibilities",
      "clause": "2.5",
      "text": "Executive sponsor ([role]): receives the monthly report and decides any window missed for more than [5] working days."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "2",
      "section_title": "Roles and responsibilities",
      "clause": "2.6",
      "text": "Third parties that administer a system must patch to these windows and report completion in writing."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "3",
      "section_title": "Asset inventory",
      "clause": "3.1",
      "text": "The inventory records, for every asset: owner; platform type (IT, OT, IoT, mobile, cloud, virtual machine, container); who administers it (internal, third party, shared); the tool that manages it; whether it is reachable from the internet; its maintenance group; any legal, contractual or outage limit on patching; and the date it was last patched."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "3",
      "section_title": "Asset inventory",
      "clause": "3.2",
      "text": "An asset is added before it goes into production. Automated discovery runs at least [weekly]."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "3",
      "section_title": "Asset inventory",
      "clause": "3.3",
      "text": "An asset found by discovery that has no owner is given one within [5] working days or isolated."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "4.1",
      "text": "Each vulnerability takes the severity the vendor publishes. If the vendor publishes none, the policy owner assigns one from the organization's risk analysis. A vulnerability listed in the CISA Known Exploited Vulnerabilities catalog is class 1 whatever its vendor label. If two classes apply, the shorter window applies."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "4.2",
      "text": "The window starts when the vendor releases the patch. If no patch exists, the window starts when one becomes available and the mitigation in Annex A applies meanwhile."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "4.3",
      "text": "Windows:"
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "",
      "text": "Class: 1. Known exploited, internet-facing; Window: 3 calendar days; Applies to: Systems reachable from the internet"
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "",
      "text": "Class: 1. Known exploited, other; Window: 14 calendar days; Applies to: All other systems"
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "",
      "text": "Class: 2. Critical; Window: 14 calendar days; Applies to: All systems"
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "",
      "text": "Class: 3. High; Window: 30 calendar days; Applies to: All systems [set 14 if you hold Cyber Essentials]"
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "",
      "text": "Class: 4. Medium; Window: 90 calendar days; Applies to: All systems"
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "",
      "text": "Class: 5. Low; Window: 180 calendar days; Applies to: All systems"
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "",
      "text": "Class: Routine baseline; Window: Every month, or more often; Applies to: Operating system and application updates"
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "4.4",
      "text": "A window that cannot be met is escalated to the executive sponsor before it expires and recorded under Annex A."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "5",
      "section_title": "Testing and staging",
      "clause": "5.1",
      "text": "Every maintenance group has a canary set of [number or percent] assets that receives each patch first."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "5",
      "section_title": "Testing and staging",
      "clause": "5.2",
      "text": "A patch moves from canary to the full group after [2] working days with no incident, or sooner if the patch is class 1."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "5",
      "section_title": "Testing and staging",
      "clause": "5.3",
      "text": "A rollback method is written down before deployment. If none exists, say so in the change record and name the fallback."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "5",
      "section_title": "Testing and staging",
      "clause": "5.4",
      "text": "Test evidence (what was tested, by whom, result, date) is kept with the change record."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "6",
      "section_title": "Maintenance windows",
      "clause": "6.1",
      "text": "Standard windows by group: [group, day, hours, time zone]. The schedule is published [5] working days ahead."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "6",
      "section_title": "Maintenance windows",
      "clause": "6.2",
      "text": "Installation is forced after [number] days from the start of the window, by direct execution or by restricting network access of the unpatched asset."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "6",
      "section_title": "Maintenance windows",
      "clause": "6.3",
      "text": "Reboots needed to finish an install happen inside the same window. An asset that cannot reboot is handled under Annex A."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "7",
      "section_title": "Emergency patching",
      "clause": "7.1",
      "text": "The policy owner (or deputy [role]) may declare an emergency for named assets when a vulnerability is class 1, when a vendor issues an emergency update, or when the policy owner judges that waiting for the standard window is unacceptable."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "7",
      "section_title": "Emergency patching",
      "clause": "7.2",
      "text": "While an emergency is declared, the standard windows and change lead times are suspended for the named assets only. The declaration records who declared it, the time, the assets and the reason."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "7",
      "section_title": "Emergency patching",
      "clause": "7.3",
      "text": "Canary installation may run for minutes to hours; full installation follows in the hours or days the emergency allows."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "7",
      "section_title": "Emergency patching",
      "clause": "7.4",
      "text": "When the patch is installed and verified, the declaration is closed and the standard windows resume."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "8",
      "section_title": "Reporting and metrics",
      "clause": "8.1",
      "text": "Each month the patch coordinator reports to the executive sponsor: the share of assets patched inside their window, by class and by asset importance; the mean and median days to patch; open exceptions with age; assets with no owner."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "8",
      "section_title": "Reporting and metrics",
      "clause": "8.2",
      "text": "Evidence for every reported figure is exportable from [system] for [retention period]."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "9",
      "section_title": "Review and approval",
      "clause": "9.1",
      "text": "The policy is reviewed at least every 12 months, and when a framework named in section 4 changes its timing."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "9",
      "section_title": "Review and approval",
      "clause": "9.2",
      "text": "Changes are approved by [role]. The approved version, date and approver are recorded on the cover."
    },
    {
      "template": "patch-management-policy-template",
      "template_title": "Patch management policy template",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-policy-template/",
      "section": "Annex A",
      "section_title": "Exceptions",
      "clause": "",
      "text": "Exceptions follow the exceptions clause ([insert clause text])."
    },
    {
      "template": "small-business",
      "template_title": "Patch management policy for small business",
      "template_url": "https://patchmanagementpolicy.com/templates/small-business/",
      "section": "1",
      "section_title": "Purpose and scope",
      "clause": "1.1",
      "text": "[Company name] keeps its computers, phones, network devices and cloud services up to date so that known security flaws are closed quickly."
    },
    {
      "template": "small-business",
      "template_title": "Patch management policy for small business",
      "template_url": "https://patchmanagementpolicy.com/templates/small-business/",
      "section": "1",
      "section_title": "Purpose and scope",
      "clause": "1.2",
      "text": "Scope: laptops, desktops, servers, tablets, mobile phones, firewalls, routers, and every cloud service (IaaS, PaaS and SaaS) that staff use for company work, whether the company or a person owns the device. Personal devices that open company data are in scope."
    },
    {
      "template": "small-business",
      "template_title": "Patch management policy for small business",
      "template_url": "https://patchmanagementpolicy.com/templates/small-business/",
      "section": "1",
      "section_title": "Purpose and scope",
      "clause": "1.3",
      "text": "Software that the maker no longer supports is removed. Where it cannot be removed, the IT lead records why and when it will go."
    },
    {
      "template": "small-business",
      "template_title": "Patch management policy for small business",
      "template_url": "https://patchmanagementpolicy.com/templates/small-business/",
      "section": "2",
      "section_title": "Roles and responsibilities",
      "clause": "2.1",
      "text": "IT lead ([name], backup [name]): owns this policy and the monthly check. If an outside IT provider ([provider]) does the work, the IT lead is still accountable and keeps the provider's monthly written report."
    },
    {
      "template": "small-business",
      "template_title": "Patch management policy for small business",
      "template_url": "https://patchmanagementpolicy.com/templates/small-business/",
      "section": "2",
      "section_title": "Roles and responsibilities",
      "clause": "2.2",
      "text": "Every employee: installs prompted updates within [3] days and restarts when asked."
    },
    {
      "template": "small-business",
      "template_title": "Patch management policy for small business",
      "template_url": "https://patchmanagementpolicy.com/templates/small-business/",
      "section": "2",
      "section_title": "Roles and responsibilities",
      "clause": "2.3",
      "text": "Director ([name]): hears about any update that is more than 14 days late."
    },
    {
      "template": "small-business",
      "template_title": "Patch management policy for small business",
      "template_url": "https://patchmanagementpolicy.com/templates/small-business/",
      "section": "3",
      "section_title": "Asset inventory",
      "clause": "3.1",
      "text": "One spreadsheet or tool lists every device and cloud service, its owner, whether it updates itself, and the date of the last check."
    },
    {
      "template": "small-business",
      "template_title": "Patch management policy for small business",
      "template_url": "https://patchmanagementpolicy.com/templates/small-business/",
      "section": "3",
      "section_title": "Asset inventory",
      "clause": "3.2",
      "text": "A new device is added on the day it is issued."
    },
    {
      "template": "small-business",
      "template_title": "Patch management policy for small business",
      "template_url": "https://patchmanagementpolicy.com/templates/small-business/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "",
      "text": "Update type: Fixes a flaw the maker calls critical or high; Window: 14 days from release"
    },
    {
      "template": "small-business",
      "template_title": "Patch management policy for small business",
      "template_url": "https://patchmanagementpolicy.com/templates/small-business/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "",
      "text": "Update type: Listed as exploited in the CISA Known Exploited Vulnerabilities catalog; Window: 3 days if the system is reachable from the internet, otherwise 14 days"
    },
    {
      "template": "small-business",
      "template_title": "Patch management policy for small business",
      "template_url": "https://patchmanagementpolicy.com/templates/small-business/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "",
      "text": "Update type: Everything else; Window: Next monthly cycle"
    },
    {
      "template": "small-business",
      "template_title": "Patch management policy for small business",
      "template_url": "https://patchmanagementpolicy.com/templates/small-business/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "4.1",
      "text": "Automatic updates are switched on wherever the product allows it. The IT lead checks every month, on the Wednesday after the second Tuesday, that nothing is waiting."
    },
    {
      "template": "small-business",
      "template_title": "Patch management policy for small business",
      "template_url": "https://patchmanagementpolicy.com/templates/small-business/",
      "section": "5",
      "section_title": "Testing and staging",
      "clause": "5.1",
      "text": "The IT lead's own device and one volunteer's device get updates first, then everyone else after [2] working days. Servers are updated outside working hours with a backup taken first."
    },
    {
      "template": "small-business",
      "template_title": "Patch management policy for small business",
      "template_url": "https://patchmanagementpolicy.com/templates/small-business/",
      "section": "6",
      "section_title": "Maintenance windows",
      "clause": "6.1",
      "text": "Servers and network devices: [day, time]. Laptops: restarts allowed any weekday before [time]."
    },
    {
      "template": "small-business",
      "template_title": "Patch management policy for small business",
      "template_url": "https://patchmanagementpolicy.com/templates/small-business/",
      "section": "8",
      "section_title": "Reporting and metrics",
      "clause": "8.1",
      "text": "Monthly note to the director: devices checked, devices late, reason, date fixed."
    },
    {
      "template": "saas-company",
      "template_title": "Patch management policy for a SaaS company",
      "template_url": "https://patchmanagementpolicy.com/templates/saas-company/",
      "section": "1",
      "section_title": "Purpose and scope",
      "clause": "1.1",
      "text": "This policy covers production and non-production workloads of [Company name]: host operating systems, container base images, application images, libraries and packages, build tooling, managed databases and queues, and employee endpoints."
    },
    {
      "template": "saas-company",
      "template_title": "Patch management policy for a SaaS company",
      "template_url": "https://patchmanagementpolicy.com/templates/saas-company/",
      "section": "1",
      "section_title": "Purpose and scope",
      "clause": "1.2",
      "text": "For each managed service, the inventory records which patches the provider applies and which the company applies (the shared responsibility line). Provider-applied patches are monitored through [provider notices], not assumed."
    },
    {
      "template": "saas-company",
      "template_title": "Patch management policy for a SaaS company",
      "template_url": "https://patchmanagementpolicy.com/templates/saas-company/",
      "section": "3",
      "section_title": "Asset inventory",
      "clause": "3.1",
      "text": "The inventory adds: image name and digest; base image and its source; package manifest or software bill of materials for each release; the pipeline that builds it; runtime location (cluster, region, account)."
    },
    {
      "template": "saas-company",
      "template_title": "Patch management policy for a SaaS company",
      "template_url": "https://patchmanagementpolicy.com/templates/saas-company/",
      "section": "3",
      "section_title": "Asset inventory",
      "clause": "3.2",
      "text": "Inventory data is read from the cloud provider and the registry by API at least [daily]."
    },
    {
      "template": "saas-company",
      "template_title": "Patch management policy for a SaaS company",
      "template_url": "https://patchmanagementpolicy.com/templates/saas-company/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "4.1",
      "text": "Windows follow general policy section 4.3."
    },
    {
      "template": "saas-company",
      "template_title": "Patch management policy for a SaaS company",
      "template_url": "https://patchmanagementpolicy.com/templates/saas-company/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "4.2",
      "text": "For a container or image, the window ends when a rebuilt image is running in production and the vulnerable image is no longer running, not when the rebuild is merged."
    },
    {
      "template": "saas-company",
      "template_title": "Patch management policy for a SaaS company",
      "template_url": "https://patchmanagementpolicy.com/templates/saas-company/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "4.3",
      "text": "Third-party and open source components are patched by updating the dependency and rebuilding. The pipeline fails a release that carries a class 1 or class 2 finding unless an exception is recorded."
    },
    {
      "template": "saas-company",
      "template_title": "Patch management policy for a SaaS company",
      "template_url": "https://patchmanagementpolicy.com/templates/saas-company/",
      "section": "5",
      "section_title": "Testing and staging",
      "clause": "5.1",
      "text": "Patched images go through the same automated tests as any release. They deploy to [canary percent] of production first, then expand if error rate and latency stay within [thresholds] for [period]."
    },
    {
      "template": "saas-company",
      "template_title": "Patch management policy for a SaaS company",
      "template_url": "https://patchmanagementpolicy.com/templates/saas-company/",
      "section": "5",
      "section_title": "Testing and staging",
      "clause": "5.2",
      "text": "Rollback is redeployment of the previous image digest."
    },
    {
      "template": "saas-company",
      "template_title": "Patch management policy for a SaaS company",
      "template_url": "https://patchmanagementpolicy.com/templates/saas-company/",
      "section": "6",
      "section_title": "Maintenance windows",
      "clause": "6.1",
      "text": "Rolling replacement is the default and needs no customer-visible window. Hosts that cannot be replaced use the standard windows in general policy section 6."
    },
    {
      "template": "saas-company",
      "template_title": "Patch management policy for a SaaS company",
      "template_url": "https://patchmanagementpolicy.com/templates/saas-company/",
      "section": "6",
      "section_title": "Maintenance windows",
      "clause": "6.2",
      "text": "Live kernel patching, where used, covers only the vulnerabilities its vendor supports. It does not replace the next scheduled reboot or replacement."
    },
    {
      "template": "saas-company",
      "template_title": "Patch management policy for a SaaS company",
      "template_url": "https://patchmanagementpolicy.com/templates/saas-company/",
      "section": "8",
      "section_title": "Reporting and metrics",
      "clause": "8.1",
      "text": "Reports add: share of running workloads on an image younger than [30] days; oldest running image age; findings past window by team."
    },
    {
      "template": "saas-company",
      "template_title": "Patch management policy for a SaaS company",
      "template_url": "https://patchmanagementpolicy.com/templates/saas-company/",
      "section": "8",
      "section_title": "Reporting and metrics",
      "clause": "8.2",
      "text": "For each monthly report, export from [system]: the inventory snapshot, the list of changes with test evidence, and the exceptions list. These are the records given to an auditor."
    },
    {
      "template": "enterprise",
      "template_title": "Enterprise patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/enterprise/",
      "section": "2",
      "section_title": "Roles and responsibilities",
      "clause": "2.1",
      "text": "Policy owner ([CISO]): owns this policy and the windows. Approves changes to maintenance plans."
    },
    {
      "template": "enterprise",
      "template_title": "Enterprise patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/enterprise/",
      "section": "2",
      "section_title": "Roles and responsibilities",
      "clause": "2.2",
      "text": "Patch program lead ([role]): runs the cycle across all groups and reports monthly to the [risk committee]."
    },
    {
      "template": "enterprise",
      "template_title": "Enterprise patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/enterprise/",
      "section": "2",
      "section_title": "Roles and responsibilities",
      "clause": "2.3",
      "text": "Group owners ([role per maintenance group]): own the maintenance plan for their group, approve outage time, and accept test results. Group owners may delegate day-to-day approval in writing to [role]; the delegation names the group, the limits, and an expiry date no later than [12] months."
    },
    {
      "template": "enterprise",
      "template_title": "Enterprise patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/enterprise/",
      "section": "2",
      "section_title": "Roles and responsibilities",
      "clause": "2.4",
      "text": "Business unit heads: receive the group-level report and own late items in their units."
    },
    {
      "template": "enterprise",
      "template_title": "Enterprise patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/enterprise/",
      "section": "2",
      "section_title": "Roles and responsibilities",
      "clause": "2.5",
      "text": "Change advisory board ([name]): reviews only changes that fall outside a maintenance plan. Plan-conforming patches are pre-approved."
    },
    {
      "template": "enterprise",
      "template_title": "Enterprise patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/enterprise/",
      "section": "3",
      "section_title": "Asset inventory",
      "clause": "3.1",
      "text": "The inventory may be held in more than one system. The patch program lead keeps a register that names each source of record, the asset types it covers, and how often it syncs."
    },
    {
      "template": "enterprise",
      "template_title": "Enterprise patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/enterprise/",
      "section": "3",
      "section_title": "Asset inventory",
      "clause": "3.2",
      "text": "Each asset is assigned to exactly one maintenance group. Assets that cannot meet their group's plan move to a separate group with its own plan; they are not left as exceptions in the group."
    },
    {
      "template": "enterprise",
      "template_title": "Enterprise patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/enterprise/",
      "section": "3",
      "section_title": "Asset inventory",
      "clause": "3.3",
      "text": "Authenticated scanning or agent reporting is the source for installed software. Unauthenticated scans are used only for discovery."
    },
    {
      "template": "enterprise",
      "template_title": "Enterprise patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/enterprise/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "4.1",
      "text": "Group importance is High, Moderate or Low, set by the group owner and confirmed by the policy owner."
    },
    {
      "template": "enterprise",
      "template_title": "Enterprise patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/enterprise/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "4.2",
      "text": "Windows (calendar days from vendor release):"
    },
    {
      "template": "enterprise",
      "template_title": "Enterprise patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/enterprise/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "",
      "text": "Class: 1. Known exploited, internet-facing; High importance group: 3; Moderate importance group: 3; Low importance group: 3"
    },
    {
      "template": "enterprise",
      "template_title": "Enterprise patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/enterprise/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "",
      "text": "Class: 1. Known exploited, other; High importance group: 7; Moderate importance group: 14; Low importance group: 14"
    },
    {
      "template": "enterprise",
      "template_title": "Enterprise patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/enterprise/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "",
      "text": "Class: 2. Critical; High importance group: 7; Moderate importance group: 14; Low importance group: 14"
    },
    {
      "template": "enterprise",
      "template_title": "Enterprise patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/enterprise/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "",
      "text": "Class: 3. High; High importance group: 14; Moderate importance group: 30; Low importance group: 30"
    },
    {
      "template": "enterprise",
      "template_title": "Enterprise patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/enterprise/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "",
      "text": "Class: 4. Medium; High importance group: 60; Moderate importance group: 90; Low importance group: 90"
    },
    {
      "template": "enterprise",
      "template_title": "Enterprise patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/enterprise/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "",
      "text": "Class: 5. Low; High importance group: 180; Moderate importance group: 180; Low importance group: 180"
    },
    {
      "template": "enterprise",
      "template_title": "Enterprise patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/enterprise/",
      "section": "5",
      "section_title": "Testing and staging (rings)",
      "clause": "5.1",
      "text": "Ring 0: [IT and security staff], first, for [3] working days."
    },
    {
      "template": "enterprise",
      "template_title": "Enterprise patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/enterprise/",
      "section": "5",
      "section_title": "Testing and staging (rings)",
      "clause": "5.2",
      "text": "Ring 1: [volunteer early adopters across business units], for up to [14] days for routine updates."
    },
    {
      "template": "enterprise",
      "template_title": "Enterprise patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/enterprise/",
      "section": "5",
      "section_title": "Testing and staging (rings)",
      "clause": "5.3",
      "text": "Ring 2 and later: remaining assets, in groups of [size]."
    },
    {
      "template": "enterprise",
      "template_title": "Enterprise patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/enterprise/",
      "section": "5",
      "section_title": "Testing and staging (rings)",
      "clause": "5.4",
      "text": "Class 1 updates skip Ring 1 and run Ring 0 for no more than [24] hours."
    },
    {
      "template": "enterprise",
      "template_title": "Enterprise patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/enterprise/",
      "section": "8",
      "section_title": "Reporting and metrics",
      "clause": "8.1",
      "text": "Reports are cut by importance of asset and class of vulnerability, not as one overall percentage. Each cell shows the share patched by deadline, the mean days and the median days."
    },
    {
      "template": "enterprise",
      "template_title": "Enterprise patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/enterprise/",
      "section": "8",
      "section_title": "Reporting and metrics",
      "clause": "8.2",
      "text": "The CISO sees all cells; group owners see their group; the board sees the cells for High importance assets and class 1 and 2 vulnerabilities."
    },
    {
      "template": "healthcare-hipaa",
      "template_title": "HIPAA patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/healthcare-hipaa/",
      "section": "1",
      "section_title": "Purpose and scope",
      "clause": "1.1",
      "text": "This policy applies to every electronic information system of [Company name] that creates, receives, maintains or transmits electronic protected health information, and to every system that connects to one. [Company name] is a [covered entity / business associate]."
    },
    {
      "template": "healthcare-hipaa",
      "template_title": "HIPAA patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/healthcare-hipaa/",
      "section": "1",
      "section_title": "Purpose and scope",
      "clause": "1.2",
      "text": "The policy is part of the security measures required by 45 CFR 164.308(a)(1)(ii)(B), chosen on the basis of the risk analysis required by 164.308(a)(1)(ii)(A) dated [date]."
    },
    {
      "template": "healthcare-hipaa",
      "template_title": "HIPAA patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/healthcare-hipaa/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "4.1",
      "text": "Risk level (critical, high, other) is assigned by the policy owner from the current risk analysis and recorded for each vulnerability."
    },
    {
      "template": "healthcare-hipaa",
      "template_title": "HIPAA patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/healthcare-hipaa/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "4.2",
      "text": "Windows, from the date [Company name] identifies the need to patch, where a patch is available:"
    },
    {
      "template": "healthcare-hipaa",
      "template_title": "HIPAA patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/healthcare-hipaa/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "",
      "text": "Risk level: Critical; Window now: 14 calendar days (company standard); Window if the proposed federal rule is finalized as written: 15 calendar days"
    },
    {
      "template": "healthcare-hipaa",
      "template_title": "HIPAA patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/healthcare-hipaa/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "",
      "text": "Risk level: High; Window now: 30 calendar days (company standard); Window if the proposed federal rule is finalized as written: 30 calendar days"
    },
    {
      "template": "healthcare-hipaa",
      "template_title": "HIPAA patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/healthcare-hipaa/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "",
      "text": "Risk level: All other; Window now: As set in the general policy; Window if the proposed federal rule is finalized as written: As set in this policy"
    },
    {
      "template": "healthcare-hipaa",
      "template_title": "HIPAA patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/healthcare-hipaa/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "4.3",
      "text": "Where no patch is available, the 15 and 30 days run from the date a patch becomes available, and Annex A applies meanwhile."
    },
    {
      "template": "healthcare-hipaa",
      "template_title": "HIPAA patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/healthcare-hipaa/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "4.4",
      "text": "The company standard is stricter than or equal to every figure in the proposal, so adopting it now means no change when the rule is final."
    },
    {
      "template": "healthcare-hipaa",
      "template_title": "HIPAA patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/healthcare-hipaa/",
      "section": "9",
      "section_title": "Review and approval",
      "clause": "9.1",
      "text": "This policy is reviewed and tested at least once every 12 months, and after any significant change to systems that hold ePHI."
    },
    {
      "template": "healthcare-hipaa",
      "template_title": "HIPAA patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/healthcare-hipaa/",
      "section": "9",
      "section_title": "Review and approval",
      "clause": "9.2",
      "text": "Test means: [tabletop walk-through of one critical and one high case; evidence kept for each]."
    },
    {
      "template": "healthcare-hipaa",
      "template_title": "HIPAA patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/healthcare-hipaa/",
      "section": "Annex A",
      "section_title": "Exceptions (HIPAA)",
      "clause": "A.1",
      "text": "An exception is valid only if (a) no patch is available, or (b) the only available patch would adversely affect the confidentiality, integrity or availability of ePHI."
    },
    {
      "template": "healthcare-hipaa",
      "template_title": "HIPAA patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/healthcare-hipaa/",
      "section": "Annex A",
      "section_title": "Exceptions (HIPAA)",
      "clause": "A.2",
      "text": "Each exception records the compensating controls applied, the risk analysis entry, the approver and the date for the next check."
    },
    {
      "template": "payment-card-pci-dss",
      "template_title": "PCI DSS patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/payment-card-pci-dss/",
      "section": "1",
      "section_title": "Purpose and scope",
      "clause": "1.1",
      "text": "This policy applies to every system component in the cardholder data environment of [Company name], every system connected to it, and every system that can affect its security. The scope diagram dated [date] is kept by [role]."
    },
    {
      "template": "payment-card-pci-dss",
      "template_title": "PCI DSS patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/payment-card-pci-dss/",
      "section": "1",
      "section_title": "Purpose and scope",
      "clause": "1.2",
      "text": "Third parties that host or manage in-scope components are named in [register] and are bound by clause 4."
    },
    {
      "template": "payment-card-pci-dss",
      "template_title": "PCI DSS patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/payment-card-pci-dss/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "4.1",
      "text": "Windows for in-scope components, from vendor release:"
    },
    {
      "template": "payment-card-pci-dss",
      "template_title": "PCI DSS patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/payment-card-pci-dss/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "",
      "text": "Class: Critical vulnerabilities; Window: 14 calendar days (company standard); never more than one month; Basis: PCI SSC FAQ 1597: Requirement 6.3.3, one month from release for critical vulnerabilities"
    },
    {
      "template": "payment-card-pci-dss",
      "template_title": "PCI DSS patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/payment-card-pci-dss/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "",
      "text": "Class: Known exploited; Window: 3 days internet-facing, otherwise 14 days; Basis: Company standard (CISA BOD 26-04 tiers)"
    },
    {
      "template": "payment-card-pci-dss",
      "template_title": "PCI DSS patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/payment-card-pci-dss/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "",
      "text": "Class: High and other; Window: 30, 90 and 180 days as in the general policy; Basis: Company standard; non-critical windows follow the entity's risk analysis (FAQ 1597)"
    },
    {
      "template": "payment-card-pci-dss",
      "template_title": "PCI DSS patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/payment-card-pci-dss/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "4.2",
      "text": "Where the QSA or the assessor reads the requirement differently, [role] amends this clause within [10] working days and records the reason."
    },
    {
      "template": "payment-card-pci-dss",
      "template_title": "PCI DSS patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/payment-card-pci-dss/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "4.3",
      "text": "In-scope components that cannot meet clause 4.1 are recorded under Annex A with the requirement reference [number from your copy of the standard]."
    },
    {
      "template": "payment-card-pci-dss",
      "template_title": "PCI DSS patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/payment-card-pci-dss/",
      "section": "8",
      "section_title": "Reporting and metrics",
      "clause": "8.1",
      "text": "The monthly report adds: in-scope components with a critical vulnerability past 14 days; oldest open critical age; scope changes."
    },
    {
      "template": "payment-card-pci-dss",
      "template_title": "PCI DSS patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/payment-card-pci-dss/",
      "section": "8",
      "section_title": "Reporting and metrics",
      "clause": "8.2",
      "text": "Evidence of each patch (date installed, component, vulnerability) is kept for [period set by the assessor]."
    },
    {
      "template": "federal-contractor-fedramp",
      "template_title": "FedRAMP patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/federal-contractor-fedramp/",
      "section": "1",
      "section_title": "Purpose and scope",
      "clause": "1.1",
      "text": "This policy applies to the cloud service offering [name], FedRAMP [Rev5 / 20x] certification class [A / B / C / D], and to all supporting systems in its authorization boundary."
    },
    {
      "template": "federal-contractor-fedramp",
      "template_title": "FedRAMP patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/federal-contractor-fedramp/",
      "section": "1",
      "section_title": "Purpose and scope",
      "clause": "1.2",
      "text": "Legacy authorizations: until [date] the legacy remediation requirements apply to POA&M items; from the mandatory date the Vulnerability Detection and Response (VDR) rules apply."
    },
    {
      "template": "federal-contractor-fedramp",
      "template_title": "FedRAMP patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/federal-contractor-fedramp/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "4.1",
      "text": "Timeframes are maximums measured from evaluation of the vulnerability, by the Potential Agency Impact level (N5, N4, N3, N2) and the vulnerability's internet reachability and likelihood of exploitation. They are copied from the FedRAMP rules page dated [read date] into Appendix 1 and re-read at each review."
    },
    {
      "template": "federal-contractor-fedramp",
      "template_title": "FedRAMP patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/federal-contractor-fedramp/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "4.2",
      "text": "Known Exploited Vulnerabilities are remediated by the due date shown for the entry in the CISA catalog, as required by BOD 26-04 or any successor guidance."
    },
    {
      "template": "federal-contractor-fedramp",
      "template_title": "FedRAMP patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/federal-contractor-fedramp/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "4.3",
      "text": "Other vulnerabilities are mitigated or remediated during routine operations as the provider determines necessary, within the company standard of the general policy (class 4: 90 days; class 5: 180 days)."
    },
    {
      "template": "federal-contractor-fedramp",
      "template_title": "FedRAMP patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/federal-contractor-fedramp/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "4.4",
      "text": "Where the SHOULD wording of a rule is not followed, the provider records the reason and the alternative (Annex A)."
    },
    {
      "template": "federal-contractor-fedramp",
      "template_title": "FedRAMP patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/federal-contractor-fedramp/",
      "section": "8",
      "section_title": "Reporting and metrics",
      "clause": "8.1",
      "text": "Reports show, for each class and impact level, the vulnerabilities evaluated, the timeframe applicable, the date mitigated or remediated, and any past timeframe."
    },
    {
      "template": "federal-contractor-fedramp",
      "template_title": "FedRAMP patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/federal-contractor-fedramp/",
      "section": "8",
      "section_title": "Reporting and metrics",
      "clause": "8.2",
      "text": "Legacy: POA&M items show scheduled completion against 30 days (critical and high), 90 days (moderate), 180 days (low), from discovery."
    },
    {
      "template": "managed-service-provider",
      "template_title": "MSP patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/managed-service-provider/",
      "section": "1",
      "section_title": "Purpose and scope",
      "clause": "1.1",
      "text": "This policy governs how [MSP name] patches systems that belong to its clients under written agreements. It covers each client's endpoints, servers, network devices and cloud tenants listed in that client's schedule."
    },
    {
      "template": "managed-service-provider",
      "template_title": "MSP patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/managed-service-provider/",
      "section": "1",
      "section_title": "Purpose and scope",
      "clause": "1.2",
      "text": "No system is patched, rebooted or excluded without the authority recorded in the client's agreement or a written instruction from the client contact named in the schedule."
    },
    {
      "template": "managed-service-provider",
      "template_title": "MSP patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/managed-service-provider/",
      "section": "2",
      "section_title": "Roles and responsibilities",
      "clause": "2.1",
      "text": "Service delivery lead ([role]): owns this policy."
    },
    {
      "template": "managed-service-provider",
      "template_title": "MSP patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/managed-service-provider/",
      "section": "2",
      "section_title": "Roles and responsibilities",
      "clause": "2.2",
      "text": "Client technical contact ([named in schedule]): approves the client's maintenance window and exceptions."
    },
    {
      "template": "managed-service-provider",
      "template_title": "MSP patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/managed-service-provider/",
      "section": "2",
      "section_title": "Roles and responsibilities",
      "clause": "2.3",
      "text": "Technicians: patch only inside the windows in the client schedule."
    },
    {
      "template": "managed-service-provider",
      "template_title": "MSP patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/managed-service-provider/",
      "section": "3",
      "section_title": "Asset inventory",
      "clause": "3.1",
      "text": "The inventory is kept per client and records who administers each asset (MSP, client, third party) and any contractual or regulatory limit on patching."
    },
    {
      "template": "managed-service-provider",
      "template_title": "MSP patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/managed-service-provider/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "4.1",
      "text": "Default windows are those of the general policy, section 4.3. A client may require shorter windows. A client may not lengthen them beyond the default without a signed exception that names the systems and the end date."
    },
    {
      "template": "managed-service-provider",
      "template_title": "MSP patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/managed-service-provider/",
      "section": "4",
      "section_title": "Severity and patch windows",
      "clause": "4.2",
      "text": "The window clock runs from vendor release, whoever approves. Delay waiting for client approval is recorded and reported to the client contact."
    },
    {
      "template": "managed-service-provider",
      "template_title": "MSP patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/managed-service-provider/",
      "section": "6",
      "section_title": "Maintenance windows",
      "clause": "6.1",
      "text": "Each client has its own windows and blackout dates, held in the schedule. Windows are not shared across clients unless agreed."
    },
    {
      "template": "managed-service-provider",
      "template_title": "MSP patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/managed-service-provider/",
      "section": "8",
      "section_title": "Reporting and metrics",
      "clause": "8.1",
      "text": "One report per client per month: assets in scope, share patched inside the window by class, mean and median days, exceptions with age, and delays awaiting client approval."
    },
    {
      "template": "managed-service-provider",
      "template_title": "MSP patch management policy",
      "template_url": "https://patchmanagementpolicy.com/templates/managed-service-provider/",
      "section": "8",
      "section_title": "Reporting and metrics",
      "clause": "8.2",
      "text": "Reports are delivered by [date each month] and kept for [period] after the agreement ends."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "",
      "section_title": "",
      "clause": "",
      "text": "Sits under: Patch Management Policy [version]. Owner: [Patch coordinator]. Cycle: monthly, starting on the second Tuesday."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 1",
      "section_title": "Keep the inventory current",
      "clause": "",
      "text": "Who: Patch coordinator with system owners."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 1",
      "section_title": "Keep the inventory current",
      "clause": "",
      "text": "Do: Reconcile discovery output with the inventory; assign an owner to every unowned asset; confirm each asset's maintenance group."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 1",
      "section_title": "Keep the inventory current",
      "clause": "",
      "text": "Record: Inventory snapshot dated [date]; list of assets added, removed, unowned."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 2",
      "section_title": "Watch for releases",
      "clause": "",
      "text": "Who: Patch coordinator."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 2",
      "section_title": "Watch for releases",
      "clause": "",
      "text": "Do: Check vendor advisories for every product in the inventory on the release day and again two working days later. Check the CISA Known Exploited Vulnerabilities catalog on each working day."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 2",
      "section_title": "Watch for releases",
      "clause": "",
      "text": "Record: Release log (product, advisory, release date, vendor label)."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 3",
      "section_title": "Assess and prioritize",
      "clause": "",
      "text": "Who: Patch coordinator; policy owner for disputes."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 3",
      "section_title": "Assess and prioritize",
      "clause": "",
      "text": "Do: Match each release to affected assets; assign the policy class; set the deadline = release date + window."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 3",
      "section_title": "Assess and prioritize",
      "clause": "",
      "text": "Record: Assessment sheet (advisory, assets affected, class, deadline)."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 4",
      "section_title": "Acquire and test",
      "clause": "",
      "text": "Who: Platform administrators."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 4",
      "section_title": "Acquire and test",
      "clause": "",
      "text": "Do: Download from the vendor's own channel; verify integrity; install on the canary set; observe for [2] working days (class 1: hours)."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 4",
      "section_title": "Acquire and test",
      "clause": "",
      "text": "Record: Canary result and tester, rollback method."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 5",
      "section_title": "Approve and schedule",
      "clause": "",
      "text": "Who: System owner."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 5",
      "section_title": "Approve and schedule",
      "clause": "",
      "text": "Do: Approve the deployment and the maintenance window, or state the reason for refusal; refusals go to the exceptions clause."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 5",
      "section_title": "Approve and schedule",
      "clause": "",
      "text": "Record: Approval (name, date), scheduled window."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 6",
      "section_title": "Deploy",
      "clause": "",
      "text": "Who: Platform administrators."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 6",
      "section_title": "Deploy",
      "clause": "",
      "text": "Do: Install in the scheduled window in the order canary, then groups; force installation after the grace period; roll back if a stop condition is met: [list stop conditions]."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 6",
      "section_title": "Deploy",
      "clause": "",
      "text": "Record: Deployment log per asset (installed, failed, pending, reboot required)."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 7",
      "section_title": "Verify",
      "clause": "",
      "text": "Who: Platform administrators, checked by the patch coordinator."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 7",
      "section_title": "Verify",
      "clause": "",
      "text": "Do: Confirm the patch is installed and has taken effect (version, rescan or attestation); chase failed and pending assets."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 7",
      "section_title": "Verify",
      "clause": "",
      "text": "Record: Verification result per asset; list of assets still open at the deadline."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 8",
      "section_title": "Report",
      "clause": "",
      "text": "Who: Patch coordinator."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 8",
      "section_title": "Report",
      "clause": "",
      "text": "Do: Send the monthly report defined in policy section 8 to the executive sponsor within [5] working days of the cycle's last deadline."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 8",
      "section_title": "Report",
      "clause": "",
      "text": "Record: Report and the data export behind it."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 9",
      "section_title": "Review the cycle",
      "clause": "",
      "text": "Who: Patch coordinator, policy owner."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 9",
      "section_title": "Review the cycle",
      "clause": "",
      "text": "Do: List misses and their causes; change a maintenance plan, ring or window if the same cause occurs twice."
    },
    {
      "template": "patch-management-procedure",
      "template_title": "Patch management procedure",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-management-procedure/",
      "section": "Step 9",
      "section_title": "Review the cycle",
      "clause": "",
      "text": "Record: Review notes and any change request to the policy."
    },
    {
      "template": "patch-exceptions-clause",
      "template_title": "Patch management policy exceptions clause",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-exceptions-clause/",
      "section": "Annex A",
      "section_title": "Patch exceptions",
      "clause": "A.1",
      "text": "Definition. An exception is an approved departure from a window in section 4 of this policy for named assets, for a stated period."
    },
    {
      "template": "patch-exceptions-clause",
      "template_title": "Patch management policy exceptions clause",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-exceptions-clause/",
      "section": "Annex A",
      "section_title": "Patch exceptions",
      "clause": "A.2",
      "text": "Who may request. A system owner, group owner or the patch coordinator."
    },
    {
      "template": "patch-exceptions-clause",
      "template_title": "Patch management policy exceptions clause",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-exceptions-clause/",
      "section": "Annex A",
      "section_title": "Patch exceptions",
      "clause": "A.3",
      "text": "Grounds. A request is accepted for consideration only on one of these grounds: (a) no patch is available; (b) the only available patch would adversely affect the confidentiality, integrity or availability of the system or its data; (c) the vendor no longer supports the software; (d) the disadvantages of applying the patch outweigh the security benefit and the reasons can be substantiated in writing; (e) a legal or contractual restriction prevents patching in the window."
    },
    {
      "template": "patch-exceptions-clause",
      "template_title": "Patch management policy exceptions clause",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-exceptions-clause/",
      "section": "Annex A",
      "section_title": "Patch exceptions",
      "clause": "A.4",
      "text": "The request records:"
    },
    {
      "template": "patch-exceptions-clause",
      "template_title": "Patch management policy exceptions clause",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-exceptions-clause/",
      "section": "Annex A",
      "section_title": "Patch exceptions",
      "clause": "1",
      "text": "The assets (inventory IDs), their owner and maintenance group."
    },
    {
      "template": "patch-exceptions-clause",
      "template_title": "Patch management policy exceptions clause",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-exceptions-clause/",
      "section": "Annex A",
      "section_title": "Patch exceptions",
      "clause": "2",
      "text": "The vulnerability or patch (identifier, vendor advisory, class, original deadline)."
    },
    {
      "template": "patch-exceptions-clause",
      "template_title": "Patch management policy exceptions clause",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-exceptions-clause/",
      "section": "Annex A",
      "section_title": "Patch exceptions",
      "clause": "3",
      "text": "The ground under A.3 and the evidence for it."
    },
    {
      "template": "patch-exceptions-clause",
      "template_title": "Patch management policy exceptions clause",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-exceptions-clause/",
      "section": "Annex A",
      "section_title": "Patch exceptions",
      "clause": "4",
      "text": "The measures applied meanwhile, who operates them and how their working is checked."
    },
    {
      "template": "patch-exceptions-clause",
      "template_title": "Patch management policy exceptions clause",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-exceptions-clause/",
      "section": "Annex A",
      "section_title": "Patch exceptions",
      "clause": "5",
      "text": "The requested end date."
    },
    {
      "template": "patch-exceptions-clause",
      "template_title": "Patch management policy exceptions clause",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-exceptions-clause/",
      "section": "Annex A",
      "section_title": "Patch exceptions",
      "clause": "6",
      "text": "The plan to remove the exception, with a named owner."
    },
    {
      "template": "patch-exceptions-clause",
      "template_title": "Patch management policy exceptions clause",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-exceptions-clause/",
      "section": "Annex A",
      "section_title": "Patch exceptions",
      "clause": "7",
      "text": "The requester and the date."
    },
    {
      "template": "patch-exceptions-clause",
      "template_title": "Patch management policy exceptions clause",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-exceptions-clause/",
      "section": "Annex A",
      "section_title": "Patch exceptions",
      "clause": "A.5",
      "text": "Signers. The group owner and the policy owner sign every exception. An exception on a class 1 or class 2 vulnerability also requires [executive sponsor]."
    },
    {
      "template": "patch-exceptions-clause",
      "template_title": "Patch management policy exceptions clause",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-exceptions-clause/",
      "section": "Annex A",
      "section_title": "Patch exceptions",
      "clause": "A.6",
      "text": "Maximum duration. [90] calendar days. A longer period needs the executive sponsor's signature and a fresh request, not an extension."
    },
    {
      "template": "patch-exceptions-clause",
      "template_title": "Patch management policy exceptions clause",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-exceptions-clause/",
      "section": "Annex A",
      "section_title": "Patch exceptions",
      "clause": "A.7",
      "text": "Re-check. The patch coordinator reviews every open exception at least every [30] days to determine whether the window can be met now, and records the result."
    },
    {
      "template": "patch-exceptions-clause",
      "template_title": "Patch management policy exceptions clause",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-exceptions-clause/",
      "section": "Annex A",
      "section_title": "Patch exceptions",
      "clause": "A.8",
      "text": "Expiry. An exception ends on its end date. The asset then falls under the standard window; an expired exception is reported as a missed window in the next monthly report."
    },
    {
      "template": "patch-exceptions-clause",
      "template_title": "Patch management policy exceptions clause",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-exceptions-clause/",
      "section": "Annex A",
      "section_title": "Patch exceptions",
      "clause": "A.9",
      "text": "Register. The patch coordinator keeps a register of open and closed exceptions with every field in A.4; the register is part of the monthly report."
    },
    {
      "template": "patch-exceptions-clause",
      "template_title": "Patch management policy exceptions clause",
      "template_url": "https://patchmanagementpolicy.com/templates/patch-exceptions-clause/",
      "section": "Annex A",
      "section_title": "Patch exceptions",
      "clause": "A.10",
      "text": "Escalation. A window that is going to be missed without an approved exception is escalated to the executive sponsor before it expires."
    }
  ]
}