> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/google-workspace-user-authentication-information-changed.md).
# Google Workspace user authentication information changed
### Synopsis
| Field | Value |
| -------------------- | ---------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 1 Day |
| Required Data | Google Workspace Audit Logs |
| Detection Modules | Identity Threat Module, SaaS Threat Detection, Email |
| Detector Tags | Google Workspace |
| ATT\&CK Tactic | Credential Access (TA0006), Persistence (TA0003) |
| ATT\&CK Technique | Modify Authentication Process: Multi-Factor Authentication (T1556.006), Account Manipulation (T1098) |
| Severity | Informational |
### Description
Google Workspace authentication information was changed for a user.
### Attacker's Goals
Adversaries may manipulate user authentication information to obtain Persistence or Bypass Multi-Factor Authentication (MFA) controls.
### Investigative actions
* Verify if the authentication information change was authorized.
* Follow further actions done by the user and IP address.
### Variations
Google Workspace administrative user authentication information changed
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006), Persistence (TA0003) |
| ATT\&CK Technique | Modify Authentication Process: Multi-Factor Authentication (T1556.006), Account Manipulation (T1098) |
| Severity | Low |
**Description**
Google Workspace authentication information was changed for a user.
**Attacker's Goals**
Adversaries may manipulate user authentication information to obtain Persistence or Bypass Multi-Factor Authentication (MFA) controls.
**Investigative actions**
* Verify if the authentication information change was authorized.
* Follow further actions done by the user and IP address.
Google Workspace user authentication information changed by another account
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006), Persistence (TA0003) |
| ATT\&CK Technique | Modify Authentication Process: Multi-Factor Authentication (T1556.006), Account Manipulation (T1098) |
| Severity | Low |
**Description**
Google Workspace authentication information was changed for a user.
**Attacker's Goals**
Adversaries may manipulate user authentication information to obtain Persistence or Bypass Multi-Factor Authentication (MFA) controls.
**Investigative actions**
* Verify if the authentication information change was authorized.
* Follow further actions done by the user and IP address.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/google-workspace-user-authentication-information-changed.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.