From ec2881a7e1c1e4f874211c08c499fd2f14e04a17 Mon Sep 17 00:00:00 2001 From: "Bernhard E. Reiter" Date: Fri, 27 Jan 2023 09:42:51 +0100 Subject: [PATCH] Update docs/proxy-provider-for-aggregator.md Co-authored-by: tschmidtb51 <65305130+tschmidtb51@users.noreply.github.com> --- docs/proxy-provider-for-aggregator.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/proxy-provider-for-aggregator.md b/docs/proxy-provider-for-aggregator.md index e321dd2..f34d714 100644 --- a/docs/proxy-provider-for-aggregator.md +++ b/docs/proxy-provider-for-aggregator.md @@ -5,7 +5,7 @@ calls it a *CSAF publisher*. After manually downloading the advisories from such a publisher, the tools here can be used to offer the CSAF files for automated downloading -as *CSAF aggregator*. (The construct is called *CSAF proxy provider*.) +as *CSAF aggregator*. (The construct is called *CSAF proxy provider*. See [Section 7.2.5](https://docs.oasis-open.org/csaf/csaf/v2.0/csaf-v2.0.html#725-role-csaf-aggregator) for more details.) There are three necessary steps, easiest is to use one single virtual maschine (or container) per internal provider.