DriveLock is able to enforce the PowerShell Constrained Language Mode (CLM) via a ABC-Rule, which prevents instances of PowerShell from writing the file _PSScriptPolicyTest*.ps1.
In addition, DriveLock can exclude PowerShell processes from CLM if they run in the context of specified users, via a UBC-Rule

We would like to request the following improvements to CLM enforcement via DriveLock:
- Exempt whitelisted Scripts (e.g. whitelisted by hash or signature) from being forced to tun in CLM
- Exempt PowerShell Scripts in whitelisted Paths (e.g. C:\Program Files*) from being forced to run in CLM

The ABC rule that enforces CLM can only able to constrain Powershell-Hosts (Powershell.exe, powershell_ise.exe). However Powershell Code itself is executed by the Powershell engine "System.Management.Automation.dll". If another program loads the PowerShell engine directly, it is currently not subject to CLM enforcement via DriveLock
We would therefore like to request that DriveLock be able to enforce CLM via the powershell engine itself.