Agent skill · security · borghei
cloud-security
Cloud 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.
Why this skill is useful
Provides specific cloud security posture management workflows and IAM best practices that the AI wouldn't reliably generate on its own.
What it needs
About 8k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Cloud Security Cloud breaches are rarely clever. They are a public bucket, an over-permissive role, a database on an open security group, and no audit log to reconstruct what happened. This skill covers cloud posture specifically: the configuration of identity, network exposure, encryption, detection coverage, and multi-account guardrails across AWS, Azure, and GCP. Scope boundary. This skill is deliberately narrow so it does not overlap its neighbours in engineering/. It does not cover application-code vulnerabilities, dependency CVEs, or compliance-framework mapping — that is senior-secops. It does not cover log analysis and intrusion signals — that is threat-detection. It does not cover offensive engagement planning or rules of engagement — that is red-team. It does not cover prompt injection, model extraction, or ML-pipeline threats — that is ai-security. What lives here is the posture of the cloud control plane itself: who can do what, what is reachable, what is encrypted, and what is logged. When to use this skill A cloud account or subscription is about to hold production customer data for the first time An IAM sprawl problem has accumulated and nobody knows which roles are actually admin A posture scanner produced hundreds of findings and the team needs a defensible priority order A new landing zone or multi-account structure is being designed A security questionnaire, SOC 2 audit, or customer due-diligence review asks for cloud evidence An incident occurred and the review needs to establish what the exposure was and whether logs exist to prove it Inputs the skill expects An exported resource inventory per account, covering every region (see assets/inventoryexportguide.md) An IAM principal export with policy statements, trust policies, and last-used data Account/subscription/project settings: audit logging, managed detection, org guardrails, log-archive isolation Data classification per store — which resources hold confidential, PCI, PHI, or restricted data …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/cloud-security