Back to catalog
Static reviewDevelopment

Skill dossier

performing-cloud-penetration-testing-with-pacu

Source declaration

Run authorized AWS penetration tests with Pacu, the open-source AWS exploitation framework, to enumerate IAM configuration, scan for privilege escalation paths, and test data access and lateral movement using compromised credentials. Use when conducting authorized red-team assessments of AWS environments, validating IAM policies and SCPs, or determining the blast radius of compromised AWS credentials.

The author's original description, preserved in English. It describes intent, not verified performance.

Run authorized AWS penetration tests with Pacu, the open-source AWS exploitation framework, to enumerate IAM configuration, scan for privilege escalation paths, and test data access and lateral movement using compromised credentials. Use when conducting authorized red-team assessments of AWS environments, validating IAM policies and SCPs, or determining the blast radius of compromised AWS credentials.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Run authorized AWS penetration tests with Pacu, the open-source AWS exploitation framework, to enumerate IAM configuration, scan for privilege escalation paths, and test data access and lateral movement using compromised credentials. Use when conducting authorized red-team assessments of AWS environments, validating IAM policies and SCPs, or determining the blast radius of compromised AWS credentials. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/performing-cloud-penetration-testing-with-pacu/SKILL.md:L56]
  • Step 1: Initialize Pacu Session and Configure Credentials [Source statement; provisional, not tested. Evidence: skills/performing-cloud-penetration-testing-with-pacu/SKILL.md:L58]
  • Step 2: Enumerate IAM Configuration [Source statement; provisional, not tested. Evidence: skills/performing-cloud-penetration-testing-with-pacu/SKILL.md:L84]
  • Step 3: Scan for Privilege Escalation Paths [Source statement; provisional, not tested. Evidence: skills/performing-cloud-penetration-testing-with-pacu/SKILL.md:L105]
  • Step 4: Enumerate and Test Data Access [Source statement; provisional, not tested. Evidence: skills/performing-cloud-penetration-testing-with-pacu/SKILL.md:L140]
  • Step 5: Test Lateral Movement and Persistence [Source statement; provisional, not tested. Evidence: skills/performing-cloud-penetration-testing-with-pacu/SKILL.md:L168]
  • Step 6: Validate Detection and Generate Report [Source statement; provisional, not tested. Evidence: skills/performing-cloud-penetration-testing-with-pacu/SKILL.md:L194]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/performing-cloud-penetration-testing-with-pacu/SKILL.md:L1-L33]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
32.8 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/performing-cloud-penetration-testing-with-pacu/LICENSEOther11 KB
skills/performing-cloud-penetration-testing-with-pacu/references/api-reference.mdReference2.4 KB
skills/performing-cloud-penetration-testing-with-pacu/scripts/agent.pyScript8.3 KB
skills/performing-cloud-penetration-testing-with-pacu/SKILL.mdInstruction11.1 KB

SKILL.md frontmatter

{
  "name": "performing-cloud-penetration-testing-with-pacu",
  "description": "Run authorized AWS penetration tests with Pacu, the open-source AWS exploitation framework, to enumerate IAM configuration, scan for privilege escalation paths, and test data access and lateral movement using compromised credentials. Use when conducting authorized red-team assessments of AWS environments, validating IAM policies and SCPs, or determining the blast radius of compromised AWS credentials.\n",
  "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"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: Initialize Pacu Session and Configure Credentials

    Source-described action candidate under “Step 1: Initialize Pacu Session and Configure Credentials”; not verified execution.

  4. 04
    Action

    Step 2: Enumerate IAM Configuration

    Source-described action candidate under “Step 2: Enumerate IAM Configuration”; not verified execution.

  5. 05
    Action

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

    Source-described action candidate under “Step 2: Enumerate IAM Configuration”; not verified execution.

  6. 06
    Action

    Step 3: Scan for Privilege Escalation Paths

    Source-described action candidate under “Step 3: Scan for Privilege Escalation Paths”; not verified execution.

Inspect all extracted workflow candidates (22 candidate steps)
  1. 07
    Action

    Use Pacu's privilege escalation scanner to identify all exploitable escalation vectors.

    Source-described action candidate under “Step 3: Scan for Privilege Escalation Paths”; not verified execution.

  2. 08
    Action

    Step 4: Enumerate and Test Data Access

    Source-described action candidate under “Step 4: Enumerate and Test Data Access”; not verified execution.

  3. 09
    Action

    Step 5: Test Lateral Movement and Persistence

    Source-described action candidate under “Step 5: Test Lateral Movement and Persistence”; not verified execution.

  4. 10
    Output

    Step 6: Validate Detection and Generate Report

    Source-described output candidate under “Step 6: Validate Detection and Generate Report”; not verified execution.

  5. 11
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  6. 12
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  7. 13
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  8. 14
    Action

    Initialize Pacu with the compromised credentials and run `whoami` to confirm identity

    Source-described action candidate under “Scenario: Red Team Assessment Starting from Compromised Developer Credentials”; not verified execution.

  9. 15
    Action

    Run `iamenumpermissions` to map the developer's effective permissions

    Source-described action candidate under “Scenario: Red Team Assessment Starting from Compromised Developer Credentials”; not verified execution.

  10. 16
    Action

    Execute `iamprivescscan` to identify escalation paths from developer to admin

    Source-described action candidate under “Scenario: Red Team Assessment Starting from Compromised Developer Credentials”; not verified execution.

  11. 17
    Action

    Discover the developer can call `iam:PassRole` + `lambda:CreateFunction`, creating a Lambda with an admin role

    Source-described action candidate under “Scenario: Red Team Assessment Starting from Compromised Developer Credentials”; not verified execution.

  12. 18
    Action

    Exploit the escalation to obtain admin-level temporary credentials

    Source-described action candidate under “Scenario: Red Team Assessment Starting from Compromised Developer Credentials”; not verified execution.

  13. 19
    Action

    Enumerate S3 buckets, download sensitive data, and access Secrets Manager

    Source-described action candidate under “Scenario: Red Team Assessment Starting from Compromised Developer Credentials”; not verified execution.

  14. 20
    Decision

    Verify whether GuardDuty detected the escalation and data access activities

    Source-described decision candidate under “Scenario: Red Team Assessment Starting from Compromised Developer Credentials”; not verified execution.

  15. 21
    Action

    Clean up all test artifacts and document the complete attack chain

    Source-described action candidate under “Scenario: Red Team Assessment Starting from Compromised Developer Credentials”; not verified execution.

  16. 22
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

54 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

6 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 6 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

48 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 48 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/performing-cloud-penetration-testing-with-pacu/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/performing-cloud-penetration-testing-with-pacu/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/performing-cloud-penetration-testing-with-pacu
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.