Who delivers security advisories in machine-readable form, and who does not
Checking automatically whether a security advisory affects your systems only works if the vendor publishes it in CSAF format. Our new directory shows who does: 85 sources, each checked at the publisher itself. The list is dense in German industry and thin for VPN gateways and firewalls.
If you want to compare security advisories automatically with your own inventory, you need them in a form a machine can read. A PDF or a web page has to be read by a person and compared with the inventory list. A document in CSAF format states affected products, versions and remediations in a fixed structure, and only then can the question “does this affect us?” be answered without retyping.
Before that question comes another one: which vendors deliver in this form at all? From today there is a directory for that on our website, the CSAF sources.
What the directory contains
On 9 November it listed 85 sources. Each of them publishes a provider-metadata.json, the file tools use to discover a source and to learn how to fetch its documents. 15 entries come from the BSI CSAF lister, 39 from the CERT@VDE aggregator, and 31 we retrieve directly from the publisher without them being listed in an aggregator. We retrieve every file from the publisher itself; name, role and category appear in the directory exactly as the publisher states them.
79 of the 85 sources are trusted providers. They supply checksums and an OpenPGP signature for every document, so you can verify that an advisory comes unchanged from its publisher. Microsoft lists itself in its own file as a provider, that is without this level.
Where the list is dense
More than half of the entries come via CERT@VDE, and most of them are vendors from automation and industry: Phoenix Contact, WAGO, Beckhoff, Festo, Pilz, Endress+Hauser and many more. Anyone running controllers and field devices will find a large share of their suppliers here. From classic IT, Microsoft, Cisco, Red Hat, SUSE, Siemens, Schneider Electric, Huawei and Trend Micro are among those included, along with coordinators such as the BSI, CISA and the Dutch NCSC.
Where it is thin
The standard provides three ways for a tool to find a vendor’s metadata file: an entry in security.txt, a fixed location under /.well-known/csaf/ and a fixed DNS name. For Fortinet, Palo Alto Networks, Ivanti and Citrix, we found no file on any of these three ways on 9 November.
These are, of all things, vendors of VPN gateways and firewalls, devices that sit at the edge of the network. Their vulnerabilities regularly end up in CISA’s catalog of known exploited vulnerabilities: as of 6 November it lists 38 entries for Ivanti, 32 for Fortinet, 27 for Citrix and 16 for Palo Alto Networks. Fortinet and Palo Alto Networks do publish CSAF documents, we checked one of each, but without a metadata file. A tool will then not find them on its own, and every document has to be fetched individually. The directory lists such vendors in a separate group “CSAF per advisory only”; on 9 November there were 13, including Oracle, Intel and Arista. Ivanti and Citrix appear in neither group. For their devices, reading web pages remains the way for now.
What this means for selection
Anyone assessing suppliers or preparing a tender can add the question: does the vendor publish its security advisories in CSAF format, with a provider-metadata.json? From 11 December 2027, the Cyber Resilience Act requires manufacturers to publish information about fixed vulnerabilities once a security update is available (Annex I Part II No. 4). The regulation does not prescribe a format. A vendor that delivers CSAF already releases this information today in a form your tools can read.
How the directory stays current
We regularly reconcile the list with both aggregators. New sources appear marked “new”, and sources that have not responded for a while stay listed with the date of their last response. The directory is also available in machine-readable form at hub.isidaten.com/csaf-quellen.json, structured like a CSAF lister; the “per advisory only” group is deliberately not included, as there is nothing to subscribe to. Intevation maintains a further overview with a check result per source in its CSAF Provider Index.
In the vulnerability management module of isidaten the sources can be connected directly: it reads provider-metadata.json and aggregator.json and creates several providers from one aggregator in a single step. Retrieval is limited to approved domains; cert-bund.de and certvde.com are approved out of the box, any other domain is approved by an administrator first.
Questions about this update?
Talk to us – we are happy to show you this feature in a demo.


