Adapt references to scopes to new scopes track

mbuechse · jklare · commit cf4fd52342fa · 2026-07-24T11:27:44.000+02:00
Signed-off-by: Matthias Büchse &lt;matthias.buechse@alasca.cloud&gt;
diff --git a/Standards/scs-0004-v1-achieving-certification.md b/Standards/scs-0004-v1-achieving-certification.md
@@ -8,7 +8,7 @@ track: Global
 
 ## Introduction
 
-The Sovereign Cloud Stack (SCS) issues certificates with various scopes, among them [_SCS-compatible IaaS_](https://docs.scs.community/standards/scs-compatible-iaas) (Infrastructure as a Service) and [_SCS-compatible KaaS_](https://docs.scs.community/standards/scs-compatible-kaas) (Kubernetes as a Service).
+The Sovereign Cloud Stack (SCS) issues certificates with various [scopes](https://docs.scs.community/standards/scopes/), among them _SCS-compatible IaaS_ (Infrastructure as a Service) and _SCS-compatible KaaS_ (Kubernetes as a Service).
 
 This document details how a cloud service provider (henceforth also called operator) can attain such a certificate for one of their clouds.
 
diff --git a/Standards/scs-0007-v1-certification-integrators.md b/Standards/scs-0007-v1-certification-integrators.md
@@ -36,7 +36,7 @@ Criteria for certification, proof of experience in setting up, operating and sup
 
 The organization to be certified needs to satisfy one of the following requirements
 
-a) have successfully brought at least two SCS-compliant environments of a third party (customer) into production in the last 12 months. The two environments must fulfill at least the [_Certified SCS-compatible IaaS_](https://docs.scs.community/standards/scs-compatible-iaas) or [_Certified SCS-compatible KaaS_](https://docs.scs.community/standards/scs-compatible-kaas) scope.
+a) have successfully brought at least two SCS-compliant environments of a third party (customer) into production in the last 12 months. The two environments must fulfill at least the [_SCS-compatible IaaS_](https://docs.scs.community/standards/scopes/scs-0501) or [_SCS-compatible KaaS_](https://docs.scs.community/standards/scopes/scs-0502) scope.
 
 or
 
diff --git a/Standards/scs-0007-v2-certification-integrators.md b/Standards/scs-0007-v2-certification-integrators.md
@@ -56,7 +56,7 @@ The applicant MUST achieve a total of at least FOUR points to become SCS Silver
 - two points for each SCS-compliant IaaS public-cloud environment with at least two regions or at least three availability zones being operated by the applicant for the last 12 months, one point for 6 months.
 - two points for each SCS-compliant KaaS public-cloud environment being operated by the applicant for the last 12 months, one point for 6 months.
 
-Here, an SCS-compliant environment is one that qualifies for [_SCS-compatible IaaS_](https://docs.scs.community/standards/scs-compatible-iaas) or [_SCS-compatible KaaS_](https://docs.scs.community/standards/scs-compatible-kaas), depending on the desired certification.
+Here, an SCS-compliant environment is one that qualifies for [_SCS-compatible IaaS_](https://docs.scs.community/standards/scopes/scs-0501) or [_SCS-compatible KaaS_](https://docs.scs.community/standards/scopes/scs-0502), depending on the desired certification.
 
 ### Attestation
 
diff --git a/Standards/scs-0007-w1-certification-integrators-implementation-notes.md b/Standards/scs-0007-w1-certification-integrators-implementation-notes.md
@@ -18,7 +18,7 @@ To apply for a certification as an SCS Integrator, an application request must b
 
 If the listed references are joint environments (e.g. two or more implementation partners have jointly set up an SCS environment or manage them together), it must be sufficiently demonstrated what the applicant's own share in the setup and operation of the environment is.
 
-As specified in standard scs-0007, the listed references must also be compatible with standard scs-0004, which means they must qualify as [_Certified SCS-compatible IaaS_](https://docs.scs.community/standards/scs-compatible-iaas) or [_Certified SCS-compatible KaaS_](https://docs.scs.community/standards/scs-compatible-kaas). However, they do not necessarily have to be certified according to SCS-0004. It is sufficient to demonstrate that the respective environment meets the corresponding scope in its current version. Proof is provided by running the official [SCS compliance test suite](https://github.com/SovereignCloudStack/standards/tree/main/Tests), whereby all tests must pass. The test suite can be run either by the applicant or the attestation body. For all standards included in the scope that are not covered by the test suite, additional evidence must also be provided. Ideally, the test report and additional evidence should be submitted directly together with the application request.
+As specified in standard scs-0007, the listed references must also be compatible with standard scs-0004, which means they must qualify as [_SCS-compatible IaaS_](https://docs.scs.community/standards/scopes/scs-0501) or [_SCS-compatible KaaS_](https://docs.scs.community/standards/scopes/scs-0502). However, they do not necessarily have to be certified according to SCS-0004. It is sufficient to demonstrate that the respective environment meets the corresponding scope in its current version. Proof is provided by running the official [SCS compliance test suite](https://github.com/SovereignCloudStack/standards/tree/main/Tests), whereby all tests must pass. The test suite can be run either by the applicant or the attestation body. For all standards included in the scope that are not covered by the test suite, additional evidence must also be provided. Ideally, the test report and additional evidence should be submitted directly together with the application request.
 
 In the next step, the attestation body conducts an examination based on the application request and the accompanying evidence provided. The attestation body gets in contact with the applicant in order to resolve any remaining discrepancies and open issues together.
 
diff --git a/compliance-monitor/templates/overview.md.j2 b/compliance-monitor/templates/overview.md.j2
@@ -6,7 +6,7 @@ for the time being to have the highest degree of control
 
 ### Certified SCS-compatible IaaS
 
-These environments are officially certified by the SCS certification assessment body according to [SCS-0004](https://docs.scs.community/standards/global/scs-0004). They are regularly tested against the certificate scope [SCS-compatible IaaS](https://docs.scs.community/standards/scs-compatible-iaas/).
+These environments are officially certified by the SCS certification assessment body according to [SCS-0004](https://docs.scs.community/standards/global/scs-0004). They are regularly tested against the certificate scope [SCS-compatible IaaS](https://docs.scs.community/standards/scopes/scs-0501).
 
 | Name  | Description  | Operator  | SCS-compatible IaaS  | HealthMon  |
 |-------|--------------|-----------|----------------------|:----------:|
@@ -25,7 +25,7 @@ These environments are officially certified by the SCS certification assessment
 
 ### Certified SCS-compatible KaaS
 
-These environments are officially certified by the SCS certification assessment body according to [SCS-0004](https://docs.scs.community/standards/global/scs-0004). They are regularly tested against the certificate scope [SCS-compatible KaaS](https://docs.scs.community/standards/scs-compatible-kaas/).
+These environments are officially certified by the SCS certification assessment body according to [SCS-0004](https://docs.scs.community/standards/global/scs-0004). They are regularly tested against the certificate scope [SCS-compatible KaaS](https://docs.scs.community/standards/scopes/scs-0502).
 
 | Name  | Description  | Operator  | SCS-compatible KaaS  |
 |-------|--------------|-----------|----------------------|
