> 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/a-cloud-snapshot-of-aws-database-or-storage-was-modified-or-shared.md).
# A cloud snapshot of AWS database or storage was modified or shared
### 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 Configuration, Data Detection & Response |
| ATT\&CK Tactic | Exfiltration (TA0010) |
| ATT\&CK Technique | Transfer Data to Cloud Account (T1537) |
| Severity | Informational |
### Description
A cloud identity has shared a snapshot of an AWS database or storage instance.
### Attacker's Goals
Exfiltrate sensitive data that resides on the snapshot.
### Investigative actions
* Check if the identity intended to modify the snapshot.
* Check if the identity performed additional malicious operations within the cloud environment.
### Variations
Cloud snapshot of a database or storage instance was shared public
**Synopsis**
| Field | Value |
| ----------------- | -------------------------------------- |
| ATT\&CK Tactic | Exfiltration (TA0010) |
| ATT\&CK Technique | Transfer Data to Cloud Account (T1537) |
| Severity | Low |
**Description**
A cloud identity has shared a snapshot of an AWS database or storage instance.
**Attacker's Goals**
Exfiltrate sensitive data that resides on the snapshot.
**Investigative actions**
* Check if the identity intended to modify the snapshot.
* Check if the identity performed additional malicious operations within the cloud environment.
* Check if snapshot contained sensitive information and investigate aws account that shared it.
Cloud snapshot of a database or storage instance was shared with an unknown AWS account
**Synopsis**
| Field | Value |
| ----------------- | -------------------------------------- |
| ATT\&CK Tactic | Exfiltration (TA0010) |
| ATT\&CK Technique | Transfer Data to Cloud Account (T1537) |
| Severity | Low |
**Description**
A cloud identity has shared a snapshot of an AWS database or storage instance.
**Attacker's Goals**
Exfiltrate sensitive data that resides on the snapshot.
**Investigative actions**
* Check if the identity intended to modify the snapshot.
* Check if the identity performed additional malicious operations within the cloud environment.
* Check which AWS accounts the snapshot was shared with.
---
# 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/a-cloud-snapshot-of-aws-database-or-storage-was-modified-or-shared.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.