# How Automated Vulnerability Remediation is written

Editorial policy, read 10 Nov 2026

**The short answer.** Editorial policy: every fact on Automated Vulnerability Remediation comes from a page the editor opened and dated. The first edition was read on 10 Nov 2026 and the second on 19 Nov 2026. Platforms are listed alphabetically, claims are labeled by origin, and nothing is scored or placed in an order of merit.

A platform is added when it publicly describes agents that work a vulnerability backlog after a scanner has produced findings. Each platform is described under the same seven topics, in the same order, so a reader can compare one topic across vendors without hunting for it.

Every fact carries a label. A statement on the vendor's own site is labeled a vendor claim. A statement from an outlet or another outside party is labeled a third-party source. Where a page was read and the thing was not on it, the entry says none found on that date, with the date, which describes the pages read and not the product.

Customer numbers are quoted in the vendor's own wording and labeled the vendor's claim. When the page gives no method for a figure, the entry says so. The editor does not run vendor products, so no entry describes a test the editor performed.

Each entry shows its read date. A fact read on 10 Nov 2026 or 19 Nov 2026 describes the page on that day, and vendors change their pages. A vendor can send a newer source for any fact about its platform; the entry then moves to the new page with a new read date, and the older reading is kept in the correction note.

News items link the original announcement and are added only from primary sources the editor opened on the read date. They sit as anchored entries on the news page, newest first, ordered by date and not by importance.

The security content rule is fixed. The site publishes no exploit code, no proof-of-concept steps and no scanning instructions. Where a vulnerability is discussed, the text gives preconditions, detection, mitigation and fix, taken from vendor advisories, the National Vulnerability Database and the CISA Known Exploited Vulnerabilities catalog.

Wording stays plain. Text avoids claims of superiority and instructions to buy. A guide may describe what to check in a trial or a contract; it does not say which platform to choose.

## Related pages

- [About](/about/)
- [Corrections](/corrections/)
- [Contact](/contact/)
- [Privacy](/privacy/)
- [Terms](/terms/)

## Sources

- NVD CVE API: https://nvd.nist.gov/developers/vulnerabilities (read 10 Nov 2026)
- CISA Known Exploited Vulnerabilities catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://automatedvulnerabilityremediation.com/editorial-policy/
