> 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-lambda-infrastructure-enumeration-activity.md).

# AWS Lambda infrastructure enumeration activity

### 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       | Discovery (TA0007)                     |
| ATT\&CK Technique    | Cloud Infrastructure Discovery (T1580) |
| Severity             | Informational                          |

### Description

Lambda infrastructure enumeration activity detected within a specific AWS region.

### Attacker's Goals

* Discover deployed functions and their configurations.
* Assess IAM policies, event triggers, and execution limits to evaluate privilege levels and potential abuse paths.
* Enumerate metadata for potential weaknesses or sensitive data.

### Investigative actions

* Identify and review the specific Lambda enumeration API calls executed and their frequency.
* Verify the identity performing the calls and assess if this behavior is typical or anomalous.
* Correlate with other discovery activities and check related logs for suspicious patterns or subsequent actions.


---

# 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/aws-lambda-infrastructure-enumeration-activity.md?ask=<question>&goal=<endgoal>
```

`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.