> 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/a-user-modified-an-okta-network-zone.md).
# A user modified an Okta network zone
### Synopsis
| Field | Value |
| -------------------- | ---------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 2 Days |
| Required Data | Okta Audit Log |
| Detection Modules | Identity Threat Module, SaaS Threat Detection |
| Detector Tags | Okta Audit Analytics |
| ATT\&CK Tactic | Defense Impairment (TA0112) |
| ATT\&CK Technique | Disable or Modify Tools (T1685), Disable or Modify System Firewall: Cloud Firewall (T1686.001) |
| Severity | Informational |
### Description
An Okta network zone was modified by a user.
### Attacker's Goals
An attacker may attempt to modify an Okta network zone to weaken an organization's security controls.
### Investigative actions
* Follow further actions done by the account.
* Verify that the configuration change was expected.
* Look for signs that the user account is compromised (e.g. abnormal logins, unusual activity).
* Investigate if any other network zones have been changed or removed.
### Variations
The user has made an unusual modification to the Okta Network zone
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Defense Impairment (TA0112) |
| ATT\&CK Technique | Disable or Modify Tools (T1685), Disable or Modify System Firewall: Cloud Firewall (T1686.001) |
| Severity | Medium |
**Description**
An atypical modification to the Okta Network zone has been performed by the user.
**Attacker's Goals**
An attacker may attempt to modify an Okta network zone to weaken an organization's security controls.
**Investigative actions**
* Follow further actions done by the account.
* Verify that the configuration change was expected.
* Look for signs that the user account is compromised (e.g. abnormal logins, unusual activity).
* Investigate if any other network zones have been changed or removed.
A user modified an Okta network zone with suspicious characteristics
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Defense Impairment (TA0112) |
| ATT\&CK Technique | Disable or Modify Tools (T1685), Disable or Modify System Firewall: Cloud Firewall (T1686.001) |
| Severity | Low |
**Description**
An Okta network zone was modified by a user with suspicious characteristics.
**Attacker's Goals**
An attacker may attempt to modify an Okta network zone to weaken an organization's security controls.
**Investigative actions**
* Follow further actions done by the account.
* Verify that the configuration change was expected.
* Look for signs that the user account is compromised (e.g. abnormal logins, unusual activity).
* Investigate if any other network zones have been changed or removed.
---
# 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/a-user-modified-an-okta-network-zone.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.