LoFP
/
t1003.001
t1003.001
Title
Tags
actual failures in lsass.exe that trigger a crash dump (unlikely)
t1003
t1003.001
windows
sigma
administrators can create memory dumps for debugging purposes, but memory dumps of the lsass process would be unusual.
t1003
t1003.001
windows
splunk
another service that uses a single -s command line switch
t1003
t1003.001
windows
sigma
another tool that uses command line flags similar to procdump
t1003
t1003.001
t1036
windows
sigma
another tool that uses the command line switches of xordump
t1003
t1003.001
t1036
windows
sigma
antivirus products
t1003
t1003.001
windows
sigma
av signature updates
t1003
t1003.001
t1003.002
t1003.004
t1003.006
windows
sigma
command lines that use the same flags
t1003
t1003.001
t1036
windows
sigma
dump64.exe in other folders than the excluded one
t1003
t1003.001
windows
sigma
false positives are expected in cases in which procdump just gets copied to a different directory without any renaming
t1003
t1003.001
t1036
windows
sigma
false positives may be present if an application is dumping processes, filter as needed. recommend reviewing createdump.exe usage across the fleet to better understand all usage and by what.
t1003.001
endpoint
splunk
false positives will occur based on grantedaccess 0x1010 and 0x1400, filter based on source image as needed or remove them. concern is cobalt strike usage of mimikatz will generate 0x1010 initially, but later be caught.
t1003
t1003.001
endpoint
splunk
false positives will occur based on grantedaccess and sourceuser, filter based on source image as needed. utilize this hunting analytic to tune out false positives in ttp or anomaly analytics.
t1003
t1003.001
endpoint
splunk
false positives will occur based on legitimate application requests, filter based on source image as needed.
t1003
t1003.001
endpoint
splunk
files with mimikatz in their filename
t1003
t1003.001
t1003.002
t1003.004
t1003.006
windows
sigma
google chrome googleupdate.exe
t1003
t1003.001
windows
sigma
legitimate administrator using credential dumping tool for password recovery
t1003
t1003.001
t1003.002
t1003.004
t1003.005
t1003.006
t1569
t1569.002
windows
sigma
legitimate administrator using tool for password recovery
t1003
t1003.001
t1003.002
t1003.003
t1003.004
t1003.005
windows
sigma
legitimate application that needs to do a full dump of their process
t1003
t1003.001
windows
sigma
legitimate certificate exports invoked by administrators or users (depends on processes in the environment - filter if unusable)
t1003
t1003.001
windows
sigma
legitimate mssql server actions
t1003
t1003.001
windows
sigma
legitimate software accessing lsass process for legitimate reason; update the whitelist with it
t1003
t1003.001
windows
sigma
legitimate software such as av and edr
t1003
t1003.001
windows
sigma
legitimate usage by software developers/testers
t1003
t1003.001
t1218
windows
sigma
legitimate usage of adplus for debugging purposes
t1003
t1003.001
windows
sigma
legitimate use of procdump by a developer or administrator
t1003
t1003.001
t1036
windows
sigma
naughty administrators
t1003
t1003.001
t1003.002
t1003.004
t1003.006
windows
sigma
other tools can access lsass for legitimate reasons and generate an event. in these cases, tweaking the search may help eliminate noise.
t1003
t1003.001
windows
splunk
other tools can import the same dlls. these tools should be part of a whitelist. false positives may be present with any process that authenticates or uses credentials, powershell included. filter based on parent process.
t1003
t1003.001
windows
splunk
other tools could load images into lsass for legitimate reason. but enterprise tools should always use signed dlls.
t1003.001
windows
splunk
rare case of troubleshooting by an administrator or support that has to be investigated regardless
t1003
t1003.001
windows
sigma
rare legitimate crashing of the lsass process
t1003
t1003.001
windows
sigma
rare legitimate dump of the process by the operating system due to a crash of lsass
t1003
t1003.001
windows
sigma
rare legitimate files with similar filename structure
t1003
t1003.001
windows
sigma
rare programs that contain the word dump in their name and access lsass
t1003
t1003.001
windows
sigma
some taskmgr.exe related activity
t1003
t1003.001
windows
sigma
the activity may be legitimate. other tools can access lsass for legitimate reasons, and it's possible this event could be generated in those cases. in these cases, false positives should be fairly obvious and you may need to tweak the search to eliminate noise.
t1003
t1003.001
windows
splunk
the activity may be legitimate. powershell is often used by administrators to perform various tasks, and it's possible this event could be generated in those cases. in these cases, false positives should be fairly obvious and you may need to tweak the search to eliminate noise.
t1003.001
windows
splunk
transferring sensitive files for legitimate administration work by legitimate administrator
t1003
t1003.001
t1003.002
t1003.003
zeek
windows
sigma
unknown cases in which werfault accesses lsass.exe
t1003
t1003.001
windows
sigma
unlikely
t1003
t1003.001
t1003.002
t1003.004
t1003.005
t1003.006
t1005
t1007
t1008
t1012
t1014
t1016
t1018
t1021
t1021.002
t1021.003
t1021.006
t1027
t1027.005
t1033
t1036
t1036.003
t1036.007
t1041
t1046
t1047
t1048
t1048.001
t1053
t1053.003
t1053.005
t1055
t1055.001
t1056
t1057
t1059
t1059.001
t1059.002
t1059.003
t1068
t1070
t1071
t1071.001
t1071.004
t1078
t1082
t1083
t1087
t1090
t1090.001
t1090.003
t1105
t1106
t1112
t1115
t1123
t1127
t1132
t1132.001
t1133
t1134
t1134.001
t1134.002
t1134.004
t1136
t1136.001
t1136.002
t1137
t1137.002
t1140
t1190
t1203
t1204
t1210
t1213
t1213.003
t1216
t1218
t1218.008
t1218.010
t1218.011
t1218.013
t1219
t1486
t1489
t1490
t1496
t1498
t1499
t1499.001
t1505
t1505.003
t1526
t1528
t1543
t1543.003
t1546
t1546.008
t1548
t1548.003
t1550
t1550.003
t1552
t1553
t1553.004
t1555
t1556
t1557
t1557.001
t1558
t1558.003
t1562
t1562.001
t1562.002
t1562.010
t1564
t1564.004
t1566
t1569
t1569.002
t1570
t1574
t1574.001
t1574.002
t1586
t1587
t1587.001
t1588
t1588.002
t1590
t1590.001
t1590.002
t1620
t1649
bitbucket
azure
m365
okta
macos
windows
linux
opencanary
sigma
unlikely, because no one should dump an lsass process memory
t1003
t1003.001
t1036
windows
sigma
valid user connecting using rdp
t1003
t1003.001
windows
sigma
very unlikely
t1003
t1003.001
windows
sigma
windows error reporting might produce similar behavior. in that case, check the pid associated with the \"-p\" parameter in the commandline.
t1003
t1003.001
windows
sigma