Post

Checkov baseline cleared of legacy findings

Checkov baseline cleared of legacy findings

This push removes the accumulated legacy entries from the .checkov.baseline file, replacing a long list of repeated findings with an empty failed_checks array. The housekeeping step reduces policy noise and gives the homelab a clean slate for future Checkov scans.

Implementation: removing stale Checkov baseline rows

The single commit chore(ci): clear legacy Checkov baseline entries (#1928) rewrites .checkov.baseline so that the failed_checks key now holds an empty array. The patch excerpts show the old file contained numerous duplicated CKV_SECRET_6 entries and other findings that have been stripped out, leaving only the bare schema with no retained findings. No new checks were added; the file was simply pruned to its minimal form.

Verification: confirming the baseline is empty

With the baseline now empty, the next verification step is to run Checkov against the homelab manifests and confirm that no findings are recorded in the baseline file. I will execute the CI job that reads .checkov.baseline and ensure the pipeline proceeds without the previously suppressed warnings. If new findings appear, they will surface as fresh entries rather than being hidden under old noise.

Platform engineering: baseline hygiene and transferable practice

Clearing a stale baseline is a small but essential piece of platform hygiene. The same pattern—periodically auditing and trimming policy‑as‑code baselines—applies to any team that uses static analysis tools against infrastructure manifests. By keeping the baseline in sync with the actual codebase, the homelab avoids false‑positive suppression and makes audit trails more reliable. Teams can adopt a periodic cleanup script or a CI step that diffs the baseline against the latest scan output.

This post is licensed under CC BY 4.0 by the author.