These pages describe what the provider protects, the controls a deployment must keep, and the limits of both. For the current release maturity, see Reference: Release and support lifecycle .
Pages in this section
The assets, trust boundaries, and attackers the provider is designed around, the control for each threat, and what it does not protect.
→ Security · Host HardeningThe controls a hardened deployment must have in OpenBao, on the host, for auth material, in logs and metrics, and in Kubernetes.
→ Security · Authentication Auth modelWhy the provider authenticates to OpenBao without the protected API server, how its token lifecycle works, and what the auth model does and does not protect.
→ Security · Host Linux identity modelThe users, groups, file ownership, and socket directory rules that let the API server reach the provider without reading its credentials.
→ Security · Data integrity AAD and decrypt validationWhat the additional authenticated data bound to every ciphertext protects against, how decryption rejects unknown or tampered ciphertext early, and why AAD is never disabled.
→ Security · Supply chain Verify release artifactsWhat each release verification check proves, and where the install procedures run the checks for artifacts and the provider image.
→