IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.

« Attempt to Deactivate an Okta Application Attempt to Deactivate an Okta Policy »

› › ›

Attempt to Deactivate an Okta Network Zone

edit

Attempt to Deactivate an Okta Network Zone

edit

Detects attempts to deactivate an Okta network zone. Okta network zones can be configured to limit or restrict access to a network based on IP addresses or geolocations. An adversary may attempt to modify, delete, or deactivate an Okta network zone in order to remove or weaken an organization’s security controls.

Rule type: query

Rule indices:

filebeat-*
logs-okta*

Severity: medium

Risk score: 47

Runs every: 5 minutes

Searches indices from: now-6m (Date Math format, see also Additional look-back time)

Maximum alerts per execution: 100

References:

Tags:

Elastic
Identity
Okta
Continuous Monitoring
SecOps
Network Security
Defense Evasion

Version: 6 (version history)

Added (Elastic Stack release): 7.11.0

Last modified (Elastic Stack release): 8.4.0

Rule authors: Elastic

Rule license: Elastic License v2

Potential false positives

edit

Consider adding exceptions to this rule to filter false positives if your organization’s Okta network zones are regularly modified.

Investigation guide

edit

Rule query

edit

event.dataset:okta.system and event.action:zone.deactivate

Threat mapping

edit

Framework: MITRE ATT&CK^TM

Tactic:
- Name: Defense Evasion
- ID: TA0005
- Reference URL: https://attack.mitre.org/tactics/TA0005/
Technique:
- Name: Impair Defenses
- ID: T1562
- Reference URL: https://attack.mitre.org/techniques/T1562/

Rule version history

edit

Version 6 (8.4.0 release)

Formatting only

Version 4 (7.13.0 release)

Formatting only

Version 3 (7.12.0 release)

Formatting only

Version 2 (7.11.2 release)

Formatting only

« Attempt to Deactivate an Okta Application Attempt to Deactivate an Okta Policy »