From 31f7a4886539c2a335fb673d982df6bc5db221e0 Mon Sep 17 00:00:00 2001 From: Tim Bannister Date: Thu, 25 Aug 2022 17:46:07 +0100 Subject: [PATCH] Reinstate implementation details for CVE feed announcement Once the related implementation details article is published, we can reinstate the paragraph that hyperlinks to that article. --- .../index.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/content/en/blog/_posts/2022-09-12-Announcing-the-Auto-Refreshing-Official-CVE-Feed/index.md b/content/en/blog/_posts/2022-09-12-Announcing-the-Auto-Refreshing-Official-CVE-Feed/index.md index 813493adff..7697ac8e92 100644 --- a/content/en/blog/_posts/2022-09-12-Announcing-the-Auto-Refreshing-Official-CVE-Feed/index.md +++ b/content/en/blog/_posts/2022-09-12-Announcing-the-Auto-Refreshing-Official-CVE-Feed/index.md @@ -48,6 +48,14 @@ official Kubernetes CVEs releases through their work in Kubernetes Community - via various Special Interest Groups and Committees. +## Implementation Details + +A supporting +[contributor blog](https://kubernetes.dev/blog/2022/09/12/k8s-cve-feed-alpha/) +was published that describes in depth on how this CVE feed was implemented to +ensure the feed was reasonably protected against tampering and was automatically +updated after a new CVE was announced. + ## What's Next? In order to graduate this feature, SIG Security