From 64009696df90ac3fdfa12db16d69c651343eaecc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20Prpi=C4=8D?= Date: Mon, 25 Nov 2024 08:45:37 -0500 Subject: [PATCH] Fix broken link to example CSAF document --- docs/csaf-vex.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/csaf-vex.md b/docs/csaf-vex.md index 0c1442c..0f8457a 100644 --- a/docs/csaf-vex.md +++ b/docs/csaf-vex.md @@ -38,7 +38,7 @@ Although CSAF advisory and VEX files ultimately serve different purposes, both f CSAF machine-readable standard and use the VEX profile to convey security information. The CSAF standard includes three main sections: document metadata, a product tree and vulnerability metadata. The full document structure can be found -[here](https://github.com/RedHatProductSecurity/security-data-guidelines/blob/csaf-vex-guidelines/docs/csaf-vex.json). +[here](https://github.com/RedHatProductSecurity/security-data-guidelines/blob/main/csaf-vex/csaf-vex.json). The following sections break down the information included in CSAF-VEX documents using the [VEX file for CVE-2023-20593](https://access.redhat.com/security/data/csaf/v2/vex/2023/cve-2023-20593.json) as an example.