Open santosomar opened 3 years ago
In case it's of interest, there is an emerging discussion at the following link on how to communicate advisories in a format called VEX:
This document is meant to give guidance on what interfaces and information elements are necessary as part of the technical solution to describing the state of potential vulnerabilities in a product.
Perhaps in some iteration of the security.txt standard, it might suggest that such advisories when linked in a security.txt file SHOULD comply with the VEX format.
Makes sense. FYI: The VEX community, NTIA and CSAF TC are working together. VEX is supported in CSAF. CSAF is one of the first standards supporting VEX. Some examples here.
Being that the draft is in final review by the IETF / IESG, and this can be done via a new registry field, going to recommend delaying this until the registry is up and running
Absolutely! Thank you so much for the consideration.
To follow up on this... This is a good suggestion by @tschmidtb51 Just the use of the keyword "CSAF" instead of CSAF/CVRF Repository.
# Human-readable Security Advisories
Advisories: https://example.com/security/advisories
# Machine-readable CSAF documents
CSAF: https://example.com/security/csaf-service.json
Reasoning: All other keywords are one word. CVRF didn't have a specification where and how to find those documents, CSAF does.
CSAF field has been added to the registry
Excellent! Thank you so much for your support!
This may go hand-in-hand with #200 . The request is to add a link to the machine readable and human readable advisories of a company. For example:
Some vendors also have an API (such as https://developer.cisco.com/psirt/), but unfortunately, only just a very few do.