Prefer using secrets as files over secrets as environment variables (Automated)
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill cis-gke-v180-4.4.1 --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Cis Gke V180 4.4.1?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-cis-gke-v180-4-4-1)More formats (shields.io, HTML) on the badges page.
---
name: cis-gke-v180-4.4.1
description: "Prefer using secrets as files over secrets as environment variables (Automated)"
category: cis-gke
version: "1.8.0"
author: cyberstrike-official
tags: [cis, gke, kubernetes, gcp, secrets, encryption, environment-variables]
cis_id: "4.4.1"
cis_benchmark: "CIS Google Kubernetes Engine (GKE) Benchmark v1.8.0"
tech_stack: [kubernetes, gcp, gke]
cwe_ids: []
chains_with: []
prerequisites: []
severity_boost: {}
---
# 4.4.1 Prefer using secrets as files over secrets as environment variables (Automated)
## Profile Applicability
- Level 2
## Description
Kubernetes supports mounting secrets as data volumes or as environment variables. Minimize the use of environment variable secrets.
## Rationale
It is reasonably common for application code to log out its environment (particularly in the event of an error). This will include any secret values passed in as environment variables, so secrets can easily be exposed to any user or entity who has access to the logs.
## Impact
Application code which expects to read secrets in the form of environment variables would need modification.
## Audit
Run the following command to find references to objects which use environment variables defined from secrets.
```bash
kubectl get all -o jsonpath='{range .items[?(@..secretKeyRef)]} {.kind} {.metadata.name} {"\n"}{end}' -A
```
## Remediation
If possible, rewrite application code to read secrets from mounted secret files, rather than from environment variables.
## Default Value
By default, secrets are not defined.
## References
1. https://kubernetes.io/docs/concepts/configuration/secret/#using-secrets
## Additional Information
Mounting secrets as volumes has the additional benefit that secret values can be updated without restarting the pod.
## CIS Controls
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
| ---------------- | ------------------ | ---- | ---- | ---- |
| v8 | 3 Data Protection | | | |
| v7 | 13 Data Protection | | | |
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!