T1550 Elastic Security · Elastic

Detect Use Alternate Authentication Material in Elastic Security

Adversaries may use alternate authentication material, such as password hashes, Kerberos tickets, and application access tokens, in order to move laterally within an environment and bypass normal system access controls. Authentication processes generally require a valid identity (e.g., username) along with one or more authentication factors (e.g., password, pin, physical smart card, token generator, etc.). Alternate authentication material is legitimately generated by systems after a user or application successfully authenticates by providing a valid identity and the required authentication factor(s). By stealing alternate authentication material, adversaries are able to bypass system access controls and authenticate to systems without knowing the plaintext password or any additional authentication factors. Sub-techniques include Application Access Token abuse (T1550.001), Pass the Hash (T1550.002), Pass the Ticket (T1550.003), and Web Session Cookie reuse (T1550.004).

MITRE ATT&CK

Tactic
Defense Evasion Lateral Movement
Technique
T1550 Use Alternate Authentication Material
Canonical reference
https://attack.mitre.org/techniques/T1550/

Elastic Detection Query

Elastic Security (Elastic)
eql
sequence by host.name with maxspan=5m
  [authentication where event.code in ("4624", "4769", "4776")
   and (
     (event.code == "4624" and winlog.event_data.LogonType == "9")
     or
     (event.code == "4624" and winlog.event_data.LogonType == "3"
      and winlog.event_data.AuthenticationPackageName : ("NTLM", "NTLMSSP")
      and source.ip != null
      and not source.ip in ("127.0.0.1", "::1", "-", "")
      and not winlog.event_data.TargetUserName : "*$")
     or
     (event.code == "4769"
      and winlog.event_data.TicketEncryptionType in ("0x17", "0x18")
      and winlog.event_data.Status == "0x0")
     or
     (event.code == "4776"
      and winlog.event_data.Status != null
      and not winlog.event_data.Status in ("0x0", "0", "-", ""))
   )
  ] by user.name
high severity high confidence

Detects Use of Alternate Authentication Material (T1550) by monitoring Windows Security Event logs for Pass-the-Hash (LogonType 9 NewCredentials artifact, NTLM network logons), Pass-the-Ticket (RC4-HMAC Kerberos downgrade indicating golden/silver ticket), and NTLM credential validation failures indicating hash override attempts. Uses ECS-normalised winlog fields from Winlogbeat or Elastic Agent.

Data Sources

Windows Security Event Log via Winlogbeat or Elastic AgentWindows Domain Controller event forwarding

Required Tables

logs-system.security*winlogbeat-*.ds-logs-system.security*

False Positives & Tuning

  • Scheduled tasks or services legitimately using NTLM authentication (LogonType 3) from authorised management workstations such as SCCM or Ansible
  • Legacy applications that only support RC4 Kerberos encryption (0x17) by design, especially older Windows Server 2003/2008-era services
  • NTLM validation failures (Event 4776) from stale cached credentials after password rotations, particularly during morning logon waves
Download portable Sigma rule (.yml)

Other platforms for T1550


Testing Methodology

Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Pass-the-Hash via Mimikatz sekurlsa::pth (Windows)

    Expected signal: Sysmon Event ID 1: Process Create for mimikatz.exe with parent process context. Security Event ID 4624 with LogonType=9, TargetUserName=testadmin, AuthenticationPackageName=NTLM on the local host — this fires immediately when the new process token is created. If the spawned cmd.exe then accesses a network resource, Security Event ID 4624 LogonType=3 with NTLM auth will appear on the target host. Sysmon Event ID 10 may appear if mimikatz accessed LSASS.

  2. Test 2Pass-the-Hash via Impacket wmiexec.py (Linux attacking Windows)

    Expected signal: On the target Windows host: Security Event ID 4624 with LogonType=3, AuthenticationPackageName=NTLM, IpAddress=<Linux attacker IP>, TargetUserName=testadmin. Security Event ID 4688 (or Sysmon Event ID 1) showing WmiPrvSE.exe spawning cmd.exe for the WMI command execution. No LogonType 9 event — this is a pure NTLM Type 3 network logon, demonstrating the PTH_NTLM detection branch.

  3. Test 3Pass-the-Ticket — Export and Inject Kerberos Ticket via Mimikatz

    Expected signal: Sysmon Event ID 1: Process Create for mimikatz.exe. After ticket injection, subsequent Kerberos service ticket requests from the session may appear in Security Event ID 4769 — if the injected ticket is RC4-encrypted (common with older tickets or those from tools using RC4), TicketEncryptionType=0x17 will appear. Security Event ID 4648 may appear when using the injected ticket to access network resources. klist output shows the injected service ticket.

  4. Test 4Overpass-the-Hash — Convert NTLM Hash to Kerberos TGT via Mimikatz /ptt

    Expected signal: Security Event ID 4624 LogonType=9 on the local host when the new credential token is created. Security Event ID 4768 (Kerberos TGT request) on the domain controller showing the AS-REQ using RC4-HMAC encryption (TicketEncryptionType=0x17) if the domain does not enforce AES-only. Security Event ID 4769 when the TGT is used to request service tickets for SYSVOL/CIFS access. The combination of LogonType 9 followed by Kerberos tickets from that session ties the PTH origin to subsequent Kerberos activity.

Unlock Pro Content

Get the full detection package for T1550 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections