detection.wiki

Detection rules › Panther

GSuite User Advanced Protection Change

Severity
low
Log types
GSuite.ActivityEvent
Tags
GSuite, Defense Evasion:Impair Defenses
Reference
https://support.google.com/a/answer/9378686?hl=en&sjid=864417124752637253-EU
Source
github.com/panther-labs/panther-analysis

A user disabled advanced protection for themselves.

MITRE ATT&CK coverage

TacticTechniques
StealthT1562 Impair Defenses

Rule body yaml

AnalysisType: rule
Filename: gsuite_advanced_protection.py
RuleID: "GSuite.AdvancedProtection"
DisplayName: "GSuite User Advanced Protection Change"
Enabled: true
LogTypes:
  - GSuite.ActivityEvent
Tags:
  - GSuite
  - Defense Evasion:Impair Defenses
Reports:
  MITRE ATT&CK:
    - TA0005:T1562
Severity: Low
Description: >
  A user disabled advanced protection for themselves.
Reference: https://support.google.com/a/answer/9378686?hl=en&sjid=864417124752637253-EU
Runbook: >
  Have the user re-enable Google Advanced Protection
SummaryAttributes:
  - actor:email
Tests:
  - Name: Advanced Protection Enabled
    ExpectedResult: false
    Log:
      {
        "id": { "applicationName": "user_accounts" },
        "actor": { "callerType": "USER", "email": "homer.simpson@example.com" },
        "type": "titanium_change",
        "name": "titanium_enroll",
      }
  - Name: Advanced Protection Disabled
    ExpectedResult: true
    Log:
      {
        "id": { "applicationName": "user_accounts" },
        "actor": { "callerType": "USER", "email": "homer.simpson@example.com" },
        "type": "titanium_change",
        "name": "titanium_unenroll",
      }

Detection logic

Condition

id.applicationName eq "user_accounts"
name eq "titanium_unenroll"

Indicators

Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.

FieldKindValues
id.applicationNameeq
  • user_accounts
nameeq
  • titanium_unenroll

Output fields

Fields the rule emits when it matches. Chronicle authors list these in the outcome block; they appear on the detection and $risk_score drives alerting. Sentinel / Defender XDR rules build them up through project / summarize / extend stages. Sentinel maps these into alert fields via entityMappings and customDetails; Defender XDR custom detections surface them as alert fields directly.

FieldSource
emailactor.email