borghei/Claude-Skills / engineering/cloud-security
cloud-security
VerifiedCloud posture security across AWS, Azure, and GCP — IAM least privilege, public exposure, encryption, logging coverage, landing-zone guardrails. Use when auditing a cloud account, before a production launch, or after a scan.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.9 KB |
| assets/inventory_export_guide.md | markdown | 5.5 KB |
| assets/posture_review_template.md | markdown | 2.7 KB |
| assets/sample_iam_export.json | config | 2.9 KB |
| assets/sample_inventory.json | config | 3.6 KB |
| references/cloud-control-catalog.md | markdown | 9.2 KB |
| references/landing-zone-and-guardrails.md | markdown | 9.2 KB |
| scripts/iam_least_privilege.py | script | 10.7 KB |
| scripts/iam_rules.py | script | 7.8 KB |
| scripts/posture_auditor.py | script | 10.3 KB |
| scripts/posture_rules.py | script | 8.2 KB |
assets/posture_review_template.md
View on GitHub# Cloud Posture Review — <account / subscription / project>
**Provider:** AWS / Azure / GCP
**Scope:** <accounts, regions, environments reviewed>
**Inventory export date:** YYYY-MM-DD
**Reviewer:** <name>
**Decision requested:** <e.g. approve production launch / accept residual risk / block>
---
## Executive summary
<Three sentences maximum. Lead with whether the environment is safe to run
production data in, then the single largest exposure, then what it takes to
close it.>
| Signal | Value |
|--------|-------|
| Posture score / grade | |
| Critical findings | |
| High findings | |
| Resources audited | |
| Principals reviewed | |
| Delta vs last review | |
---
## Critical findings — block until closed
| # | Resource / principal | Finding | Exposure if exploited | Owner | Due |
|---|----------------------|---------|-----------------------|-------|-----|
| 1 | | | | | |
For each critical, answer explicitly: **is it exploitable from the internet
right now, and what data is behind it?** A public bucket of marketing images
and a public bucket of customer exports are the same finding ID and completely
different incidents.
---
## Identity findings
| Principal | Tier | Finding | Escalation path? | Owner | Due |
|-----------|------|---------|------------------|-------|-----|
| | | | | | |
**Privilege-escalation paths found:** <list, or "none">
**Stale credentials to disable:** <list with last-used dates>
---
## Exposure and encryption findings
| Resource | Finding | Classification | Owner | Due |
|----------|---------|----------------|-------|-----|
| | | | | |
---
## Detection coverage gaps
| Layer | Status | Gap | Consequence in an investigation |
|-------|--------|-----|---------------------------------|
| Control-plane audit log | | | |
| Data-plane access log | | | |
| Network flow log | | | |
| Managed detection | | | |
| Log archive isolation | | | |
---
## Finding classes → preventive controls
> The point of the review. Group findings and name the guardrail that
> eliminates each class permanently, instead of listing the instances.
| Finding class | Instances | Preventive control | Where it applies | Owner |
|---------------|-----------|--------------------|------------------|-------|
| | | | | |
---
## Accepted risk
| Finding | Why accepted | Compensating control | Approver | Expires |
|---------|--------------|----------------------|----------|---------|
| | | | | |
An acceptance with no expiry date is a silent policy change. Every row needs a date.
---
## Follow-ups
- [ ] Critical findings assigned as incidents with owners
- [ ] Guardrails from the finding-class table scheduled
- [ ] Re-scan booked for +30 days; report the delta, not the absolute count
- [ ] Exceptions entered in the risk register with expiry dates
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |