HostThreatHunting

Find Policy Changes on System T1484.001

1. Use the command Get-GPResultantSetOfPolicy -ReportType HTML -Path (Join-Path -Path (Get-Location).Path -ChildPath "RSOPReport.html") within Powershell.

Identify Environemnt Variables T1543

1. Use the set command in the windows command line. Focus on the CompSpec, Path, PSModulePath, Public, and Temp folder locations.

Identify User Hotspots Usage [No TTP]

1. Look witin SOFTWARE hive for Network List Profiles.

Find Hidden Files in FAT32 T1564.001

1. Look at byte 12 of the SFN Entry. The file is hidden if the value is 0x02.

2. Use Autopsy as a secondary tool.

View Docker Image Updates in Registry T1612

1. Search HTTP logs for the "PATCH" method.

Identify Docker Logs [No Specific TTP]

1. Run docker logs [container name] in the command line.

2. Execute docker exec [container name] ls -la /var/log in the command line.

Identify Audit Policy Changes T1562.002

1. Search Windows Security logs for Event ID 4719 and the specific subcategory.

Identify Firewall Tampering 1562.004

1. Look for wierd rule names that were added within the Windows FW event logs.

2. Focus on the "Microsoft-Windows-Windows Firewall With Advanced Security/Firewall" Channel with Event ID 2004.

Identify Web Scanning T1595.003

1. Look through logs within /var/log to find GET requests within log data.

Discover System Time Change T1124

1. On a linux system, view the syslog within /var/log/syslog and look for systemd-timedated for changes in time.

AS-REP Roasting Detection T1558.004

1. Use eventvwr.msc with Windows Security Event logs event ID 4768 with ticket encryption type of 0x17 and ticket options of 0x40800010.

Beaconing Activity T1071 T1059 T1001.003T1573 T1029 T1021 T1090 T1095

1. Identify Sysmon logs with Event ID 3.

Identify TimeStomping T1070.006

1. Identify Sysmon logs with Event ID 2.

2. Look for last access date before the modified date within SFN or LFN in FAT32.

3. Use the timeline feature within Autopsy to find time anomalies.

4. Use the stat command on to review modify, change, access, and birth dates and times.

Identify Kerberaost Attack T1558.003

1. View Windows Security Event logs with Event ID 4769 as well as encryption type 0x17 with uncommon usernames.

2. Look for files with names like "Rubeus" or "PowerView" within PowerShell logs event ID 4104.

3. Use eventvwr.msc with Windows Security Event logs event ID 4768 with ticket encryption type of 0x17 and ticket options of 0x40800010.

Malware Language [No TTPs]

1. Use Detect It Easy to find the language which the malware is written.

Malware Packing T1027.002

1. Use Detect It Easy to find the entropy of each section of the malware.

Malware Signing T1553.002

1. Use SigCheck to determine if the malware is signed.

2. Use Detect It Easy to help determine if malware is signed.

User Account Lockouts T1110

1. Use Live-Forensicator Tool with .\Forensicator -EVTX EVTX, and search for UserLockOut Activites within the evtx.html, can be found here.

2. Use eventvwr.msc with Windows Security Event logs event ID 4740.

3. Use eventvwr.msc with Windows Security Event logs event ID 4767.

Examine PDFs T1024.002

1. Use pdfid.py to summarize risky aspects of the file.

2. Use pdf-parser.py to search for objects within PDFs.

3. Use peepdf.py to summarize aspects of file and search for objects.

4. Use swf_mastah.py to extract Flash from PDF files.

5. Use origami-pdf to analyze PDFs.

De-obfuscate Code T1027.010

1. Beautify the script using Notepad++ and JSTool plugins such as JSMin and JSFormat.

2. Use SpiderMonkey to analyze JavaScript and VBScript.

3. Use CScript to analyze JavaScript and VBScript.

4. Use box-js within the command line to analyze JavaScript.

5. Use base64dump.py to decode Base64 strings.

View Embedded Strings T1024

1. Run pestr on a linux operating system to view strings on an executable.

2. Run strings -a on a linux OS to view strings on an executable.

3. Run strings --encoding=l on a lnux OS to view strings of an executable.

4. Place the file in PeStudio.

Identify WMI Activity T1047

1. Focus on ShimCache, AmCache.hve, and Prefetch with wmic.exe on source machine.

2. Focus on ShimCache, AmCache.hve, and Prefetch with wmic.exe, scrons.exe, mofcomp.exe, or wmiprvse.exe on target machine.

3. Use eventvwr.msc with Microsoft-Windows-WMI-Activity%4Operational for event ID 5857, 5860, and 5861 for wmiprvse execution.

4. Use eventvwr.msc with Windows Security Event logs event ID 4688.

5. Use eventvwr.msc with Windows Security Event logs event ID 4648.

6. Use eventvwr.msc with Sysmon Event logs and Event ID 20.

7. Look for MOF files within C:\Windows\System32\wbem\AutoRecover or C:\Windows\System32\wbem\mofcomp.exe.

8. Look for MOF files in registry HKLM\SOFTWARE\Microsoft\Wbem\CIMON.

Examine RDP Connections T1563.002T1210

1. Use eventvwr.msc with Windows Security Event logs event ID 4648.

2. Use eventvwr.msc with Microsoft-Windows-TerminalServices-RDPClient%4Operational for eventid 1024 and 1102 with destination hostname or IP address.

3. View registry NTUSER\Software\Microsoft\Terminal Server Client\Servers to find RDP connections per user.

4. Focus on ShimCache and AmCache.hve with mstsc.exe for RDP source machine.

5. Focus on prefetch with mstsc.exe,rdpclip.exe or tstheme.exewithin the name of the file.

6. View jumplists at C:\Users\[username]\AppData\Roaming\Microsoft\Windows\Recent\AutomaticDestinations\ for RDP destinations and times.

7. Use eventvwr.msc with Windows Security Event logs event ID 4624 for logon type 10.

8. Use eventvwr.msc with Windows Security Event logs event ID 4778/4779 for logon source and username.

9. Use eventvwr.msc with Microsoft-Windows-RemoteDesktopServices-RdpCoreTS%4Operational for eventid 131 and 98 for connection attempt IPs and successful connections.

10. Use eventvwr.msc with Microsoft-Windows-TerminalServices-RDPClient%4Operational for eventid 1149 with source IP and Logon username.

11. Use eventvwr.msc with Microsoft-Windows-TerminalServices-LocalSessionManager%4Operational for eventid 21, 22, 25, and 41 for source IP or logon username.

12. Focus on ShimCache and AmCache.hve with rdpclip.exe or tstheme.exe for RDP destination machine.

13. Use Live-Forensicator Tool with .\Forensicator -EVTX EVTX, and search for RDP Logon Activities with an html file, can be found here.

14. Use Chainsaw and an EVTX dump to search for failed logons with ./chainsaw hunt [evtx] -r ./rules/.

15. Run the following command in PowerShell on the system: Get-NetTCPConnection | select Local*, Remote*, State, OwningProcess,` @{n="ProcName";e={(Get-Process -Id $_.OwningProcess).ProcessName}},` @{n="ProcPath";e={(Get-Process -Id $_.OwningProcess).Path}} | sort State | ft -Auto .

View Change to Logging T1070.001

1. Use eventvwr.msc with Windows System Event logs 4719.

2. Look for commands like Remove-EventLog -LogName Security, Remove-EventLog -LogName Application , or Remove-EventLog -LogName System.

3. Use TimelineExplorer to find suspicious powershell activity using input csv information.

4. Search Windows Security logs for Event ID 4719 and the specific subcategory.

View Account Changes T1098 T1070

1. Use eventvwr.msc with Windows Security Event logs event id 4724 to view password reset.

2. Use eventvwr.msc with Windows Security Event logs event id 4735 to view local group changes.

3. Use eventvwr.msc with Windows Security Event logs event id 4738 to view local password change.

4. Use eventvwr.msc with Windows Security Event logs event id 4688 to view process creation logs with the use of net.exe or net1.exe to change passwords.

5. Use wevutil.exe and search for appropriate Windows Security Eveents logs.

   • Command to use is wevutil.exe qe Security /q:"*[System[EventID=4725 or EventID=4722 or EventID=4723 or EventID=4724 or EventID=4726 or EventID=4767)]]

6. Use eventvwr.msc with Windows Security Event logs event id 4726 to remove a user account.

7. Look for commands like Remove-EventLog -LogName Security, Remove-EventLog -LogName Application, or Remove-EventLog -LogName System.

8. Look for account creation on the command line with net.exe or net1.exe with parent process cmd.exe.

9. Use Live-Forensicator Tool with .\Forensicator -EVTX EVTX, and search for User Creation Activity within the html file, can be found here.

10. Use TimelineExplorer to find suspicious powershell activity using input csv information.

Examine Macros in Word Documents T1137.001 T1564.007 T1024.002

1. Use wmd.pl to extract metadata.

2. Use olevba.py to examine metadata.

3. Unzip the docx to deflate media and other sections of the document.

4. Use oledump.py to view the macros within a document.

5. View macros within p-code called pcodedmp.py.

Examine RTF Documents T1024.002

1. Use rtfdump.py to examine the file.

Determine Persistence at Startup in Registry T1547.001

1. View registry at HKLM\Software\Microsoft\Windows\CurrentVersion\Runonce.

2. View registry at HKLM\Software\Microsoft\Windows\CurrentVersion\policies\Explorer\Run.

3. View registry at HKLM\Software\Microsoft\Windows\CurrentVersion\Run.

4. View registry at HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows\Run.

5. View registry at HKCU\Software\Microsoft\Windows\CurrentVersion\Run.

6. View registry at HKCU\Software\Microsoft\Windows\CurrentVersion\Runonce.

7. Use Systinternals autorunsc tool.

8. Use PowerShell with the following command: Get-CimInstance Win32_StartupCommand | Select-Object Name, command, Location, User | fl.

9. Use Powershell with the following command: $winlogonPath = "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon"; "Userinit: $((Get-ItemProperty -Path $winlogonPath -Name 'Userinit').Userinit)"; "Shell: $((Get-ItemProperty -Path $winlogonPath -Name 'Shell').Shell)".

Detect External Devices T1025

1. Track USBs in machine at SYSTEM\CurrentControlSet\Enum\USBSTOR or SYSTEM\CurrentControlSet\Enum\USB.

2. Create timeline for USB connections with C:\Windows\inf\setupapi.dev.log or SYSTEM\CurrentControlSet\Enum\USBSTOR\Ven_Prod_Version\USB.

3. Find the user with the USB device at SYSTEM\MountedDevices with a GUID or NTUSER.DAT\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2.

4. Find the USB volume serial number at SOFTWARE\Microsoft\WindowsNT\CurrentVersion\ENDMgmt.

5. Find the drive letter for the USB device SOFTWARE\Microsoft\Windows Portable Devices\Devices or SYSTEM\MountedDevices.

6. Device mounting creates a link file at C:\%USERPROFILE%\AppData\Roaming\Microsoft\Windows\Recent or C:\%USERPROFILE%\AppData\Roaming\Microsoft\Office\Recent.

7. Use eventvwr.msc with Windows Security Event logs 20001.

8. View USB connection time at HKLM\Software\Microsoft\Windows NT\CurrentVersion\EMDMgmt.

9. Determine UNIX timestamps for initial insertion, last insertion, etc for USB devices within the arguments secction of SYSTEM\CurrentControlSet\Enum\USBSTOR.

Identify TimeZone [No TTP]

1. Look at SYSTEM\CurrentControlSet\Control\TimeZoneInformation within the System Hive.

Explore File Deletion T1485 T1070.004 T1070.009

1. Focus on WordWheelQuery from the START menu located at NTUSER.DAT\Software\Microsoft\Windows\CurrentVersion\Explorer\WordWheelQuery.

2. View the Last Visited MRU at NTUSER.dat\Software\Microsoft\Windows\CurrentVersion\Explorer\Comdlg32\LastVisited[PID]MRU.

3. Focus on the thumbnails/thumbscache that are not deleted after file deletion at C:\%USERPROFILE%\AppData\Local\Microsoft\Windows\Explorer.

4. Examine the recycle bin at C:\$Recycle.bin.

5. View files access from IE at %USERPROFILE%\AppData\Local\Microsoft\Windows\WebCache\WebCacheV*.dat.

6. Use Rifiuti2 to exmaine the Recycle Bin.

7. Use Autopsy as a secondary tool and look within the Recycle Bin of a disk image.

8. For FAT32, look at SFN entries beginning with 0xE5 of a disk image.

9. Look at MFT using MFTECmd and see if the file is listed as "In Use".

10. Use MFTECmd with the USNJournal ($J) to find the specific file activity.

11. Use MFTECmd with the $I30 file to find the specific file activity.

Examine Executables T1547.004 T1059.006 T1559.001 T1027.004 T1027.004 T1055.002

1. View the registry at NTUSER.DAT\Software\Microsoft\Windows\CurrentVersion\Explorer\UserAssist\{GUID}\Count where the GUID is specific for the OS.

2. View the Windows Background Activity Monitor at SYSTEM\CurrentControlSet\Services\bam\UserSettings\{SID} or SYSTEM\CurrentControlSet\Services\dam\UserSettings\{SID}

3. View the Last Visited MRU at NTUSER.dat\Software\Microsoft\Windows\CurrentVersion\Explorer\Comdlg32\LastVisited[PID]MRU.

4. View the RunMRU at NTUser.dat\Software\Microsoft\Windows\CurrentVersion\Explorer\RunMRU for Start-> Run execution.

5. View the RecentApps key for program execution at NTUser.dat\Software\Microsoft\Windows\Current Version\Search\RecentApps where each GUID is a specific application.

6. View the AppCompatCache to determine time of execution and name of executable at SYSTEM\CurrentControlSet\Control\SessionManager\AppCompatCache.

7. Utilize jump lists at C:\%UserProfile%\AppData\Roaming\Microsoft\Windows\Recent\AutomaticDestinations to view user access of executables.

8. Use PECmd.exe (from Eric Zimmerman here with Command line.

   • Command to use PECmd.exe -f [prefetch_file]

9. View prefetch files at C:\Windows\Prefetch for program execution.

10. View the Amcache or recentfile cache for data storage during process creation at C:\Windows\AppCompat\Programs\Amcache.hve.

11. Run pestr on a linux operating system to view strings on an executable.

12. Run strings -a on a linux OS to view strings on an executable.

13. Run strings --encoding=l on a lnux OS to view strings of an executable.

14. Place the file in PeStudio.

15. Run peframe on a linux machine to view imports and other file properties.

16. Place the file in DetectItEasy.

17. Place the file in ExeInfoPE.

18. Analyze the file with signsrch.

19. Analyze the file with pescan.

20. Analyze the file with MASTIFF.

21. Analyze the file with Exiftool.

22. Analyze the file with TrID.

23. Analyze the file with Viper.

24. Analyze the file with PortEx.

25. Examine the execution within ProcDot.

26. Examine prefetch files with w10pf_parse.py.

27. Examine Sysmon Logs with Event ID 1.

28. Examine Windows Defender Logs with Event ID 1117 within the Channel Microsoft-Windows-Windows Defender/Operational.

29. Use regripper to examine the NTUSER.dat file for a specific user looking at UserAssist.

30. Run the following command in PowerShell on the system: Get-NetTCPConnection | select Local*, Remote*, State, OwningProcess,` @{n="ProcName";e={(Get-Process -Id $_.OwningProcess).ProcessName}},` @{n="ProcPath";e={(Get-Process -Id $_.OwningProcess).Path}} | sort State | ft -Auto .

31. Look at processes within Powershell with Get-WmiObject -Class Win32_Process | ForEach-Object {$owner = $_.GetOwner(); [PSCustomObject]@{Name=$_.Name; PID=$_.ProcessId; P_PID=$_.ParentProcessId; User="$($owner.User)"; CommandLine=if ($_.CommandLine.Length -le 60) { $_.CommandLine } else { $_.CommandLine.Substring(0, 60) + "..." }; Path=$_.Path}} | ft -AutoSize

Examine the Shimcache/Amcache

1. View the AppCompatCache to determine time of execution and name of executable at SYSTEM\CurrentControlSet\Control\SessionManager\AppCompatCache.

2. View the Amcache or recentfile cache for data storage during process creation at C:\Windows\AppCompat\Programs\Amcache.hve.

3. Focus on ShimCache and AmCache.hve with mstsc.exe for RDP source connections.

4. Focus on ShimCache and AmCache.hve with rdpclip.exe or tstheme.exe for RDP destination machine.

Examine Application Crashes T1499.004

1. Use eventvwr.msc with Windows Security Event logs 1001.

Examine SMB Shares/Sessions T1021

1. Use Get-WmiObject within Powershell.

   • Command to use is Get-WmiObject -Class win32_share

2. Use Get-SMBSession within Powershell.

   • Command to use is Get-SmbSession | Select-Object ClientComputerName,Dialect,SecondsExist,SecondsIdle

3. Use Get-SMBMapping within Powershell.

4. Examine remotely mapped shares at NTUSER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2 on source machine.

5. Look for ShimCache, Amcache, BAM, DAM, or Prefetch with net.exe or net1.exe on source machine.

6. Use eventvwr.msc with Windows Security Event logs event ID 4648 on source machine.

7. Use eventvwr.msc with Windows Security Event logs event ID 4624, 4672, 4776, 4768, 4769, 5140, and 5145 on destination machine.

8. Use Powershell with the command: Get-CimInstance -Class Win32_Share.

Examine Services T1569 T1569.002

1. Use Get-Service within Powershell.

2. Use Get-CimInstance -ClassName Win32_Service | Format-List Name, Caption, Description,PathName within Powershell.

3. Use Get-WinEvent within Powershell looking for Event ID 7045 in the Security Log.

   • Command to use is Get-WinEvent -LogName System | Where-Object -Property ID -EQ 7045 | Format-List -Property TimeCreated,Message.

4. Use volatility with a forensic image.

   • Version 3 uses windows.svcscan.SvcScan

5. Use DeepBlueCLI (from here) and Powershell.

6. Use eventvwr.msc with Windows Security Event logs 4697.

7. Use eventvwr.msc with Windows System Event logs 7034, 7035, 7036, 7040 in that order.

8. Use eventvwr.msc with Windows System Event logs 6045 for service installation on a server.

9. Use sc.exe to query services.

   • Command to use sc.exe query state= all

10. Use wevutil.exe and search for appropriate Windows Security Events logs.

    • Command to use is wevutil.exe qe Security /q:"*[System[(EventID=7045)]]

11. Use eventvwr.msc with Windows System Event logs 7045.

12. View registry for new service creations at SYSTEM\CurrentControlSet\Services\[servicename].

13. Within Powershell run the command: Get-CimInstance -ClassName Win32_Service | Where-Object { $_.State -eq "Running" } | Select-Object Name, DisplayName, State, StartMode, PathName, ProcessId | ft -AutoSize.

14. Within Powershell, look for non-running services with Get-CimInstance -ClassName Win32_Service | Where-Object { $_.State -ne "Running" } | Select-Object @{Name='Name'; Expression={if ($_.Name.Length -gt 22) { "$($_.Name.Substring(0,19))..." } else { $_.Name }}}, @{Name='DisplayName'; Expression={if ($_.DisplayName.Length -gt 45) { "$($_.DisplayName.Substring(0,42))..." } else { $_.DisplayName }}}, State, StartMode, PathName, ProcessId | Format-Table -AutoSize

Analyze OneNote Files T1137

1. Use OneNoteAnalyzer found here

Unsigned Files in C:\Windows\System32 T1587.002

1. Use sigcheck within Sysinternals.

   • sigcheck -u -e C:\Windows\System32 -accepteula

Alternate Data Streams T1564.004

1. Use streams within Sysinternals

   • streams C:\Users\Administrator\Desktop\maliciousfile.txt -accepteula

2. Use more to view the ADS files on the command line.

   • more < C:\Users\Administrator\Desktop\maliciousfile.txt:ads.txt

3. Use Get-WinEvent with Sysmon Event Logs.

   • Command to use is Get-WinEvent -Path <Path to Log> -FilterXPath '*/System/EventID=8'

4. Use eventvwr.msc with Sysmon Event logs and Event ID 8.

5. With Sysmon logs, look for event ID 15.

6. Use MFTECmd with the USNJournal ($J) to find the specific file activity.

7. Use MFTECmd with the $I30 file to find the specific file activity.

Autoruns T1547

1. Use autoruns within Sysinternals

   • autoruns

2. Use osquery on the Windows Command line.

   • Command to use in interactive mode is select path from autoexec;.

Dump Processes on Host T1059

1. Use procdump within Sysinternals

   • procdump -accepteula

Explore Processes T1059 T1055

1. Use procexp within Sysinternals

   • procexp -accepteula

2. Use Process Hacker

   • Download as Desktop application

3. Use procmon within SysInternals

   • procmon -accepteula

4. Use Get-WinEvent with Sysmon Event Logs.

   • Command to use is Get-WinEvent -Path <Path to Log> -FilterXPath '*/System/EventID=1'

   • Command to use is Get-WinEvent -Path <Path to Log> -FilterXPath '*/System/EventID=8'

5. Use eventvwr.msc with Sysmon Event logs and Event ID 1.

6. Use eventvwr.msc with Sysmon Event logs and Event ID 8.

7. Use osquery on the Windows Command line.

   • Command to use in interactive mode is select sid,path from userassist.

8. Use DeepBlueCLI (from here) and Powershell.

9. Use eventvwr.msc with Windows Security Event logs 4688.

10. Use Get-Process within Powershell.

11. Use Get-CimInstance -Class Win32_Process | Select-Object ProcessId, ProcessName,CommandLine within Powershell.

12. Use volatility with a forensic image.

    • Version 3 uses windows.pslist.Pslist, windows.pstree.PsTree, windows.netscan.NetScan, windows.cmdline.Cmdline, windows.dlllist.DllList

13. Use SRUM Dump to examine system usages related to processes.

14. View the registry at NTUSER.DAT\Software\Microsoft\Windows\CurrentVersion\Explorer\UserAssist\{GUID}\Count where the GUID is specific for the OS.

15. View the Windows Background Activity Monitor at SYSTEM\CurrentControlSet\Services\bam\UserSettings\{SID} or SYSTEM\CurrentControlSet\Services\dam\UserSettings\{SID}

16. View the Last Visited MRU at NTUSER.dat\Software\Microsoft\Windows\CurrentVersion\Explorer\Comdlg32\LastVisited[PID]MRU.

17. View the RunMRU at NTUser.dat\Software\Microsoft\Windows\CurrentVersion\Explorer\RunMRU for Start-> Run execution.

18. Examine the execution within ProcDot.

19. Use eventvwr.msc with Windows Security Event logs 4663.

20. Use eventvwr.msc with Sysmon Event logs and Event ID 10.

21. Use eventvwr.msc with Sysmon Event logs and Event ID 25.

22. Use eventvwr.msc with Sysmon Event logs and Event ID 8.

23. Use Live Forensicator with .\Forensicator -EVTX EVTX and identify processes within processes.html.

24. Examine prefetch files with w10pf_parse.py.

25. Examine Windows Defender Logs with Event ID 1117 within the Channel Microsoft-Windows-Windows Defender/Operational.

26. Run the following command in PowerShell on the system: Get-NetTCPConnection | select Local*, Remote*, State, OwningProcess,` @{n="ProcName";e={(Get-Process -Id $_.OwningProcess).ProcessName}},` @{n="ProcPath";e={(Get-Process -Id $_.OwningProcess).Path}} | sort State | ft -Auto .

27. Look at processes within Powershell with Get-WmiObject -Class Win32_Process | ForEach-Object {$owner = $_.GetOwner(); [PSCustomObject]@{Name=$_.Name; PID=$_.ProcessId; P_PID=$_.ParentProcessId; User="$($owner.User)"; CommandLine=if ($_.CommandLine.Length -le 60) { $_.CommandLine } else { $_.CommandLine.Substring(0, 60) + "..." }; Path=$_.Path}} | ft -AutoSize

Explore Registry Activity T1564.001 T1574T1112T1070.007 T1070.009T1003.002T1027.011T1137T1012 T1033 T1569.002 T1552.002

1. Use procmon within SysInternals

   • procmon -accepteula

2. Use Get-WinEvent with Sysmon Event Logs.

   • Command to use is Get-WinEvent -Path <Path to Log> -FilterXPath '*/System/EventID=13'

   • Command to use is Get-WinEvent -Path <Path to Log> -FilterXPath '*/System/EventID=12'

3. Use eventvwr.msc with Sysmon Event logs and Event ID 12.

4. Use eventvwr.msc with Sysmon Event logs and Event ID 13.

5. Use eventvwr.msc with Windows Security Event logs 4657.

6. Use Get-ChildItem with the specific registry key in Powershell.

7. Use Get-ItemProperty with the specific registry key in Powershell.

8. Use Regshot to compare initial registry with final registry post execution.

9. Use RegRipper.

   • Command to use is regripper -f [Hive] -a.

10. Look for registry modifications to HKLM\SYSTEM\CurrentControlSet\Services\<NetworkProviderName>\NetworkProvider, HKLM\SYSTEM\CurrentControlSet\Control\Lsa\ Notification Packages, or HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order.

11. Use regripper to examine the NTUSER.dat file for a specific user looking at UserAssist.

Explore Scheduled Tasks T1036.004 T1053.005

1. Use Get-WinEvent with Sysmon Event Logs.

   • Command to use is Get-WinEvent -Path <Path to Log> -FilterXPath '*/System/EventID=1'

2. Use eventvwr.msc with Sysmon Event logs and Event ID 1.

3. Use Get-ScheduledTask within Powershell. https://learn.microsoft.com/en-us/sysinternals/downloads/procmon

   • Command to use is Get-ScheduledTask -TaskName [TaskName]

4. Use Export-ScheduledTask within Powershell.

   • Command to use is Get-ScheduledTask -TaskName [Name].

5. Use eventvwr.msc with Windows Security Event logs 4698.

6. Use eventvwr.msc with Windows Security Event logs 4702.

7. Use eventvwr.msc with Windows Security Event logs 4699.

8. Use eventvwr.msc with Windows Security Event logs 4701.

9. Identify processes of at.exe or schtasks.exe on the source machine.

10. View registry at Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tasks or Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree on target machine to find scheduled tasks.

11. Look for hive key changes in the NetSh key with Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Netsh".

Explore Process Thread Activity T1134.003 T1574.005 T1574.010 T1055.003 T1055.005 T1620

1. Use procmon within SysInternals

   • procmon -accepteula

2. Use Get-WinEvent with Sysmon Event Logs and look at the call trace.

   • Command to use is Get-WinEvent -Path <Path to Log> -FilterXPath '*/System/EventID=10'

3. Use eventvwr.msc with Sysmon Event logs and look at call trace in Event ID 10.

4. Use osquery on the Windows Command line.

   • Command to use in interactive mode is select sid,path from userassist;.

5. Use DeepBlueCLI (from here) and Powershell.

6. Examine the execution within ProcDot.

7. Examine changes in DLLs residing in C:\Windows\System32.

8. Use eventvwr.msc with Windows Security Event logs 4663.

9. Use eventvwr.msc with Sysmon Event logs and Event ID 10.

10. Use eventvwr.msc with Sysmon Event logs and Event ID 25.

11. Use eventvwr.msc with Sysmon Event logs and Event ID 8.

12. Use Live Forensicator with .\Forensicator -EVTX EVTX and identify processes within processes.html.

13. Run the following command in PowerShell on the system: Get-NetTCPConnection | select Local*, Remote*, State, OwningProcess,` @{n="ProcName";e={(Get-Process -Id $_.OwningProcess).ProcessName}},` @{n="ProcPath";e={(Get-Process -Id $_.OwningProcess).Path}} | sort State | ft -Auto .

14. Look at processes within Powershell with Get-WmiObject -Class Win32_Process | ForEach-Object {$owner = $_.GetOwner(); [PSCustomObject]@{Name=$_.Name; PID=$_.ProcessId; P_PID=$_.ParentProcessId; User="$($owner.User)"; CommandLine=if ($_.CommandLine.Length -le 60) { $_.CommandLine } else { $_.CommandLine.Substring(0, 60) + "..." }; Path=$_.Path}} | ft -AutoSize

Explore File Read Activity [No TTP]

1. Use procmon within SysInternals

   • procmon -accepteula

2. Use LECmd.exe (from Eric Zimmerman here with Command line.

   • Command to use LECmd.exe -f [shortcut_file]

   • Shortcut files: C:\Users\<username>\AppData\Roaming\Microsoft\Windows\Recent\ or C:\Users\<username>\AppData\Roaming\Microsoft\Office\Recent\

3. View the OpenSaveMRU to detect file opening at NTUSER.dat\Software\Microsoft\Windows\CurrentVersion\Explorer\ComDlg32\OpenSave[PID]MRU.

4. View the Last Visited MRU at NTUSER.dat\Software\Microsoft\Windows\CurrentVersion\Explorer\Comdlg32\LastVisited[PID]MRU.

5. Examine the RecentFiles at NTUSER.DAT\Software\Microsoft\Windows\CurrentVersion\Explorer\RecentDocs.

6. Examine Office RecentFiles at NTUSER.DAT\Sofware\Microsoft\Office\VERSION.

7. Focus on Shellbags for find file access at NTUSER.DAT\Software\Microsoft\Windows\Shell\BagMRU or NTUSER.DAT\Software\Microsoft\Windows\Shell\Bags.

8. Each open of file creates a link file at C:\%USERPROFILE%\AppData\Roaming\Microsoft\Windows\Recent or C:\%USERPROFILE%\AppData\Roaming\Microsoft\Office\Recent.

9. Utilize jump lists at C:\%UserProfile%\AppData\Roaming\Microsoft\Windows\Recent\AutomaticDestinations to view user access of files.

10. Use PECmd.exe (from Eric Zimmerman here with Command line.

    • Command to use PECmd.exe -f [prefetch_file]

11. View prefetch files at C:\Windows\Prefetch for program execution.

12. View files access from IE at %USERPROFILE%\AppData\Local\Microsoft\Windows\WebCache\WebCacheV*.dat.

13. Examine prefetch files with w10pf_parse.py.

14. Use MFTECmd with the USNJournal ($J) to find the specific file activity.

15. Use MFTECmd with the $I30 file to find the specific file activity.

16. Looked at Typed Paths within NTUSER.dat\Software\Microsoft\Windows\CurrentVersion\Explorer\TypedPaths or NTUSER.dat\Software\Microsoft\Windows\CurrentVersion\Explorer\WordWheelQuery.

Explore File Download T1546.016 T1027.006 T1566.002 T1218.001 T1189 T1203T1608.004 T1218.005 T1204.001 T1176 T1185

1. View the MRU at NTUSER.DAT\Software\Microsoft\Windows\CurrentVersion\Explorer\ComDlg32\OpenSave[PID]MRU.

2. View email attachments at %USERPROFILE%\AppData\Local\Microsoft\Outlook.

3. View skype history at C\%USERPROFILE%\AppData\Roaming\Skype\[skypename].

4. View IE user account and download history at %USERPROFILE%\AppData\Local\Microsoft\Windows\WebCache\WebCacheV*.dat.

5. View Firefox user account at %USERPROFILE%\AppData\Roaming\Mozilla\Firefox\Profiles\[randomtext].default\places.sqlite.

6. View chrome user account at %USERPROFILE%\AppData\Local\Google\Chrome\UserData\Default\History.

7. View firefox download history at %USERPROFILE%\AppData\Roaming\Mozilla\Firefox\Profiles\[randomtext].default\downloads.sqlite.

8. View user downloads within C:\User\*\Downloads.

9. View Sysmon Event ID 22 for domain queries.

10. Use RegRipper to find file downloads via user hive.

    • Command to run is regripper -f [Hive] -a

11. View edge user downloads looking at the History sqlite3 database table, specifically the downloads table.

12. View edge user downloads looking at the History sqlite3 database table, specifically the urls table.

13. View edge user downloads looking at the History sqlite3 database table, specifically the downloads_url_chains table.

View Email Attachments T1566.001T1566.002

1. View email attachments at %USERPROFILE%\AppData\Local\Microsoft\Outlook.

View Skype History [No TTP]

1. View skype history at C\%USERPROFILE%\AppData\Roaming\Skype\[skypename].

View Firefox History T1189 T1203T1608.004 T1218.001 T1218.005 T1204.001 T1176 T1185

1. View Firefox user account and history at %USERPROFILE%\AppData\Roaming\Mozilla\Firefox\Profiles\[randomtext].default\places.sqlite.

2. View firefox download history at %USERPROFILE%\AppData\Roaming\Mozilla\Firefox\Profiles\[randomtext].default\downloads.sqlite.

3. Focus on cookiest at %\USERPROFILE%\AppData\Roaming\Mozilla\Firefox\Profiles\[random].default\cookies.sqlite.

4. Look at user cache at \%USERPROFILE%\AppData\Local\Mozilla\Firefox\Profiles\[random].default\Cache.

5. View the session restore within %\USERPROFILE%\AppData\Roaming\Mozilla\Firefox\Profiles\[random].default\sessionstore.js.

6. View flash cookies at %APPDATA%\Roaming\Macromedia\FlashPlayer\#SharedObjects\[random].

View Chrome History T1189 T1203T1608.004 T1218.001 T1218.005 T1204.001 T1176 T1185

1. View chrome user account and history at %USERPROFILE%\AppData\Local\Google\Chrome\User Data\Default\History.

2. Focus on cookies at %\USERPROFILE%\AppData\Local\Google\Chrome\UserData\Default\Local Storage.

3. Look at user cache at %USERPROFILE%\AppData\Local\Google\Chrome\User Data\Default\Cache.

4. Look at session restore data at %USERPROFILE%\AppData\Local\Google\Chrome\User Data\Default.

5. View flash cookies at %APPDATA%\Roaming\Macromedia\FlashPlayer\#SharedObjects\[random].

Explore Internet Explorer or Edge Browsing History T1189 T1203T1608.004 T1218.001 T1218.005 T1204.001 T1176 T1185

1. Use Autopsy as a secondary tool.

   • View information located at: C:\Users\<username>\AppData\Local\Microsoft\Windows\WebCache\WebCacheV*.dat

2. Focus on cookies at %\USERPROFILE%\AppData\Roaming\Microsoft\Windows\Cookies or %\USERPROFILE%\AppData\Local\Microsoft\Windows\INetCookies.

3. Look at user cache or Edge at \%USERPROFILE%\AppData\Local\Packages\microsoft.microsoftedge_[APPID]\AC\MicrosoftEdge\Cache or for IE at %\USERPROFILE%\AppData\Local\Microsoft\Windows\INetCache\IE.

4. Look at session restore data in IE at %USERPROFILE%\AppData\Local\Microsoft\Internet Explorer\Recovery.

5. View flash cookies at %APPDATA%\Roaming\Macromedia\FlashPlayer\#SharedObjects\[random].

6. Use Pasco to inspect index.dat file.

7. Use Live Forensicator with ./Forensicator -BROWSER BROWSER and search for histories within the BROWSWER_HISTORY folder.

8. Use Live Forensicator with ./Forensicator -BROWSER BROWSER and search for histories within the BrowserHistory.html file.

9. If given a History SQLite3 table, use sql statements to examine the various tables and open the db with sqlite3.

10. View edge user downloads looking at the History sqlite3 database table, specifically the downloads table.

11. View edge user downloads looking at the History sqlite3 database table, specifically the urls table.

12. View edge user downloads looking at the History sqlite3 database table, specifically the downloads_url_chains table.

View Cookies T1606.001 T1539 T1550.004

1. Focus on cookies at %\USERPROFILE%\AppData\Roaming\Microsoft\Windows\Cookies or %\USERPROFILE%\AppData\Local\Microsoft\Windows\INetCookies.

2. Focus on cookies at %\USERPROFILE%\AppData\Local\Google\Chrome\UserData\Default\Local Storage.

3. Focus on cookiest at %\USERPROFILE%\AppData\Roaming\Mozilla\Firefox\Profiles\[random].default\cookies.sqlite.

4. View flash cookies at %APPDATA%\Roaming\Macromedia\FlashPlayer\#SharedObjects\[random].

Explore Deleted Files T1070.004 T1485

1. Use Autopsy as a secondary tool.

2. Use LECmd.exe (from Eric Zimmerman here with Command line.

   • Command to use LECmd.exe -f [shortcut_file]

   • Shortcut files: C:\Users\<username>\AppData\Roaming\Microsoft\Windows\Recent\ or C:\Users\<username>\AppData\Roaming\Microsoft\Office\Recent\

3. Use MFTECmd with the USNJournal to find the specific file activity.

Explore Shortcut Files T1080 T1547.009 T1222 T1204.002

1. Use LECmd.exe (from Eric Zimmerman here with Command line.

   • Command to use LECmd.exe -f [shortcut_file]

   • Shortcut files: C:\Users\<username>\AppData\Roaming\Microsoft\Windows\Recent\ or C:\Users\<username>\AppData\Roaming\Microsoft\Office\Recent\

2. Each open of file creates a link file at C:\%USERPROFILE%\AppData\Roaming\Microsoft\Windows\Recent or C:\%USERPROFILE%\AppData\Roaming\Microsoft\Office\Recent.

Explore File Write Activity [No TTP]

1. Use procmon within SysInternals

   • procmon -accepteula

2. Use LECmd.exe (from Eric Zimmerman here with Command line.

   • Command to use LECmd.exe -f [shortcut_file]

   • Shortcut files: C:\Users\<username>\AppData\Roaming\Microsoft\Windows\Recent\ or C:\Users\<username>\AppData\Roaming\Microsoft\Office\Recent\

3. Use MFTECmd with the USNJournal to find the specific file activity.

Explore Prefetch Files T1204

1. Use PECmd.exe (from Eric Zimmerman here with Command line.

   • Command to use PECmd.exe -f [prefetch_file]

2. View prefetch files at C:\Windows\Prefetch for program execution.

3. Examine prefetch files with w10pf_parse.py.

Parse Windows 10 Timeline [No TTP]

1. Use WxTCmd.exe (from Eric Zimmerman here on Windows Command line.

   • Command to use WxTCmd.exe -f [timeline_file]

   • Timeline file: C:\Users\<username>\AppData\Local\ConnectedDevicesPlatform\{randomfolder}\ActivitiesCache.db

Parse Windows Jump Lists [No TTP]

1. Use JLECmd.exe (from Eric Zimmerman here on Windows Command line.

   • Command to use JLECmd.exe -f [jumplist_file]

   • Jump List file: C:\Users\<username>\AppData\Roaming\Microsoft\Windows\Recent\AutomaticDestinations

Explore File Creation Activity

1. Use Get-WinEvent with Sysmon Event Logs.

   • Command to use is Get-WinEvent -Path <Path to Log> -FilterXPath '*/System/EventID=11'

2. Use eventvwr.msc with Sysmon Event logs and Event ID 11.

3. Use LECmd.exe (from Eric Zimmerman here with Command line.

   • Command to use LECmd.exe -f [shortcut_file]

   • Shortcut files: C:\Users\<username>\AppData\Roaming\Microsoft\Windows\Recent\ or C:\Users\<username>\AppData\Roaming\Microsoft\Office\Recent\.

4. Look at Sysmon Event logs for event ID 11.

5. Use MFTECmd with the USNJournal ($J) to find the specific file activity.

6. Use MFTECmd with the $I30 file to find the specific file activity.

Explore Powershell Activity T1059.001 T1546.013

1. Use eventvwr.msc on a Windows system and navigate to Applications and Services Logs -> Microsoft -> Windows -> PowerShell -> Operational.

2. Use DeepBlueCLI (from here) and Powershell.

3. Use wevutil.exe to find Powershell execution.

   • Command to use is wevutil.exe qe “Windows PowerShell” /q:"*[System[(EventID=501 or EventID=500)]]"

4. Use wevutil.exe to find Powershell execution to find Get calls.

   • Command to use is wevutil.exe qe "Microsoft-Windows-PowerShell/Operational" /q:"*[System[(EventID=4104)]]" /c:1000 /rd:true /f:text | findstr /i "Get-"

5. Use wevutil.exe to find Powershell execution to find invoke execution calls.

   • Command to use is wevutil.exe qe "Microsoft-Windows-PowerShell/Operational" /q:"*[System[(EventID=4104)]]" /c:1000 /rd:true /f:text | findstr /i "iex"

6. Focus on ShimCache, AmCache.hve, Prefetch, DAM, and BAM with powershell.exe on source machine.

7. Use eventvwr.msc to view Microsoft-Windows-WinRM%4Operational logs for event id 6, 8, 15, 16, or 33 on source machine for remote connection.

8. Use eventvwr.msc to view Microsoft-Windows-PowerShell%4Operational for event id 40961, 40962, 8193, 8194, and 8197 on source machine for remote connection.

9. Use eventvwr.msc to view Microsoft-Windows-PowerShell%4Operational for event id 4103, 4104, 53504 on target machine for remote connection.

10. Use eventvwr.msc to view Microsoft-Windows-WinRM%4Operational logs for event id 91 or 168 on target machine for remote connection.

11. Use PSReadline to view full script blocks.

12. Use TimelineExplorer to find suspicious powershell activity using input csv information.

13. View PowerShell Script blocks within PowerShell-Operational.evtx logs with event ID 4104.

14. Use RegRipper to highlight powershell downloads with IEX Download String.

    • Command to use regripper -f [Hive] -a.

15. Look for history file at APPDATA\Microsoft\Windows\PowerShell\PSReadLine\ConsoleHost_history.txt.

View PowerShell Command Execution T1059.001 T1546.013

1. Use eventvwr.msc on a Windows system and navigate to Applications and Services Logs -> Microsoft -> Windows -> PowerShell -> Operational and look for EventID 4104.

2. Use eventvwr.msc on a Windows system and navigate to Applications and Services Logs -> Microsoft -> Windows -> PowerShell -> Operational and look for EventID 800.

3. Use eventvwr.msc on a Windows system and look for event ID 4104 within the Powershell (Microsoft-Windows-Powershell) log.

4. Use DeepBlueCLI (from here) and Powershell.

5. Focus on ShimCache, AmCache.hve, Prefetch, DAM, and BAM with powershell.exe on source machine.

6. Use TimelineExplorer to find suspicious powershell activity using input csv information.

7. View PowerShell Script blocks within PowerShell-Operational.evtx logs with event ID 4104.

8. Examine prefetch files with w10pf_parse.py.

9. Use RegRipper to highlight powershell downloads with IEX Download String that can be found in LastRunMRU.

   • Command to use regripper -f [Hive] -a.

Determine the Number Of Log Names [No TTP]

1. Use wevutil.exe with Powershell

   • Command is wevutil.exe el

2. Use Get-WinEvent with Powershell

   • Command is Get-WinEvent -ListLog *

Determine User Account Creation T1078.002 T1136.002 T1098

1. Use Get-WinEvent with XPath queries using PowerShell.

   • Command would be Get-WinEvent -LogName Security -FilterXPath '*/System/EventID=4720 and */EventData/Data[@Name="TargetUserName"]="[UserName]"'

2. Use DeepBlueCLI (from here) and Powershell.

3. Look for account creation on the command line with net.exe or net1.exe with parent process cmd.exe.

4. Use Live-Forensicator Tool with .\Forensicator -EVTX EVTX, and search for User Creation Activity within the html file, can be found here.

5. Using powershell look for users with Get-CimInstance -Class Win32_UserAccount -Filter "LocalAccount=True" | Format-Table Name, PasswordRequired, PasswordExpires, PasswordChangeable.

Determine PowerShell Down Grade Attack T1059.001 T1546.013

1. Use Get-WinEvent using PowerShell.

   • Command would be Get-WinEvent -LogName "Windows PowerShell" | Where-Object Id -eq 400 | Foreach-Object {$version = [Version] ( $_.Message -replace '(?s).*EngineVersion=([\d\.]+)*.*','$1') if($version -lt ([Version] "5.0")) { $_ }}

2. User eventvwr.msc on a Windows system and filter for event ID 400 within the PowerShell logs.

   • EngineVersion will have a different number than other PowerShell logs.

Determine Log Clearing T1070.001 T1485

1. Use eventvwr.msc on a Windows system and filter for event ID 104 within the Microsoft-Windows-Eventlog source.

2. Use eventvwr.msc with Windows Security Event logs 517.

3. Use eventvwr.msc with Windows Security Event logs 1102 to view Audit log clearing.

4. Look for commands like Remove-EventLog -LogName Security, Remove-EventLog -LogName Application , or Remove-EventLog -LogName System.

5. Use TimelineExplorer to find suspicious powershell activity using input csv information.

Explore Group Enumeration T1069

1. Use eventvwr.msc on a Windows system and filter for event ID 4799 within Security event logs.

2. Look for unusual groups using powershell with Get-LocalGroup | ForEach-Object { $members = Get-LocalGroupMember -Group $_.Name; if ($members) { Write-Output "`nGroup: $($_.Name)"; $members | ForEach-Object { Write-Output "`tMember: $($_.Name)" } } }.

Determine Number of Network Connections T1021

1. Use Get-WinEvent with Sysmon Event Logs.

   • Command to use is Get-WinEvent -Path <Path to Log> -FilterXPath '*/System/EventID=3 | Measure-Object

Find Common Meterpreter Connections T1572 T1090 T1001 T1041

1. Use Get-WinEvent with Sysmon Event Logs.

   • Command to use is Get-WinEvent -Path <Path to Log> -FilterXPath '*/System/EventID=3 and */EventData/Data[@Name="DestinationPort"] and */EventData/Data=4444'

   • Command to use is Get-WinEvent -Path <Path to Log> -FilterXPath '*/System/EventID=3 and */EventData/Data[@Name="DestinationPort"] and */EventData/Data=5555

Find Mimikatz Execution T1003.005 T1003.004 T1003.001 T1649 T1558.001 T1558.002 T1552.004 T1550.002 T1550.003 T1555

1. Use Get-WinEvent with Sysmon Event Logs.

   • Command to use is Get-WinEvent -Path <Path to Log> -FilterXPath '*/System/EventID=10 and */EventData/Data[@Name="TargetImage"] and */EventData/Data="C:\Windows\system32\lsass.exe"'

2. Use DeepBlueCLI (from here) and Powershell.

3. View the Last Visited MRU at NTUSER.dat\Software\Microsoft\Windows\CurrentVersion\Explorer\Comdlg32\LastVisited[PID]MRU.

4. Examine the execution within ProcDot.

5. Use eventvwr.msc with Windows Security Event logs Event ID 4688 with vssadmin.

6. View ESENT logs with Event ID 325, 326, or 327 in Windows Application Logs.

7. Look for access to C:\Windows\System32\config\directory.

8. Identify interactions with HKLM\SAM\Domains\Accounts\Users.

9. Look for process access to common password locations with Sysmon Event ID 10 or 1.

10. Look for process creation Event ID 4688 to common password storage locations.

Find Common RAT Connections. T1021

1. Use Get-WinEvent with Sysmon Event Logs.

   • Command to use is Get-WinEvent -Path <Path to Log> -FilterXPath '*/System/EventID=3 and */EventData/Data[@Name="DestinationPort"] and */EventData/Data=8080'

2. Use DeepBlueCLI (from here) and Powershell.

View Installed Programs T1543 T1036.005T1569

1. Use osquery on the Windows Command line.

   • Command to use select * from programs;

2. Look at the Application Event log to find events for msiinstaller.

3. Use MFTECmd to look at downloaded files from the $MFT on a system.

4. Look at Application Event log for event ID 1033.

View All Users T1078.002T1136.002T1098 T1070.009 T1531

1. Use osquery on the Windows Command line.

   • Command to use select * from users;

2. Use Get-LocalUser within Powershell.

   • Command to use Get-LocalUser | Where-Object 'Enabled' -eq $True

3. Use Get-LocalGroup within Powershell.

4. Use Get-LocalGroupMember within Powershell with a specific group in mind.

Determine Browser Extension T1176

1. Use osquery on the Windows Command line.

   • Command to use select * from ie_extensions;

View UserAssist Activity [No TTP]

1. Use osquery on the Windows Command line.

   • Command to use in interactive mode is select sid,path from userassist;.

2. View the registry at NTUSER.DAT\Software\Microsoft\Windows\CurrentVersion\Explorer\UserAssist\{GUID}\Count where the GUID is specific for the OS.

3. Examine Word Wheel Query with regripper.

4. Use regripper to examine the NTUSER.dat file for a specific user.

Parse $MFT for Windows NTFS T1564

1. Use MFTECmd.exe on the Windows command line.

   • Command to use MCTECmd.exe -f [file] --csv [path_to_csv_output]

2. Use Autopsy as a secondary tool.

3. Pull out specific files and examine using --de option for MFTECmd.exe.

4. Use bless to examine the $MFT.

Parse $Boot for Windows NTFS T1564

1. Use MFTECmd.exe on the Windows command line.

   • Command to use MCTECmd.exe -f [file] --csv [path_to_csv_output]

2. Use Autopsy as a secondary tool.

Parse $J for Windows NTFS T1564

1. Use MFTECmd.exe (from Eric Zimmerman here on the Windows command line.

   • Command to use MCTECmd.exe -f [file] --csv [path_to_csv_output]

2. Use Autopsy as a secondary tool.

Parse $SDS for Windows NTFS T1564

1. Use MFTECmd.exe (from Eric Zimmerman here on the Windows command line.

   • Command to use MCTECmd.exe -f [file] --csv [path_to_csv_output]

2. Use Autopsy as a secondary tool.

Parse Volume Shadow Copies for Windows NTFS T1564

1. Use MFTECmd.exe (from Eric Zimmerman here on the Windows command line.

   • Command to use MCTECmd.exe -f [file] --csv [path_to_csv_output]

2. Use Autopsy as a secondary tool.

Parse $LogFile for Windows NTFS T1564

1. Use MFTECmd.exe (from Eric Zimmerman here on the Windows command line.

   • Command to use MCTECmd.exe -f [file] --csv [path_to_csv_output]

2. Use Autopsy as a secondary tool.

Find Service Creation T1569.002 T1543.003

1. Use DeepBlueCLI (from here) and Powershell.

2. Use eventvwr.msc with Windows System Event logs 7045.

3. Use eventvwr.msc with Windows Security Event logs 4697.

View User Authentications T1078

1. Use LogonTracer to map out logons by users.

2. Use eventvwr.msc with Windows Security Event logs 4624.

3. View the SAM at C:\Windows\system32\config\SAM or SAM\Domains\Account\Users.

4. Use eventvwr.msc with Windows Security Event logs 4625 for failed logons.

5. Use eventvwr.msc with Windows Security Event logs 4634 for logoff.

6. Use eventvwr.msc with Windows Security Event logs 4647 for logoff.

7. Use eventvwr.msc with Windows Security Event logs 4648 for run as login.

8. Use eventvwr.msc with Windows Security Event logs 4672 for admin login.

9. Use eventvwr.msc with Windows Security Event logs 4778 for RDP login.

10. Use eventvwr.msc with Windows Security Event logs 4779 for RDP logoff.

11. Use eventvwr.msc with Windows Security Event logs 4776 for NTLM authentication.

12. Use eventvwr.msc with Windows Security Event logs 4768 for TGT successful logon.

13. Use eventvwr.msc with Windows Security Event logs 4769 for TGS access to service.

14. Use eventvwr.msc with Windows Security Event logs 4771/4772 failed ticket logon.

15. Use wevutil.exe and search for appropriate Windows Security Eveents logs.

    • Command to use is wevutil.exe qe Security /q:"*[System[(EventID=4624 or EventID=4625)]]

16. Look for gpscript.exe /logon execution for user logons.

17. Use eventvwr.msc with Windows Security Event logs 4770 for kerberos ticket renewal.

18. Use Live-Forensicator Tool with .\Forensicator -EVTX EVTX, and search for RDP Logon Activities with an html file, can be found here.

19. Use Chainsaw and an EVTX dump to search for failed logons with ./chainsaw hunt [evtx] -r ./rules/.

20. Use powershell with Get-LocalUser | Select-Object Name, LastLogon.

Examine Startup Actions T1547

1. View desktop.ini for actions taken during startup.

2. Use Systinternals autorunsc tool.

3. Use PowerShell with the following command: Get-CimInstance Win32_StartupCommand | Select-Object Name, command, Location, User | fl.

4. Use Powershell with the following command: $winlogonPath = "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon"; "Userinit: $((Get-ItemProperty -Path $winlogonPath -Name 'Userinit').Userinit)"; "Shell: $((Get-ItemProperty -Path $winlogonPath -Name 'Shell').Shell)".

View Hosted Web Application Exploitation T1190

1. Use eventvwr.msc with Windows Security Event logs 4688 for process creation events on the host.

2. View suspicious php or .jsp files within /var/log/httpd/access.log.

3. View suspicious php files within /var/log/apache2/access.log.

Identify Phishing Attempts T1566

1. Look for registry modifications to HKLM\SYSTEM\CurrentControlSet\Services\<NetworkProviderName>\NetworkProvider, HKLM\SYSTEM\CurrentControlSet\Control\Lsa\ Notification Packages, or HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order.

Identity Suspicious DLLs T1574

1. Examine changes in DLLs residing in C:\Windows\System32.

2. Look for non-digitally signed DLLs.

3. Use eventvwr.msc with Sysmon Event logs and Event ID 25.

4. Use eventvwr.msc with Sysmon Event logs and Event ID 10.

Identify Credential Dumping T1003

1. Use eventvwr.msc with Windows Security Event logs Event ID 4688 with vssadmin.

2. View ESENT logs with Event ID 325, 326, or 327 in Windows Application Logs.

Identify Brute Force Attempts T1110

1. Use eventvwr.msc with Windows Security Event logs Event ID 4776.

2. Use eventvwr.msc with Windows Security Event logs Event ID 4740.

3. Use eventvwr.msc with Windows Security Event logs Event ID 4624.

4. Use eventvwr.msc with Windows Security Event logs Event ID 4625.

5. Use eventvwr.msc with Windows Security Event logs Event ID 4768.

6. Use eventvwr.msc with Windows Security Event logs Event ID 4771.

7. Use eventvwr.msc with Windows Security Event logs Event ID 4769.

8. Use eventvwr.msc with Windows Security Event logs Event ID 4776.

9. Use eventvwr.msc with Terminal-Services-RemoteConnectionManager Event ID 1149.

10. Use eventvwr.msc with ListenerRDP-TCP Event ID 261.

11. Use eventvwr.msc with Terminal-Services-LocalSessionManager Event ID 21.

12. Use Live-Forensicator Tool with .\Forensicator -EVTX EVTX, and search for RDP Logon Activities with an html file, can be found here.

13. Use Chainsaw and an EVTX dump to search for failed logons with ./chainsaw hunt [evtx] -r ./rules/.

14. Use TimelineExplorer to find suspicious powershell activity using input csv information.

Identify Credentials in Group Policy T1552.006

1. Look for powershell command executiono with Get-GPPPassword.

Identify Credentials in Password Stores T1555

1. Look for access to C:\Windows\System32\config\directory.

2. Identify interactions with HKLM\SAM\Domains\Accounts\Users.

3. Look for process access to common password locations with Sysmon Event ID 10 or 1.

4. Look for process creation Event ID 4688 to common password storage locations.

Identify Proxy Usage T1090

1. Look for registry interactions with HKLM\System\CurrentControlSet\Services\PortProxy\v4tov4\tcp.