Enhanced Security Measures in Place:   To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.

Compile Payload Source Code Locally

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Compile Payload Source Code Locally

L2 Linker

Dear Team,

 

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.

Venu
2 REPLIES 2

L3 Networker

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. 

L2 Linker

Thank you @eumbach for the quick suggestion

 

Venu
  • 1160 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!