Potential Okta Password in AlternateID Field
Detects when a user has potentially entered their password into the username field, which will cause the password to be retained in log files.
Detection logic
Detection requirements
- Platform
- ContainersIaaSIdentity ProviderLinuxmacOSNetwork DevicesOffice SuiteSaaSWindows
The rule states no platform. This is derived from the ATT&CK technique it maps to.
- Log source product
- okta
- Log source service
- okta
Known benign triggers
- Unlikely
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 |
|---|---|
| developer.okta.com/docs/reference/api/system-log/ | 54from 2 sources |
| help.okta.com/en-us/Content/Topics/users-groups-profiles/usgp-create-character-restriction.htm | Only this detection cites it |
| www.mitiga.io/blog/how-okta-passwords-can-be-compromised-uncovering-a-risk-to-user-data | Only this detection cites it |
From the source
- At source
- Open at source
- Upstream identifier
- 91b76b84-8589-47aa-9605-c837583b82a9
- Tagged by the source as
- attack.credential-access
Licence
- Published under
- Detection Rule License 1.1Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Aug 26, 2026
- Version
- 1