> For the complete documentation index, see [llms.txt](https://docs.taloflow.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taloflow.ai/security/platform-controls/secrets-management.md).

# Secrets Management

How Taloflow stores and delivers runtime secrets (and why we avoid env vars).

### Scope

This page covers how Taloflow handles application secrets in Kubernetes.

It focuses on how secrets are stored, scoped, and mounted at runtime.

### Approach

Taloflow delivers runtime secrets to workloads using **Kubernetes Secrets mounted as files**.

We avoid injecting secrets via environment variables.

### Kubernetes Secret volume security layers

When a secret is mounted as a volume, Kubernetes provides multiple layers of protection.

1. **tmpfs**: Secret volumes are memory-backed by default. They are not written to node disk.
2. **`readOnly: true`**: Pods can’t modify mounted secret files.
3. **`defaultMode: 0400`**: Secret files are readable only by the owner (typically `root`).
4. **Namespace isolation**: A Secret only exists in its namespace. Other namespaces can’t reference it.
5. **Encryption at rest (etcd)**: Kubernetes can encrypt Secrets at rest in etcd.
6. **No env var exposure**: Secret files are not present in the process environment table.

{% hint style="info" %}
Security is defense-in-depth. The mount settings reduce accidental leakage. RBAC still governs *who can read the Secret* via the API.
{% endhint %}

### Why we avoid environment variables for secrets

Environment variables are easy to leak.

Common paths:

* Included in debug output and crash dumps.
* Visible in some process inspection workflows.
* Accidentally echoed by startup scripts.

Mounting secrets as files reduces these risks.

### Validation notes (for audits and questionnaires)

If you’re validating Taloflow’s Kubernetes secret posture, typical checks include:

* Secret volumes are mounted **read-only**.
* Secret volume file mode is **restricted** (for example, `0400`).
* Workloads cannot access secrets outside their **namespace**.
* Secrets are **encrypted at rest** in the cluster backing store (etcd).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.taloflow.ai/security/platform-controls/secrets-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.