Google Workspace User Sign-in from Atypical Device Type
Detects the first time a Google Workspace user is observed authenticating from a device of a given type (e.g., WINDOWS, MAC, ANDROID, IOS, LINUX) within a historical window. Note that…
Description
Detects the first time a Google Workspace user is observed authenticating from a device of a given type (e.g., WINDOWS, MAC, ANDROID, IOS, LINUX) within a historical window. Note that "DEVICE_REGISTER_UNREGISTER_EVENT" events do not represent one-time physical device enrollments; the Google Reports API emits a fresh "google_workspace.device.id" on each event, and the same physical device may produce multiple events per day as sessions/sync renewals occur. The rule therefore surfaces a user authenticating from a new device type, not a new physical device. This is still high-fidelity because adversaries who compromise a Workspace identity via AiTM kits or stolen OAuth refresh tokens frequently relay sessions from device types that diverge from the legitimate user's baseline (e.g., a WINDOWS session appearing for a known macOS user, or simultaneous WINDOWS+MAC sessions within minutes), which is the canonical kit fingerprint. Because the underlying token retains access after password rotation, treat unexpected device-type divergence as a compromise indicator and revoke tokens, not just credentials.
Detection logic
Its licence does not clear it for publishing here
Sunturai publishes a detection's own text where the licence it arrived under has been reviewed and permits it, and Elastic License 2.0 has not. The query as its source wrote it, its canonical form and the hash that pins this revision are in the workspace record.
Detection requirements
- Platform
- ContainersESXiIaaSIdentity ProviderLinuxmacOSNetwork DevicesOffice SuiteSaaSWindows
The rule states no platform. This is derived from the 2 ATT&CK techniques it maps to.
- Log source category
- event_index
Known benign triggers
- A user legitimately enrolling a new personal or corporate device (new laptop, replacement phone, BYOD enrollment). Validate by confirming the device registration timing aligns with a known device refresh, IT hardware ticket, or onboarding event.
- Bulk device enrollment campaigns (e.g., MDM rollout, fleet refresh) where many users register the same new device type in a short window. Consider suppressing during planned rollouts.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| any.run/malware-trends/tycoon/ | 12 |
| developers.google.com/workspace/admin/reports/v1/appendix/activity/mobile | 2 |
| www.elastic.co/security-labs/google-workspace-attack-surface-part-one | 28 |
From the source
- At source
- Open at source
- Upstream identifier
- e0916edd-ea8c-49d2-882e-2cf6af161dd7
- Tagged by the source as
- Data Source: Google WorkspaceData Source: Google Workspace Device LogsDomain: CloudDomain: IdentityDomain: SaaSNoise: MediumPerformance: FastPlatform: Google WorkspaceResources: Investigation GuideRule Type: New TermsTactic: Initial AccessTactic: PersistenceUse Case: Identity and Access AuditUse Case: Threat Detection
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Sep 20, 2026
- Version
- 3