diff --git a/populateClouds.js b/populateClouds.js
index 7fc1128332..8b205915a0 100644
--- a/populateClouds.js
+++ b/populateClouds.js
@@ -11,8 +11,8 @@ async function insertCloudTable(pathIn, pathOut) {
 }
 
 insertCloudTable(
-  `standards/certification/overview.template.md`,
-  `standards/certification/overview.md`
+  `standards/certification/monitor.template.md`,
+  `standards/certification/monitor.md`
 ).catch((e) => {
   console.log(e)
 })
diff --git a/sidebarsStandards.js b/sidebarsStandards.js
index f017d34e3e..1c859a5179 100644
--- a/sidebarsStandards.js
+++ b/sidebarsStandards.js
@@ -10,6 +10,11 @@ const sidebars = {
         id: 'certification/overview'
       },
       items: [
+        {
+          type: 'doc',
+          label: 'Compliance Monitor',
+          id: 'certification/monitor'
+        },
         {
           type: 'doc',
           label: 'Compliance Check Pipeline',
diff --git a/standards/certification/monitor.template.md b/standards/certification/monitor.template.md
new file mode 100644
index 0000000000..7c768e2fe9
--- /dev/null
+++ b/standards/certification/monitor.template.md
@@ -0,0 +1,4 @@
+<!-- markdownlint-disable -->
+# SCS Compliance Monitor
+
+<!--CLOUDS-->
diff --git a/standards/certification/overview.template.md b/standards/certification/overview.md
similarity index 88%
rename from standards/certification/overview.template.md
rename to standards/certification/overview.md
index 273306e199..55e71de0e8 100644
--- a/standards/certification/overview.template.md
+++ b/standards/certification/overview.md
@@ -1,4 +1,3 @@
-<!-- markdownlint-disable -->
 # Certification
 
 SCS provides a certification framework with various [scopes](https://docs.scs.community/standards/scopes/).
@@ -23,4 +22,4 @@ The standard [SCS-0007](https://docs.scs.community/standards/global/scs-0007) de
 
 ## Compliant cloud environments
 
-<!--CLOUDS-->
+See the [SCS Compliance Monitor](https://docs.scs.community/standards/certification/monitor) for a list of compliant cloud environments.
diff --git a/standards/certification/pipeline.md b/standards/certification/pipeline.md
index ee672a362f..a62ccbac79 100644
--- a/standards/certification/pipeline.md
+++ b/standards/certification/pipeline.md
@@ -1,7 +1,7 @@
 # SCS Compliance Check Pipeline Manual
 
 The SCS compliance check suite runs automated tests, generates a signed report for the run, and feeds it to
-the compliance monitor. Roughly speaking, this process has to be performed daily, for instance, using a
+the [SCS Compliance Monitor](https://docs.scs.community/standards/certification/monitor). Roughly speaking, this process has to be performed daily, for instance, using a
 continuous-integration "pipeline".
 
 Providers of public clouds do not need to use their own pipelines; those clouds can be tested via the
@@ -35,7 +35,7 @@ to be used for purposes other than compliance testing (such as the
    Github first and then clone the fork.
 
 3. Add your subject to the results table. This is necessary so your subject shows up in the
-   [compliance monitor web-site](https://compliance.sovereignit.cloud/page/table). Add the following lines
+   compliance monitor. Add the following lines
    (substituting all-caps parts except `HM`) to
    [compliance-monitor/templates/overview.md.j2](https://github.com/SovereignCloudStack/standards/blob/main/compliance-monitor/templates/overview.md.j2):