ePO BT Privilege Management App 26.4.1
This release updates the BeyondTrust Privilege Management App, which hosts the Web Policy Editor and Privilege Management Reporting for Trellix ePO, the PM Reporting database, and the EPM for Windows and EPM for Mac endpoint agents. It begins the rollout of QuickStart version 2, introduces secure built-in application groups in the Web Policy Editor and deprecates the legacy "Any …" groups, and adds smart card authentication with Pointsharp Net iD Client. The ePO extension is not updated in this release. Deploy the updated Windows and Mac agents to get the endpoint changes, and read the action panel below before you upgrade.
📦 At a glance
| Component | Runs on | What changed | Your action |
|---|---|---|---|
| BeyondTrust Privilege Management App | ePO server | New features, enhancements, fixes | Upgrade |
| Web Policy Editor (in the PM App) | ePO server | New features, enhancements, fixes, deprecation | Included in the PM App upgrade |
| PM Reporting UI (in the PM App) | ePO server | Enhancements | Included in the PM App upgrade |
| PM Reporting Database | Database server | Fixes | Upgrade |
| ePO extension | ePO server | No changes | No action |
| EPM for Windows | Endpoint | New features, enhancements, fixes | Deploy |
| EPM for Mac | Endpoint | Fixes | Deploy |
See Build numbers for versions for every component.
🚨 Action required before upgrade
- The minimum .NET Framework version rises from 4.6.2 to 4.7.2 for Power Rules, PowerShell audit scripts, Agent Protection, Trace Config and the RADIUS authentication dialog. On Windows Server 2016 you must install 4.7.2 or later to keep using those features.
Actions after upgrade (recommended)
- Legacy "Any …" application groups are marked deprecated. Policy Assistant flags any policy still using one and offers a one-click switch to the secure equivalent.
- macOS 26 QuickStart policies: Re-apply the updated QuickStart template to existing macOS policies to restore the Support Desk challenge on Privacy & Security (see Policy templates / QuickStart).
For more information, see QuickStart policy adoption guide.
⭐ Highlights
QuickStart V2, on Windows and macOS
On Windows, QuickStart has been rebuilt as a single policy that covers both desktop and Windows Server, so there is no longer a separate server template to select or maintain. The new policy reflects the configuration our field teams have found works best in real customer environments, which means it can be deployed as it ships without needing to be modified by hand first. Administrators get a trusted starting point and protection on day one, rather than a template that has to be reworked before it is useful.
The macOS QuickStart policy has also been refreshed. Both policies have been updated to meet current accessibility and branding standards.
If you are already using QuickStart, nothing changes in your environment. Your existing policy continues to run exactly as it does today, and the new version is available for you to adopt when you are ready. Guidance for bringing the new content into a running policy is published in the knowledge base.
ℹ️ Requires Policy Editor 26.4, and Windows or Mac agent 26.4.
For more information, see QuickStart policy adoption guide.
Secure built-in application groups, and "Any" legacy groups deprecated
The Web Policy Editor now includes secure <Any Application>, <Any Signed Application>, <Any UAC Prompt> and <Any Signed UAC Prompt> built-in groups and marks the legacy "Any …" groups as (Deprecated). Policy Assistant also flags any policy that still uses a deprecated group and offers a one-click fix that switches it to the secure equivalent.
ℹ️ Requires PM Cloud 26.4, Policy Editor 26.4, and Windows agent 26.4.
Smart card authentication with Pointsharp Net iD Client
EPM for Windows now supports smart cards that use Pointsharp Net iD Client, so users can authenticate in EPM messages on their device with the same card they use to sign in to Windows.
ℹ️ Requires Windows agent 26.4.
🧩 Changes by component
Issues reported by customers through an escalation are listed first.
BeyondTrust Privilege Management App 26.4.2
No new features or enhancements.
Web Policy Editor 26.4.1
🆕 New features
Policy Assistant one-click fix
Secure built-in application groups and deprecation of the legacy "Any …" groups, with a Policy Assistant one-click fix. See Highlights.
Policy Assistant warning for loosely matched rundll32.exe rules
The Policy Assistant now warns you when a policy contains a rule that elevates rundll32.exe with a loosely-matched command line ending in .dll, which a standard user could abuse to run their own DLL as an administrator.
✨ Enhancements
Updated the Java runtime used by the Policy Editor to 25.0.5 to apply the latest security fixes.
🛠️ Issues resolved
| Description | Resolution |
|---|---|
In the Windows QuickStart template, .reg files opened with regedit.exe bypassed the registry rule and were not audited. | The registry rule now audits .reg files opened with regedit.exe. Existing QuickStart policies don’t update automatically. To apply the fix, create a new policy from the updated template, or exclude regedit.exe and reg.exe from (BT) Any Trusted Executable in Passive - All Users. |
Privilege Management Reporting 26.4.1
PM Reporting UI 26.4.1.4 (in the PM App)
✨ Enhancements
Updated third-party libraries used by the PM Reporting UI to their latest versions to resolve known vulnerabilities.
PM Reporting Database 26.4.2.1
🛠️ Issues resolved
| Description | Resolution |
|---|---|
| The Discovery All report timed out and failed to load when the On-Demand / Auto filter was applied to a large number of events. | The Discovery All report now loads without timing out when the On-Demand / Auto filter is applied, even with a large number of events. |
ePO extension
The ePO extension is not updated in 26.4.1.
EPM for Windows 26.4.1
🆕 New features
- QuickStart V2: One Windows policy for desktop and server. See Highlights.
- Added support for smart cards managed by 3rd party key storage providers. See Highlights.
✨ Enhancements
.NET runtime updated to 10.0.14
Updated the .NET runtime bundled with the endpoint app to 10.0.14 to apply Microsoft's latest security patches.
Minimum .NET Framework version is now 4.7.2
-
The minimum .NET Framework version for Power Rules, PowerShell audit scripts, Agent Protection, Trace Config and the RADIUS authentication dialog box is now 4.7.2 (previously 4.6.2). Microsoft ends support for 4.6.2 on 12 January 2027.
-
Windows Server 2019 and later include 4.7.2.
-
On Windows Server 2016, install .NET Framework 4.7.2 or later to use these features.
🛠️ Issues resolved
| Description | Resolution |
|---|---|
| An account filter on an Application Rule was ignored when the rule matched an uninstaller, so the rule applied to everyone the Workstyle covers. | Uninstaller rules now honor the account filter for uninstalls started from Settings, Control Panel, or the command line, and apply only to the accounts in the filter. |
| When Endpoint Privilege Management elevated an Electron application that requires administrator rights for a standard user, the application could open a blank window and then close within a second of launch. | Electron applications that require administrator rights now open and run correctly when Endpoint Privilege Management elevates them for a standard user. |
| A child process launched from the Open or Save dialog of an elevated application could keep the elevated rights when the rule matched the built-in Any Application group. | The new secure built-in groups, such as <Any Application>, now force standard user rights on these dialogs. Policies that still use the deprecated Any groups keep the previous behavior until you switch them to the new groups, which Policy Assistant offers as a one-click fix. |
| When an application had Force standard user rights on File Open/Save common dialogs enabled, a Content Rule that allows access could let users create, rename, delete, or overwrite protected files from the Open or Save dialog. | Users can no longer create, rename, delete, or overwrite protected files from these dialogs when this option is enabled, even when a Content Rule allows access. |
| The Privilege Management service could stop unexpectedly if a policy update was applied while a COM elevation with a PowerRules script was in progress. | The Privilege Management service now keeps running when a policy update is applied during a COM elevation with a PowerRules script. |
| The Privilege Management service could stop unexpectedly if a policy update was applied while a process that inherits its rule from its parent process was starting. | The Privilege Management service now keeps running when a policy update is applied while a process that inherits its rule from its parent process is starting. |
Windows endpoints running Cortex XDR could stop unexpectedly with a KMODE_EXCEPTION_NOT_HANDLED blue screen error when Cortex XDR scanned running processes. | Windows endpoints running Cortex XDR no longer stop with a blue screen error when Cortex XDR scans running processes. |
| When an Application Rule elevated Windows Settings, choosing Restart or Shut down from the Windows Start menu could do nothing, and no error appeared. | Restart and Shut down now work as expected when an Application Rule elevates Windows Settings. |
| Processes matched through Child Inheritance, from grandchildren onward, could be missing application details such as the file path and hashes in their audit events, or might not receive the rule’s admin rights. | Processes matched through Child Inheritance at every level now receive the rule’s admin rights, and their audit events include the full application details. |
| Audit events for child processes that inherited a rule through Child Inheritance showed a blank Application Group in Analytics, so you couldn’t filter or report on child process activity by Application Group. | These audit events now show the Application Group, so you can filter and report on child process activity by Application Group in Analytics. |
| Application Rules that match on Product Name or Product Description could fail to match an application whose file version information was non-standard, so a different rule applied instead. | These rules now match correctly when an application’s file version information is non-standard. |
| Agent Protection could turn back on soon after it was suspended with an uninstall token, which blocked the uninstall of Package Manager and the PMC Adapter. This happened when something checked the PMC Adapter’s service status, such as a WMI query. | Agent Protection now stays suspended after you suspend it with an uninstall token, even when something checks the PMC Adapter’s service status, so you can uninstall Package Manager and the PMC Adapter. |
| Audit events for blocked applications reported the rule’s token, such as Add Admin Rights or Custom, instead of Passive (No Change). | Block events in the event log, BeyondInsight, ePO, and PMC now report Passive (No Change), and the [PG_TOKEN_NAME] variable in audit scripts and messages returns Unmodified for Block rules. |
EPM for Mac 26.4.1
🛠️ Issues resolved
| Description | Resolution |
|---|---|
| When an installer package inside an application bundle triggered a message, the message showed the enclosing application instead of the package. As a result, Program Path and Program Name told users they were approving the application, not the package that would actually run. | Messages triggered by an installer package inside an application bundle now show the package in Program Path and Program Name. |
With Anti-Tamper enabled, root-context scripts, such as audit scripts deployed by MDM, couldn’t read EPM settings from defendpoint.plist and returned blank output with no error. | You can now run pmfmdiag settings to report the effective settings without disabling Anti-Tamper. The output includes a SHA-256 digest that you can use to compare configuration across endpoints. |
| On Macs set to a time zone other than UTC, the BeyondTrust Application recorded incorrect start and stop times for Just-In-Time Admin sessions. | The BeyondTrust Application now records the correct Just-In-Time Admin session start and stop times in every time zone. |
| On macOS 26, Apple renamed the code-signing authority for the Privacy & Security pane in System Settings, so the QuickStart rule for that pane stopped matching. Standard users on the High Flexibility and Medium Flexibility Workstyles who changed a setting such as Full Disk Access saw a weaker confirmation prompt instead of the Support Desk challenge their Workstyle defines. | The QuickStart rule now matches the renamed code-signing authority, and users on the affected Workstyles see the Support Desk challenge again. To restore this control, re-apply the updated QuickStart template to existing macOS policies. |
🔐 Security fixes
| Component | Security fixes | Details |
|---|---|---|
| BeyondTrust Privilege Management App | 1 | Third-party framework update. |
| Web Policy Editor | 1 | Third-party runtime update. |
| Privilege Management Reporting | 3 | Third-party framework update and build credential hardening. |
| EPM for Windows | 16 | Anti-tamper hardening, privilege-boundary and memory-protection fixes, and third-party runtime and library updates. |
| EPM for Mac | 0 | None in this release. |
🔄 Compatibility
| Component | Recommended | Also supported |
|---|---|---|
| BeyondTrust Privilege Management App | 26.4.2 | |
| ePO extension | Not updated in 26.4.1 | |
| PM Reporting Database | 26.4.2.1 | |
| EPM for Windows | 26.4.1.273 | 26.3.1.289 | 26.2.1.417 | 26.1.23.0 | 25.8.12.0 | 25.4.270.0 | 25.4.184.0 | 25.2.1.0 | 24.8.98.0 | 24.7.425.0 | 24.5.361.0 |
| EPM for Mac | 26.4.1.2 | 26.3.2.1 | 26.2.1.1 | 26.1.0.120 | 25.8.0.53 | 25.4.2.2 | 25.4.1.2 | 25.2.0.1 | 24.8.0.1 | 24.7.0.1 | 24.5.2.3 | 24.5.1.1 | 24.5.0 |
Build numbers
| Component | Build |
|---|---|
| Web Policy Editor | 26.4.1.28 |
| EPM for Windows | 26.4.1.273 |
| EPM for Mac | 26.4.1.2 |
| PM Reporting | UI 26.4.1.4, Database 26.4.2.1 |
| Event Collector | 26.4.1.4 |
| Policy templates / QuickStart | v16.2.0 |