Back to catalog
Static reviewDevelopment

Skill dossier

auditing-aws-s3-bucket-permissions

Source declaration

Systematically audit AWS S3 bucket permissions to identify publicly accessible buckets, overly permissive ACLs, misconfigured bucket policies, and missing encryption settings using AWS CLI, S3audit, and Prowler to enforce least-privilege data access controls.

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

Systematically audit AWS S3 bucket permissions to identify publicly accessible buckets, overly permissive ACLs, misconfigured bucket policies, and missing encryption settings using AWS CLI, S3audit, and Prowler to enforce least-privilege data access controls.

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.

Systematically audit AWS S3 bucket permissions to identify publicly accessible buckets, overly permissive ACLs, misconfigured bucket policies, and missing encryption settings using AWS CLI, S3audit, and Prowler to enforce least-privilege data access controls. 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/auditing-aws-s3-bucket-permissions/SKILL.md:L54]
  • Step 1: Enumerate All S3 Buckets and Account-Level Block Public Access [Source statement; provisional, not tested. Evidence: skills/auditing-aws-s3-bucket-permissions/SKILL.md:L56]
  • Step 2: Check Each Bucket's Public Access Block and ACL Configuration [Source statement; provisional, not tested. Evidence: skills/auditing-aws-s3-bucket-permissions/SKILL.md:L78]
  • Step 3: Analyze Bucket Policies for Overly Permissive Access [Source statement; provisional, not tested. Evidence: skills/auditing-aws-s3-bucket-permissions/SKILL.md:L95]
  • Step 4: Verify Encryption and Versioning Settings [Source statement; provisional, not tested. Evidence: skills/auditing-aws-s3-bucket-permissions/SKILL.md:L120]
  • Step 5: Run Prowler S3-Specific Checks [Source statement; provisional, not tested. Evidence: skills/auditing-aws-s3-bucket-permissions/SKILL.md:L144]
  • Step 6: Use IAM Access Analyzer for S3 Public and Cross-Account Findings [Source statement; provisional, not tested. Evidence: skills/auditing-aws-s3-bucket-permissions/SKILL.md:L164]
  • Step 7: Generate Audit Report and Remediate [Source statement; provisional, not tested. Evidence: skills/auditing-aws-s3-bucket-permissions/SKILL.md:L182]

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/auditing-aws-s3-bucket-permissions/SKILL.md:L1-L32]

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
30.6 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/auditing-aws-s3-bucket-permissions/LICENSEOther11 KB
skills/auditing-aws-s3-bucket-permissions/references/api-reference.mdReference2.3 KB
skills/auditing-aws-s3-bucket-permissions/scripts/agent.pyScript6.5 KB
skills/auditing-aws-s3-bucket-permissions/SKILL.mdInstruction10.7 KB

SKILL.md frontmatter

{
  "name": "auditing-aws-s3-bucket-permissions",
  "description": "Systematically audit AWS S3 bucket permissions to identify publicly accessible buckets, overly permissive ACLs, misconfigured bucket policies, and missing encryption settings using AWS CLI, S3audit, and Prowler to enforce least-privilege data access controls.\n",
  "domain": "cybersecurity",
  "subdomain": "cloud-security",
  "tags": [
    "cloud-security",
    "aws",
    "s3",
    "bucket-permissions",
    "data-protection",
    "access-control"
  ],
  "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": [
    "T1530",
    "T1619",
    "T1078.004",
    "T1537",
    "T1567.002"
  ]
}

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: Enumerate All S3 Buckets and Account-Level Block Public Access

    Source-described action candidate under “Step 1: Enumerate All S3 Buckets and Account-Level Block Public Access”; not verified execution.

  4. 04
    Action

    Check the account-level S3 Block Public Access settings first, then list all buckets with their regions.

    Source-described action candidate under “Step 1: Enumerate All S3 Buckets and Account-Level Block Public Access”; not verified execution.

  5. 05
    Action

    Step 2: Check Each Bucket's Public Access Block and ACL Configuration

    Source-described action candidate under “Step 2: Check Each Bucket's Public Access Block and ACL Configuration”; not verified execution.

  6. 06
    Action

    Step 3: Analyze Bucket Policies for Overly Permissive Access

    Source-described action candidate under “Step 3: Analyze Bucket Policies for Overly Permissive Access”; not verified execution.

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

    Step 4: Verify Encryption and Versioning Settings

    Source-described action candidate under “Step 4: Verify Encryption and Versioning Settings”; not verified execution.

  2. 08
    Action

    Check that all buckets have server-side encryption enabled and versioning configured for data protection.

    Source-described action candidate under “Step 4: Verify Encryption and Versioning Settings”; not verified execution.

  3. 09
    Action

    Step 5: Run Prowler S3-Specific Checks

    Source-described action candidate under “Step 5: Run Prowler S3-Specific Checks”; not verified execution.

  4. 10
    Action

    Step 6: Use IAM Access Analyzer for S3 Public and Cross-Account Findings

    Source-described action candidate under “Step 6: Use IAM Access Analyzer for S3 Public and Cross-Account Findings”; not verified execution.

  5. 11
    Output

    Step 7: Generate Audit Report and Remediate

    Source-described output candidate under “Step 7: Generate Audit Report and Remediate”; not verified execution.

  6. 12
    Action

    Key Concepts

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

  7. 13
    Action

    Tools & Systems

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

  8. 14
    Action

    Common Scenarios

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

  9. 15
    Input

    Run `aws s3api get-bucket-acl` and find a grant to `AllUsers` with `READ` permission

    Source-described input candidate under “Scenario: Identifying a Publicly Readable Bucket Containing Customer Data”; not verified execution.

  10. 16
    Action

    Check `get-bucket-policy` and discover a policy with `Principal: ""` and `s3:GetObject`

    Source-described action candidate under “Scenario: Identifying a Publicly Readable Bucket Containing Customer Data”; not verified execution.

  11. 17
    Action

    Confirm Block Public Access is not enabled at the bucket or account level

    Source-described action candidate under “Scenario: Identifying a Publicly Readable Bucket Containing Customer Data”; not verified execution.

  12. 18
    Action

    Enumerate bucket contents to assess data sensitivity

    Source-described action candidate under “Scenario: Identifying a Publicly Readable Bucket Containing Customer Data”; not verified execution.

  13. 19
    Action

    Immediately enable Block Public Access on the bucket

    Source-described action candidate under “Scenario: Identifying a Publicly Readable Bucket Containing Customer Data”; not verified execution.

  14. 20
    Decision

    Review CloudTrail S3 data events to determine if unauthorized access occurred

    Source-described decision candidate under “Scenario: Identifying a Publicly Readable Bucket Containing Customer Data”; not verified execution.

  15. 21
    Output

    Report the finding with timeline, data inventory, and remediation confirmation

    Source-described output candidate under “Scenario: Identifying a Publicly Readable Bucket Containing Customer Data”; 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

15 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

9 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 9 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

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

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/auditing-aws-s3-bucket-permissions/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/auditing-aws-s3-bucket-permissions/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/auditing-aws-s3-bucket-permissions
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.