How do I install the Cis K8S V200 3.1.2 skill?

Run npx skillmds@latest add cyberstrikeus/cis-k8s-v200-3-1-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Cis K8S V200 3.1.2 skill do?

Service account token authentication should not be used for users (Manual) It is listed under DevOps & Infra on SkillMD.

Is Cis K8S V200 3.1.2 safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cis K8S V200 3.1.2?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cis K8S V200 3.1.2 free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cis K8S V200 3.1.2?

cyberstrikeus (@cyberstrikeus) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cis K8S V200 3.1.2 by cyberstrikeus

Name: Cis K8S V200 3.1.2
Author: cyberstrikeus

File contents

CIS Kubernetes Benchmark v2.0.0 - Control 3.1.2

Profile Applicability

Level: 1 - Master Node

Description

Kubernetes provides service account tokens which are intended for use by workloads running in the Kubernetes cluster, for authentication to the API server.

These tokens are not designed for use by end-users and do not provide for features such as revocation or expiry, making them insecure. A newer version of the feature (Bound service account token volumes) does introduce expiry but still does not allow for specific revocation.

Rationale

With any authentication mechanism the ability to revoke credentials if they are compromised or no longer required, is a key control. Service account token authentication does not allow for this due to the use of JWT tokens as an underlying technology.

Impact

External mechanisms for authentication generally require additional software to be deployed.

Audit Procedure

Review user access to the cluster and ensure that users are not making use of service account token authentication.

Remediation

Alternative mechanisms provided by Kubernetes such as the use of OIDC should be implemented in place of service account tokens.

Default Value

Service account token authentication is enabled by default.

CIS Controls

Controls Version	Control	IG 1	IG 2	IG 3
v8	6.2 Establish an Access Revoking ProcessEstablish and follow a process, preferably automated, for revoking access to enterprise assets, through disabling accounts immediately upon termination, rights revocation, or role change of a user. Disabling accounts, instead of deleting accounts, may be necessary to preserve audit trails.	●	●	●
v7	16.7 Establish Process for Revoking AccessEstablish and follow an automated process for revoking system access by disabling accounts immediately upon termination or change of responsibilities of an employee or contractor. Disabling these accounts, instead of deleting accounts, allows preservation of audit trails.		●	●

Profile

Level 1 - Master Node (Manual)

---name: cis-k8s-v200-3-1-2description: Service account token authentication should not be used for users (Manual)---# CIS Kubernetes Benchmark v2.0.0 - Control 3.1.2## Profile Applicability- **Level:** 1 - Master Node## DescriptionKubernetes provides service account tokens which are intended for use by workloads running in the Kubernetes cluster, for authentication to the API server.These tokens are not designed for use by end-users and do not provide for features such as revocation or expiry, making them insecure. A newer version of the feature (Bound service account token volumes) does introduce expiry but still does not allow for specific revocation.## RationaleWith any authentication mechanism the ability to revoke credentials if they are compromised or no longer required, is a key control. Service account token authentication does not allow for this due to the use of JWT tokens as an underlying technology.## ImpactExternal mechanisms for authentication generally require additional software to be deployed.## Audit ProcedureReview user access to the cluster and ensure that users are not making use of service account token authentication.## RemediationAlternative mechanisms provided by Kubernetes such as the use of OIDC should be implemented in place of service account tokens.## Default ValueService account token authentication is enabled by default.## CIS Controls| Controls Version | Control | IG 1 | IG 2 | IG 3 || ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---- | ---- | ---- || v8 | 6.2 Establish an Access Revoking Process<br/>Establish and follow a process, preferably automated, for revoking access to enterprise assets, through disabling accounts immediately upon termination, rights revocation, or role change of a user. Disabling accounts, instead of deleting accounts, may be necessary to preserve audit trails. | ● | ● | ● || v7 | 16.7 Establish Process for Revoking Access<br/>Establish and follow an automated process for revoking system access by disabling accounts immediately upon termination or change of responsibilities of an employee or contractor. Disabling these accounts, instead of deleting accounts, allows preservation of audit trails. | | ● | ● |## Profile**Level 1 - Master Node** (Manual)

Frequently asked questions

Cis K8S V200 3.1.2