Detection: GCP Detect accounts with high risk roles by project

DEPRECATED DETECTION

This detection has been marked as deprecated by the Splunk Threat Research team. This means that it will no longer be maintained or supported. If you have any questions or concerns, please reach out to us at research@splunk.com.

Updated Date: 2024-10-17 ID: 27af8c15-38b0-4408-b339-920170724adb Author: Rod Soto, Splunk Type: Hunting Product: Splunk Enterprise Security

Description

This search provides detection of accounts with high risk roles by projects. Compromised accounts with high risk roles can move laterally or even scalate privileges at different projects depending on organization schema.

Search

1`google_gcp_pubsub_message` data.protoPayload.request.policy.bindings{}.role=roles/owner OR roles/editor OR roles/iam.serviceAccountUser OR roles/iam.serviceAccountAdmin OR roles/iam.serviceAccountTokenCreator OR roles/dataflow.developer OR roles/dataflow.admin OR roles/composer.admin OR roles/dataproc.admin OR roles/dataproc.editor 
2| table data.resource.type data.protoPayload.authenticationInfo.principalEmail data.protoPayload.authorizationInfo{}.permission data.protoPayload.authorizationInfo{}.resource data.protoPayload.response.bindings{}.role data.protoPayload.response.bindings{}.members{} 
3| `gcp_detect_accounts_with_high_risk_roles_by_project_filter`

Data Source

No data sources specified for this detection.

Macros Used

Name	Value
google_gcp_pubsub_message	`sourcetype="google:gcp:pubsub:message"`
gcp_detect_accounts_with_high_risk_roles_by_project_filter	`search *`

gcp_detect_accounts_with_high_risk_roles_by_project_filter is an empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Annotations

- MITRE ATT&CK

+ Kill Chain Phases

+ NIST

+ CIS

- Threat Actors

ID	Technique	Tactic
T1078	Valid Accounts	Defense Evasion

KillChainPhase.DELIVERY

KillChainPhase.EXPLOITAITON

KillChainPhase.INSTALLATION

NistCategory.DE_AE

Cis18Value.CIS_10

APT18

APT28

APT29

APT33

APT39

APT41

Akira

Axiom

Carbanak

Chimera

Cinnamon Tempest

Dragonfly

FIN10

FIN4

FIN5

FIN6

FIN7

FIN8

Fox Kitten

GALLIUM

INC Ransom

Indrik Spider

Ke3chang

LAPSUS$

Lazarus Group

Leviathan

OilRig

POLONIUM

PittyTiger

Play

Sandworm Team

Silence

Silent Librarian

Star Blizzard

Suckfly

Threat Group-3390

Volt Typhoon

Wizard Spider

menuPass

Default Configuration

This detection is configured by default in Splunk Enterprise Security to run with the following settings:

Setting	Value
Disabled	true
Cron Schedule	`0 * * * *`
Earliest Time	`-70m@m`
Latest Time	`-10m@m`
Schedule Window	`auto`
Creates Risk Event	False

This configuration file applies to all detections of type hunting.

Implementation

You must install splunk GCP add-on. This search works with gcp:pubsub:message logs

Known False Positives

Accounts with high risk roles should be reduced to the minimum number needed, however specific tasks and setups may be simply expected behavior within organization

Associated Analytic Story

GCP Cross Account Activity

Risk Based Analytics (RBA)

Risk Message	Risk Score	Impact	Confidence
tbd	25	50	50

The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.

References

Detection Testing

Test Type	Status	Dataset	Source	Sourcetype
Validation	Not Applicable	N/A	N/A	N/A
Unit	❌ Failing	N/A	`N/A`	`N/A`
Integration	❌ Failing	N/A	`N/A`	`N/A`

Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

Source: GitHub | Version: 3