QuickStart policy adoption guide
Prepare for the new Windows QuickStart policy
The new QuickStart policies reduce how much privilege your users get when they elevate an application, and it governs far more of the built-in tools that attackers use to move through a network. Because it changes the privilege model rather than adding to it, plan your move rather than importing it into a live environment. This guide tells you what changes, what needs your attention first, and how to roll it out safely.
Scope of this guide
This guide covers the Windows QuickStart policy for Endpoint Privilege Management (EPM) for Windows. It is written for the administrator who maintains your EPM policy.
Moving to the new policy is your choice
If you already use the Windows QuickStart policy, it stays exactly as it is. BeyondTrust does not migrate it automatically or replace it with the new policy. You decide whether to adopt the new policy, and when.
Nothing changes on your endpoints until you turn it on
Every Workstyle except SYSTEM is inactive. Importing the policy applies nothing to your endpoints. Changes take effect only after you activate a Workstyle and assign it to computers, so you can import the policy today and take as long as you need to review it.
What is changing
The previous policy elevated almost everything to full administrator. The new policy introduces a second, smaller privilege level and uses it for most elevations so a compromised process has much less to work with.
| Previous policy | New policy | |
|---|---|---|
| Workstyles | 6 (5 disabled at import) | 6 (5 disabled at import) |
| Application Groups | 27 | 52 |
| Messages | 7 | 9 |
| Governed living-off-the-land tools | ~34 | ~145 |
| Privilege levels | Full admin only | Full admin and basic admin |
| Ability to remove admin rights | Not available | Available |
Most elevations now grant reduced privileges. User Account Control (UAC) prompts elevate to basic admin instead of full admin in most tiers.
Changes that need your attention first
Review these before you activate anything in production.
1. DLL blocking is now a separate Policy Editor feature
The Microsoft Recommended Blocked DLLs group (16 entries, including WSL libraries, mfc40.dll, MSBuild, and WebDAV client DLLs) is no longer built into the QuickStart policy. DLL blocking is now a separate Policy Editor feature that adds the group to your policy when you turn it on.
What to do: If you relied on that group, enable DLL blocking in the Policy Editor instead of recreating the rules by hand.
2. Custom applications need remapping
If you added applications to Add Admin - Medium Flexibility or Add Admin - Low Flexibility, those groups are now empty placeholders under new names. Your entries do not carry across on their own.
What to do: For each application you added, decide whether it needs full admin or whether basic admin is enough, then add it to the matching Add Full Admin or Add Basic Admin group. See Application Group name changes for the full mapping.
3. Legacy ActiveX controls have narrower coverage
ActiveX controls (.ocx) now appear only in the unsigned Any UAC Prompt group. They are no longer included in the signed variant.
Microsoft retired ActiveX along with Internet Explorer in 2022, so any unknown use of an ActiveX control now carries the same level of risk as an unsigned process.
What to do: If you still run signed ActiveX controls, govern them with an explicit rule.
4. The Notification (Trusted) message no longer exists
Any rule that references this message needs updating. Allow Notification is the closest replacement.
What to do: Search your customized rules for references to Notification (Trusted) and repoint them.
What you gain
A second, smaller privilege level
Add Basic Admin grants elevated privileges with a reduced privilege set. It now handles most elevation scenarios: UAC prompts, restricted system functions, and built-in Windows tools. It limits lateral movement and credential access even if the elevated process is compromised.
Add Full Admin grants the complete local administrator token; the same as the old Add Admin. The new policy reserves it for cases that genuinely need it, such as hardware wizards, debugging tools, and support desk sessions.
The ability to remove admin rights
The new Drop Admin token strips administrator privileges from a process that starts with an admin token but does not need one. The policy ships with one example: the Microsoft Teams Add-in Installer.
Group membership without elevation
Add Admin Group Membership adds the user to the local Administrators group without elevating the process token. This suits applications that check group membership rather than actual privilege — Windows System Settings, for instance.
Coverage of living-off-the-land tools
Living-off-the-land binaries and scripts (LOLBAS) are built-in Windows tools that attackers abuse. The new policy governs about 145 of them, up from about 34, including command shells, debuggers, script hosts, and remote assistance tools.
Some of the newly governed tools are ones your users touch daily, so review these before your pilot:
- Windows Terminal and WSL:
wsl.exe,wslhost.exe, and the Bash launcher are in the recommended restricted group. Windows Terminal is the first Store app in a LOLBAS group. - Microsoft Edge and Edge WebView2: governed for the first time.
- Windows Task Manager and Microsoft Management Console (
mmc.exe): everyday administrative tools that now fall under governance. - PowerShell 7 (
pwsh.exe) is now governed, and single entries for Windows PowerShell and PowerShell ISE replace the separate 32-bit and 64-bit entries.
See Newly governed tools by category for the full list.
If your developers use WSLElevated WSL launches were already gated. With the Restricted LOLBAS groups in use, High and Medium Flexibility users verify their identity when they launch WSL tools with elevation. If that's disruptive, move those users into explicit Add Basic Admin groups to reduce prompts while keeping the audit trail.
BeyondTrust maintains these definitions. Entries carry a (BT) prefix and update with each policy release, so you no longer track new entries yourself.
Blocking in every tier
Microsoft Recommended Blocks, 36 applications, now apply in each flexibility Workstyle (High, Medium, and Low) instead of Low Flexibility only. Every tier gets that protection.
An audit-only path for unknown applications
The previous policy used one (Default) Any Application rule as the catch-all for both normal and right-click elevation. The new policy splits it in two:
(Default) Add Basic Admin — Any Application (On-Demand): Strictly governs explicit user action through the right-click shell extension, elevating to basic admin.(Default) Passive — Any Application: Silently audits unclassified applications without elevating privileges.
The policy also contains a hidden, BeyondTrust-managed group named <Any Application>. No rule targets it directly. Instead, most application definitions in the policy use it as their child application group, so any process started by an elevated application matches it and inherits the parent’s privileges. You don’t need to add it to a rule, and you shouldn’t edit or remove it.
Use the audit data to decide whether to write an allow, elevation, or block rule.
Start passive, then tightenThe Passive - Restricted LOLBAS group audits PowerShell, WScript, MSHTA, and remote support tools rather than blocking or elevating them. Use that audit data to decide what to restrict, then promote entries to basic admin or block as your security posture matures.
Migrate to the new policy
Step 1: Back up and review
- Export your existing Windows QS policy and store the backup outside EPM.
- Note which Workstyles are enabled and which flexibility tier each user group is assigned to.
- List your customizations: populated Medium or Low Flexibility groups, custom messages, modified rules for restricted tools, and any non-standard filters.
Step 2: Map your customizations
- For each application in Add Admin - All Users (Business Apps), decide whether it needs full admin or basic admin. Add it to Add Full Admin - All Users or Add Basic Admin - All Users.
- Move applications from the old Add Admin - High/Medium/Low Flexibility groups into the matching Add Basic Admin or Add Full Admin tier group.
- Move applications from Passive - High/Medium/Low Business Apps into Passive - High/Medium/Low Flexibility.
- Move blocked applications from Block - Blocked Apps into Block - All Users, or into a tier-specific block group.
- If you relied on DLL blocking, enable it in the Policy Editor.
Leave the (BT) entries aloneA
(BT)prefix marks a BeyondTrust-maintained application definition. Do not remove or change these. BeyondTrust updates them in future policy releases. Add your own entries without the prefix so you can tell them apart at a glance.
Step 3: Pilot
- Import the new policy as a separate policy. Do not overwrite your live policy.
- Enable the All Users Workstyle in a test group first. Verify blocking and basic elevation before you touch the flexibility tiers.
- Enable one flexibility tier at a time. Start with High Flexibility — it is the least disruptive to test.
- Monitor audit events for unexpected blocks and elevations, especially for built-in Windows tools now governed by the Restricted LOLBAS groups. Expect fewer prompts overall: removing the overlapping UAC categories stops one launch from triggering several prompts.
Step 4: Verify and roll out
Confirm that your pilot users can complete their normal work, that no business application is unexpectedly blocked, and that prompt volume is manageable. Then extend the enabled Workstyles to your production groups one tier at a time.
Tell your users what to expect
Send your users a note before you enable the policy. The changes they notice are small but they generate helpdesk calls if they arrive unannounced. Copy and adapt the following:
We are updating how your computer handles applications that need administrator access.
When you run some tools that need administrator access, command-line and scripting tools in particular, you may be asked to confirm your identity or give a reason. This is expected. Follow the prompt as usual, and contact the helpdesk if a tool you need for your job is blocked.
Review your pilot audit logs before you send this. They tell you which applications newly prompt in your environment, so you can name the specific tools your users care about.
Reference
Application Group name changes
Groups now follow a consistent pattern: [Action] - [Scope] [(On-Demand)]. The action prefix is Add Full Admin, Add Basic Admin, Drop Admin, Passive, or Block.
| Previous group | New equivalent |
|---|---|
| Add Admin - All Users (Business Apps) [16 apps] | Add Basic Admin - All Users [5 apps], plus tier-specific groups |
| Add Admin - All Users (Windows Functions) [15 apps] | Add Full Admin - All Users [6 apps] |
| Add Admin - High Flexibility [11 apps] | Add Basic Admin / Add Full Admin - High Flexibility (empty; populate as needed) |
| (Recommended) Restricted Functions [32 apps] | (Recommended) Add Basic Admin - Restricted LOLBAS [145 apps] |
| (Recommended) Restricted Functions (On-Demand) [34 apps] | (Recommended) Add Basic Admin - Restricted LOLBAS (On-Demand) [144 apps] |
| Passive - Allowed Functions & Apps [10 apps] | Passive - All Users [13 apps] |
| Block - Blocked Apps [3 apps] | Block - All Users [3 apps] |
| Passive - High/Medium/Low Business Apps (empty) | Passive - High/Medium/Low Flexibility (empty) |
| No equivalent | Add Admin Group - High Flexibility [2 apps] |
| No equivalent | Drop Admin - All Users [1 app] |
Workstyle changes
| Workstyle | Assignments | What changed |
|---|---|---|
| All Users | 7 → 14 | Becomes the primary enforcement layer. Separate full admin and basic admin paths replace the single Add Admin path. Drop Admin added. |
| High Flexibility | 15 → 21 | UAC prompts elevate to basic admin instead of full admin. New group membership token for System Settings. Full admin for 10 debugging tools, basic admin for 145 restricted tools, both with authentication and reason prompts. On-demand catch-all remains. |
| Medium Flexibility | → 22 | Same two-tier model as High Flexibility, with support desk authentication for restricted tools. Trusted and signed UAC uses a yes/no prompt; signed UAC uses select reason; any UAC uses authentication and reason. |
| Low Flexibility | → 20 | Most restrictive tier. Microsoft Recommended Blocks remain here and now also apply in High and Medium Flexibility. All UAC prompt types use basic admin with a support desk prompt. No general on-demand catch-all. All users request access through the support desk. |
| SYSTEM | 1 rule | Keep Privileges for Restricted System Functions. Anti-tamper protection is the primary function. CaptureHostInfo is enabled. |
| Administrators | 1 rule | Screen Readers via the Add System Integrity token. Remains disabled by default. |
LOLBAS Application Groups
Five Application Groups now govern living-off-the-land tools. Three are new.
| Application Group | Previous count | New count | Action |
|---|---|---|---|
| Add Basic Admin - Restricted LOLBAS | 32 | 145 | Add basic admin, with authentication prompt |
| Add Basic Admin - Restricted LOLBAS (On-Demand) | 34 | 144 | Add basic admin, with authentication prompt |
| Add Full Admin - Restricted LOLBAS | — | 10 | Add full admin, with authentication prompt |
| Add Full Admin - Restricted LOLBAS (On-Demand) | — | 10 | Add full admin, with authentication prompt |
| Passive - Restricted LOLBAS | — | 9 | Passive, audit only |
Newly governed tools by category
These functional categories are governed in the LOLBAS Application Groups for the first time. All entries are executables unless noted.
| Category | Notable entries and security rationale |
|---|---|
| Shell and scripting | Sudo, ScriptRunner, RunScriptHelper, MSHTA, CScript, WScript |
| System administration | Microsoft Management Console (mmc.exe), Server Manager, Windows Task Manager, Settings (admin flow), SCM Config Tool |
| Network and security | OpenSSH for Windows, BITS utility (bitsadmin), Network Command Shell (netsh), Packet Monitor (pktmon), CertUtil |
| Permission tools | ICACLS, takeown, cacls, SubInAcl — all four primary tools used to manipulate access control lists (ACLs) and object ownership. |
| Package and install tools | WinGet (local manifest mode), Web Deploy, .NET installer, Windows Installer DLL execution path (includes both exe and msi types). |
| Browser | Microsoft Edge and Edge WebView2 governed in a LOLBAS group for the first time |
| Developer toolchain | MSBuild, Roslyn compiler (csc.exe), AddInProcess, AddInUtil, aspnet_compiler, SQL PowerShell |
| Volume shadow and storage | Disk Shadow (diskshadow.exe) — commonly abused by attackers to extract credentials from Volume Shadow Copies (VSS). |
| Microsoft Teams | A specific Teams launch path that can be used to bypass restrictions |
Message changes
Only these messages changed. The Authentication & Reason, Select Reason, Support Desk, and Yes / No allow messages, Block Message, and Block Notification are unchanged.
| Message | Status | Notes |
|---|---|---|
| Allow Notification | New | Informational only. No authentication or reason required. |
| Request Message | New | Asks the user for a reason and sends an authorization request through your helpdesk integration. |
| Notification (Trusted) | Removed | Replaced by Allow Notification. Update any rule that references it. |
Application type coverage
UAC groups govern what happens when a process requests elevation and matches no more specific rule. Their type composition has changed.
| UAC group | Previous types | New types | Difference |
|---|---|---|---|
| Any Trusted & Signed UAC Prompt | exe, com, msi | exe, com, msi | Redundant *.msp Installer definition removed. Still covered by the * Installer definition. |
| Any Signed UAC Prompt | exe, com, msi, ocx | exe, com, msi, unex | Redundant *.msp Installer definition removed. ocx removed and unex added. |
| Any UAC Prompt | exe, com, msi, ocx | exe, com, msi, ocx, unex | Redundant *.msp Installer definition removed. unex added. |
Note: The previous UAC groups contained two Installer definitions: one matching any filename (*) and one matching *.msp. The * definition already covers .msp files, so the new policy drops the separate *.msp definition. Patch files are still governed as before, and you don't need to change anything.
Two more changes reduce prompts. A new (Default) Passive - Windows Store App Parent Process group audits child processes of Store apps, which previously fell through to the catch-all. And Passive - All Users now includes trusted installer packages, Windows Installer embedding, and Microsoft Teams.
Related resources
- BeyondTrust EPM documentation
- Windows QuickStart policy release notes in the Management Console under Help > Release Notes
- BeyondTrust Support
- LOLBAS project reference
For questions about your specific environment, contact your BeyondTrust account team or open a support case.
Updated about 4 hours ago