Okta Login Without Push
Description
Identifies successful Okta logins not followed by Push Security authorization within 60 minutes. Push Security provides additional identity verification beyond Okta MFA as a defense-in-depth strategy. Missing Push Security verification suggests compromised credentials, session hijacking, or MFA bypass where attackers satisfied Okta authentication but cannot complete additional verification.
Query
Detection:
- Group:
- ID: Push
RuleID: Push.Security.Authorized.IdP.Login
Absence: true
- ID: Okta
RuleID: Okta.Login.Success
MatchCriteria:
field_name:
- GroupID: Push
Match: new.email
- GroupID: Okta
Match: actor.alternateId
Schedule:
RateMinutes: 1440
TimeoutMinutes: 10
LookbackWindowMinutes: 1800
Rule dependencies
⚠ Higher-order rule. It fires on other rules' alerts, not on raw events, so it cannot fire on its own. Deploy the rules it depends on too.
Depends on
-
correlates · Panther group
Okta.Login.Successwithin 1800m
Excludes
Push.Security.Authorized.IdP.Login— excluded, not a dependency
Analyst notes
- Query Okta System Log for all authentication events by actor.alternateId in the 90 minutes around the login to check if Push Security authentication occurred outside the 60-minute detection window, and review the source IP, geolocation, device, and MFA method used
- Query Push Security logs for any authentication attempts or failures by the same user in the 2 hours around the Okta login to determine if the user attempted but failed to complete Push Security verification
- Check Okta audit logs for all application access, permission changes, and administrative actions during the Okta session to identify suspicious activity that may indicate compromised credentials or session hijacking