Cloud containers
Cloud and container security testing - AWS, Azure, GCP, Docker, and Kubernetes misconfigurations and exploitation.From its SKILL.md
npx -y skills add transilienceai/communitytools --skill cloud-containersAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.9 KB, as published. Nobody here has run it
Cloud & Containers
Test cloud infrastructure and container environments for security misconfigurations and exploitation paths.
Techniques
| Platform | Key Vectors |
|---|---|
| AWS | S3 bucket exposure, IAM misconfig, metadata service, Lambda abuse |
| Azure | Blob storage, RBAC flaws, managed identity, App Service misconfig |
| GCP | Cloud Storage, service account keys, metadata server, IAM |
| Docker | Container escape, privileged mode, socket exposure, image vulnerabilities |
| Kubernetes | RBAC bypass, secret exposure, pod escape, API server access |
Workflow
- Enumerate cloud resources and services
- Test IAM/RBAC configurations
- Check storage and secrets exposure
- Test container isolation and escape paths
- Document findings with cloud-specific evidence
Two lanes — attack vs assess
This skill covers both, and they are different jobs producing different artifacts. Do not mix them in one deliverable.
| Lane | You have | You produce | Start at |
|---|---|---|---|
| Offensive | a cloud target to attack | exploited findings with a PoC | reference/INDEX.md |
| Posture | read-only credentials and a "review the configuration" ask | one evidenced verdict per control in a pinned catalogue | reference/posture/INDEX.md |
Reference
reference/INDEX.md- Router for platform-specific attack scenarios (AWS, Azure, GCP, Docker, K8s)reference/posture/INDEX.md- Credentialed read-only configuration review (CSPM): run order, verdict vocabulary, the four false-pass traps, pinned catalogues, and the licensing rule for benchmark-derived content