-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[New Rule] okta_mfa_pw_reset #101
Comments
Hey @barnabys-drew, Thanks for this. Am I correct in understanding that your rule detects when an MFA factor is deactivated for an Okta user followed by their password being reset? Do you want to include Okta's Can you please open a pull request to stage your proposed rule and we can work on it together in there? Nice rule by the way. |
Hey @threat-punter! Good call out. That would be a better field to catch all of the MFA reset events, and would make this just as suspicious as the event field I submitted. The 30 minute time window / short time window is what I think makes this suspicious. Granted you could run into the issue where someone happens to get a new phone, and then a corporate pw reset policies takes in affect in that time window, but I think the likihood of both happening at the time would be very unlikely. Let me change this, and get a PR in order. Best, |
What suspicious scenario are you thinking of here? An attacker gains access to a user's Okta account, deactivates one of their MFA factors, and then performs a password reset for the account? Or are you thinking of a compromised Okta admin account carrying out these actions? |
Here is an example pull request if it helps at all: #97 |
When we made the rule, the scenario was presented to us as the latter, but depending on the configuration of Okta in the environment it could be both from my understanding. Should I map the mitre technique to something else or am reading into this more than I should be hah? The scenario I was thinking was a users account gets compromised, attacker then goes and changes user PW and MFA to prevent user access - leading into a total takeover |
I think your MITRE ATT&CK technique selection is fine, as you're talking about the act of an adversary disabling MFA. |
Description
This detection is looking for MFA and Password resets in a 30 minute window. This is suspicious given normal activity should only constitute a password reset OR MFA reset (ala a replacement phone)
Log Types
OKTA
YARA-L Rule
References
No response
Test Data
The text was updated successfully, but these errors were encountered: