Remediation workflows
Beyond secret detection, Vault Radar has a suite of features to help teams efficiently remediate issues found by Radar.
The features are:
- Notification integrations
- Resource based roles
- Remediation recommendations
- Remediation actions
Notification integrations and resource-based roles are configured by platform operators. For those, see the Administration Guide: Observability and alert management and Identity and access management. The remaining sections describe the remediation experience for developers and teams consuming Vault Radar.
Remediation recommendations
Remediation documents provide recommendations to developers based on the type of secret found in code and the secret's activeness. There are currently four provided core remediation documents.
- Active or unknown AWS secrets
- Active or unknown GCP secrets
- Active or unknown secrets (general)
- Inactive secrets
Organizations can also create their own custom remediation documents and add the link to Vault Radar to make it available in-product.
Remediation recommendations are also accessible within GitHub pull requests when using the Vault Radar GitHub App.
Remediation actions
Remediation actions allows Vault Radar administrators to setup a connection between Radar and Vault that allows development teams to easily store leaked secrets in the correct Vault locations so they can expedite the remediation steps.
For instructions on how to set up remediation actions with Vault, read the Copy leaked secrets into HashiCorp Vault documentation.