GCP Detect accounts with high risk roles by project
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.
- Type: Hunting
-
Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Last Updated: 2020-10-09
- Author: Rod Soto, Splunk
- ID: 27af8c15-38b0-4408-b339-920170724adb
Annotations
ATT&CK
ID | Technique | Tactic |
---|---|---|
T1078 | Valid Accounts | Defense Evasion, Initial Access, Persistence, Privilege Escalation |
Kill Chain Phase
- Exploitation
NIST
CIS20
CVE
Search
1
2
3
`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
| 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{}
| `gcp_detect_accounts_with_high_risk_roles_by_project_filter`
Macros
The SPL above uses the following Macros:
Note that gcp_detect_accounts_with_high_risk_roles_by_project_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
Required field
- _time
- data.protoPayload.request.policy.bindings{}.role
- 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{}
How To Implement
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
RBA
Risk Score | Impact | Confidence | Message |
---|---|---|---|
25.0 | 50 | 50 | tbd |
Reference
- https://github.com/dxa4481/gcploit
- https://www.youtube.com/watch?v=Ml09R38jpok
- https://cloud.google.com/iam/docs/understanding-roles
Test Dataset
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 | version: 1