We wanted to restrict compilers on our environment after a pentest resulted with Compile Payload Source Code Locally, we have common compilers like csc.exe and GCC/MinGW.
We wanted to know how to identify any common suspicious behavior exe's along with the csc.exe and GCC/MinGW compilers, suggest me the best way to restrict the compilers.
Hello @VenuK ,
We have used an active directory group to identify developers in our environment and then created a policy to allow for that AD group in XDR to run compilers.
We also are using a codesigning certificate to 'whitelist' any developer applications which follow the signing 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!