# Corrections Log and Open Source Gaps, Edition 1

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

## Corrections

The corrections log is empty as of 19 Nov 2026, the date of the first edition. When a page changes because of an error, the entry gives the date, the page and the change. Five source gaps are open and listed below, because a gap can become an error the day the text is readable.

### Log

| Date | Page | What was wrong | What changed |
|---|---|---|---|
| None yet | None | None | None |

Corrections log, empty as of 19 Nov 2026. New entries are added first.

### Open gaps from the first edition

These are not errors; they are statements the site could not check against the issuer's text on 19 Nov 2026. Each is marked on the page it affects. A gap leaves this list when the text is read, and a page that said something different is corrected with an entry in the log above. Two gaps closed before the first edition went out and are not listed: the FedRAMP notice NTC-0014 and the clause number for the PCI DSS one-month rule, which were read in full from fedramp.gov and from PCI SSC FAQ 1597 on 19 Nov 2026.

1. PCI DSS v4.0.1: the requirement text returned HTTP 403. The one-month window and the number 6.3.3 come from PCI SSC FAQ 1597 (May 2025), not from the standard.
2. ISO/IEC 27001:2022 Annex A 8.8 and SOC 2 criteria CC7.1 and CC8.1: clause text not read.
3. CISA BOD 26-04 Table 1: values were read from an image by eye.
4. CIS Controls: wording is from the v8 guide of August 2023; the v8.1 wording of 7.3, 7.4 and 7.7 is unconfirmed.
5. Essential Eight maturity model: not readable, so no row exists.

### How to report an error

Write to [editor@patchmanagementpolicy.com](mailto:editor@patchmanagementpolicy.com) with the page address, the sentence, and the issuer's text or URL that shows the difference. A source that the site could not read is the most useful thing to send; the [contact page](https://patchmanagementpolicy.com/contact/) lists what else helps.

What counts as a correction: a wrong number, a wrong clause reference, a wrong date, a label that does not match the source, a link that no longer supports the claim. Wording changes that do not alter a fact are not logged. See the [editorial policy](https://patchmanagementpolicy.com/editorial-policy/) for the rules and the [patch window table](https://patchmanagementpolicy.com/patch-windows/) for the rows affected.

### 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
- [FedRAMP, notice NTC-0014](https://www.fedramp.gov/notices/0014/), read 19 Nov 2026
- [CIS Controls v8 (August 2023 guide), Control 7 safeguards](https://storage.pardot.com/799323/1693938137QgfIAdmE/CIS_Controls__v8__Critical_Security_Controls__2023_08.pdf), read 19 Nov 2026

Last reviewed 19 Nov 2026

### Related pages

- [Editorial Policy: sources, labels and read dates](https://patchmanagementpolicy.com/editorial-policy/)
- [Contact the Editor of Patch Management Policy](https://patchmanagementpolicy.com/contact/)
- [How the Patch Window Table Is Built and Read](https://patchmanagementpolicy.com/method/)
- [Patch Window Table: Deadlines in 12 Frameworks](https://patchmanagementpolicy.com/patch-windows/)
