Lateral Movement (TA0008)(external, opens in a new tab or window)
Discovery (TA0007)(external, opens in a new tab or window)
Credential Access (TA0006)(external, opens in a new tab or window)
text code block:FROM logs-aws.cloudtrail-* | WHERE (event.action == "AssumeRoleWithWebIdentity" AND user.name like "system:serviceaccount:*") // S3 PutObject/GetObject is too common in legit pod SA behavior OR (event.action IN ("ListBuckets", "DescribeInstances", "GetCallerIdentity", "ListUsers", "ListRoles", "ListAttachedRolePolicies", "GetRolePolicy", "GetSecretValue", "ListSecrets", "GetParameters", "DescribeParameters", "ListKeys", "Decrypt", "ListFunctions", "GetAuthorizationToken", "SendCommand", "StartSession", "CreateUser", "CreateAccessKey", "AttachRolePolicy", "CreateRole", "PutRolePolicy", "UpdateAssumeRolePolicy", "UpdateFunctionCode", "UpdateFunctionConfiguration", "ModifyInstanceAttribute", "StopLogging", "DeleteTrail") AND aws.cloudtrail.user_identity.type == "AssumedRole") | GROK aws.cloudtrail.response_elements "accessKeyId=%{NOTSPACE:issued_key_id}," | EVAL access_key = COALESCE(issued_key_id, aws.cloudtrail.user_identity.access_key_id) | EVAL is_assume = CASE(event.action == "AssumeRoleWithWebIdentity", 1, 0) | EVAL is_post_exploit = CASE(event.action != "AssumeRoleWithWebIdentity", 1, 0) | EVAL phase = CASE( event.action == "AssumeRoleWithWebIdentity", "initial_access", event.action IN ("ListBuckets", "DescribeInstances", "ListUsers", "ListRoles", "GetCallerIdentity", "ListAttachedRolePolicies", "GetRolePolicy", "ListFunctions"), "recon", event.action IN ("GetSecretValue", "ListSecrets", "GetParameters", "GetAuthorizationToken", "Decrypt"), "credential_access", event.action IN ("SendCommand", "StartSession"), "lateral_movement", event.action IN ("CreateUser", "CreateAccessKey", "AttachRolePolicy", "CreateRole", "PutRolePolicy", "UpdateAssumeRolePolicy", "UpdateFunctionCode", "UpdateFunctionConfiguration", "ModifyInstanceAttribute"), "persistence", event.action IN ("StopLogging", "DeleteTrail"), "defense_evasion" ) | STATS Esql.assume_count = SUM(is_assume), Esql.post_exploit_count = COUNT_DISTINCT(event.action), Esql.attack_phases = VALUES(phase), Esql.event_action_values = VALUES(event.action), Esql.source_ip_values = VALUES(source.ip), Esql.source_as_organization_name_values = VALUES(source.as.organization.name), Esql.user_name_values = VALUES(user.name), Esql.user_agent_original_values = VALUES(user_agent.original), Esql.cloud_account_id_values = VALUES(cloud.account.id), Esql.data_stream_namespace_values = VALUES(data_stream.namespace), Esql.first_seen = MIN(@timestamp), Esql.last_seen = MAX(@timestamp), Esql.total_calls = COUNT(*) BY access_key | WHERE access_key is not null and Esql.assume_count >= 1 AND Esql.post_exploit_count >= 3 | EVAL aws.cloudtrail.user_identity.access_key_id = MV_FIRST(access_key) | KEEP aws.cloudtrail.user_identity.access_key_id, Esql.*
Install detection rules in Elastic Security
Detect AWS Lateral Movement from Kubernetes SA via AssumeRoleWithWebIdentity in the Elastic Security detection engine by installing this rule into your Elastic Stack.
To setup this rule, check out the installation guide for Prebuilt Security Detection Rules(external, opens in a new tab or window).