MediumSigmaHQ Michaela Adams +1

Potential Access Token Abuse

Detects potential token impersonation and theft. Example, when using "DuplicateToken(Ex)" and "ImpersonateLoggedOnUser" with the "LOGON32_LOGON_NEW_CREDENTIALS flag".

Detection logic

Detection requirements

Platform: Windows
The rule states no platform. This is derived from the ATT&CK technique it maps to.
Log source product: windows
Log source service: security

Known benign triggers

Anti-Virus

References

Links the source published beside this detection. Reference is the link the source wrote, unmodified. Class is decided by this catalogue from the host and path, not stated by the source. Cited by counts published detections citing the same resource, including this one, and the sources beneath it count the repositories this catalogue ingests, which is not the same as independent research.
Reference	Class	Cited by
www.elastic.co/fr/blog/how-attackers-abuse-access-token-manipulation	Product documentation	Only this detection cites it
www.manageengine.com/log-management/cyber-security/access-token-manipulation.html	Unclassified	Only this detection cites it

Detection rules

Potential Access Token Abuse

Detection logic

Detection requirements

Known benign triggers

MITRE ATT&CK mappings

References

From the source

Licence

Authorship

Detection rules