Serverless Execution T1648

Authoring guide

Patterns shared across the 12 rules above: which fields they filter on, what specific values they look for, and what they exclude. The catalog normalizes field names across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.

Fields filtered most (17 distinct)

The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.

Top indicator values (29 distinct)

Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique. Click a value to expand the rules under this technique that use it.

Rules under this technique

Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.

Elastic 11 rules

• AWS Lambda Function Created or Updated
• AWS Lambda Layer Added to Existing Function
• Azure Automation Runbook Created or Modified
• First Occurrence GitHub Event for a Personal Access Token (PAT)
• First Occurrence of GitHub Repo Interaction From a New IP
• First Occurrence of GitHub User Interaction with Private Repo
• First Occurrence of Private Repo Event from Specific GitHub Personal Access Token (PAT)
• First Time AWS CloudFormation Stack Creation
• GitHub App Deleted
• GitHub Repo Created
• High Number of Cloned GitHub Repos From PAT

YARA-L 1 rule

• AWS Lambda Update Function Code