| name | pentest-cloud |
| description | Cloud and infrastructure testing. Storage misconfig, WAF detection, email security. |
| user-invocable | true |
| allowed-tools | ["Bash","Agent","Read"] |
/pentest-cloud โ Cloud & Infrastructure Testing
Test a target application's cloud infrastructure for storage misconfigurations, WAF presence, and email security (SPF, DKIM, DMARC).
Input
The target URL is provided via $ARGUMENTS. If no URL is provided, ask the user for one.
Steps
-
Parse the target URL from $ARGUMENTS.
-
Delegate to cloud-agent using the Agent tool. The agent must run the following commands, collecting all JSON output:
pentest -k -j -o ./findings cloud storage <url>
pentest -k -j -o ./findings cloud waf <url>
pentest -k -j -o ./findings cloud email <url>
-
Read the JSON outputs from ./findings/ to gather all results.
-
Report cloud-specific findings covering:
- Storage misconfigurations: Publicly accessible S3 buckets, Azure Blob containers, GCS buckets with listing enabled, open Firebase storage
- WAF detection: Identified WAF vendor (Cloudflare, AWS WAF, Akamai, etc.), WAF bypass potential, rate limiting policies
- Email security: SPF record validity, DKIM configuration, DMARC policy (none/quarantine/reject), email spoofing risk
For each finding, include:
- Severity rating
- Evidence (URLs, DNS records, response headers)
- Remediation steps specific to the cloud provider
Notes
- All cloud commands are passive and safe to run without explicit consent.
- Storage enumeration checks for publicly known bucket naming patterns.
- WAF detection helps inform testing strategy for other skills.
- Use
-k to skip SSL verification for targets with self-signed certs.
- Use
-j for machine-readable JSON output.
- Use
-o ./findings to persist results for later reporting.