From 40700fa252c619ddab05ef559447524e07cec289 Mon Sep 17 00:00:00 2001 From: George Vanburgh Date: Fri, 15 Apr 2022 14:11:38 +0100 Subject: [PATCH] Fix a link to use-cases Signed-off-by: George Vanburgh --- content/docs/latest/spire-about/comparisons.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/latest/spire-about/comparisons.md b/content/docs/latest/spire-about/comparisons.md index 3e6c3fcc..99a665c8 100644 --- a/content/docs/latest/spire-about/comparisons.md +++ b/content/docs/latest/spire-about/comparisons.md @@ -16,7 +16,7 @@ Secrets managers typically control, audit and securely store sensitive informati A common architectural challenge in deploying secrets managers is how to securely store the credential that is used by the workload to access the secret store itself. This is sometimes called "credential zero", the "bootstrap credential", or more broadly, the process of "secure introduction". -By contrast, while SPIRE does _generate_ SPIFFE identities that can be used to [authenticate to other systems](/docs/latest/spire-integrations/use-cases/), SPIRE does not aim to store existing keys (such as a database password) on behalf of a workload. +By contrast, while SPIRE does _generate_ SPIFFE identities that can be used to [authenticate to other systems](/docs/latest/spire-about/use-cases/), SPIRE does not aim to store existing keys (such as a database password) on behalf of a workload. SPIRE's attestation policies provide a flexible and powerful solution for secure introduction to secrets managers. A common use of SPIRE-issued [SVIDs](/docs/latest/spiffe/concepts/#spiffe-verifiable-identity-document-svid) is to authenticate to secret stores to allow an application to retrieve secrets.