Skip to main content
Solved

report visibility who starts CMD/Powershell commands in elevated rights

  • December 22, 2025
  • 2 replies
  • 38 views

All our workstations are managed through Intune in User Mode, which means that there are no Admin rights on the workstations by default as part of our security hardening. Applications to be installed is dictated through the Company Portal. 

However we do have some apps that are very difficult to package for Company Portal deployment and BTRS is then the route to go through and through the session the engineer has the ability to elevate command prompt/powershell prompt to install the particular application. Also for admin elevated tasks, BTRS is the lifeline. 

Of course we do detect left and right that engineers “abuse” the rights and install apps without proper approval which in turn could be a security risk. Is there an “easy” way through any of the reports (haven't found any so far) to see who did elevation of command prompts/powershell prompts which can then be evaluated if it was correct use or abuse. 

 

Best answer by tclowater

Hey ​@edwinb77,

 

This is unfortunately a risk with allowing full powershell/cmd admin without restrictions to commands. We recommend restricting the commands individuals are allowed to run to an approved set rather than the full suite of commands. Note, if there is a powershell script, the script contents aren’t evaluated against policy and we recommend putting a hash match to ensure the approved version is allowed to run. 

2 replies

tclowater
BeyondTrust Employee
  • BeyondTrust Employee
  • Answer
  • December 30, 2025

Hey ​@edwinb77,

 

This is unfortunately a risk with allowing full powershell/cmd admin without restrictions to commands. We recommend restricting the commands individuals are allowed to run to an approved set rather than the full suite of commands. Note, if there is a powershell script, the script contents aren’t evaluated against policy and we recommend putting a hash match to ensure the approved version is allowed to run. 


  • Author
  • Rising Star
  • January 5, 2026

I've just been reading the patch notes for 25.3.x and there is a mention about forensic monitoring in the shell command, we have the upgrading to do, so may help in our search and monitoring.