Windows privilege escalation via local kerberos relay over LDAP

This rule is part of a beta feature. To learn more, contact Support.
이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.

Goal

Detects potential privilege escalation attempts using local Kerberos relay attacks over LDAP.

Strategy

This detection monitors Windows event logs for successful logon events with specific characteristics of Kerberos relay attacks. The detection looks for Event ID 4624 (successful logon) with Kerberos authentication from the loopback address (127.0.0.1) targeting privileged accounts. It specifically filters for logon type 3 (network logon), Kerberos authentication, a non-zero IP port, and a target SID matching the local Administrator account pattern.

The technique exploits Windows authentication mechanisms to relay Kerberos tickets locally, potentially granting attackers elevated privileges. By monitoring for Kerberos authentication from the loopback address that targets administrator accounts, we can identify attempts to leverage this technique for privilege escalation.

Triage & Response

  • Identify the {{host}} where the suspicious Kerberos authentication occurred.
  • Review the logon events to determine the source process and user context that initiated the authentication.
  • Check for other suspicious activities surrounding the event, such as unusual process creations.
  • Look for evidence of LDAP-based attacks by examining LDAP query logs or network traffic.
  • Verify if there were any recent patches missing for Kerberos or LDAP services.
  • Reset credentials for the affected Administrator account if malicious activity is confirmed.
  • Check for persistence mechanisms that may have been established using the elevated privileges.
  • Implement LDAP signing and channel binding to prevent future relay attacks.
  • Review domain controller security settings and patch levels.