> 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/an-identity-successfully-extracted-multiple-secrets-within-the-organization.md).
# An identity successfully extracted multiple secrets within the organization
### Synopsis
| Field | Value |
| -------------------- | ----------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | 1 Hour |
| Deduplication Period | 5 Days |
| Required Data | AWS Audit Log |
| Detection Modules | Cloud |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | Credentials from Password Stores: Cloud Secrets Management Stores (T1555.006) |
| Severity | Low |
### Description
An identity successfully dumped multiple secrets from the project. 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 successfully enumerated and extracted multiple secrets within the organization
**Synopsis**
| Field | Value |
| ----------------- | ----------------------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | Credentials from Password Stores: Cloud Secrets Management Stores (T1555.006) |
| Severity | Medium |
**Description**
An identity successfully dumped multiple secrets from the project. 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 successfully extracted multiple secrets within the organization across multiple regions
**Synopsis**
| Field | Value |
| ----------------- | ----------------------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | Credentials from Password Stores: Cloud Secrets Management Stores (T1555.006) |
| Severity | Medium |
**Description**
An identity successfully dumped multiple secrets from the project. 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 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/an-identity-successfully-extracted-multiple-secrets-within-the-organization.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.