Detection rules › Panther
GSuite Workspace Gmail Security Sandbox Disabled
A Workspace Admin Has Disabled The Security Sandbox
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Initial Access | T1566 Phishing |
Rule body yaml
AnalysisType: rule
Filename: gsuite_workspace_gmail_security_sandbox_disabled.py
RuleID: "GSuite.Workspace.GmailSecuritySandboxDisabled"
DisplayName: "GSuite Workspace Gmail Security Sandbox Disabled"
Enabled: true
LogTypes:
- GSuite.ActivityEvent
Tags:
- GSuite
Reports:
MITRE ATT&CK:
- TA0001:T1566
Severity: Medium
Description: >
A Workspace Admin Has Disabled The Security Sandbox
Reference: https://support.google.com/a/answer/7676854?hl=en#zippy=%2Cfind-security-sandbox-settings%2Cabout-security-sandbox-rules-and-other-scans
Runbook: >
Gmail's Security Sandbox enables rule based scanning of email content.
If this change was not intentional, inspect the other actions taken by this actor.
SummaryAttributes:
- actor:email
Tests:
- Name: Workspace Admin Disables Security Sandbox
ExpectedResult: true
Log:
{
"actor":
{
"callerType": "USER",
"email": "example@example.io",
"profileId": "12345",
},
"id":
{
"applicationName": "admin",
"customerId": "D12345",
"time": "2022-12-11 03:31:41.212000000",
"uniqueQualifier": "-12345",
},
"ipAddress": "12.12.12.12",
"kind": "admin#reports#activity",
"name": "CHANGE_APPLICATION_SETTING",
"parameters":
{
"APPLICATION_EDITION": "enterprise",
"APPLICATION_NAME": "Gmail",
"NEW_VALUE": "false",
"ORG_UNIT_NAME": "Example IO",
"SETTING_NAME": "AttachmentDeepScanningSettingsProto deep_scanning_enabled",
},
"type": "APPLICATION_SETTINGS",
}
- Name: Admin Set Default Calendar SHARING_OUTSIDE_DOMAIN Setting to READ_ONLY_ACCESS
ExpectedResult: false
Log:
{
"actor":
{
"callerType": "USER",
"email": "example@example.io",
"profileId": "12345",
},
"id":
{
"applicationName": "admin",
"customerId": "D12345",
"time": "2022-12-11 01:06:26.303000000",
"uniqueQualifier": "-12345",
},
"ipAddress": "12.12.12.12",
"kind": "admin#reports#activity",
"name": "CHANGE_CALENDAR_SETTING",
"parameters":
{
"DOMAIN_NAME": "example.io",
"NEW_VALUE": "READ_ONLY_ACCESS",
"OLD_VALUE": "DEFAULT",
"ORG_UNIT_NAME": "Example IO",
"SETTING_NAME": "SHARING_OUTSIDE_DOMAIN",
},
"type": "CALENDAR_SETTINGS",
}
- Name: ListObject Type
ExpectedResult: false
Log:
{
"actor":
{ "email": "user@example.io", "profileId": "118111111111111111111" },
"id":
{
"applicationName": "drive",
"customerId": "D12345",
"time": "2022-12-20 17:27:47.080000000",
"uniqueQualifier": "-7312729053723258069",
},
"ipAddress": "12.12.12.12",
"kind": "admin#reports#activity",
"name": "rename",
"parameters":
{
"actor_is_collaborator_account": null,
"billable": true,
"doc_id": "1GGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG",
"doc_title": "Document Title- Found Here",
"doc_type": "presentation",
"is_encrypted": null,
"new_value": ["Document Title- Found Here"],
"old_value": ["Document Title- Old"],
"owner": "user@example.io",
"owner_is_shared_drive": null,
"owner_is_team_drive": null,
"primary_event": true,
"visibility": "private",
},
"type": "access",
}
Detection logic
Condition
id.applicationName eq "admin"
name eq "CHANGE_APPLICATION_SETTING"
parameters.APPLICATION_NAME eq "gmail"
parameters.NEW_VALUE eq "false"
parameters.SETTING_NAME eq "AttachmentDeepScanningSettingsProto deep_scanning_enabled"
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.
| Field | Kind | Values |
|---|---|---|
id.applicationName | eq |
|
name | eq |
|
parameters.APPLICATION_NAME | eq |
|
parameters.NEW_VALUE | eq |
|
parameters.SETTING_NAME | eq |
|
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.
| Field | Source |
|---|---|
actor | actor.email |
applicationName | id.applicationName |
name | |
type | |
parameters | |
ORG_UNIT_NAME | parameters.ORG_UNIT_NAME |