Corrections

How FirewallSync corrects errors, and a public log of significant corrections to published articles.

We try to get things right. When we don’t, we fix it in the open.

How to report an error

Send the article URL, what is wrong and, if you can, a source that shows the correct information. Email editors@firewallsync.com or see the contact page. We read every report.

What we do

  • Factual errors (a wrong configuration flag, a misattributed score, a misdescribed attack, an outdated vendor default) are fixed in the article, and the article shows an updated date.
  • Significant errors, ones that could lead a reader to a worse security decision or misstate what a source says, are also explained in a “Correction” note at the end of the article and listed in the log below.
  • Typos, broken links and formatting are fixed without a note.
  • Fast-moving advisories (unpatched zero-days, vendor bulletins that are still being revised) are updated as the vendor publishes new information. Those updates are not corrections unless what we said was wrong at the time.

We do not silently remove published articles to hide mistakes.

Correction log

Newest first. Each entry links to the corrected article.

DateArticleWhat was wrongWhat changed
Oct 13, 2026VEX Explained: What a “Not Affected” Statement MeansSaid OpenVEX meets CISA’s minimum requirements for VEX. The OpenVEX specification says it aims to meet them.Wording corrected in three places; correction note added.
Oct 12, 2026CISA BOD 26-04 ExplainedDescribed CVSS scores as “listed in NVD” when they were CISA’s enrichment (ADP) scores in the CVE records. Said every KEV entry added on October 8 was marked for forensic triage; CVE-2015-5477 (BIND) is not.Table column, footnote and sources table corrected; correction note added.