UAC

(redirected from User Account Control)
Also found in: Medical, Acronyms, Wikipedia.

UAC

(User Account Control) The management of user accounts in Windows, starting with Vista. Because malware has greater control of the computer when it is running in administrator mode, UAC was designed to enable more users to run their computers as a standard user rather than as administrator. A computer is more secure against attack if it is running with fewer privileges.

Admin Approval Mode
The default mode in UAC is the Admin Approval Mode, which requires administrators to approve functions that were allowed in Windows XP without a prompt. For example, although standard users are unable to add programs, a user running as administrator does have the right to install new applications. However, in order to prevent unwanted programs from being slipped in "under the covers," the administrator must approve any installation first. See user account and account control.
References in periodicals archive ?
Forensics, reverse engineering malware, hacking techniques, and implementing defenses in the kernel, such as DEP, ASLR and User Account Control are just a few examples.
Other visual changes include a new File Explorer icon (considerably less yellow than the current version) and a new look for User Account Control (UAC) dialog boxes, which celebrate their tenth anniversary this year.
Back in 2007 when Windows Vista was released, it included a new feature called UAC (User Account Control) that resulted in a lot of headache for both the IT user and the out-there consumer.
WinRAR has been better adapted for Windows User Account Control (UAC).
oeThe UFOQ website has been designed and developed within an open source Content Management System (CMS) with highly secured and configurable User Account Control (UAC).
There's a password manager and something similar to the User Account Control (UAC) on Windows, that sets up permissions for various apps, how they go online and who has access.
Microsoft's design improves on the mistake of creating applications that require privileges and end up being funnelled inefficiently through Windows User Account Control (UAC), but leaves hanging the question of whether even standard user apps should be allowed in the first place.
Many have noted how heavy criticism of the (http://arstechnica.com/security/2008/04/vistas-uac-security-prompt-was-designed-to-annoy-you/) User Account Control (UAC) in Windows Vista , which included a number of unsolicited security pop ups, prompted (http://www.crn.com/news/applications-os/213300664/microsoft-relents-will-change-windows-7-uac.htm) Microsoft to tweak the feature in Windows 7, and use that as hope that Microsoft will do the same for Windows 8.1.
Granted, Microsoft's design improves on the mistake of creating applications that require privileges and end up being funnelled inefficiently through Windows User Account Control (UAC), but leaves hanging the question of whether even standard user apps should be allowed in the first place.
Nevertheless, while the world has moved on from the insecure mindset of old this has ended up creating a problem almost as significant as the one being solved; controlling risk by locking down applications, and shutting off privilege escalation completely using Windows 7 and Vista User Account Control (UAC).