Performing Cloud Penetration Testing With Pacu
Overview
Cybersecurity skill for performing cloud penetration testing with pacu. Follows industry best practices and security standards.
When to Use
Trigger phrases:
"performing cloud penetration testing with pacu"
"Performing authorized AWS penetration testing using Pacu, the open-source AWS ex"
When conducting authorized penetration testing of AWS environments
When validating the effectiveness of IAM policies, SCPs, and permission boundaries
When assessing the blast radius of a compromised set of AWS credentials
When testing detection capabilities of GuardDuty, Security Hub, and custom alerting
When building red team exercises against AWS cloud infrastructure
Do not use for unauthorized testing of any AWS account, for testing AWS infrastructure itself (covered by shared responsibility), for DDoS or volumetric attacks without AWS approval, or for production account testing without explicit authorization and breakglass procedures.
When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
Prerequisites
- Written authorization from the AWS account owner with defined scope and rules of engagement
- Pacu v1.5+ installed (
pip install pacu)
- Test AWS credentials with limited starting permissions (simulates compromised credential scenario)
- CloudTrail logging enabled to capture all Pacu activity for post-engagement review
- GuardDuty enabled to validate detection of Pacu activities
- Emergency contact and rollback procedures documented
Workflow
# Example: IOC detection
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs(text: str) -> dict:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
- Plan Operations — Define objectives, scope, and success criteria for cloud penetration testing operations.
- Prepare Environment — Set up tools, access, and data sources required for cloud penetration testing.
- Execute Core Workflow — Use pacu to perform cloud penetration testing operations following established procedures.
- Validate Results — Verify that results meet quality standards and objectives.
- Report Findings — Document results, observations, and recommendations.
- Follow Up — Track remediation actions and verify fixes where applicable.
Tools
- pacu — Primary tool for this skill
- Analysis Platform — Data processing and visualization
- Collaboration Tools — Team coordination and knowledge sharing
Process
- Design — Define interface, identify patterns, plan implementation
- Implement — Write code following existing conventions, add tests
- Verify — Run tests, check integration, validate behavior
Verification
Anti-Rationalization Table
| Rationalization |
Reality |
| "We are too small to be targeted" |
Automated attacks target everyone. Size does not matter. |
| "Security slows us down" |
A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" |
Vulnerabilities in production are exploited within hours. Fix before deploy. |
1---2name: performing-cloud-penetration-testing-with-pacu3description: Use when performing authorized AWS penetration testing using Pacu, the open-source AWS exploitation framework, to enumerate IAM configurations, discover privilege escalation paths, test credential harvesting, and validate security controls through systematic attack simulation. . Use when working with performing cloud penetration testing with pacu.4license: Apache-2.05---67# Performing Cloud Penetration Testing With Pacu89## Overview1011Cybersecurity skill for performing cloud penetration testing with pacu. Follows industry best practices and security standards.1213## When to Use14**Trigger phrases:**15- "performing cloud penetration testing with pacu"16- "Performing authorized AWS penetration testing using Pacu, the open-source AWS ex"171819- When conducting authorized penetration testing of AWS environments20- When validating the effectiveness of IAM policies, SCPs, and permission boundaries21- When assessing the blast radius of a compromised set of AWS credentials22- When testing detection capabilities of GuardDuty, Security Hub, and custom alerting23- When building red team exercises against AWS cloud infrastructure2425**Do not use** for unauthorized testing of any AWS account, for testing AWS infrastructure itself (covered by shared responsibility), for DDoS or volumetric attacks without AWS approval, or for production account testing without explicit authorization and breakglass procedures.262728## When NOT to Use2930- When you lack proper authorization for testing31- For production systems without change management32- When the task requires legal or compliance expertise beyond technical scope333435## Prerequisites3637- Written authorization from the AWS account owner with defined scope and rules of engagement38- Pacu v1.5+ installed (`pip install pacu`)39- Test AWS credentials with limited starting permissions (simulates compromised credential scenario)40- CloudTrail logging enabled to capture all Pacu activity for post-engagement review41- GuardDuty enabled to validate detection of Pacu activities42- Emergency contact and rollback procedures documented4344## Workflow4546```python47# Example: IOC detection48import re4950IOC_PATTERNS = {51 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",52 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",53 "hash_md5": r"\b[a-f0-9]{32}\b",54 "hash_sha256": r"\b[a-f0-9]{64}\b",55}5657def extract_iocs(text: str) -> dict:58 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}59```60611. **Plan Operations** — Define objectives, scope, and success criteria for cloud penetration testing operations.622. **Prepare Environment** — Set up tools, access, and data sources required for cloud penetration testing.633. **Execute Core Workflow** — Use pacu to perform cloud penetration testing operations following established procedures.644. **Validate Results** — Verify that results meet quality standards and objectives.655. **Report Findings** — Document results, observations, and recommendations.666. **Follow Up** — Track remediation actions and verify fixes where applicable.6768## Tools6970- **pacu** — Primary tool for this skill71- **Analysis Platform** — Data processing and visualization72- **Collaboration Tools** — Team coordination and knowledge sharing737475## Process76771. **Design** — Define interface, identify patterns, plan implementation781. **Implement** — Write code following existing conventions, add tests791. **Verify** — Run tests, check integration, validate behavior8081## Verification8283- [ ] All cloud penetration testing procedures executed completely and documented84- [ ] Findings validated against multiple data sources85- [ ] False positives identified and filtered86- [ ] Results documented with evidence and timestamps87- [ ] Recommendations provided with risk-based prioritization8889## Anti-Rationalization Table9091| Rationalization | Reality |92|---|---|93| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |94| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |95| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |