Security

The security posture of the platform and the controls that protect your workloads — secrets, certificates, isolation and data protection.

6 articles

• Data Protection and Residency

  Where your data lives, and how it is protected while it lives there, comes down to two things you control directly: how sensitive values are stored, and which regions you deploy to. This article explains both so you can make an informed choice.

  3 min

• Private Networking

  Bahriya keeps your projects isolated from one another by default and lets you open only the specific connections your workloads need. This article explains the private-by-default model and how network policies build on it.

  3 min

• Secrets and Vault Best Practices

  Sensitive values — database passwords, API keys, signing tokens, private certificates — need to live somewhere your application can reach at runtime but that never ends up in a log line, a source repository, or a container image. Bahriya's vault exists for exactly this. This article collects the practices that keep those values safe.

  3 min

• Securing Your Container

  Most container security comes down to a handful of habits: ship a small image, run as a non-privileged user, keep secrets out of the build, and gate the ingress. This article is a practical checklist you can work through for any workload you deploy.

  3 min

• Security

  This article describes how Bahriya protects your applications and data.

  2 min

• TLS and Certificates

  All traffic to your containers is encrypted with TLS. For the common cases you never touch a certificate — Bahriya provisions and renews them for you. For the cases where you supply your own certificate material, the vault holds it. This article covers both.

  3 min