> 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/suspicious-secrets-dump-activity.md).
# Suspicious secrets dump activity
### Synopsis
| Field | Value |
| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | 1 Hour |
| Deduplication Period | 5 Days |
| Required Data | Requires one of the following data sources:
AWS Audit Log OR Azure Audit Log OR Gcp Audit Log
|
| Detection Modules | Cloud |
| ATT\&CK Tactic | Credential Access (TA0006), Collection (TA0009) |
| ATT\&CK Technique | Unsecured Credentials (T1552), Data from Cloud Storage (T1530), Credentials from Password Stores: Cloud Secrets Management Stores (T1555.006) |
| Severity | Informational |
### Description
An identity dumped multiple secrets from the project, considerably more than usual. This may indicate an attacker's attempt to dump sensitive information from the cloud environment.
### Attacker's Goals
Collect secrets from the cloud environment.
### Investigative actions
* Check the accessed secrets' designation.
* Verify that the identity did not dump any sensitive information that it shouldn't.
### Variations
An identity extracted every secret within the organization across multiple regions
**Synopsis**
| Field | Value |
| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006), Collection (TA0009) |
| ATT\&CK Technique | Unsecured Credentials (T1552), Data from Cloud Storage (T1530), Credentials from Password Stores: Cloud Secrets Management Stores (T1555.006) |
| Severity | Medium |
**Description**
An identity dumped multiple secrets from the project, considerably more than usual. This may indicate an attacker's attempt to dump sensitive information from the cloud environment.
**Attacker's Goals**
Collect secrets from the cloud environment.
**Investigative actions**
* Check the accessed secrets' designation.
* Verify that the identity did not dump any sensitive information that it shouldn't.
An identity extracted multiple secrets within the organization across multiple regions
**Synopsis**
| Field | Value |
| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006), Collection (TA0009) |
| ATT\&CK Technique | Unsecured Credentials (T1552), Data from Cloud Storage (T1530), Credentials from Password Stores: Cloud Secrets Management Stores (T1555.006) |
| Severity | Low |
**Description**
An identity dumped multiple secrets from the project, considerably more than usual. This may indicate an attacker's attempt to dump sensitive information from the cloud environment.
**Attacker's Goals**
Collect secrets from the cloud environment.
**Investigative actions**
* Check the accessed secrets' designation.
* Verify that the identity did not dump any sensitive information that it shouldn't.
---
# 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/suspicious-secrets-dump-activity.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.