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 Policy Rule
edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.
Attempt to Deactivate an Okta Policy Rule
editDetects attempts to deactivate a rule within an Okta policy. An adversary may attempt to deactivate a rule within an Okta policy 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
- Identity and Access
Version: 6 (version history)
Added (Elastic Stack release): 7.9.0
Last modified (Elastic Stack release): 7.13.0
Rule authors: Elastic
Rule license: Elastic License v2
Potential false positives
editConsider adding exceptions to this rule to filter false positives if Okta MFA rules are regularly deactivated in your organization.
Investigation guide
edit## Config The Okta Fleet integration, Filebeat module, or similarly structured data is required to be compatible with this rule.
Rule query
editevent.dataset:okta.system and event.action:policy.rule.deactivate
Rule version history
edit- Version 6 (7.13.0 release)
-
- Formatting only
- Version 5 (7.12.0 release)
-
- Formatting only
- Version 4 (7.11.2 release)
-
- Formatting only
- Version 3 (7.11.0 release)
-
- Rule name changed from: Attempt to Deactivate Okta MFA Rule
- Version 2 (7.10.0 release)
-
-
Updated query, changed from:
event.module:okta and event.dataset:okta.system and event.action:policy.rule.deactivate
-