Gcp Failed Mfa
Description
Manually authenticated to the GCP portal and failed to pass MFA challenge by typing in a wrong code. Tenant specific details have been replaced in the dataset including tenant id, user names, ips, etc.
MITRE ATT&CK Techniques
| ID | Technique | Tactic |
|---|---|---|
| T1621 | Multi-Factor Authentication Request Generation | Credential Access |
Environment Details
| Field | Value |
|---|---|
| Environment | attack_range |
| Directory | gcp_failed_mfa |
| Test Date | 2022-10-14 |
Datasets
The following datasets were collected during this attack simulation:
Gws_login
- Path:
/datasets/attack_techniques/T1621/gcp_failed_mfa/gws_login.log - Sourcetype:
gws:reports:login - Source:
gws:reports:login
Related Detections
The following detections in our security content repository use this attack data for testing:
| Detection Name | Type | Source | MITRE ATT&CK | Analytic Story |
|---|---|---|---|---|
| GCP Authentication Failed During MFA Challenge | TTP |
Cloud | T1078.004, T1586.003, T1621 | GCP Account Takeover, Scattered Lapsus$ Hunters |
Usage Instructions
Replay with Splunk Attack Data
Replay attack data with replay.py from Splunk Attack Data.
1python replay.py --dataset /datasets/attack_techniques/T1621/gcp_failed_mfa/gws_login.log --index attack_data
Manual Import
- Download the dataset files from the paths listed above
- Configure your Splunk instance with the appropriate sourcetypes
- Import the logs using the Splunk Add Data wizard
Related Content
Find more detections and analytics for this attack technique in our security content repository.
Source: GitHub | Version: 1.0