> 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-ssm-parameters-retrieval.md).

# AWS SSM parameters retrieval

### 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        | SSM Remote Management Analytics                                               |
| ATT\&CK Tactic       | Credential Access (TA0006)                                                    |
| ATT\&CK Technique    | Credentials from Password Stores: Cloud Secrets Management Stores (T1555.006) |
| Severity             | Informational                                                                 |

### Description

An attempt was made to retrieve parameters stored in AWS SSM.

### Attacker's Goals

Exfiltrate sensitive secrets stored in AWS SSM parameter store.

### Investigative actions

* Investigate the purpose of the encrypted parameter and assess the sensitivity of its contents.
* Check if the access aligns with known workflows or automation, or if it indicates abnormal activity.

### Variations

<details>

<summary>AWS SSM encrypted parameters retrieval</summary>

**Synopsis**

| Field             | Value                                                                         |
| ----------------- | ----------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Credential Access (TA0006)                                                    |
| ATT\&CK Technique | Credentials from Password Stores: Cloud Secrets Management Stores (T1555.006) |
| Severity          | Informational                                                                 |

**Description**

An attempt was made to retrieve encrypted parameters stored in AWS SSM.

**Attacker's Goals**

Exfiltrate sensitive secrets stored in AWS SSM parameter store.

**Investigative actions**

* Investigate the purpose of the encrypted parameter and assess the sensitivity of its contents.
* Check if the access aligns with known workflows or automation, or if it indicates abnormal activity.

</details>


---

# 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/aws-ssm-parameters-retrieval.md?ask=<question>&goal=<user_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.
