This is what I'm referring to. It's the "minimal process that is associated with a pico profider kernel-mode driver." I'm curious if Traps can see these processes in Windows 10 when using Windows Subsystem for Linux (WSL). Bashware can leverage these processes to avoid detection from antivirus software installed on windows by utilizing these processes and I'm looking for clarification on how Traps does or does not protect against this.
So I actually just looked through my processes on the ESM console and they do detect processes running from within the Bash shell. I looked at a few of them that I know I would have been using and from what I can see non of them are protected by default, meaning you would have to setup the process in a provisional or protected state yourself.
Hope that helps, looks like you could pretty easily make Traps compliant with whatever protections you need but it wouldn't be enabled by default.
I actually don't have any specific to these types of processes, as far as I'm aware I'm the only person running Bash in our enviroment and I only use it for it's built in SSH capablities. That being said setting up process protection and linking subsequent EPM rules would be the same as adding protection to a custom or otherwise unprotected process; I highly recommend reaching out to your SE and getting in touch with your regions endpoint protection team, they can help you along this process.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!