From 9b584f2c9957d06986617b920ce2e02bdbe936a9 Mon Sep 17 00:00:00 2001 From: Patrik Spiess Date: Mon, 26 Feb 2024 14:50:49 +0100 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=9D=20Add=20Hashicorp=20Vault=20as=20a?= =?UTF-8?q?=20mitigation=20of=20the=20unencrypted=20inventory=20risk?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../developer/architecture/9_risks_technical_depths.rst | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/source/developer/architecture/9_risks_technical_depths.rst b/docs/source/developer/architecture/9_risks_technical_depths.rst index 3ec8169..9188f72 100644 --- a/docs/source/developer/architecture/9_risks_technical_depths.rst +++ b/docs/source/developer/architecture/9_risks_technical_depths.rst @@ -56,6 +56,5 @@ There are several things done to mitigate this risk: not the first suggestion in the documentation. - The risk of exposing the inventory and how to minimize this risk is clearly stated in the documentation at :ref:`usage_inventory`. - -*Note: There are ideas about supporting HashiCorp Vault as storage backend for the credentials. If -you want to support us there, please reach out to us on GitHub.* +- To make the handling of sensitive data a bit safer you may store such data in a Hashicorp Vault + service which is documented here: :ref:`vault_service`.