performing-cloud-penetration-testing-with-pacu

name	performing-cloud-penetration-testing-with-pacu
description	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.
domain	cybersecurity
subdomain	cloud-security
tags	["cloud-security","aws","pacu","penetration-testing","offensive-security","iam-exploitation"]
version	1.0
author	mahipal
license	Apache-2.0
nist_csf	["PR.IR-01","ID.AM-08","GV.SC-06","DE.CM-01"]
mitre_attack	["T1078.004","T1530","T1537","T1580","T1068"]
source	https://github.com/mukul975/Anthropic-Cybersecurity-Skills
source_commit	04450304b12645cb2b974ab96d28c0664758a88d
note	Vendored verbatim from an external Apache-2.0 security-skill library, pinned by commit. Exceeds the internal 300-line skill guideline (agent-code-constraints.md) -- kept as-is because this is vendored reference material (forensics/threat-intel procedure), not Yana AI-authored content, and trimming would damage technical accuracy.

Performing Cloud Penetration Testing with Pacu

When to Use

• 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.

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

Step 1: Initialize Pacu Session and Configure Credentials

Set up a Pacu session with the test credentials and define the engagement scope.

# Install Pacu
pip install pacu

# Start Pacu
pacu

# Create a new session for the engagement
Pacu > set_keys --key-alias pentest-target
# Enter Access Key ID: AKIA...
# Enter Secret Access Key: ...

# Verify identity
Pacu > whoami

# Review available modules
Pacu > list
Pacu > search iam
Pacu > search ec2
Pacu > search s3

Step 2: Enumerate IAM Configuration

Run IAM enumeration modules to map users, roles, policies, and group memberships.

# Comprehensive IAM enumeration
Pacu > run iam__enum_users_roles_policies_groups

# Enumerate detailed permissions for the current principal
Pacu > run iam__enum_permissions

# Enumerate account authorization details (requires iam:GetAccountAuthorizationDetails)
Pacu > run iam__get_credential_report


Pacu > run iam__enum_roles


Pacu > data iam