User Account Control (UAC)
What is User Account Control (UAC)?
User Account Control (UAC)A Windows security feature introduced in Vista that runs interactive sessions with a limited token and prompts for consent or credentials before an administrative action elevates.
User Account Control (UAC) is a Windows access-control feature Microsoft introduced in Windows Vista and refined in subsequent releases. When an administrator logs on, Windows generates two tokens — a filtered standard token used for normal activity and a full administrator token. Any operation that requires elevation triggers the Consent UI (secure desktop prompt), and only after approval does the full token apply. UAC mitigates malware that runs as the user by forcing explicit confirmation for actions such as installing drivers or modifying HKLM. It is not a security boundary on its own — Microsoft documents that UAC prompts on the standard desktop can be bypassed by trusted auto-elevating processes, which is why attackers chase UAC-bypass techniques (fodhelper, computerdefaults, ICMLuaUtil). Defenders set UAC to Always Notify and combine it with LAPS, AppLocker, and EDR.
● Examples
- 01
A standard user clicking Run as administrator on regedit triggers the secure-desktop UAC prompt for credentials.
- 02
Attackers using fodhelper.exe to auto-elevate a payload by abusing the Windows shell registry to bypass UAC.
● Frequently asked questions
What is User Account Control (UAC)?
A Windows security feature introduced in Vista that runs interactive sessions with a limited token and prompts for consent or credentials before an administrative action elevates. It belongs to the Identity & Access category of cybersecurity.
What does User Account Control (UAC) mean?
A Windows security feature introduced in Vista that runs interactive sessions with a limited token and prompts for consent or credentials before an administrative action elevates.
How does User Account Control (UAC) work?
User Account Control (UAC) is a Windows access-control feature Microsoft introduced in Windows Vista and refined in subsequent releases. When an administrator logs on, Windows generates two tokens — a filtered standard token used for normal activity and a full administrator token. Any operation that requires elevation triggers the Consent UI (secure desktop prompt), and only after approval does the full token apply. UAC mitigates malware that runs as the user by forcing explicit confirmation for actions such as installing drivers or modifying HKLM. It is not a security boundary on its own — Microsoft documents that UAC prompts on the standard desktop can be bypassed by trusted auto-elevating processes, which is why attackers chase UAC-bypass techniques (fodhelper, computerdefaults, ICMLuaUtil). Defenders set UAC to Always Notify and combine it with LAPS, AppLocker, and EDR.
How do you defend against User Account Control (UAC)?
Defences for User Account Control (UAC) typically combine technical controls and operational practices, as detailed in the full definition above.
What are other names for User Account Control (UAC)?
Common alternative names include: User Account Control, UAC prompt.
● Related terms
- identity-access№ 1002
SeDebugPrivilege
A powerful Windows user-right that lets a holder open, read, and modify the memory of any process — including LSASS — making it a prime target for attackers seeking credential theft.
- identity-access№ 1162
Token Impersonation
A Windows privilege-escalation technique (MITRE ATT&CK T1134) where an attacker duplicates an existing access token and uses it to run code in another user's security context.
- vulnerabilities№ 860
Privilege Escalation
A class of vulnerabilities that lets an attacker gain rights beyond those originally granted, such as moving from a normal user to administrator.