Attempt to Delete an Okta Network Zone

calendar Dec 9, 2024 · Use Case: Identity and Access Audit Data Source: Okta Use Case: Network Security Monitoring Tactic: Defense Evasion  ·
Share on: linkedin copy

Detects attempts to delete 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.

Elastic rule (View on GitHub)

 1[metadata]
 2creation_date = "2020/11/06"
 3integration = ["okta"]
 4maturity = "production"
 5updated_date = "2024/12/09"
 6min_stack_version = "8.15.0"
 7min_stack_comments = "Breaking change at 8.15.0 for the Okta Integration."
 8
 9[rule]
10author = ["Elastic"]
11description = """
12Detects attempts to delete an Okta network zone. Okta network zones can be configured to limit or restrict access to a
13network based on IP addresses or geolocations. An adversary may attempt to modify, delete, or deactivate an Okta network
14zone in order to remove or weaken an organization's security controls.
15"""
16false_positives = [
17    """
18    Consider adding exceptions to this rule to filter false positives if Oyour organization's Okta network zones are
19    regularly deleted.
20    """,
21]
22index = ["filebeat-*", "logs-okta*"]
23language = "kuery"
24license = "Elastic License v2"
25name = "Attempt to Delete an Okta Network Zone"
26note = """## Triage and analysis
27
28### Investigating Attempt to Delete an Okta Network Zone
29
30Okta network zones can be configured to limit or restrict access to a network based on IP addresses or geolocations. Deleting a network zone in Okta might remove or weaken the security controls of an organization, which might be an indicator of an adversary's attempt to evade defenses.
31
32#### Possible investigation steps:
33
34- Identify the actor associated with the alert by examining the `okta.actor.id`, `okta.actor.type`, `okta.actor.alternate_id`, or `okta.actor.display_name` fields.
35- Examine the `event.action` field to confirm the deletion of a network zone.
36- Investigate the `okta.target.id`, `okta.target.type`, `okta.target.alternate_id`, or `okta.target.display_name` fields to identify the network zone that was deleted.
37- Review the `event.time` field to understand when the event happened.
38- Check the actor's activities before and after the event to understand the context of this event.
39
40### False positive analysis:
41
42- Verify the `okta.client.user_agent.raw_user_agent` field to understand the device and software used by the actor. If these match the actor's typical behavior, it might be a false positive.
43- Check if the actor is a known administrator or a member of the IT team who might have a legitimate reason to delete a network zone.
44- Cross-verify the actor's actions with any known planned changes or maintenance activities.
45
46### Response and remediation:
47
48- If unauthorized access or actions are confirmed, immediately lock the affected actor's account and require a password change.
49- If a network zone was deleted without authorization, create a new network zone with similar settings as the deleted one.
50- Review and update the privileges of the actor who initiated the deletion.
51- Identify any gaps in the security policies and procedures and update them as necessary.
52- Implement additional monitoring and logging of Okta events to improve visibility of user actions.
53- Communicate and train the employees about the importance of following proper procedures for modifying network zone settings.
54
55## Setup
56
57The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule."""
58references = [
59    "https://help.okta.com/en/prod/Content/Topics/Security/network/network-zones.htm",
60    "https://developer.okta.com/docs/reference/api/system-log/",
61    "https://developer.okta.com/docs/reference/api/event-types/",
62    "https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy",
63    "https://www.elastic.co/security-labs/monitoring-okta-threats-with-elastic-security",
64    "https://www.elastic.co/security-labs/starter-guide-to-understanding-okta",
65]
66risk_score = 47
67rule_id = "c749e367-a069-4a73-b1f2-43a3798153ad"
68severity = "medium"
69tags = [
70    "Use Case: Identity and Access Audit",
71    "Data Source: Okta",
72    "Use Case: Network Security Monitoring",
73    "Tactic: Defense Evasion",
74]
75timestamp_override = "event.ingested"
76type = "query"
77
78query = '''
79event.dataset:okta.system and event.action:zone.delete
80'''
81
82
83[[rule.threat]]
84framework = "MITRE ATT&CK"
85[[rule.threat.technique]]
86id = "T1562"
87name = "Impair Defenses"
88reference = "https://attack.mitre.org/techniques/T1562/"
89[[rule.threat.technique.subtechnique]]
90id = "T1562.007"
91name = "Disable or Modify Cloud Firewall"
92reference = "https://attack.mitre.org/techniques/T1562/007/"
93
94
95
96[rule.threat.tactic]
97id = "TA0005"
98name = "Defense Evasion"
99reference = "https://attack.mitre.org/tactics/TA0005/"

Triage and analysis

Investigating Attempt to Delete an Okta Network Zone

Okta network zones can be configured to limit or restrict access to a network based on IP addresses or geolocations. Deleting a network zone in Okta might remove or weaken the security controls of an organization, which might be an indicator of an adversary's attempt to evade defenses.

Possible investigation steps:

  • Identify the actor associated with the alert by examining the okta.actor.id, okta.actor.type, okta.actor.alternate_id, or okta.actor.display_name fields.
  • Examine the event.action field to confirm the deletion of a network zone.
  • Investigate the okta.target.id, okta.target.type, okta.target.alternate_id, or okta.target.display_name fields to identify the network zone that was deleted.
  • Review the event.time field to understand when the event happened.
  • Check the actor's activities before and after the event to understand the context of this event.

False positive analysis:

  • Verify the okta.client.user_agent.raw_user_agent field to understand the device and software used by the actor. If these match the actor's typical behavior, it might be a false positive.
  • Check if the actor is a known administrator or a member of the IT team who might have a legitimate reason to delete a network zone.
  • Cross-verify the actor's actions with any known planned changes or maintenance activities.

Response and remediation:

  • If unauthorized access or actions are confirmed, immediately lock the affected actor's account and require a password change.
  • If a network zone was deleted without authorization, create a new network zone with similar settings as the deleted one.
  • Review and update the privileges of the actor who initiated the deletion.
  • Identify any gaps in the security policies and procedures and update them as necessary.
  • Implement additional monitoring and logging of Okta events to improve visibility of user actions.
  • Communicate and train the employees about the importance of following proper procedures for modifying network zone settings.

Setup

The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.

References

Related rules

to-top