Editorial policy

Every claim rests on text read from its source on a stated date, 19 Nov 2026 for the first edition. Standards and government text come first, quotes stay short and exact, vendor statements are labeled as the vendor's, and a page changes its modified date only when a fact on it changes.

  1. RemediateCovered here
  2. Mitigate now, fix laterCovered here
  3. Accept with a dated exceptionCovered here

How each kind of statement is treated

Kind of statementTreatmentExample on the site
A definitionQuoted from the issuer in quotation marks, with the document and sectionRemediation as "eliminated through patching, decommissioning the system, or another action" (CISA BOD 26-04)
A countComputed by script from a named version of the source, with the read date1,786 KEV entries in catalog version 2026.11.18
A dateTaken from the issuer's own page; a day count is marked as arithmetic by this site7 Dec 2026 to 7 Mar 2027 is 90 days
A vendor claimShown as the vendor's and linked to the vendor pageCloudflare managed ruleset documentation
An absenceWritten as "None found on" plus the date, a statement about one day's readingNo KEV required action read on 19 Nov 2026 names MFA
An inferenceLabeled as where the cited text points, never as a ruling on an organizationA decision row's guidance label

Each fact in the data files carries one label: primary (text from the standard, law or directive itself), vendor (the vendor's own statement), third-party (a report by someone else) or none-found (a dated search that returned nothing).

Sources and quotes

  • Primary text first. Directives, standards and regulator pages from CISA, NIST, FedRAMP and PCI SSC are quoted from their own pages. Where a PDF was read, the quote was matched to the extracted text.
  • Short quotes, exact wording. A quote keeps the source's words; only typographic quotation marks are changed to plain ones. Anything longer than a sentence is paraphrased and linked.
  • Standards with closed text. Where a standard's own text cannot be opened, the page cites an official public page of the issuer that states the requirement, such as a PCI SSC FAQ, or leaves the clause out. A source that was not opened is never cited, and no reader page carries a note about it.
  • Numbers only with a source. A number appears with the document, the section or row, and the read date, as in BOD 26-04 Table 1, read from the table image.

Wording and safety

The two key words are used as the sources use them. Remediation means the vulnerability is eliminated (BOD 26-04 wording); mitigation means exposure or impact is reduced while the vulnerability remains. Where a source uses them differently, such as NIST SP 800-40 Rev. 4 counting patching as a form of mitigating risk (Section 2.1), the page says so. The difference guide sets this out. The site contains no exploit code, proof-of-concept steps, payloads or scanning and probing instructions. Controls are described by what they change, how to verify them and what evidence to keep.

Changes and licensing

A fact that changes at its source is updated with a new read date, and the change is logged on the corrections page, which is empty so far. Report an error to editor@remediationvsmitigation.com. Data and forms are under CC BY 4.0; the terms give the cite line. For the scope of the site see the about page.

Sources

Last reviewed