Repository navigation
docs: CIS benchmark scanning (kube-bench) + archived k3s-cis results - #18
Merged
Merged
Conversation
- docs/cis-benchmark.md: how to run the cluster against CIS benchmarks with kube-bench (in-cluster Job), which benchmark to pick (k3s-cis-1.24 for accurate k3s hardening vs eks-stig/cis-1.24), how to capture JSON via jq, target scoping, and how to read the results. Includes the latest run summary and the two actionable node FAILs (4.2.6 protect-kernel-defaults, 4.2.10 kubelet TLS). - security/benchmark-results/: new folder for archived scan output (compliance evidence). k3s-cis-1.24-20260713.json is the full-detail jq output (28 PASS / 25 FAIL / 54 WARN / 18 INFO) with every check's audit + remediation. Read-only assessment; CIS IDs (not STIG V-IDs). No secrets in the JSON. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
docs/cis-benchmark.md— how to run the cluster against CIS benchmarks with kube-bench (in-cluster read-only Job): which benchmark to pick (k3s-cis-1.24for accurate k3s hardening vseks-stig/cis-1.24), capturing JSON viajq, target scoping (node,policies), and interpreting results. Includes the latest run summary and the two actionable node FAILs.security/benchmark-results/— new folder for archived scan output as compliance evidence.k3s-cis-1.24-20260713.json— full-detailjqoutput, every check'saudit/actual/remediationpreserved.README.md— index + naming convention.Latest audit (
k3s-cis-1.24, all targets)Actionable node FAILs:
4.2.6(--protect-kernel-defaults=truenot set) and4.2.10(kubelet TLS flags — benign on k3s, auto-managed certs).Notes: read-only assessment; these are CIS IDs, not STIG V-IDs (accurate framework for k3s). JSON scanned — no secrets, only benign remediation text.
🤖 Generated with Claude Code