agentleFS
kaandgnshkaandgnsh/Claude-Blue/skills/compliance-audit/audit-evidence-package/SKILL.md

audit-evidence-package

Skill0 starsChanged 14 days agoMITView on GitHub

Prepare audit evidence that auditors accept on first submission — system-generated reports with parameters and timestamps, populations and samples, completeness and accuracy (IPE) support, screenshots with context, chain from control to evidence — for SOC 2, ISO 27001, PCI DSS, SOX ITGC and internal audit. Use when responding to audit requests (PBC lists), building evidence collection, or after evidence was rejected.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Audit Evidence Package

What auditors need

ElementRequirement
Control mappingWhich control and requirement this evidence supports
PopulationComplete list for the period (e.g., all terminations Jan–Jun), with how it was generated
Completeness & accuracy (IPE)Query/report parameters, system name, run date/time, row count, who ran it; ideally a screenshot of the query/filter
SampleAuditor-selected or random sample with selection method (control-testing-sampling)
Operating evidenceFor each sample item: ticket, approval, timestamp, system state proving the control operated
Period coverageDates align with audit period (Type II: whole period)
IntegrityOriginal exports (CSV/JSON) with hash, not edited spreadsheets

Good screenshots

Show system name/URL, logged-in user, date/time (taskbar clock or system timestamp), filters applied, and the relevant setting/value. Prefer exports or API output with metadata over screenshots where possible.

Example: "Terminated users removed within 1 business day"

  1. HR system termination report for the period (population) — report name, parameters, run time, count.
  2. Sample of 25 terminations.
  3. For each: termination date/time (HR), account disable time (IdP audit log user.lifecycle.deactivate / Entra Disable account), delta.
  4. Exceptions explained with remediation.

Automation

Collect recurring evidence via scripts/APIs on a schedule (IdP MFA reports, cloud config snapshots, vulnerability SLA reports), store immutably with timestamps — reduces audit scramble (continuous-control-monitoring).

Output

Request ID | Control | Evidence item | Source system | Generated by/when | Population size | Sample | Result | File (hash)

Related skills

control-testing-sampling, control-mapping, continuous-control-monitoring, access-certification

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.