Credential Access and Abuse

Description of Use Case

This is a use case of two distinct halves: dumping credentials from systems and abusing credentials to authenticate. The scoring reflects this perfectly. For dumping, endpoint memory and API monitoring are supreme. For abuse, detailed authentication logs (both on-prem and cloud) are the most critical. The highest scores went to specialized sensors purpose-built for detecting these specific activities.

Techniques Evaluated

  • T1078 Valid Accounts

  • T1110.003 Password Spraying

  • T1003.001 LSASS Memory

  • T1558.003 Pass-the-Ticket

  • T1550.003 Pass-the-Hash

  • T1098 Account Manipulation

  • T1555 Credentials from Password Stores

  • T1621 Multi-Factor Authentication Request Generation

  • T1528 Steal Application Access Token

  • T1552.001 Unsecured Credentials: Files

Top Scoring Log Sources

Log Source

Score

EDR: Credential Dumping / LSASS Access

26.5

Sysmon: EID 10: Process Access (LSASS)

26.5

Azure AD Identity Protection Alerts

26.4

EDR: API Calls (LSARetrievePrivateData, etc.)

25.8

EDR: Auth w/ NTLM/Pass-the-Hash

25.6

EDR: Browser Credential Store Access

24.8

Sysmon: EID 1: Process Create

24.2

Windows Security: EID 4738, 4732

23.8

Cloud Provider Logs (Anomalous Token Use)

23.1

Windows Security: EID 4688: Process Creation

22.7

Evaluation of Log Source Types

The data clearly splits into two top-tier categories: Memory/API Monitoring for the dumping phase and Detailed Authentication Logs for the abuse phase. Generic process logs are a solid secondary source, useful for seeing the tools being run, while generic file logs are a distant third.

Technology Comparison: Endpoint Security (EDR/Sysmon) & Cloud Identity Protection are co-dominant > Native Windows Authentication Logs

Scoring Data

The raw TC scores broken down by metric can be found here: Credential Access & Abuse