control-audit

Installation
SKILL.md

Control Audit — Audit Readiness for Control Frameworks

Get a control set ready for an external auditor: decide what's in scope, list the controls, write the evidence request an auditor would send for each one, test what you can from the repo and exported configs, and record what's missing or failing. The result is a control matrix, an evidence-request list, and a findings.json of control gaps that rates each gap by the exposure it leaves, not by how an auditor might word the opinion.

This is the program-level layer. It doesn't re-run technical audits: when a control's evidence is a technical check (branch protection, MFA enforcement, encryption at rest), it hands the check to the skill that owns it and folds the result back in.

Cross-references: csf-mapping (crosswalk a control set to NIST CSF 2.0, and governance-level gap analysis), pci-audit and hipaa-audit (code-facing audits when the in-scope data is cardholder data or PHI), iam-audit (access reviews, MFA, joiner/mover/leaver evidence), cloud-audit (logging, encryption, network and backup settings), secrets-audit, dependency-audit and container-audit (vulnerability management evidence), siem-detection (monitoring and alerting evidence), incident-triage (incident response plan and test evidence), privacy-engineering (SOC 2 Privacy category), finding-triage (dispositions after the audit), security-comms (readiness updates for executives and the board).

When to use

  • "We have a SOC 2 Type 2 in six months, where are we?" or "the auditor sent a PBC list, help us answer it"
  • Building or reviewing a control matrix, and writing evidence requests per control
  • "Our ISO 27001 Stage 2 is in May" or "is our Statement of Applicability defensible?"
  • Writing or reviewing an SSP and POA&M against an 800-53 baseline, or getting ready for FedRAMP (Rev5 or 20x)
  • Readiness review before fieldwork: which controls lack evidence, which failed in the period, which are only on paper
  • Re-running after remediation, matched by fingerprint

Input: the framework and criteria in scope, the system description or boundary, the audit period, and whatever evidence the user can share (policies, ticket exports, config exports, the repo).

Installs
70
GitHub Stars
519
First Seen
Oct 28, 2026