From 855cd4a9f53fe591b1ce095433a8069a8159b930 Mon Sep 17 00:00:00 2001 From: Felix Kronlage-Dammers Date: Wed, 18 Feb 2026 21:20:35 +0100 Subject: [PATCH] deep link to page number this was a suggestion from @depressiveRobot in #1099, since we link the same document/passage here, adopt this. Signed-off-by: Felix Kronlage-Dammers --- Standards/scs-0124-v1-security-of-iaas-service-software.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Standards/scs-0124-v1-security-of-iaas-service-software.md b/Standards/scs-0124-v1-security-of-iaas-service-software.md index 94b1200dd..d2f90bac8 100644 --- a/Standards/scs-0124-v1-security-of-iaas-service-software.md +++ b/Standards/scs-0124-v1-security-of-iaas-service-software.md @@ -110,7 +110,7 @@ From the moment a vulnerability is disclosed these are the advised reaction time 3. Mid (CVSS = 4.0 – 6.9): 1 month 4. Low (CVSS = 0.1 – 3.9): 3 months -[^1]: [C5 criteria catalog with timeframes for responses on page 70.](https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/CloudComputing/ComplianceControlsCatalogue/2020/C5_2020.pdf?__blob=publicationFile&v=3) +[^1]: [Cloud Computing Compliance Criteria Catalogue – C5:2020 with time frames for responses on page 70.](https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/CloudComputing/ComplianceControlsCatalogue/2020/C5_2020.pdf?__blob=publicationFile&v=3#page=72) This standard will follow this guidance and refer to these timeframes as "reasonable timeframes".