Patch Management Policy

How to track vendor patch releases

Track vendor releases by their published rhythm. Microsoft ships on the second Tuesday (next: 8 Dec 2026, then 12 Jan 2027), Oracle on the third Tuesday of January, April, July and October (next: 19 Jan 2027), Fortinet on the second Tuesday, Android on the first Monday. Read 19 Nov 2026.

Release calendar for the next 90 days

A calendar is only a prompt: every vendor below reserves the right to publish outside it. The table lists the rule each vendor states and the next dates that follow from it as of 19 Nov 2026. Dates after the vendor's own list were computed from the rule and are marked.

Sources: vendor pages listed below, read 19 Nov 2026. Where the page lists dates they are quoted; otherwise the date is computed from the stated rule.
Vendor or feedStated rhythmNext dates
Microsoft (Windows)Security update on the second Tuesday, typically 10:00 AM Pacific; optional preview update in the fourth week; out-of-band as needed8 Dec 2026, 12 Jan 2027 (computed from the rule)
FortinetAdvisories on the second Tuesday of the month; critical issues may go out of cycle8 Dec 2026, 12 Jan 2027 (computed)
OracleCritical Patch Update on the third Tuesday of January, April, July and October; pre-release announcement the Thursday before19 Jan 2027, 20 Apr 2027 (listed by Oracle)
AndroidBulletin on the first Monday of each month, with two patch levels (the 1st and the 5th)7 Dec 2026, 4 Jan 2027 (computed)
CiscoIndividual advisories usually on a Wednesday at 1600 GMT; bundles for FXOS and NX-OS (fourth Wednesday of February and August), IOS XR (second Wednesday of March and September), IOS and IOS XE (fourth Wednesday of March and September)24 Feb 2027, 10 Mar 2027, 24 Mar 2027 (computed)
KubernetesMonthly patch release, cherry-pick deadline a few days before15 Dec 2026, 12 Jan 2027 (listed by the project)
AppleNo fixed day stated on the security releases pageLast listed: iOS 27.2.1 and macOS releases on 9 Nov 2026; HomeView 27.2.1 on 18 Nov 2026

Feeds that are not vendor calendars

CISA's Known Exploited Vulnerabilities catalog is machine-readable. On 19 Nov 2026 the JSON feed showed catalog version 2026.11.18 with 1,786 entries, of which 302 were added in 2026 through 18 November (a count made from the feed's dateAdded field) (CISA KEV feed). CISA's BOD 26-04 tells federal agencies to “monitor KEV Catalog updates” and offers email alerts for additions; a private organization can subscribe the same way and treat an addition as a trigger for assessment.

Not every vendor posts to CISA. For operational technology, NIST SP 800-82 Rev. 3 notes that “not all vendors report known vulnerabilities to CISA,” and advises vendor-specific notifications in addition (NIST SP 800-82 Rev. 3).

Eight questions to put to each software maker

NIST SP 800-40 Rev. 4 section 3.7 offers a sample questionnaire for procurement that doubles as a monitoring checklist. Its items include how often the maker expects to release emergency updates, for how many years it commits to fixing vulnerabilities, whether updates follow a schedule “(weekly, monthly, quarterly, etc.),” how disruptive a patch is (restart or reboot), and whether rollback is provided for uninstalling patches. Put the answers beside each vendor in the inventory, and record the channel you subscribed to, the date, and who receives it.

The record to keep

  • The subscription list: vendor, channel, owner, date last confirmed.
  • A dated log of releases received and the asset groups each touches.
  • A note when a vendor published outside its stated rhythm, since that is when a calendar-only process fails.

Class-specific rhythms are on the pages for Windows, network devices and databases.

Sources

Last reviewed 19 Nov 2026