PowerShell Protect
Changelog for PowerShell Protect
- Fixed an issue where not all formats of Invoke-Expression would be detected with the built in rule.
- Fixed an issue where license files were not correctly validated
- Added support to PowerShell Universal for generating PowerShell Protect configuration files
- Added support for sending events to PowerShell Universal
- Built-in rules no longer require a license.
- Improved error logging for failed conditions
- Fixed an issue where invalid configurations would cause exceptions in built-in rules
- Added support for Application Hash (SHA256) conditions
- Added support for Assembly conditions
- Added support for Assembly Hash (SHA256) conditions
- Added support for specifying a license within the configuration file
- Added support for matching any condition on a rule
- Fixed an issue where you could specify -Format for -Tcp or -UDP on New-PSPAction
- Added built-in detection for attempts to explore Log4j CVE-2021-44228
- Added support for sending event log actions based on rules
- Added subscription activation caching to prevent excessive web requests
- Added support for disabling individual rules with
-DisabledBuiltinConditions - PowerShell Protect is now a part of PowerShell Pro Tools.
Last modified 2mo ago