Windows: Suspicious Kerberos Ticket Requests from PowerShell Using KerberosRequestorSecurityToken

Flags PowerShell command lines that reference KerberosRequestorSecurityToken and .GetRequest() for suspicious Kerberos ticket requests.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Swachchhanda Shrawan Poudel (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2025-11-18
Updated
2026-07-30

ATT&CK techniques

Cred Access
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule identifies process executions from PowerShell (powershell.exe/pwsh.exe) that call System.IdentityModel.Tokens.KerberosRequestorSecurityToken and invoke .GetRequest(). Such scripted Kerberos ticket request activity can indicate Kerberos ticket abuse, including techniques aimed at service ticket extraction. The detection relies on process creation telemetry and command-line content indicating the .NET KerberosRequestorSecurityToken request pattern.

Related detections9 linkedT1558.003 — drag to rearrange
Malicious Kerberos Ticket File Creation Indicating Credential Theft (via file_event)
Suspicious Kerberoasting via setspn Service Principal Query
Masquerading Kerberos Ticket Abuse via Rubeus (via process_creation)
Possible Targeted Kerberoasting via servicePrincipalName Modification
Suspicious SQL Service Principal Name Enumeration via Setspn
Windows Process Creation: RemoteKrbRelay Kerberos Relay Tool Execution
Windows Kerberos KDC Key Distribution Failure: No Suitable Encryption Key or Unsupported EType
Rubeus HackTool Execution via PowerShell ScriptBlock Flags (Windows)
Windows Process Creation: KrbRelay.exe Kerberos Relay Tool Execution
Windows: Suspicious Kerberos Ticket Requests from PowerShell Using KerberosRequestorSecurityToken
Pivot detection · T1558.003 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.