vault-fips

Apps

Fips

Stig

Updated 22 hours ago

Vault-FIPS Overview

Secure your stack with a hardened Vault-FIPS image freshly-built by Minimus. Minimus images always include the most up-to-date package version for all packages and dependencies contained in the image.

Use this image as a cross-platform secrets manager, authentication tool, or as part of an infrastructure-as-code stack. HashiCorp Vault provides a unified interface, tight access control, and a detailed audit log and is used to securely access API keys, passwords, certificates, and more.

FIPS 140-3 Certification

This image is FIPS-validated to ensure its cryptographic operations meet the Federal Information Processing Standards (FIPS) required for secure government and regulated environments. Its core cryptographic modules are validated under the NIST Cryptographic Module Validation Program (CMVP) and comply with the FIPS 140-3 standard.

To verify that the FIPS 140-3 provider is configured and active, follow the instructions in the FIPS compliance tab.

Try It Out

Take the Minimus Vault image for a test run. First, run Vault in dev mode:

docker run --cap-add=IPC_LOCK -e 'VAULT_DEV_ROOT_TOKEN_ID=myroot' -p 8200:8200 \
--name=minimus-vault-dev \
reg.mini.dev/vault-fips

In another terminal, set the environment variables to fetch the Vault CLI authentication token:

export VAULT_ADDR='http://127.0.0.1:8200'
export VAULT_TOKEN='myroot'
# myroot is the default root token generated when running Vault in dev mode

Now, check your Vault container's status:

curl \
  --header "X-Vault-Token: $VAULT_TOKEN" \
  $VAULT_ADDR/v1/sys/health

You should see the server’s health and readiness status report, for example:

{
  "initialized": true,           
  "sealed": false,               
  "standby": false,             
  "version": "1.19.3",           
  "enterprise": false,           
  "cluster_name": "...",         
  "cluster_id": "..."            
}

Technical Considerations

The Vault-FIPS image provided by Minimus is a slim, security-hardened alternative to the public image from Docker Hub. The images are largely interchangeable, with a few differences as noted below.

Vault-FIPS built by Minimus:

Runs as root to support required functions. The public image also runs as root.
The image does not expose a volume by default. The public image exposes the volumes /vault/file and /vault/logs.
The image has an additional environment variable: SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt.
Drill down on the version specification tab to see the default user, listening ports, entrypoint, volumes, environment variables, etc.

The Payoff

A hardened, minimal image that will remain more secure for the long run and accrue vulnerabilities at a slower rate.

See the risk reduction dashboard for a detailed CVE comparison over the past 30 days.
Review the compliance report to see the default hardening and security configurations for the image.

Terms & Info

Trademark

This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.

Disclaimer

Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.