Remote Services: Cloud Services T1021.007

Tactic: Lateral Movement

Adversaries may log into accessible cloud services within a compromised environment using Valid Accounts that are synchronized with or federated to on-premises user identities. The adversary may then perform management actions or access cloud-hosted resources as the logged-on user.

Events covered

1 catalog event is tagged with this technique by at least one rule.

Authoring guide

Patterns shared across the 19 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 (26 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.

FieldRulesHowSample values
operationName6contains 5, in 1 devicemanagementconfigurationpolicy, create mobileapp, devicecompliancescript, devicehealthscript, devicemanagementscript
sourcetype4eq 4azure:monitor:activity
EventType3eq 2, in 2AssumeRoleWithWebIdentity, AttachRolePolicy, ConsoleLogin, CreateAccessKey, GetSigninToken
EventID2eq 24104, UserLoggedIn
Provider_Name2eq 2signin.amazonaws.com, ssm.amazonaws.com
aws::eventName2eq 2GetSigninToken
aws::eventSource2eq 2signin.amazonaws.com
aws::userIdentity.type2eq 2AssumedRole
data_stream.dataset2eq 2aws.cloudtrail
event.outcome2eq 2success
responseStatus.code2ne 2403
Esql.assume_count1ge 11
Esql.post_exploit_count1ge 13
ScriptBlockText1in 1*install-module -name aadinternals*, *install-module -name az.resources*, *install-module -name azuread*
access_key1is_not_null 1

Top indicator values (75 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.

FieldKindValueRules (here)Corpus reach
sourcetypeeq
azure:monitor:activity
45
aws::eventNameeq
GetSigninToken
24
aws::eventSourceeq
signin.amazonaws.com
26
aws::userIdentity.typeeq
AssumedRole
212
data_stream.dataseteq
aws.cloudtrail
2141
event.outcomeeq
success
2251
responseStatus.codene
403
22
Esql.assume_countge
1
1
Esql.post_exploit_countge
3
1
EventIDeq
4104
1268
EventIDeq
UserLoggedIn
16
EventTypeeq
AssumeRoleWithWebIdentity
12
EventTypeeq
StartSession
1
EventTypein
AttachRolePolicy
13
EventTypein
ConsoleLogin
1
EventTypein
CreateAccessKey
13
EventTypein
CreateRole
13
EventTypein
CreateUser
13
EventTypein
Decrypt
1
EventTypein
DeleteTrail
1
EventTypein
DescribeInstances
12
EventTypein
DescribeParameters
1
EventTypein
GetAuthorizationToken
1
EventTypein
GetCallerIdentity
12
EventTypein
GetParameters
12
EventTypein
GetRolePolicy
1
EventTypein
GetSecretValue
1
EventTypein
GetSigninToken
1
EventTypein
ListAttachedRolePolicies
1
EventTypein
ListBuckets
12

Exclusions (23 distinct)

Field/operator/value combinations excluded by rules under this technique (top-level not() clauses), sorted by how many rules exclude each. These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths. Click a value to expand the rules under this technique that exclude it.

FieldKindValueRules excluding
user.groupscontains
system:authenticated
2
user.groupscontains
system:nodes
2
userAgentcontains
jersey/${project.version}
2
p_log_typecontains
amazon.eks
1
p_log_typecontains
azure.monitoractivity
1
p_log_typecontains
gcp.auditlog
1
protoPayload.requestMetadata.callerSuppliedUserAgentin
GoogleHC/1.0
1
protoPayload.requestMetadata.callerSuppliedUserAgentin
GoogleKubernetesEngineFrontend
1
protoPayload.resourceNameends_with
healthz
1
protoPayload.resourceNameends_with
livez
1
protoPayload.resourceNameends_with
readyz
1
requestURIends_with
healthz
1
requestURIends_with
livez
1
requestURIends_with
readyz
1
stagene
ResponseComplete
1

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.

Platform (all)
Domain (all)

Sigma 1 rule

Elastic 6 rules

Splunk 5 rules

YARA-L 1 rule

Panther 6 rules