Back to catalog
Static reviewDevelopment

Skill dossier

remediating-s3-bucket-misconfiguration

Source declaration

Provides step-by-step procedures for remediating Amazon S3 bucket misconfigurations that expose sensitive data: enabling S3 Block Public Access, auditing bucket policies and ACLs, enforcing encryption, configuring access logging, and deploying automated remediation with AWS Config and Lambda. Use when AWS Config or Security Hub flags public or unencrypted S3 buckets, or preparing audit evidence for storage security controls.

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

Provides step-by-step procedures for remediating Amazon S3 bucket misconfigurations that expose sensitive data: enabling S3 Block Public Access, auditing bucket policies and ACLs, enforcing encryption, configuring access logging, and deploying automated remediation with AWS Config and Lambda. Use when AWS Config or Security Hub flags public or unencrypted S3 buckets, or preparing audit evidence for storage security 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.

Provides step-by-step procedures for remediating Amazon S3 bucket misconfigurations that expose sensitive data: enabling S3 Block Public Access, auditing bucket policies and ACLs, enforcing encryption, configuring access logging, and deploying automated remediation with AWS Config and Lambda. Use when AWS Config or Security Hub flags public or unencrypted S3 buckets, or preparing audit evidence for storage security 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/remediating-s3-bucket-misconfiguration/SKILL.md:L54]
  • Step 1: Identify All Public and Misconfigured Buckets [Source statement; provisional, not tested. Evidence: skills/remediating-s3-bucket-misconfiguration/SKILL.md:L56]
  • Step 2: Enable S3 Block Public Access at Account Level [Source statement; provisional, not tested. Evidence: skills/remediating-s3-bucket-misconfiguration/SKILL.md:L89]
  • Step 3: Audit and Remediate Bucket Policies and ACLs [Source statement; provisional, not tested. Evidence: skills/remediating-s3-bucket-misconfiguration/SKILL.md:L118]
  • Step 4: Enforce Default Encryption [Source statement; provisional, not tested. Evidence: skills/remediating-s3-bucket-misconfiguration/SKILL.md:L164]
  • Step 5: Enable Access Logging and Monitoring [Source statement; provisional, not tested. Evidence: skills/remediating-s3-bucket-misconfiguration/SKILL.md:L197]
  • Step 6: Deploy Preventive Controls with SCP and Config [Source statement; provisional, not tested. Evidence: skills/remediating-s3-bucket-misconfiguration/SKILL.md:L222]

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/remediating-s3-bucket-misconfiguration/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.7 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/remediating-s3-bucket-misconfiguration/LICENSEOther11 KB
skills/remediating-s3-bucket-misconfiguration/references/api-reference.mdReference2.5 KB
skills/remediating-s3-bucket-misconfiguration/scripts/agent.pyScript7.5 KB
skills/remediating-s3-bucket-misconfiguration/SKILL.mdInstruction11.7 KB

SKILL.md frontmatter

{
  "name": "remediating-s3-bucket-misconfiguration",
  "description": "Provides step-by-step procedures for remediating Amazon S3 bucket misconfigurations that expose sensitive data: enabling S3 Block Public Access, auditing bucket policies and ACLs, enforcing encryption, configuring access logging, and deploying automated remediation with AWS Config and Lambda. Use when AWS Config or Security Hub flags public or unencrypted S3 buckets, or preparing audit evidence for storage security controls.\n",
  "domain": "cybersecurity",
  "subdomain": "cloud-security",
  "tags": [
    "s3-security",
    "bucket-misconfiguration",
    "data-exposure",
    "public-access-block",
    "aws-config"
  ],
  "version": "1.0.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",
    "T1573"
  ]
}

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: Identify All Public and Misconfigured Buckets

    Source-described action candidate under “Step 1: Identify All Public and Misconfigured Buckets”; not verified execution.

  4. 04
    Action

    Use multiple detection methods to identify S3 buckets with public access. Rely on AWS Config rules, S3 Access Analyzer, and Macie rather than manual inspection.

    Source-described action candidate under “Step 1: Identify All Public and Misconfigured Buckets”; not verified execution.

  5. 05
    Action

    Step 2: Enable S3 Block Public Access at Account Level

    Source-described action candidate under “Step 2: Enable S3 Block Public Access at Account Level”; not verified execution.

  6. 06
    Action

    Apply the four Block Public Access settings at the AWS account level as a safety net. This prevents any bucket in the account from being made public, regardless of individual bucket policies or ACLs.

    Source-described action candidate under “Step 2: Enable S3 Block Public Access at Account Level”; not verified execution.

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

    Step 3: Audit and Remediate Bucket Policies and ACLs

    Source-described action candidate under “Step 3: Audit and Remediate Bucket Policies and ACLs”; not verified execution.

  2. 08
    Action

    Step 4: Enforce Default Encryption

    Source-described action candidate under “Step 4: Enforce Default Encryption”; not verified execution.

  3. 09
    Action

    Step 5: Enable Access Logging and Monitoring

    Source-described action candidate under “Step 5: Enable Access Logging and Monitoring”; not verified execution.

  4. 10
    Action

    Step 6: Deploy Preventive Controls with SCP and Config

    Source-described action candidate under “Step 6: Deploy Preventive Controls with SCP and Config”; not verified execution.

  5. 11
    Action

    Use Service Control Policies to prevent disabling Block Public Access across the organization. Deploy AWS Config rules with auto-remediation.

    Source-described action candidate under “Step 6: Deploy Preventive Controls with SCP and Config”; 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
    Action

    Immediately enable Block Public Access on the specific bucket to stop the exposure

    Source-described action candidate under “Scenario: Data Breach from Publicly Readable S3 Bucket Containing PII”; not verified execution.

  10. 16
    Action

    Revoke all public ACLs by setting BucketOwnerEnforced ownership controls

    Source-described action candidate under “Scenario: Data Breach from Publicly Readable S3 Bucket Containing PII”; not verified execution.

  11. 17
    Action

    Audit CloudTrail and S3 access logs to determine which IP addresses accessed the exposed objects

    Source-described action candidate under “Scenario: Data Breach from Publicly Readable S3 Bucket Containing PII”; not verified execution.

  12. 18
    Action

    Run Macie on the bucket to classify the types of PII exposed and assess regulatory notification requirements

    Source-described action candidate under “Scenario: Data Breach from Publicly Readable S3 Bucket Containing PII”; not verified execution.

  13. 19
    Action

    Enable account-level Block Public Access to prevent recurrence across all buckets

    Source-described action candidate under “Scenario: Data Breach from Publicly Readable S3 Bucket Containing PII”; not verified execution.

  14. 20
    Action

    Deploy an SCP preventing any principal except SecurityAdmin from modifying Block Public Access settings

    Source-described action candidate under “Scenario: Data Breach from Publicly Readable S3 Bucket Containing PII”; not verified execution.

  15. 21
    Action

    Create a pre-signed URL mechanism or S3 Access Point for the legitimate partner sharing use case

    Source-described action candidate under “Scenario: Data Breach from Publicly Readable S3 Bucket Containing PII”; 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

8 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

2 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 2 location(s) in the collected text; 2 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/remediating-s3-bucket-misconfiguration/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/remediating-s3-bucket-misconfiguration/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/remediating-s3-bucket-misconfiguration
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.