> 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-started-an-aws-ssm-session.md).
# An identity started an AWS SSM session
### Synopsis
| Field | Value |
| -------------------- | ----------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 3 Days |
| Required Data | AWS Audit Log |
| Detection Modules | Cloud |
| Detector Tags | Cloud Lateral Movement Analytics, SSM Remote Management Analytics |
| ATT\&CK Tactic | Lateral Movement (TA0008) |
| ATT\&CK Technique | Remote Services: Direct Cloud VM Connections (T1021.008), Remote Services: Cloud Services (T1021.007) |
| Severity | Informational |
### Description
An identity started an AWS SSM interactive session.
### Attacker's Goals
Gaining unauthorized access, executing unauthorized commands, or compromising sensitive information within the target system.
### Investigative actions
* Examine the specifics of the SSM session, including the source IP address, identity, and timestamp.
* Validate the permissions and roles associated with the user initiating the SSM session to ensure they align with the expected level of access.
* Follow further actions taken by the identity or on the relevant instance.
### Variations
An identity started an unusual AWS SSM session
**Synopsis**
| Field | Value |
| ----------------- | ----------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Lateral Movement (TA0008) |
| ATT\&CK Technique | Remote Services: Direct Cloud VM Connections (T1021.008), Remote Services: Cloud Services (T1021.007) |
| Severity | Medium |
**Description**
An identity started an AWS SSM interactive session.
**Attacker's Goals**
Gaining unauthorized access, executing unauthorized commands, or compromising sensitive information within the target system.
**Investigative actions**
* Examine the specifics of the SSM session, including the source IP address, identity, and timestamp.
* Validate the permissions and roles associated with the user initiating the SSM session to ensure they align with the expected level of access.
* Follow further actions taken by the identity or on the relevant instance.
An unusual identity started an AWS SSM session
**Synopsis**
| Field | Value |
| ----------------- | ----------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Lateral Movement (TA0008) |
| ATT\&CK Technique | Remote Services: Direct Cloud VM Connections (T1021.008), Remote Services: Cloud Services (T1021.007) |
| Severity | Low |
**Description**
An identity started an AWS SSM interactive session.
**Attacker's Goals**
Gaining unauthorized access, executing unauthorized commands, or compromising sensitive information within the target system.
**Investigative actions**
* Examine the specifics of the SSM session, including the source IP address, identity, and timestamp.
* Validate the permissions and roles associated with the user initiating the SSM session to ensure they align with the expected level of access.
* Follow further actions taken by the identity or on the relevant instance.
---
# 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/an-identity-started-an-aws-ssm-session.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.