cloud-containers
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
Reference
reference/cloud-security.md- Platform-specific attack guides (AWS, Azure, GCP, Docker, K8s)
More from transilienceai/communitytools
hackerone
HackerOne bug bounty automation - parses scope CSVs, deploys parallel pentesting agents for each asset, validates PoCs, and generates platform-ready submission reports. Use when testing HackerOne programs or preparing professional vulnerability submissions.
50reconnaissance
Domain assessment and web application mapping - subdomain discovery, port scanning, endpoint enumeration, API discovery, and attack surface analysis.
40ai-threat-testing
Offensive AI security testing and exploitation framework. Systematically tests LLM applications for OWASP Top 10 vulnerabilities including prompt injection, model extraction, data poisoning, and supply chain attacks. Integrates with pentest workflows to discover and exploit AI-specific threats.
38osint
Open-source intelligence gathering - company repository enumeration, secret scanning, git history analysis, employee footprint, and code exposure discovery.
37social-engineering
Social engineering testing - phishing, pretexting, vishing, and physical security assessment techniques.
37source-code-scanning
Security-focused source code review and SAST. Scans for vulnerabilities (OWASP Top 10, CWE Top 25), CVEs in third-party dependencies/packages, hardcoded secrets, malicious code, and insecure patterns. Use when given source code, a repo path, or asked to "audit", "scan", "review" code security, or "check dependencies for CVEs".
35