Harness Secrets Management Overview
Harness includes a built-in Secrets Management feature that enables you to store encrypted secrets, such as access keys, and use them in your Harness account. Some key points about Secrets Management:
- Secrets are always stored in encrypted form and decrypted when they are needed.
- Harness Manager does not have access to your key management system, and only the Harness Delegate, which sits in your private network, has access to it. Harness never makes secrets management accessible publicly. This adds an important layer of security.
In this topic:
- Before You Begin
- Visual Summary
- Harness Secrets Management Process Overview
Before You Begin
You can choose to use your own secrets management solution, or the built-in Harness Secrets Manager. This diagram shows how Harness handles secrets:
Harness Secrets Management Process Overview
Harness sends only encrypted data to the Secrets Manager, as follows:
- Your browser sends data over HTTPS to Harness Manager.
- Harness Manager relays encrypted data to the Harness Delegate, also over HTTPS.
- The Delegate exchanges a key pair with the Secrets Manager, over an encrypted connection.
- The Harness Delegate uses the encrypted key and the encrypted secret and then discards them. The keys never leave the Delegate.
You can manage your secrets in Harness using either a Key Management Service or third-party Secrets Manager.
Using Key Management Services
Google Cloud Key Management Service is the default Secrets Manager in Harness and is named Harness Secrets Manager Google KMS.
The Key Management Service (Google Cloud KMS or AWS KMS) only stores the key. Harness uses envelope encryption to encrypt and decrypt secrets. The encrypted secret and the encrypted Data Encryption Key (used for envelope encryption) are stored in the Harness database.
Using Third-Party Secrets Managers
You can also use third-party Secrets Managers — HashiCorp Vault, Azure Key Vault, and AWS Secrets Manager.
These Secrets Managers store the key, perform encryption and decryption, and also store the secrets (encrypted key pair). Neither the keys nor the secrets are stored in the Harness database. A reference to the secret is stored in the Harness database.
Secrets in Harness Community and On-Prem Accounts
In Community and On-Prem accounts, Harness uses a random-key secrets store as the Harness Secrets Manager.
All Harness secrets managers require a running Harness Delegate to encrypt and decrypt secrets.
If you created a Harness trial account, a Delegate is typically provisioned by Harness, and the default Harness Secrets Manager performs encryption/decryption.
Harness Secrets and Harness Git Experience
When you set up Harness Git Experience, you select the Connectivity Mode for Git syncing. You have two options:
- Connect Through Manager: Harness SaaS will connect to your Git repo whenever you make a change and Git and Harness sync.
- Connect Through Delegate: Harness will make all connections using the Harness Delegate. This option is used for Harness On-Prem frequently, but it is also used for Harness SaaS. See Harness On-Premise Overview.
if you select Connect Through Manager, the Harness Manager decrypts the secrets you have set up in the Harness Secrets Manager.
This is different than Connect Through Delegate where only the Harness Delegate, which sits in your private network, has access to your key management system.