Cloud Service Dashboard T1538

Tactic: Discovery

An adversary may use a cloud service dashboard GUI with stolen credentials to gain useful information from an operational cloud environment, such as specific services, resources, and features. For example, the GCP Command Center can be used to view all assets, review findings of potential security risks, and run additional queries, such as finding public IP addresses and open ports.

Authoring guide

Patterns shared across the 4 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 (18 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
ClientIp1is_not_null 1
EntityName1in 1account, competitor, contact
EventType1eq 1, in 1CreateAssociation, DescribeInstancePatches, GetInventory
InstanceUrl1eq 1honeypot_dataverse_instances
Message1eq 1UserSignIn
Provider_Name1eq 1ssm.amazonaws.com
aws::eventName1in 1CreateTrail, StartLogging, UpdateTrail
aws::requestParameters1contains 1aws-gathersoftwareinventory
data_stream.dataset1eq 1aws.cloudtrail
event.outcome1eq 1success
eventType1eq 1policy.evaluate_sign_on, user.authentication.sso
eventtype1eq 1
outcome.result1eq 1CHALLENGE, SUCCESS
ratio1lt 10.5
sourcetype1eq 1OktaIM2:log

Top indicator values (30 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
EntityNamein
account
1
EntityNamein
competitor
1
EntityNamein
contact
1
EntityNamein
lead
1
EntityNamein
opportunity
1
EventTypeeq
CreateAssociation
1
EventTypein
DescribeInstancePatches
1
EventTypein
GetInventory
1
EventTypein
GetInventorySchema
1
EventTypein
ListCommands
1
EventTypein
ListInventoryEntries
1
InstanceUrleq
honeypot_dataverse_instances
1
Messageeq
UserSignIn
16
Provider_Nameeq
ssm.amazonaws.com
15
aws::eventNamein
CreateTrail
1
aws::eventNamein
StartLogging
1
aws::eventNamein
UpdateTrail
14
aws::requestParameterscontains
aws-gathersoftwareinventory
1
data_stream.dataseteq
aws.cloudtrail
1141
event.outcomeeq
success
1251
eventTypeeq
policy.evaluate_sign_on
13
eventTypeeq
user.authentication.sso
12
outcome.resulteq
CHALLENGE
1
outcome.resulteq
SUCCESS
17
ratiolt
0.5
12
sourcetypeeq
OktaIM2:log
112
target{}.typeeq
AppInstance
1
total_challengesgt
0
1
total_challengesgt
2
1
userne
unknown
14

Exclusions (3 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
aws::userIdentity.typeeq
AWSService
1
userends_with
@onmicrosoft.com
1
usereq
honeypot_authorized_users
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)

Elastic 1 rule

Splunk 1 rule

Kusto 1 rule

Panther 1 rule