diff --git a/source/img/security/verify-installer-linux-modified.png b/source/img/security/verify-installer-linux-modified.png
new file mode 100644
index 0000000..df44852
Binary files /dev/null and b/source/img/security/verify-installer-linux-modified.png differ
diff --git a/source/img/security/verify-installer-linux-modified@2.png b/source/img/security/verify-installer-linux-modified@2.png
new file mode 100644
index 0000000..df44852
Binary files /dev/null and b/source/img/security/verify-installer-linux-modified@2.png differ
diff --git a/source/img/security/verify-installer-win.png b/source/img/security/verify-installer-win.png
new file mode 100644
index 0000000..5afac38
Binary files /dev/null and b/source/img/security/verify-installer-win.png differ
diff --git a/source/img/security/verify-installer-win@2x.png b/source/img/security/verify-installer-win@2x.png
new file mode 100644
index 0000000..59a715b
Binary files /dev/null and b/source/img/security/verify-installer-win@2x.png differ
diff --git a/source/index.rst b/source/index.rst
index 9f730b0..aa38414 100644
--- a/source/index.rst
+++ b/source/index.rst
@@ -54,6 +54,7 @@ If you are interested in the security of Cryptomator, have a look at our :ref:`s
    security/security-target.rst
    security/architecture.rst
    security/best-practices.rst
+   security/verify-installers.rst
 
 .. toctree::
    :hidden:
diff --git a/source/security/verify-installers.rst b/source/security/verify-installers.rst
new file mode 100644
index 0000000..2a03094
--- /dev/null
+++ b/source/security/verify-installers.rst
@@ -0,0 +1,48 @@
+Verify Installer Signatures
+===========================
+
+If you are not sure whether an alleged Cryptomator installer is legitimate, you can verify its authenticity and integrity.
+
+
+.. _security/verify-installers/linux:
+
+Linux (AppImage)
+-------------
+
+Using the `AppImage.asc` signature file, you can check the authenticity and integrity of the `AppImage` file. First download both files and verify it in following four simple steps:
+
+.. image:: ../img/security/verify-installer-linux-modified@2.png
+    :alt: How to check the code signing certificate on Linux
+    :width: 1316px
+    :align: center
+
+#. Use ``gpg --list-keys --fingerprint 58117AFA1F85B3EEC154677D615D449FE6E6A235`` to make sure you have loaded the GPG key. If it is not available, download it from a keyserver e.g.: ``gpg --keyserver keys.gnupg.net --recv-keys 58117AFA1F85B3EEC154677D615D449FE6E6A235`` or another trusted source like from Cryptobot using Github ``curl -sSL https://github.com/cryptobot.gpg | gpg --import -``.
+
+#. Use ``gpg --verify cryptomator-*.AppImage.asc cryptomator-*.AppImage`` to execute the verification process (replace ``*`` with the downloaded version).
+
+The message should say:
+
+3. ``gpg: Good signature from "Cryptobot <releases@cryptomator.org>"``
+4. ``Primary key fingerprint: 5811 7AFA 1F85 B3EE C154  677D 615D 449F E6E6 A235``
+
+If shown, you can ignore the following warning:
+
+``gpg: WARNING: This key is not certified with a trusted signature!``
+
+.. _security/verify-installers/windows:
+
+Windows (exe)
+-------------
+
+Our Windows installers are signed using a code signing certificate. You can verify the signature in five simple steps:
+
+.. image:: ../img/security/verify-installer-win@2x.png
+    :alt: How to check the code signing certificate on Windows
+    :width: 1316px
+    :align: center
+
+#. Right click on the file and click on Properties.
+#. Select the Digital Signatures tab: It should show a signature by ``Skymatic GmbH``.
+#. Click on Details.
+#. Click on View Certificates.
+#. Click on Details. The serial number of our certificate should be ``63c45bff1a148d60ed2994d3a2639034``.