aws-iam
Use when managing AWS IAM.
SKILL.mdskills/aws-iam/SKILL.md
GitHubAws Iam
"Use when managing AWS IAM."
Trigger
Activate this skill when the user mentions:
- aws, iam, permissions, security workflows or issues
- Building, fixing, or optimizing aws iam
- Questions about aws best practices
Core Concepts
- Threat modeling and risk assessment
- Attack surface analysis
- Defense in depth
- Zero-trust architecture
- Compliance and audit requirements
Step-by-Step Workflow
- Scope — Define assets, threats, attack surface
- Expected: Documented scope with trust boundaries
- Assess — Identify vulnerabilities, evaluate risk
- Expected: Prioritized findings with CVSS scores
- Remediate — Apply secure-by-design fixes
- Expected: Vulnerabilities closed
- Verify — Re-test and validate remediation
- Expected: Independent verification complete
- Document — Record findings and lessons learned
- Expected: Audit-ready report
Tools & Technologies
- Vulnerability scanners
- SAST/DAST tools
- SIEM platforms
- Pen-testing frameworks
Best Practices
- Document decisions and rationale (ADRs, design docs, runbooks)
- Version everything - code, configs, data, and documentation
- Test incrementally; never claim passing without verification
- Respect domain-specific regulations and ethical standards
- Measure outcomes with meaningful metrics
Common Pitfalls
- Scope creep → Unclear boundaries → Define scope explicitly
- Tool reliance without analysis → False positives → Manual validation required
Tags
aws, iam, permissions, security
LoopyLuci/Skills - 2026-09-24