# How the Patch Window Table Is Built and Read

Canonical: https://patchmanagementpolicy.com/method/
Last reviewed: 19 Nov 2026

## How the patch window table is built

Every window on this site was read from the issuer's own text on 19 Nov 2026 and carries a quote, a URL and that read date. Four texts could not be opened that day: the PCI DSS v4.0.1 requirements, ISO/IEC 27001 Annex A 8.8, the SOC 2 criteria and the Essential Eight maturity model.

### What a row holds

A row in the [patch window table](https://patchmanagementpolicy.com/patch-windows/) has eight fields: framework, version, clause number, the clause text, the timing, who it applies to, the severity basis and the source URL with its read date. The clause text is quoted verbatim and kept short. The timing field is the issuer's number or the words "no number set"; it is never inferred from other documents.

Each row is labeled primary (standards and government text), vendor (a company describing its own product or schedule) or third-party. Microsoft's release schedule is labeled vendor even though Microsoft is the primary source for it.

### Texts that could not be read

| Text | What happened on 19 Nov 2026 | What the site does |
|---|---|---|
| PCI DSS v4.0.1 requirement text | The standard PDF returned HTTP 403 and the library needs an agreement form | Quotes PCI SSC FAQ 1597 (Requirement 6.3.3, one month for critical) and the blog summary; the standard's own wording is not quoted |
| ISO/IEC 27001:2022 Annex A 8.8 | iso.org returned HTTP 403; the text is paywalled | No clause text, no timing |
| SOC 2 criteria CC7.1 and CC8.1 | The AICPA page needs a script and an account | No clause text, no timing |
| Essential Eight maturity model | cyber.gov.au did not load by curl or by the fetch tool | No row written |
| BOD 26-04 Table 1 | The table is an image on the page; values were read by eye | Marked as read from an image |
| HHS fact sheet on the HIPAA NPRM | HTTP 403 | The Federal Register text is used instead |

Gaps recorded on 19 Nov 2026. A gap is stated as "could not be read", never filled from memory.

The corrections page lists the same gaps as [open items](https://patchmanagementpolicy.com/corrections/).

### How the builder picks a window

For each severity the builder looks at the frameworks you ticked, lists the numbers they state, and offers the shortest one as the default, shown with the framework it came from. Severity names are mapped by the words each issuer uses: Cyber Essentials "critical or high risk" and PCI "critical" map to the highest two levels; BOD 26-04 is mapped by its Table 1 rows, not by a single label.

Clocks differ too. Cyber Essentials counts from release, FedRAMP's legacy page from discovery, the HIPAA proposal from "identifying the need to patch", and BOD 26-04 from the KEV listing or the agency's identification, whichever comes first. The builder prints the clock start next to every window so two numbers are never compared without it.

### What the site does not do

No tool in the [directory](https://patchmanagementpolicy.com/tools/) is graded or called better than another; the same eight fields are read for each, vendors appear alphabetically, and claims are labeled as the vendor's. Clause readings are not legal or audit advice; the assessor or regulator reads the clause in force. For the editorial rules see the [editorial policy](https://patchmanagementpolicy.com/editorial-policy/).

### Sources

- [PCI SSC blog, Just Published: PCI DSS v4.0.1 (11 Jun 2024)](https://blog.pcisecuritystandards.org/just-published-pci-dss-v4-0-1), read 19 Nov 2026
- [CISA, BOD 26-04, Prioritizing Security Updates Based on Risk](https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk), read 19 Nov 2026
- [Federal Register, HIPAA Security Rule NPRM, 90 FR 898 (6 Jan 2025)](https://www.federalregister.gov/documents/2025/01/06/2024-30983/hipaa-security-rule-to-strengthen-the-cybersecurity-of-electronic-protected-health-information), read 19 Nov 2026
- [NCSC, Cyber Essentials Requirements for IT Infrastructure v3.3, Security Update Management](https://www.ncsc.gov.uk/sites/default/files/2026-11/Cyber-Essentials-Requirements-for-IT-Infrastructure-v3-3.pdf), read 19 Nov 2026
- [FedRAMP legacy playbook, POA&M, Remediation Requirements](https://www.fedramp.gov/legacy/playbook/csp/authorization/poam/), read 19 Nov 2026

Last reviewed 19 Nov 2026

### Related pages

- [Patch Window Table: Deadlines in 12 Frameworks](https://patchmanagementpolicy.com/patch-windows/)
- [Patch Window Table Method: Row Rules and Read Log](https://patchmanagementpolicy.com/patch-windows/method/)
- [Editorial Policy: sources, labels and read dates](https://patchmanagementpolicy.com/editorial-policy/)
- [Corrections Log and Open Source Gaps, Edition 1](https://patchmanagementpolicy.com/corrections/)
