Ensure that default service accounts are not actively used (Automated)
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill cis-gke-v190-4.1.4 --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Cis Gke V190 4.1.4?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-cis-gke-v190-4-1-4)More formats (shields.io, HTML) on the badges page.
---
name: cis-gke-v190-4.1.4
description: "Ensure that default service accounts are not actively used (Automated)"
category: cis-gke
version: "1.9.0"
author: cyberstrike-official
tags: [cis, gke, kubernetes, gcp, rbac, service-accounts, cluster-roles, secrets, wildcards]
cis_id: "4.1.4"
cis_benchmark: "CIS Google Kubernetes Engine (GKE) Benchmark v1.9.0"
tech_stack: [kubernetes, gcp, gke]
cwe_ids: []
chains_with: []
prerequisites: []
severity_boost: {}
---
# 4.1.4 Ensure that default service accounts are not actively used (Automated)
## Profile Applicability
- Level 1
## Description
The `default` service account should not be used to ensure that rights granted to applications can be more easily audited and reviewed.
## Rationale
Kubernetes provides a `default` service account which is used by cluster workloads where no specific service account is assigned to the pod.
Where access to the Kubernetes API from a pod is required, a specific service account should be created for that pod, and rights granted to that service account.
The default service account should be configured such that it does not provide a service account token and does not have any explicit rights assignments.
## Impact
All workloads which require access to the Kubernetes API will require an explicit service account to be created.
## Audit
For each namespace in the cluster, review the rights assigned to the default service account and ensure that it has no roles or cluster roles bound to it apart from the defaults.
Additionally ensure that the `automountServiceAccountToken: false` setting is in place for each default service account.
## Remediation
Create explicit service accounts wherever a Kubernetes workload requires specific access to the Kubernetes API server.
Modify the configuration of each default service account to include this value:
```yaml
automountServiceAccountToken: false
```
## Default Value
By default the `default` service account allows for its service account token to be mounted in pods in its namespace.
## References
1. https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/
## CIS Controls
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
| ---------------- | ------------------------------------------------------- | ---- | ---- | ---- |
| v8 | 5.3 Disable Dormant Accounts | \* | \* | \* |
| v7 | 4.3 Ensure the Use of Dedicated Administrative Accounts | \* | \* | \* |
| v7 | 5.2 Maintain Secure Images | | \* | \* |
| v7 | 16.9 Disable Dormant Accounts | \* | \* | \* |

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!