A security administrator needs to harden a standalone Windows 11 Enterprise computer by ensuring that only digitally signed executables can request privilege elevation, while requiring administrators to re-enter credentials on a dimmed, isolated desktop. Place the administrative configuration and verification steps in the correct chronological order.
- 1Launch the Local Security Policy console by executing secpol.msc from an elevated prompt.
- 2Expand Security Settings and navigate to Local Policies > Security Options.
- 3Enable the policy 'User Account Control: Only elevate executables that are signed and validated'.
- 4Set 'User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode' to 'Prompt for credentials on the secure desktop'.
- 5Execute an unsigned installation package to verify that elevation is automatically denied.
Answer
The correct sequence begins with launching secpol.msc, navigating to Security Options under Local Policies, enabling the policy to only elevate signed and validated executables, configuring administrator prompt behavior to require credentials on the secure desktop, and finally testing the policy by executing an unsigned application.
The correct procedural order requires launching the Local Security Policy console (secpol.msc), navigating to Local Policies -> Security Options, enabling digital signature enforcement for elevated binaries, setting administrative prompt behavior to require credentials on the secure desktop, and finally executing a verification test using an unsigned binary.
Step-by-Step Solution
Key Concept
Windows Local Security Policy configuration for User Account Control (UAC) code signing enforcement and secure desktop privilege elevation behavior
Estimated Time:2m 0s