Detectionhightest

PetitPotam Suspicious Kerberos TGT Request

Detect suspicious Kerberos TGT requests. Once an attacer obtains a computer certificate by abusing Active Directory Certificate Services in combination with PetitPotam, the next step would be to leverage the certificate for malicious purposes. One way of doing this is to request a Kerberos Ticket Granting Ticket using a tool like Rubeus. This request will generate a 4768 event with some unusual fields depending on the environment. This analytic will require tuning, we recommend filtering Account_Name to the Domain Controller computer accounts.

Convert In Phoenix Studio

Open this Sigma rule in the converter with the YAML preloaded and ready for backend selection.

Launch
Mauricio Velazco, Michael HaagCreated Thu Sep 02Updated Wed Oct 056a53d871-682d-40b6-83e0-b7c1a6c4e3a5windows
Log Source
Windowssecurity
ProductWindows← raw: windows
Servicesecurity← raw: security

Definition

The advanced audit policy setting "Account Logon > Kerberos Authentication Service" must be configured for Success/Failure

Detection Logic
Detection Logic3 selectors
detection:
    selection:
        EventID: 4768
        TargetUserName|endswith: '$'
        CertThumbprint|contains: '*'
    filter_local:
        IpAddress: '::1'
    filter_thumbprint:
        CertThumbprint: ''
    condition: selection and not 1 of filter_*
False Positives

False positives are possible if the environment is using certificates for authentication. We recommend filtering Account_Name to the Domain Controller computer accounts.

Rule Metadata
Rule ID
6a53d871-682d-40b6-83e0-b7c1a6c4e3a5
Status
test
Level
high
Type
Detection
Created
Thu Sep 02
Modified
Wed Oct 05
Path
rules/windows/builtin/security/win_security_petitpotam_susp_tgt_request.yml
Raw Tags
attack.credential-accessattack.t1187
View on GitHub