> 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/chrome-os-remote-access-policy-was-modified-in-google-workspace.md).

# Chrome OS Remote Access policy was modified in Google Workspace

### 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                              |
| Detector Tags        | Google Workspace                                    |
| ATT\&CK Tactic       | Defense Evasion (TA0005), Lateral Movement (TA0008) |
| ATT\&CK Technique    | Impair Defenses (T1562), Remote Services (T1021)    |
| Severity             | Informational                                       |

### Description

A user modified Chrome OS Remote Access configuration in Google Workspace.

### Attacker's Goals

Adversaries may modify remote access settings to maintain persistent access and bypass security controls.

### Investigative actions

* Verify if the configuration change was authorized.
* Investigate the source IP address and account involved for malicious activity.
* Follow further actions performed by the account and Remote Access connections performed.

### Variations

<details>

<summary>Suspicious Chrome OS Remote Access policy was modified in Google Workspace</summary>

**Synopsis**

| Field             | Value                                               |
| ----------------- | --------------------------------------------------- |
| ATT\&CK Tactic    | Defense Evasion (TA0005), Lateral Movement (TA0008) |
| ATT\&CK Technique | Impair Defenses (T1562), Remote Services (T1021)    |
| Severity          | Low                                                 |

**Description**

A user modified Chrome OS Remote Access configuration in Google Workspace.

* This is the first time the user performs this operation in the last 30 days.

**Attacker's Goals**

Adversaries may modify remote access settings to maintain persistent access and bypass security controls.

**Investigative actions**

* Verify if the configuration change was authorized.
* Investigate the source IP address and account involved for malicious activity.
* Follow further actions performed by the account and Remote Access connections performed.

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/chrome-os-remote-access-policy-was-modified-in-google-workspace.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
