Point of trivia (though interesting and possibly useful)
WoWw64 = Windows 32-bit on Windows 64-bit[1], and is used to run 32-bit applications on 64-bit windows.
Windows and Live forensics
These commands are the grunt-work required to verify your EDR application works
You need to be able to run these commands in terminal
There are times your EDR tool will be lying to you, or the EDR is opaque in how it makes decisions
A great place to research Windows CLI commands is SS64,
Begin with network connections
netstat
netstat (or network statistics) is a cross-platform CLI tool to monitor network traffic
Unfortunately, some of the switches are different depending on the OS, and and the specifics can be found on the Wikipedia Page
-naob
2. a - displays all active TCP and connections and TCP/UDP ports
3. n - displays active TCP connectives, expressed numerically, no attempt to determine name
4. o - displays active TCP connections with their PID
5. b - displays the executable involved
1. NOTE: The executable is listed after all the connection it's made
2.
3. NOTE: On macOS, b reports the total bytes in the traffic
-f
Windows specific; shows FQDN, may need to be run multiple times
Can be helpful in identifying services that don't resolve to a FQDN, and are suspicious
However, also takes longer to run, so not necessarily helpful for broad traffic filtering
NET
NET is a Windows command to manage and investigate network resources
NET Commands
net view
Shows all shares active on the windows session
You will need to run it against a clean system to know what's normal
net use
Show who is making outbound connections from the system (*outbound connections)
net session
Show who has an active session with this system right now (inbound connections)
Follow up with Windows Processes
tasklist
tasklist shows all tasks running on the computer, in this moment, and their PID
Can be run locally or remotely
One problem is that all svchosts.exe appear identical, and can be easy to gloss over
Tasklist Commands
tasklist
tasklist /svc
For each exe running, it lists the associated services
tasklist /m
All the DLLs associated with each executable
tasklist /m /fi "pid eq [pid]
/m - Lists all tasks curring using the given exe/dll name
/fi - Apply a pre-configured filter (e.g., by PID, but status, by username, etc.)
/u domain\user </p password>
Run tasklist as a different user
If the password is not entered in the optional switch, then the user will be prompted after running
WMIC
Windows Management Instrumentation Command-line (WMIC) is a (now deprecated) command-line method of working with WMI.
The new/supported method is using PowerShell, and commands can be found with Get-Command -Noun *WMI* and Get-Command -Noun *CIM*
WMIC Commands
wmic process list full
List all processes
wmic process get name,parentprocessid,processid
Shows the ID and process ID of each process running
wmic process where processid=[PID] get commandline
See what commands were used to launch the process
Processes started through mouse/keyboard interaction list the full path of the executable
Processes started through command line tend to only show the name of the executable and any switches used, but it's anything the person enters into the CLI