Elastic
Start free trial
Loading

Google Workspace Custom Admin Role Created

Elastic Stack Serverless Security

Detects when a custom admin role is created in Google Workspace. An adversary may create a custom admin role in order to elevate the permissions of other user accounts and persist in their target’s environment.

Rule type: query

Rule indices:

  • filebeat-*
  • logs-google_workspace*

Severity: medium

Risk score: 47

Runs every: 10m

Searches indices from: now-130m (https://www.elastic.co/guide/en/elasticsearch/reference/current/common-options.html#date-math[Date Math format], see also Additional look-back time)

Maximum alerts per execution: 100

References:

Tags:

  • Elastic
  • Cloud
  • Google Workspace
  • Continuous Monitoring
  • SecOps
  • Identity and Access

Version: 14

Rule authors:

  • Elastic

Rule license: Elastic License v2

Investigation guide

  • As per Google's documentation, Google Workspace administrators may observe lag times ranging from minutes up to 3 days between the time of an event's occurrence and the event being visible in the Google Workspace admin/audit logs.
  • This rule is configured to run every 10 minutes with a lookback time of 130 minutes.
  • To reduce the risk of false negatives, consider reducing the interval that the Google Workspace (formerly G Suite) Filebeat module polls Google's reporting API for new events.
  • By default, var.interval is set to 2 hours (2h). Consider changing this interval to a lower value, such as 10 minutes (10m).
  • See the following references for further information:
    • https://support.google.com/a/answer/7061566
    • /beats/docs/reference/ingestion-tools/beats-filebeat/filebeat-module-google_workspace.md

Rule query

event.dataset:google_workspace.admin and event.provider:admin and event.category:iam and event.action:CREATE_ROLE

Framework: MITRE ATT&CKTM