Security Advisory Triage

Turn a vulnerability claim into an evidence-based applicability decision. A public post is a useful lead, not proof that a named system is affected or compromised.

Prerequisites

• An advisory link, CVE/vendor identifier, product name, or quoted claim.
• Read-only access to local version/configuration evidence when the user wants a specific asset checked.
• Current web access for authoritative advisory research. If it is unavailable, mark affected-version conclusions unverified.

Trigger

• "Are we affected by this CVE?"
• "Check this security advisory against our deployment"
• "Is this exploit post real and relevant to us?"
• "Which version fixes this vulnerability?"
• "Does this exposed feature mean we were compromised?"

Workflow