Ensure that the --peer-cert-file and --peer-key-file arguments are set as appropriate (Automated)
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill cis-k8s-v1110-2.5 --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Cis K8s V1110 2.5?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-cis-k8s-v1110-2-5)More formats (shields.io, HTML) on the badges page.
---
name: cis-k8s-v1110-2.5
description: "Ensure that the --peer-cert-file and --peer-key-file arguments are set as appropriate (Automated)"
category: cis-k8s
version: "1.11.0"
author: cyberstrike-official
tags: [cis, kubernetes, etcd, peer-tls, encryption]
cis_id: "2.5"
cis_benchmark: "CIS Kubernetes Benchmark v1.11.0"
tech_stack: [kubernetes]
cwe_ids: []
chains_with: []
prerequisites: []
severity_boost: {}
---
# 2.5 Ensure that the --peer-cert-file and --peer-key-file arguments are set as appropriate (Automated)
## Profile Applicability
- Level 1 - Master Node
## Description
etcd should be configured to make use of TLS encryption for peer connections.
## 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 encrypted in transit and also amongst peers in the etcd clusters.
## Impact
etcd cluster peers would need to set up TLS for their communication.
## Audit
Run the following command on the etcd server node:
```bash
ps -ef | grep etcd
```
Verify that the `--peer-cert-file` and `--peer-key-file` arguments are set as appropriate.
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
Follow the etcd service documentation and configure peer TLS encryption as appropriate for your etcd cluster.
Then, edit the etcd pod specification file `/etc/kubernetes/manifests/etcd.yaml` on the master node and set the below parameters.
```
--peer-client-file=</path/to/peer-cert-file>
--peer-key-file=</path/to/peer-key-file>
```
## 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 communication over TLS is not configured.
## References
1. https://coreos.com/etcd/docs/latest/op-guide/security.html
2. https://kubernetes.io/docs/admin/etcd/
## CIS Controls
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
| ---------------- | ------------------------------------------------- | ---- | ---- | ---- |
| v8 | 3.11 Encrypt Sensitive Data at Rest | | X | X |
| v7 | 14.4 Encrypt All Sensitive Information in Transit | | X | X |
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!