HashiConf 2025 Don't miss the live stream of HashiConf Day 2 happening now View live stream

Introduction

Note

These guides were reorganized in August 2026. The previous Solution Design Guide and Operating Guides (Adoption, Standardization, Scaling) have been replaced with three role-based guide types: Installation, Administration, and User. Read the HVD 2.0 release notes for full details on what changed and where to find the content you need.

Why use HashiCorp Validated Designs?

HashiCorp Validated Designs (HVD) provide practitioners with opinionated guidance for achieving production-grade deployments of HashiCorp products. These designs are purpose-built for delivering foundational use cases, with a baseline level of architectural and operational maturity. They draw on the field experiences of Solutions Engineers and Solutions Architects working with customers across a wide range of environments and organizational requirements.

Each guide provides access to an opinionated reference architecture, including key design decisions and the rationale behind them. Where applicable, guides identify modular design components that you can adjust to align with organizational or regulatory requirements without compromising the overall integrity of the implementation. For many deployments we include Terraform modules to automate large portions of infrastructure provisioning and software installation.

Note

This guidance for HCP Vault Radar is emerging guidance. We continually update it as we identify common best practices and configurations to help customers get the most from the product.

Throughout this guide, the terms HCP Vault Radar, Vault Radar, and Radar are interchangeable. There is no self-managed or enterprise version of Vault Radar.

This Administration Guide covers the ongoing configuration, operation, and governance of HCP Vault Radar for the platform, security operations (SecOps), and HCP administrator teams who run Radar as a service for their organization.

Because Vault Radar is a software-as-a-service (SaaS) offering delivered through the HashiCorp Cloud Platform (HCP), there is no self-managed installation to perform: HashiCorp operates the underlying platform. This guide therefore assumes your organization already has access to an HCP organization with Vault Radar enabled. Infrastructure concerns that do not apply to a fully-managed SaaS product — such as backup, disaster recovery, upgrades, and capacity sizing — are handled by HashiCorp and are out of scope for this guide.

What this guide covers

  • People and process — the roles and responsibilities involved in running Vault Radar.
  • Identity and access management — HCP roles and resource-based access control for operators and consumers.
  • Data source onboarding — connecting and tuning the data sources Radar scans.
  • Agent deployment — deploying and scaling agents for scanning private, non-internet-accessible sources.
  • Observability and alert management — configuring alerting, notification, and ticketing integrations.

Related guides

For how developers and application teams consume Vault Radar — deployment models, using Radar in developer pipelines, and remediating findings — see the User Guide.

Edit this page on GitHub