> 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-command-line-interface-cli-command-was-executed-from-an-aws-serverless-compute-service.md).
# A Command Line Interface (CLI) command was executed from an AWS serverless compute service
### Synopsis
| Field | Value |
| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 5 Days |
| Required Data | AWS Audit Log |
| Detection Modules | Cloud |
| Detector Tags | Cloud Serverless Function Credentials Theft Analytics |
| ATT\&CK Tactic | Initial Access (TA0001), Credential Access (TA0006), Execution (TA0002) |
| ATT\&CK Technique | Valid Accounts: Cloud Accounts (T1078.004), Steal Application Access Token (T1528), Unsecured Credentials (T1552), Command and Scripting Interpreter: Cloud API (T1059.009) |
| Severity | Low |
### Description
AWS serverless compute service token was used to execute a Command Line Interface (CLI) command. This may indicate token theft due to the nature of serverless compute.
### Attacker's Goals
Exfiltrate serverless token and abuse it.
### Investigative actions
* Verify whether the serverless-attached identity's credentials were intentionally used in CLI.
* Check what CLI commands were executed using the serverless attached token.
* Check if the suspected serverless function is compromised.
### Variations
A Command Line Interface (AWS-CLI) command was executed from an AWS serverless compute service
**Synopsis**
| Field | Value |
| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Initial Access (TA0001), Credential Access (TA0006), Execution (TA0002) |
| ATT\&CK Technique | Valid Accounts: Cloud Accounts (T1078.004), Steal Application Access Token (T1528), Unsecured Credentials (T1552), Command and Scripting Interpreter: Cloud API (T1059.009) |
| Severity | Informational |
**Description**
AWS serverless compute service token was used to execute a Command Line Interface (CLI) command. This may indicate token theft due to the nature of serverless compute.
**Attacker's Goals**
Exfiltrate serverless token and abuse it.
**Investigative actions**
* Verify whether the serverless-attached identity's credentials were intentionally used in CLI.
* Check what CLI commands were executed using the serverless attached token.
* Check if the suspected serverless function is compromised.
Unusual Command Line Interface (CLI) command was executed from an AWS serverless compute service
**Synopsis**
| Field | Value |
| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Initial Access (TA0001), Credential Access (TA0006), Execution (TA0002) |
| ATT\&CK Technique | Valid Accounts: Cloud Accounts (T1078.004), Steal Application Access Token (T1528), Unsecured Credentials (T1552), Command and Scripting Interpreter: Cloud API (T1059.009) |
| Severity | Low |
**Description**
AWS serverless compute service token was used to execute a Command Line Interface (CLI) command. This may indicate token theft due to the nature of serverless compute.
**Attacker's Goals**
Exfiltrate serverless token and abuse it.
**Investigative actions**
* Verify whether the serverless-attached identity's credentials were intentionally used in CLI.
* Check what CLI commands were executed using the serverless attached token.
* Check if the suspected serverless function is compromised.
---
# 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-command-line-interface-cli-command-was-executed-from-an-aws-serverless-compute-service.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.