Okta Multi-Factor Authentication Disabled
The following analytic identifies an attempt to disable multi-factor authentication (MFA) for an Okta user. It leverages OktaIM2 logs to detect when the 'user.mfa.factor.deactivate' command is executed. This activity…
Description
The following analytic identifies an attempt to disable multi-factor authentication (MFA) for an Okta user. It leverages OktaIM2 logs to detect when the 'user.mfa.factor.deactivate' command is executed. This activity is significant because disabling MFA can allow an adversary to maintain persistence within the environment using a compromised valid account. If confirmed malicious, this action could enable attackers to bypass additional security layers, potentially leading to unauthorized access to sensitive information and prolonged undetected presence in the network.
Detection logic
Detection requirements
- Platform
- IaaSIdentity ProviderLinuxmacOSOffice SuiteSaaSWindows
The rule states no platform. This is derived from the ATT&CK technique it maps to.
- Log source category
- okta
Known benign triggers
- Legitimate use case may require for users to disable MFA. Filter lightly and monitor for any unusual activity.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| attack.mitre.org/techniques/T1556/ | 7 |
| splunkbase.splunk.com/app/6553 | 8 |
From the source
- At source
- Open at source
- Upstream identifier
- 7c0348ce-bdf9-45f6-8a57-c18b5976f00a
- Tagged by the source as
- Okta Account TakeoverScattered Lapsus$ HuntersOkta TenantapplicationSplunk CloudSplunk EnterpriseSplunk Enterprise Securityidentity
Licence
- Published under
- Apache License 2.0Read the licence
- Attribution
- Required
- Obtained under
- Apache-2.0Read the origin licence
Authorship
- Written by
- Published
- Aug 26, 2026
- Version
- 1