A kubeconfig embeds static cluster credentials (‹path›)
What this means
‹path› contains ‹static credentials› embedded credential(s): bearer tokens, client keys or passwords. Unlike a cloud login, these usually do not expire, so a copied kubeconfig keeps working against the cluster.
How to fix it
- Switch each cluster entry to an exec plugin that fetches short-lived tokens (
aws eks update-kubeconfig,gcloud container clusters get-credentials,az aks get-credentialsorkubelogin). - Revoke the embedded token or certificate on the cluster.
- Keep any kubeconfig that must hold static credentials readable by you alone (
chmod 600).
Check it yourself
Run a scan and look for BLWK-CRED-008 in the results:
sh
bulwark scanInstalled the standalone CLI package instead of the app? The command is bulwarkctl.
How Bulwark decides
Bulwark reads credential_stores and reports this check when:
text
kind == "kube_config" and static_credentials > 0If a value can't be read, Bulwark reports the check as undetermined rather than passing it. View the rule source.
References
Related checks
- A long-lived AWS access key is stored on disk ·
BLWK-CRED-001 - Git stores passwords and tokens in plain text (‹path›) ·
BLWK-CRED-002 - Docker registry logins are stored in the config file ·
BLWK-CRED-003 - A credential file can be read by other users ·
BLWK-CRED-004 - Secrets are written into a shell startup file (‹path›) ·
BLWK-CRED-005 - An npm token is stored in plain text (‹path›) ·
BLWK-CRED-006