pilot-compliance-audit

Generate quarterly Kubernetes compliance reports with per-resource violations and fingerprinted evidence.

14|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/confighub/cub-scout --skill pilot-compliance-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pilot-compliance-audit
Source: https://github.com/confighub/cub-scout/tree/main/skills/pilot-compliance-audit
Command: npx skills add https://github.com/confighub/cub-scout --skill pilot-compliance-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pilot needs to produce a structured compliance report for auditors that clearly explains which Kubernetes resources comply with a declared security baseline and includes fingerprint-stable evidence for each finding.

Core Features & Use Cases

  • Quarterly/monthly compliance reporting: Generates an auditor-facing report using Pilot’s compliance-report framing and an evidence inventory suitable for long retention windows.
  • Source-truth verdicts with receipts: Runs scope-resolved compare source-truth plus scan, then verifies and persists per-resource receipts so violations can be re-validated later.
  • Cross-cutting audit evidence: Includes ConfigHub audit-trail entries, scan findings, and (when applicable) fleet outliers to contextualize decisions across the declared scope.
  • Compliance vocabulary mapping: Translates cub-scout receipt verdicts (PASS/WATCH/BLOCK/INCONCLUSIVE) into auditor-oriented categories (Compliant / Compliant with caveats / Non-compliant / Insufficient evidence).

Quick Start

Ask Pilot to generate a quarterly compliance report with evidence for a specific baseline View, for example: "Pilot, run the quarterly compliance audit for view prod-baseline-q2-2026 and produce this quarter's policy violations plus their evidence."

Frequently Asked Questions about pilot-compliance-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate auditor-ready Kubernetes compliance evidence for a quarterly audit?

To generate Kubernetes compliance evidence, you run a periodic audit over a declared scope like a namespace or cluster. The process renders an auditor-facing report detailing per-resource violations and fingerprinted evidence using source-truth comparisons and risk-pattern scans.

What is fingerprinted evidence in a Kubernetes compliance report?

Fingerprinted evidence in a compliance report is validation-friendly, persisted receipt data for each resource finding. It allows auditors to re-verify compliance verdicts later by ensuring the scanned state remains stable and traceable over long retention windows.

How do compliance scan verdicts map to auditor categories?

Compliance scan verdicts like PASS, WATCH, BLOCK, and INCONCLUSIVE are translated into auditor-oriented categories. These map directly to Compliant, Compliant with caveats, Non-compliant, and Insufficient evidence to clarify policy violation statuses.

Can I run a compliance audit across a Kubernetes fleet and check for outliers?

Yes, you can run a compliance audit across a Kubernetes fleet. The process includes optional fleet outlier checks to contextualize decisions and identify resources that deviate from the declared security baseline within the scope.

Does generating Kubernetes compliance evidence require write access to the cluster?

Generating Kubernetes compliance evidence does not require write access. The audit process stays strictly read-only while resolving scope, comparing source-truth, scanning risk patterns, and persisting validation-friendly receipts.