How do I install the Cis K8S V200 2.6 skill?

Run npx skillmds@latest add cyberstrikeus/cis-k8s-v200-2-6 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 2.6 skill do?

Ensure that the --peer-auto-tls argument is not set to true (Automated) It is listed under DevOps & Infra on SkillMD.

Is Cis K8S V200 2.6 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 2.6?

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 2.6 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 2.6?

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

Cis K8S V200 2.6 by cyberstrikeus — Agent Skill

Name: Cis K8S V200 2.6
Author: cyberstrikeus

File contents

CIS Kubernetes Benchmark v2.0.0 - Control 2.6

Profile Applicability

Level: 1 - Master Node

Description

Do not use automatically generated self-signed certificates for TLS connections between peers.

Rationale

etcd is a highly-available key value store used by Kubernetes deployments for persistent storage of all of its REST API objects. These objects are sensitive in nature and should be accessible only by authenticated etcd peers in the etcd cluster. Hence, do not use self-signed certificates for authentication.

Impact

All peers attempting to communicate with the etcd server will require a valid client certificate for authentication.

Audit Procedure

Run the following command on the etcd server node:

ps -ef | grep etcd

Verify that if the --peer-auto-tls argument exists, it is not set to true. Note: This recommendation is applicable only for etcd clusters. If you are using only one etcd server in your environment then this recommendation is not applicable.

Remediation

Edit the etcd pod specification file /etc/kubernetes/manifests/etcd.yaml on the master node and either remove the --peer-auto-tls parameter or set it to false.

--peer-auto-tls=false

Default Value

Note: This recommendation is applicable only for etcd clusters. If you are using only one etcd server in your environment then this recommendation is not applicable.

By default, --peer-auto-tls argument is set to false.

References

CIS Controls

Controls Version	Control	IG 1	IG 2	IG 3
v8	5.2 Use Unique PasswordsUse unique passwords for all enterprise assets. Best practice implementation includes, at a minimum, an 8-character password for accounts using MFA and a 14-character password for accounts not using MFA.	●	●	●
v7	4.4 Use Unique PasswordsWhere multi-factor authentication is not supported (such as local administrator, root, or service accounts), accounts will use passwords that are unique to that system.		●	●

Profile

Level 1 - Master Node (Automated)

---name: cis-k8s-v200-2-6description: Ensure that the --peer-auto-tls argument is not set to true (Automated)---# CIS Kubernetes Benchmark v2.0.0 - Control 2.6## Profile Applicability- **Level:** 1 - Master Node## DescriptionDo not use automatically generated self-signed certificates for TLS connections between peers.## Rationaleetcd is a highly-available key value store used by Kubernetes deployments for persistent storage of all of its REST API objects. These objects are sensitive in nature and should be accessible only by authenticated etcd peers in the etcd cluster. Hence, do not use self-signed certificates for authentication.## ImpactAll peers attempting to communicate with the etcd server will require a valid client certificate for authentication.## Audit ProcedureRun the following command on the etcd server node:```bashps -ef | grep etcd```Verify that if the `--peer-auto-tls` argument exists, it is not set to `true`. **Note:** This recommendation is applicable only for etcd clusters. If you are using only one etcd server in your environment then this recommendation is not applicable.## RemediationEdit the etcd pod specification file `/etc/kubernetes/manifests/etcd.yaml` on the master node and either remove the `--peer-auto-tls` parameter or set it to `false`.```--peer-auto-tls=false```## Default Value**Note:** This recommendation is applicable only for etcd clusters. If you are using only one etcd server in your environment then this recommendation is not applicable.By default, `--peer-auto-tls` argument is set to `false`.## References1. https://coreos.com/etcd/docs/latest/op-guide/security.html2. https://kubernetes.io/docs/admin/etcd/3. https://coreos.com/etcd/docs/latest/op-guide/configuration.html#peer-auto-tls## CIS Controls| Controls Version | Control | IG 1 | IG 2 | IG 3 || ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---- | ---- | ---- || v8 | 5.2 Use Unique Passwords<br/>Use unique passwords for all enterprise assets. Best practice implementation includes, at a minimum, an 8-character password for accounts using MFA and a 14-character password for accounts not using MFA. | ● | ● | ● || v7 | 4.4 Use Unique Passwords<br/>Where multi-factor authentication is not supported (such as local administrator, root, or service accounts), accounts will use passwords that are unique to that system. | | ● | ● |## Profile**Level 1 - Master Node** (Automated)

Frequently asked questions

Cis K8S V200 2.6