Arcus logo

Centralize secret management independent from application

Differentiating between configuration data and secrets is critical for the security of applications. HTTP ports, application name... can all be seen as public data but access tokens, private keys... should not be in the same group. Accessing them in a centralized manner and secure manner is therefore important.

The Arcus secret store is the answer. The secret store will be the single point of truth in interacting with required secrets for your application. Multiple 'secret providers' can be configured that accesses the secrets from external sources like: Azure Key Vault, HashiCorp Vault, Docker secrets, environment variables... and the secret store will provide a single access point for the application to fetch those secrets.

An example of how to implement an Azure KeyVault and appsettings config file and how well the secret store integrates within an application:

using Microsoft.Extensions.Hosting;

public class Program
    public static void Main(string[] args)

    public static IHostBuilder CreateHostBuilder(string[] args) =>
            .ConfigureAppConfiguration((context, config) =>
            .ConfigureSecretStore((context, config, builder) =>
                var keyVaultName = config["KeyVault_Name"];

A secret store reference can be injected into your application to retrieve back the secrets from your configured sources:

using Arcus.Security.Core;

public class OrderController : ControllerBase
    private readonly ISecretProvider _secretStore;

    public OrderController(ISecretProvider secretStore)
        _secretStore = secretStore;

    public async Task<IActionResult> Orders()
        string secret = await _secretStore.GetRawSecretAsync("MySecret");

The Arcus secret store is by-default integrated in all our .NET project templates! For more information, see our documentation site.