Skip to content

Vendor advisories

Many vendors of industrial products, and coordinators such as BSI and CISA, publish their security advisories as machine-readable CSAF 2.0 documents. Affectra reads the advisories of a fixed list of providers, matches your components against the products they name, and shows them on your findings as Vendor advisories.

A finding shows a vendor advisory when the advisory names one of the finding’s CVEs. For each advisory you see:

  • the provider, such as Siemens ProductCERT or BSI CERT-Bund WID;
  • the advisory’s ID, such as SSA-104023, which links to the advisory at the provider;
  • for products the advisory says are fixed, the version that fixes them, and a link to the vendor’s fix where it gives one.

The API returns them in each finding’s vendor_advisories. The agent tools return them too: explain_finding lists the advisories for a finding’s CVEs.

An advisory the provider withdraws, or removes from its list, no longer shows.

An advisory also creates a finding when it names one of your components as affected. Affectra compares only for components that no supported ecosystem describes (see How matching works), in three ways:

  • By package URL, when the advisory names the package by purl.
  • By CPE, when the advisory names the product by CPE and your SBOM gives the component a CPE, or your mapping does. The finding is marked CPE (or your mapping).
  • By your vendor product mapping, when an admin of your organization has mapped the package to a product that the advisory names by model number, SKU or product name. The finding is marked your mapping, and only your organization sees it.

The advisory must say the product is known affected at your component’s version: that exact version, or a version range it gives in the vers: notation. If the advisory also says a version at or below yours is fixed, there is no finding. Advisories that say “all versions” create a finding only through a vendor product mapping. A range given only in words (“all versions before V3.1”) never creates one. Most advisories today name products only by name or model number; without a vendor product mapping those show as vendor advisories but create no finding.

When the vendor’s advisory and other sources report the same CVEs for a component, the vendor’s advisory is the best-ranked chip in the row for the CVE, and the others are listed beside it. See One finding for several advisories.

Provider Kind
BSI CERT-Bund WID Coordinator
CERT@VDE Coordinator
Phoenix Contact PSIRT, hosted by CERT@VDE Vendor
CISA Coordinator
Siemens ProductCERT Vendor

Each provider is off until its terms of use have been reviewed for this use. An installation turns providers on one by one, so yours may show advisories from some of these providers or from none. The attribution each provider asks for is on Licences and notices.

Affectra loads an advisory only after these checks:

  • It comes from the provider’s own server. Affectra follows no redirects and contacts no other host.
  • Its SHA-512 hash matches.
  • It is signed with one of the provider’s OpenPGP keys that Affectra knows. When a provider starts using a new key, its new advisories wait until Affectra has checked and added that key.
  • It is valid CSAF 2.0.
  • It is marked TLP:CLEAR or TLP:WHITE, meaning it may be shared without limits. Advisories with restricted sharing, such as TLP:GREEN, are never loaded, because Affectra’s vulnerability data is shared by every organization.

Affectra checks each provider every 6 hours, like OSV. See Vulnerability sources.