cloud-audit
Cloud Audit — Cloud Infrastructure Security Review
Audit cloud infrastructure configurations for misconfigurations, excessive permissions, public exposure, and compliance gaps. Covers AWS, GCP, and Azure, plus the PaaS deployment platforms many small teams run everything on (Vercel, Netlify, Heroku, Render, Railway, Fly).
Cross-references: iam-audit for the consultant-style IAM deep-dive (design / audit / migrate across identity providers and federation patterns) — this skill includes an IAM section but stays at the cloud-posture level; for role design, JIT access, workload identity federation, and migration plans, invoke iam-audit. container-audit for Kubernetes-specific posture sitting on top of cloud. secrets-audit for secrets-manager hygiene and rotation. patch-sweep for responding to a CVE wave across a fleet of PaaS apps (this skill's PaaS section is the posture half of that). scanner-pipeline for running Supabase's security advisor and the other scanners on a schedule.
Findings are recorded in the shared findings.json format (see Verify, then record). Dispositions, usually set later by finding-triage: Fixed / Deferred / Accepted Risk / Mitigated (platform/config) / Requires major migration.
Authorization
Audit only cloud accounts, projects, subscriptions and PaaS teams the user owns or is authorized to review, with credentials provided for that purpose. The pre-approved commands are read-only lists and describes. Never change a policy, rotate a key, delete a resource or redeploy as part of the audit: recommend it and let the owner run it. If the audit credentials grant more than read access, report that as a finding of its own.
Scope the Audit
Identify:
- Cloud provider(s) and account(s)
- Regions in use
- Whether CLI tools are available (
aws,gcloud,az,vercel,heroku,netlify,fly,railway,gh) or reviewing IaC files (Terraform, CloudFormation, Pulumi) - For PaaS: every team/account and GitHub owner/org in scope, and which of them belong to clients or other maintainers