Check your assets against every advisory

Paste or upload the industrial products you run, with their versions. The Brief checks them against every story in its archive and marks each match Affected, Not affected or Check.

Your list stays in this browser. It is read and matched on this page and is never uploaded or sent anywhere. Tick Remember to keep it in this browser for next time.

How the check works

Results are grouped by asset, most serious first. Under each asset, every advisory that concerns it: the severity, whether the flaw is known to be exploited, when to act, how your version compares, the fixed version, what to do, what to do until you can patch, how to check whether you are exposed, signs to watch for, the CVE records, the advisory itself and a before-the-patch worksheet. Stories about the same flaw (a shared CVE, or a later update) are shown as one advisory.

• Affected: the story lists your product, and your version is inside a range it says is affected.
• Not affected: the story lists your product, and your version is outside every affected range. Confirm with the vendor advisory before closing it.
• Check: the story names your product but gives no versions, your line has no version, or a version cannot be compared. Stories before 28 October 2026 carry no version data, so a product named in them is always Check.

Products and versions come from the advisory itself: for CISA ICS advisories, CISA's machine-readable CSAF file; otherwise the story's source text, keeping only names and version numbers that appear in it. Names are matched loosely (case and punctuation ignored), so read each match. The Brief covers what it has published, not every advisory ever issued: no match is not proof that a product is safe. Methodology