AWS Compliance Evidence Mapper

SkillCloud & infra

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.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the AWS Compliance Evidence Mapper skill

What this skill tells your AI

The instructions your AI receives, as published by vincentchuwaichow/vanguard-frontier-agentic in skills/aws/aws-compliance-evidence-mapper/SKILL.md and read by ahel’s review.

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 — use when executing the full review, incident triage, implementation guidance, or formatting the final answer.
  • Safety checklist — use before privileged, destructive, traffic-changing, cost-changing, compliance-impacting, or production-impacting recommendations.
  • Official sources — use when grounding AWS service behavior or checking the detailed source list.
  • Compliance Evidence Chain Guide — use for domain-specific failure modes, safe workflow, verification targets, and pushback criteria.

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.

Signals

GitHub stars
22
Forks
3
Last commit
Sep 2026

ahel review

  • S4info
    community integration — published by vincentchuwaichow, not aws

Automated review, not a security audit. Ruleset v1+k2.

Advanced
Catalog kind
skill
Gateway key
aws-compliance-evidence-mapper
Source
github.com/vincentchuwaichow/vanguard-frontier-agentic