cloud-penetration-testing

Conduct comprehensive security assessments of cloud infrastructure across Microsoft Azure, Amazon Web Services (AWS), and Google Cloud Platform (GCP).

By sickn33 · 303 installs

npx skills add sickn33/agentic-awesome-skills --skill cloud-penetration-testing

Source repository · Upstream listing

⚠️ AUTHORIZED USE ONLY This skill is for educational purposes or authorized security assessments only. You must have explicit, written permission from the system owner before using this tool. Misuse of this tool is illegal and strictly prohibited. Mandatory confirmation gate Before running any command that probes, exploits, changes, persists on, extracts data from, or attempts credential access against a target: 1. Ask the user to state the exact target URL, IP, account, or resource. 2. Ask the user to confirm written authorization and the permitted scope. 3. Show the exact command(s) and explain their expected effect. 4. Wait for explicit confirmation in the current conversation. Without that confirmation, remain read only and provide defensive guidance only. Prefer a sandbox, disposable VM, or controlled lab. AUTHORIZED USE ONLY: Use this skill only for authorized security assessments, defensive validation, or controlled educational environments. Cloud Penetration Testing Detailed Guide Read [the detailed guide](references/detailed guide.md) before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end to end work, read the guide completely. Prerequisites Required Tools Required Knowledge Cloud architecture fundamentals Identity and Access Management (IAM) API authentication mechanisms DevOps and automation concepts Required Access Written authorization for testing Test credentials or access tokens Defined scope and rules of engagement Constraints and Limitations Legal Requirements Only test with explicit written authorization Respect scope boundaries between cloud accounts Do not access production customer data Document all testing activities Technical Limitations MFA may prevent credential based attacks Conditional Access policies may restrict access CloudTrail/Activity Logs record all API calls Some resources require specific regional access Detection Considerations Cloud providers log all API activity Unusual access patterns trigger alerts Use slow, deliberate enumeration Consider GuardDuty, Security Center, Cloud Armor Examples Example 1: Azure Password Spray Scenario: Test Azure AD password policy Example 2: AWS S3 Bucket Enumeration Scenario: Find and access misconfigured S3 buckets Example 3: GCP Service Account Compromise Scenario: Pivot using compromised service account When to Use This skill is applicable to execute the workflow or actions described in the overview.