- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
07-26-2024 01:35 AM
07-26-2024 06:39 AM
hello @Touseef-ur rehman
you can define a policy for powershell.exe, and with parameters including the shell commands you wish to allow.
the invocation of this commands need to be in the format of "powershell.exe Install-module..." meaning opening PowerShell, then just typing "install-module.." will not be caught, but a full "powershell.exe Install-Module..." will be elevated...
to note: the "parent" process of PowerShell, should be allow without child processes...
in this way you can maintain least privilege, and specific elevations for shell commands.
cheers!
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!

