Skip to content

Commit e23e99c

Browse files
committed
Move explanation of DigiSov into a separate page.
Use a short description as overview page. Signed-off-by: Kurt Garloff <kurt@garloff.de>
1 parent 9668bb8 commit e23e99c

File tree

2 files changed

+46
-1
lines changed

2 files changed

+46
-1
lines changed

sidebarsStandards.js

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,10 @@ const sidebars = {
77
label: 'Certification',
88
link: {
99
type: 'doc',
10-
id: 'certification/digisov-and-cert'
10+
id: 'certification/cert-levels'
1111
},
1212
items: [
13+
'certification/digisov-and-cert',
1314
{
1415
type: 'category',
1516
label: 'Scopes and Versions',
Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
# SCS certification overview
2+
3+
## Digital sovereignty drives SCS certification
4+
5+
The SCS project takes a comprehensive perspective on digital sovereignty.
6+
Please read [Digital Sovereignty and SCS certification](digisov-and-cert)
7+
for more details.
8+
9+
The basic level, control over data that at least allows to comply with the
10+
European GDPR regulation, is *not* certified by SCS; while the SCS software
11+
makes it easy to build (local) clouds that fulfill these, it depends on the
12+
operators of the infrastructure what compliance rules they fulfill.
13+
14+
The SCS project however has defined certification levels for levels two,
15+
three and four in the sovereignty taxonomy.
16+
17+
| Digital Sovereignty level | SCS certification |
18+
|-----------------------------------|-------------------------|
19+
| 1: Data Sov'ty / Legal compliance | (Refer to ENISA/Gaia-X) |
20+
| 2: Provider switching / Tech Compatiiblity | SCS-compatible |
21+
| 3: Ability to shape technology | SCS-open |
22+
| 4: Transparency & SKills for Operations | SCS-sovereign |
23+
24+
As of September 2024, the *SCS-compatible* certification level is defined
25+
and used; the details for the higher levels are still being worked on.
26+
27+
## Certification process
28+
29+
To get certified, the infrastructure needs to fulfill the criteria.
30+
As far as possible, these are implemented as automated tests that run
31+
continuously (daily) to assure continuous compliance. The results are
32+
made transparent via the the [Certified Clouds overview](overview) page.
33+
34+
To get officially certified with the right to use the SCS brand and getting
35+
listed on this page requires to work with the Forum SCS-Standards at the
36+
[OSB Alliance](https://osb-alliance.com/) which takes over this aspect
37+
from the [SCS project](https://scs.community/). It requires membership
38+
or certification fees to cover the efforts of standardization and
39+
certification.
40+
41+
The process is described in more details on the
42+
[Getting SCS-compatible certification (for Operators)](getting-scs-compatible-certified)
43+
page. An example with technical testing and adjustments is on the
44+
[Testing and Adjustment example](test-and-adapt-example) page.

0 commit comments

Comments
 (0)