https://feed.craftedsignal.io/tags/gworkspace/Trending threats, MITRE ATT&CK coverage, and detection metadata — refreshed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioFri, 26 Jan 2024 10:00:00 +0000https://feed.craftedsignal.io/briefs/2024-01-26-gworkspace-suspicious-login/Fri, 26 Jan 2024 10:00:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2024-01-26-gworkspace-suspicious-login/Detect Google Workspace login activity that Google has classified as suspicious, potentially indicating initial access, privilege escalation, defense evasion, or persistence attempts.This brief focuses on detecting suspicious login activity within Google Workspace environments, as flagged by Google’s internal risk assessment mechanisms. Google Workspace logs login events and classifies them based on various risk factors, including the use of less secure applications, programmatic logins, and other anomalies. This detection capability is crucial for identifying potential compromises, unauthorized access attempts, and malicious activities within the Google Workspace ecosystem. Analyzing these flagged events allows security teams to proactively respond to threats before they escalate, preventing data breaches and maintaining the integrity of sensitive information. This alert focuses on logins classified as ‘suspicious_login_less_secure_app’, ‘suspicious_login’, and ‘suspicious_programmatic_login’.

Attack Chain

1. Initial Access: An attacker gains initial access using compromised credentials or brute-force techniques targeting Google Workspace accounts.
2. Login Attempt: The attacker attempts to log in to a Google Workspace account using a less secure application (e.g., an older email client without modern authentication) or via programmatic login.
3. Suspicious Activity Detection: Google’s internal systems analyze the login attempt and flag it as suspicious based on various risk factors, such as unusual location, time of day, or login method.
4. Event Logging: Google Workspace logs the suspicious login event, including the reason for the classification (e.g., ‘suspicious_login_less_secure_app’).
5. Potential Privilege Escalation: Upon successful login, the attacker may attempt to escalate privileges within the Google Workspace environment to gain broader access.
6. Defense Evasion: The attacker might use techniques to evade detection, such as disabling security features or modifying audit logs.
7. Persistence: The attacker establishes persistence by creating new accounts, modifying existing ones, or installing malicious apps.
8. Data Exfiltration/Malicious Activity: The attacker uses the compromised account to exfiltrate sensitive data or perform other malicious activities, such as sending phishing emails.

Impact

Successful exploitation can lead to unauthorized access to sensitive data stored within Google Workspace, including emails, documents, and other files. This can result in data breaches, financial loss, and reputational damage. The number of affected users depends on the scope of the compromised account and the attacker’s ability to escalate privileges. Targeted sectors are broad, affecting any organization relying on Google Workspace for collaboration and data storage.

Recommendation

• Deploy the provided Sigma rule to your SIEM to detect suspicious login activity classified by Google Workspace (logsource: gcp, service: google_workspace.login).
• Investigate any alerts generated by the Sigma rule to determine the legitimacy of the login attempt and take appropriate action, such as resetting passwords or disabling compromised accounts.
• Enforce multi-factor authentication (MFA) for all Google Workspace accounts to mitigate the risk of credential compromise.
• Disable or restrict the use of less secure apps within Google Workspace to reduce the attack surface.
• Monitor Google Workspace audit logs for other suspicious activities, such as unusual file access or data exfiltration attempts.

]]>mediumadvisoryinitial-accessprivilege-escalationdefense-evasionpersistencegworkspacehttps://feed.craftedsignal.io/briefs/2024-01-gworkspace-email-forwarding/Wed, 03 Jan 2024 12:00:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2024-01-gworkspace-email-forwarding/Detects automatic email forwarding to external domains in Google Workspace, which may indicate data leakage or misuse by malicious insiders or compromised accounts.This brief focuses on detecting unauthorized email forwarding to external domains within Google Workspace environments. The primary concern is the potential for data exfiltration or misuse by malicious insiders or threat actors who have compromised user accounts. The activity is logged by Google Workspace and can be monitored using the Google Workspace Admin Reports API. The event name associated with this activity is email_forwarding_out_of_domain, which is generated when a user configures automatic email forwarding to an address outside the organization’s domain. Successful exploitation of this technique can lead to the leakage of sensitive information, intellectual property theft, or compliance violations.

Attack Chain

1. An attacker gains unauthorized access to a Google Workspace user account, potentially through phishing, credential stuffing, or other methods.
2. The attacker navigates to the Gmail settings for the compromised account.
3. The attacker configures automatic email forwarding to an external email address controlled by the attacker (e.g., a Gmail, Outlook, or ProtonMail address).
4. The attacker sets up filters to forward specific types of emails, such as those containing sensitive keywords or originating from key personnel.
5. Legitimate emails are received by the compromised user and automatically forwarded to the external address.
6. The attacker collects the forwarded emails, extracting sensitive data or using it for further malicious activities.
7. The attacker covers their tracks by deleting audit logs or modifying forwarding rules.

Impact

Successful exploitation of unauthorized email forwarding can lead to significant data breaches, intellectual property theft, and compliance violations. The impact can range from exposure of sensitive customer data to the loss of competitive advantage due to stolen trade secrets. Depending on the volume and nature of the data exfiltrated, organizations may face legal and regulatory penalties, as well as reputational damage.

Recommendation

• Deploy the provided Sigma rule to your SIEM to detect email_forwarding_out_of_domain events in Google Workspace logs (logsource: gcp, service: google_workspace.login).
• Investigate any alerts generated by the Sigma rule to determine the legitimacy of the email forwarding configuration.
• Implement multi-factor authentication (MFA) for all Google Workspace accounts to reduce the risk of account compromise.
• Regularly review and audit email forwarding rules to identify and remove any unauthorized configurations.
• Train users to recognize and report phishing attempts to prevent account compromise.

]]>mediumadvisorydata-leakagegworkspaceemail-forwarding