# Contact the Editor of Patch Management Policy

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

## Contact

Write to editor@patchmanagementpolicy.com. The most useful message names a page, quotes the sentence and links the issuer's text. Messages about a source that could not be read on 19 Nov 2026, such as PCI DSS v4.0.1 or ISO/IEC 27001 Annex A 8.8, are especially welcome.

### Address

[editor@patchmanagementpolicy.com](mailto:editor@patchmanagementpolicy.com). There is no contact form, because the site runs no server-side code and loads no scripts; the address is a plain mail link.

No response time is promised. A confirmed correction is entered on the [corrections page](https://patchmanagementpolicy.com/corrections/) with its date.

Mail is the only channel. If you quote a clause in your message, give the issuer's own URL, not a copy, so the reading can be compared with the text in force.

### What to include, by kind of message

| You are writing about | Include |
|---|---|
| A wrong number or clause | Page address, the sentence, the issuer's text or URL, and the date you read it |
| A source the site could not read | Which one (see the method), the passage you can read, and where it is published |
| A tool entry in the directory | The tool, the field, the vendor page that shows the difference, and the date |
| A template | Which one in the template set, the sentence, and the framework clause it should match |
| A change in a framework | The framework, the new effective date and the issuer's notice |

Message guide, edition of 19 Nov 2026.

### Items that change on a known date

Some entries have a date that will move the table. Writing about these is useful before the date, not after: the FedRAMP vulnerability detection and response rules become mandatory on 7 Dec 2026 with a grace period to 7 Mar 2027 (per notice NTC-0014, read in full on 19 Nov 2026), and CISA states that it reassesses BOD 26-04 Table 1 once per fiscal year.

Messages are used to answer you and to fix the site, as set out on the [privacy page](https://patchmanagementpolicy.com/privacy/). License for reuse of what you find here is on the [about page](https://patchmanagementpolicy.com/about/).

### Sources

- [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

Last reviewed 19 Nov 2026

### Related pages

- [Corrections Log and Open Source Gaps, Edition 1](https://patchmanagementpolicy.com/corrections/)
- [How the Patch Window Table Is Built and Read](https://patchmanagementpolicy.com/method/)
- [About Patch Management Policy: scope and sources](https://patchmanagementpolicy.com/about/)
- [Privacy: what this site logs and for how long](https://patchmanagementpolicy.com/privacy/)
