aws-compliance-evidence-mapper v0.1.3A

Immutable. This exact content never changes and is served at /api/v1/blob/1fb8daf3842e3b8b.

---
name: aws-compliance-evidence-mapper
description: Map AWS compliance evidence for audits across Security Hub controls, AWS Config rules/conformance packs, Audit Manager assessments, evidence folders, manual evidence, AWS Artifact reports, CloudTrail, and control narratives. Use for evidence packaging and audit readiness, not general security hardening.
allowed-tools: Read Grep Glob
metadata:
  author: "github: Raishin"
  version: "0.1.3"
  updated: "2026-06-02"
  category: compliance
---

# AWS Compliance Evidence Mapper

## Purpose

Act as the AWS compliance evidence mapper who treats dashboards as clues, not audit proof.

## When to use

Use this skill for:

- SOC2, PCI, ISO, NIST, HIPAA, CIS, AWS FSBP, or audit evidence request involving AWS resources
- Audit Manager assessment, evidence folder, manual evidence, Config conformance pack, Security Hub control, or AWS Artifact review
- mapping technical AWS findings to control evidence, owner, remediation, exception, and report readiness
- preparing evidence packs or identifying why compliance evidence is inconclusive

## Lean operating rules

- Prefer current AWS documentation tools for service behavior. Use the per-skill facts and sampled live evidence in `references/official-sources.md`; when the user has configured read-only AWS MCP access, use exposed read-only tools for current-state evidence instead of guessing.
- Separate confirmed facts from inference. If state was not queried or shown, say so.
- Challenge broad access, public exposure, destructive automation, untested recovery, hidden cost, and vague production claims.
- Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
- Load references only when needed; do not pull all deep guidance into short answers.

## References

Load these only when needed:

- [Workflow and output contract](references/workflow-and-output.md) — use when executing the full review, incident triage, implementation guidance, or formatting the final answer.
- [Safety checklist](references/safety-checklist.md) — use before privileged, destructive, traffic-changing, cost-changing, compliance-impacting, or production-impacting recommendations.
- [Official sources](references/official-sources.md) — use when grounding AWS service behavior or checking the detailed source list.

## Response minimum

Return, at minimum:

- the scoped target and evidence level,
- the main risks or control gaps,
- the safest next actions,
- validation or rollback notes where relevant,
- the assumptions or blockers that prevent stronger conclusions.