title: secret management in on premise application
body: <p>The .net core server code I'm working on is going to be hosted both in cloud infrastructure and on premises.</p>
  <p>There are many options to handle secret management (connection strings etc...):</p>
  <ul>
  <li>Big cloud providers are offering dedicated secret management solutions (<a href="https://docs.aws.amazon.com/kms/latest/developerguide/overview.html" rel="nofollow noreferrer">AWS KMS</a>, <a href="https://azure.microsoft.com/en-us/services/key-vault/" rel="nofollow noreferrer">Azure Key Vault</a>, etc..).</li>
  <li>Popular orchestrators, offer also their own service (Kubernetes Secrets for example)</li>
  <li>In development, we have dedicated <a href="https://docs.microsoft.com/en-us/aspnet/core/security/app-secrets?view=aspnetcore-5.0&amp;tabs=windows#secret-manager" rel="nofollow noreferrer">secret management tools &amp; process</a> (which are nice)</li>
  </ul>
  <p>But how can I store securely secrets on premise hosting? I doubt setting it as a simple variable environment is considered as safe?</p>