> 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/s3-configuration-deletion.md). # S3 configuration deletion ### 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 Disaster Recovery Risks, Cloud Data Asset Stealth Tactics, Cloud Data Asset Configuration, Data Detection & Response | | ATT\&CK Tactic | Impact (TA0040) | | ATT\&CK Technique | Data Encrypted for Impact (T1486) | | Severity | Informational | ### Description An S3 bucket configuration has been deleted. This may affect the S3 access, and the objects it contains. ### Attacker's Goals Modify the S3 configuration and expose stored sensitive data. ### Investigative actions * Check what data is stored on the S3. * Check which configuration change has been made. * Verify this change did not make this S3 publicly available. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/s3-configuration-deletion.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.