Attempt to Modify an Okta Network Zone

  1[metadata]
  2creation_date = "2020/05/21"
  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 modify 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 modified.
 20    """,
 21]
 22index = ["filebeat-*", "logs-okta*"]
 23language = "kuery"
 24license = "Elastic License v2"
 25name = "Attempt to Modify an Okta Network Zone"
 26note = """## Triage and analysis
 27
 28### Investigating Attempt to Modify an Okta Network Zone
 29
 30The modification of an Okta network zone is a critical event as it could potentially allow an adversary to gain unrestricted access to your network. This rule detects attempts to modify, delete, or deactivate an Okta network zone, which may suggest an attempt to remove or weaken an organization's security controls.
 31
 32#### Possible investigation steps:
 33
 34- Identify the actor related to the alert by reviewing `okta.actor.id`, `okta.actor.type`, `okta.actor.alternate_id`, or `okta.actor.display_name` fields in the alert.
 35- Review the `okta.client.user_agent.raw_user_agent` field to understand the device and software used by the actor.
 36- Examine the `okta.outcome.reason` field for additional context around the modification attempt.
 37- Check the `okta.outcome.result` field to confirm the network zone modification attempt.
 38- Check if there are multiple network zone modification attempts from the same actor or IP address (`okta.client.ip`).
 39- Check for successful logins immediately following the modification attempt.
 40- Verify whether the actor's activity aligns with typical behavior or if any unusual activity took place around the time of the modification attempt.
 41
 42### False positive analysis:
 43
 44- Check if there were issues with the Okta system at the time of the modification attempt. This could indicate a system error rather than a genuine threat activity.
 45- Check the geographical location (`okta.request.ip_chain.geographical_context`) and time of the modification attempt. If these match the actor's normal behavior, it might be a false positive.
 46- Verify the actor's administrative rights to ensure they are correctly configured.
 47
 48### Response and remediation:
 49
 50- If unauthorized modification is confirmed, initiate the incident response process.
 51- Immediately lock the affected actor account and require a password change.
 52- Consider resetting MFA tokens for the actor and require re-enrollment.
 53- Check if the compromised account was used to access or alter any sensitive data or systems.
 54- If a specific modification technique was used, ensure your systems are patched or configured to prevent such techniques.
 55- Assess the criticality of affected services and servers.
 56- Work with your IT team to minimize the impact on users and maintain business continuity.
 57- If multiple accounts are affected, consider a broader reset or audit of MFA tokens.
 58- Implement security best practices [outlined](https://www.okta.com/blog/2019/10/9-admin-best-practices-to-keep-your-org-secure/) by Okta.
 59- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 60
 61## Setup
 62
 63The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule."""
 64references = [
 65    "https://help.okta.com/en/prod/Content/Topics/Security/network/network-zones.htm",
 66    "https://developer.okta.com/docs/reference/api/system-log/",
 67    "https://developer.okta.com/docs/reference/api/event-types/",
 68    "https://www.elastic.co/security-labs/testing-okta-visibility-and-detection-dorothy",
 69    "https://www.elastic.co/security-labs/monitoring-okta-threats-with-elastic-security",
 70    "https://www.elastic.co/security-labs/starter-guide-to-understanding-okta",
 71]
 72risk_score = 47
 73rule_id = "e48236ca-b67a-4b4e-840c-fdc7782bc0c3"
 74severity = "medium"
 75tags = [
 76    "Use Case: Identity and Access Audit",
 77    "Data Source: Okta",
 78    "Use Case: Network Security Monitoring",
 79    "Tactic: Defense Evasion",
 80]
 81timestamp_override = "event.ingested"
 82type = "query"
 83
 84query = '''
 85event.dataset:okta.system and event.action:(zone.update or network_zone.rule.disabled or zone.remove_blacklist)
 86'''
 87
 88
 89[[rule.threat]]
 90framework = "MITRE ATT&CK"
 91[[rule.threat.technique]]
 92id = "T1562"
 93name = "Impair Defenses"
 94reference = "https://attack.mitre.org/techniques/T1562/"
 95[[rule.threat.technique.subtechnique]]
 96id = "T1562.007"
 97name = "Disable or Modify Cloud Firewall"
 98reference = "https://attack.mitre.org/techniques/T1562/007/"
 99
100
101
102[rule.threat.tactic]
103id = "TA0005"
104name = "Defense Evasion"
105reference = "https://attack.mitre.org/tactics/TA0005/"