> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/aws-s3-bucket-was-exposed-to-public-access.md).
# AWS S3 bucket was exposed to public access
### Synopsis
| Field | Value |
| -------------------- | ------------------------------------------------------------------------------------------ |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 1 Day |
| Required Data | AWS Audit Log |
| Detection Modules | Cloud |
| Detector Tags | Cloud Data Asset Exfiltration, Cloud Data Asset Public Exposure, Data Detection & Response |
| ATT\&CK Tactic | Defense Evasion (TA0005) |
| ATT\&CK Technique | Impair Defenses (T1562) |
| Severity | Low |
### Description
AWS S3 bucket was publicly shared.
### Attacker's Goals
* The attacker wants to maintain indirect control over the resource.
* The attacker intends to allow public access, making it harder to detect future activity.
* Attackers are constantly monitoring for public assets to steal sensitive information.
### Investigative actions
* Check if the identity intended to change the state of the bucket or object to public.
* Review the bucket ACL policy.
* Restrict permissions for the identity if needed.
### Variations
AWS S3 bucket was exposed to public access by admin cloud identity
**Synopsis**
| Field | Value |
| ----------------- | ------------------------ |
| ATT\&CK Tactic | Defense Evasion (TA0005) |
| ATT\&CK Technique | Impair Defenses (T1562) |
| Severity | Informational |
**Description**
AWS S3 bucket was publicly shared.
**Attacker's Goals**
* The attacker wants to maintain indirect control over the resource.
* The attacker intends to allow public access, making it harder to detect future activity.
* Attackers are constantly monitoring for public assets to steal sensitive information.
**Investigative actions**
* Check if the identity intended to change the state of the bucket or object to public.
* Review the bucket ACL policy.
* Restrict permissions for the identity if needed.
AWS S3 bucket was exposed to public access containing sensitive information
**Synopsis**
| Field | Value |
| ----------------- | ------------------------ |
| ATT\&CK Tactic | Defense Evasion (TA0005) |
| ATT\&CK Technique | Impair Defenses (T1562) |
| Severity | High |
**Description**
AWS S3 bucket was publicly shared.
**Attacker's Goals**
* The attacker wants to maintain indirect control over the resource.
* The attacker intends to allow public access, making it harder to detect future activity.
* Attackers are constantly monitoring for public assets to steal sensitive information.
**Investigative actions**
* Check if the identity intended to change the state of the bucket or object to public.
* Review the bucket ACL policy.
* Restrict permissions for the identity if needed.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/aws-s3-bucket-was-exposed-to-public-access.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.