Attempt to Deactivate Okta Policy

edit

An adversary may attempt to deactivate an Okta policy in order to weaken an organization’s security controls. For example, an adversary may attempt to deactivate an Okta multi-factor authentication (MFA) policy in order to weaken the authentication requirements for user accounts.

Rule type: query

Rule indices:

  • filebeat-*
  • logs-okta*

Severity: low

Risk score: 21

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
  • Monitoring

Version: 2 (version history)

Added (Elastic Stack release): 7.9.0

Last modified (Elastic Stack release): 7.10.0

Rule authors: Elastic

Rule license: Elastic License

Potential false positives

edit

If the behavior of deactivating Okta policies is expected, consider adding exceptions to this rule to filter false positives.

Investigation guide

edit

The Okta Filebeat module must be enabled to use this rule.

Rule query

edit
event.dataset:okta.system and event.action:policy.lifecycle.deactivate

Threat mapping

edit

Framework: MITRE ATT&CKTM

Rule version history

edit
Version 2 (7.10.0 release)
  • Updated query, changed from:

    event.module:okta and event.dataset:okta.system and
    event.action:policy.lifecycle.deactivate