# Editorial Policy: sources, labels and read dates

Canonical: https://patchmanagementpolicy.com/editorial-policy/
Last reviewed: 19 Nov 2026

## Editorial policy

Every fact on this site carries a source URL and a read date, and every number carries both. Sources are labeled primary, vendor or third-party. The first edition, dated 19 Nov 2026, lists 31 tools in the directory: 16 that deploy patches and 15 that prioritize them, each read by the same eight fields.

### Sourcing rules

1. A standard or regulation is quoted from its own text. If the text could not be opened, the page says "could not be read on 19 Nov 2026" and writes nothing in its place.
2. A quote is short and verbatim. A claim in our own words sits beside the quote that supports it.
3. A number appears only with its source and the date it was read. A number we counted ourselves, such as an entry count in a public feed, says so.
4. Absence is dated: "none found on 19 Nov 2026", never a flat statement that something does not exist.
5. Security content stays at preconditions, detection, mitigation and fix. No exploit code, proof-of-concept steps or payloads.

### Labels

| Label | Meaning | Example on this site |
|---|---|---|
| Primary | Standards, laws, government directives | CISA BOD 26-04, NIST SP 800-40 Rev. 4 |
| Vendor | A company describing its own product, price or schedule | Microsoft's Patch Tuesday rule, any tool's feature page |
| Third-party | Analysis by someone who is not the maker | Mandiant time-to-exploit study |

Labels used in the data files and on the pages, as of 19 Nov 2026.

### Tools in the directory

Each tool in the [directory](https://patchmanagementpolicy.com/tools/) is read through the same eight fields: what it patches, how it deploys, approval and staging, compliance reporting, pricing, what it does well as the vendor states it, limits found, and dated facts. Vendors are listed alphabetically within their kind. No tool is graded or called better than another, and a vendor's claim is shown as the vendor's.

### Hosting and mail

The site is static files on Amazon S3 served by Amazon CloudFront, with no cookies, no analytics and no third-party scripts. Logs are covered on the [privacy page](https://patchmanagementpolicy.com/privacy/). Templates and data are under CC BY 4.0, with the cite line on the [about page](https://patchmanagementpolicy.com/about/).

### Changing a page

A correction changes the page text, moves the page's modified date and is entered on the [corrections page](https://patchmanagementpolicy.com/corrections/) with the date, the page and what changed. Report an error to [editor@patchmanagementpolicy.com](mailto:editor@patchmanagementpolicy.com). The way clauses are read is described in the [method](https://patchmanagementpolicy.com/method/). How the templates and data may be reused, and what a reader may rely on, is set out in the [terms of use](https://patchmanagementpolicy.com/terms/).

### Sources

- [NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning (April 2022)](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf), 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

Last reviewed 19 Nov 2026

### Related pages

- [How the Patch Window Table Is Built and Read](https://patchmanagementpolicy.com/method/)
- [Corrections Log and Open Source Gaps, Edition 1](https://patchmanagementpolicy.com/corrections/)
- [About Patch Management Policy: scope and sources](https://patchmanagementpolicy.com/about/)
- [Patch Management Tools Directory: Two Kinds, Same Fields](https://patchmanagementpolicy.com/tools/)
