Privilege (computing)

<h2 id="theory">Theory</h2>
Privileges can either be automatic, granted, or applied for. 
An automatic privilege exists when there is no requirement to have permission to perform an action. For example, on systems where people are required to log into a system to use it, logging out will not require a privilege. Systems that do not implement file protection - such as <a href="/facts/MS-DOS/fVrrz1uN">MS-DOS</a> - essentially give unlimited privilege to perform any action on a file.
A granted privilege exists as a result of presenting some credential to the privilege granting authority. This is usually accomplished by logging on to a system with a <a href="/facts/User_(computing)/zQRzG0KG">username</a> and <a href="/facts/Password/WEoul230">password</a>, and if the username and password supplied are correct, the user is granted additional privileges.
A privilege is applied for by either an executed program issuing a request for advanced privileges, or by running some program to apply for the additional privileges. An example of a user applying for additional privileges is provided by the <a href="/facts/Sudo/7jhmGdqg">sudo</a> command to run a command as <a href="/facts/Superuser/0Brr6ol7">superuser (root)</a> user, or by the <a href="/facts/Kerberos_(protocol)/RMXs3P1w">Kerberos</a> authentication system.
Modern processor architectures have multiple <a href="/facts/CPU_modes/XuWr6Gg1">CPU modes</a> that allows the OS to run at different <a href="/facts/Protection_ring/27y4kjHs">privilege levels</a>. Some processors have two levels (such as user and supervisor); <a href="/facts/I386/ag5eSgWv">i386</a>+ processors have four levels (#0 with the most, #3 with the least privileges). Tasks are tagged with a privilege level. Resources (segments, pages, ports, etc.) and the privileged instructions are tagged with a demanded privilege level. When a task tries to use a resource, or execute a privileged instruction, the processor determines whether it has the permission (if not, a "protection fault" interrupt is generated). This prevents user tasks from damaging the OS or each other.
In computer programming, exceptions related to privileged instruction violations may be caused when an array has been accessed out of bounds or an invalid pointer has been dereferenced when the invalid memory location referenced is a privileged location, such as one controlling device input/output. This is particularly more likely to occur in programming languages such as <a href="/facts/C_(programming_language)/Ky2No763">C</a>, which use pointer arithmetic or do not check array bounds automatically.

<h3>Criticism</h3>
Mark Miller has critiqued the framing of privilege as being poorly defined and hard to measure, and suggested that authority can be defined as the set of things a program can do, which is more helpful.<a class="footnote-ref" id="fnref:2" href="#fn:2">2</a>

<h2 id="unix">Unix</h2>
On <a href="/facts/Unix-like/YAKrAxzd">Unix-like</a> systems, the <a href="/facts/Superuser/0Brr6ol7">superuser</a> (commonly known as 'root') owns all the privileges. Ordinary users are granted only enough permissions to accomplish their most common tasks. UNIX systems have built-in security features. Most users cannot set up a new user account nor do other administrative procedures. The user “root” is a special user, something called super-user, which can do anything at all on the system. This high degree power is necessary to fully administer a UNIX system, but it also allows its user to make a mistake and cause system problems. 
Unprivileged users usually cannot:

<ul><li>Adjust <a href="/facts/Kernel_(operating_system)/uEj4U3Rz">kernel</a> options;</li>
<li>modify system files, or files of other users.</li>
<li>change the ownership of any files;</li>
<li>change the <a href="/facts/Runlevel/zLSVXQ7o">runlevel</a> (on systems with <a href="/facts/UNIX_System_V/Epm6GEY4">System V</a>-style initialization);</li>
<li>change the file mode of any files;</li>
<li>adjust ulimits or <a href="/facts/Disk_quota/ld30QhUB">disk quotas</a>;</li>
<li>start, stop and remove <a href="/facts/Daemon_(computing)/bzuEVGGX">daemons</a>;</li>
<li>signal processes of other users;</li>
<li>create <a href="/facts/Device_file/t8ISnXft">device nodes</a>;</li>
<li>create or remove users or groups;</li>
<li>mount or unmount volumes (although it is becoming common to allow regular users to mount and unmount <a href="/facts/Removable_media/CGJoaUF3">removable media</a>, such as <a href="/facts/Compact_disc/g51GRloc">compact discs</a> - this is typically accomplished via <a href="/facts/Filesystem_in_Userspace/RnSLIf1H">FUSE</a>);</li>
<li>execute the contents of any sbin/ directory (although it is becoming common to simply restrict the behavior of such programs when executed by regular users);</li>
<li><a href="/facts/Port_(computer_networking)/ygoHVKNC">bind ports</a> below 1024.</li></ul>
<h2 id="windows-nt">Windows NT</h2>
On <a href="/facts/Windows_NT/EtccWvxQ">Windows NT</a>-based systems, privileges are delegated in varying degrees. These delegations can be defined using the local security policy manager (secpol.msc). The following is an abbreviated list of the default assignments:

<ul><li>'NT AUTHORITY\System' is the closest equivalent to the Superuser on Unix-like systems. It has many of the privileges of a classic Unix superuser (such as being a trustee on every file created);</li>
<li>'Administrator' is one of the closest equivalents to the superuser (root) on Unix-like systems. However, this user cannot override as many of the operating system's protections as the superuser can;</li>
<li>members of the 'Administrators' group have privileges almost equal to 'Administrator';</li>
<li>members of the 'Power Users' group have the ability to install programs and <a href="/facts/Backup/ldV72CkU">backup</a> the system.</li>
<li>members of the 'Users' group are the equivalent to unprivileged users on Unix-like systems.</li></ul>
Windows defines a number of administrative privileges<a class="footnote-ref" id="fnref:3" href="#fn:3">3</a> that can be assigned individually to users and/or groups. An account (user) holds only the privileges granted to it, either directly or indirectly through group memberships. Upon installation a number of groups and accounts are created and privileges are granted to them. However, these grants can be changed at a later time or though a <a href="/facts/Group_Policy/FGn7Kluc">group policy</a>. Unlike Linux, no privileges are implicitly or permanently granted to a specific account.
Some administrative privileges (e.g. taking ownership of or restoring arbitrary files) are so powerful that if used with malicious intent they could allow the entire system to be compromised. With <a href="/facts/User_Account_Control/BjUhEq9u">user account control</a> (on by default since <a href="/facts/Windows_Vista/IASEUCTB">Windows Vista</a>) Windows will strip the user token of these privileges at login. Thus, if a user logs in with an account with broad system privileges, he/she will still not be running with these system privileges. Whenever the user wants to perform administrative actions requiring any of the system privileges he/she will have to do this from an elevated process. When launching an elevated process, the user is made aware that his/her administrative privileges are being asserted through a prompt requiring his/her consent. Not holding privileges until actually required is in keeping with the <a href="/facts/Principle_of_least_privilege/sqsT4tln">principle of least privilege</a>.
Elevated processes will run with the full privileges of the user, not the full privileges of the system. Even so, the privileges of the user may still be more than what is required for that particular process, thus not completely <a href="/facts/Principle_of_least_privilege/sqsT4tln">least privilege</a>.
The DOS-based <a href="/facts/Windows_Me/fjENFRNa">Windows ME</a>, Windows 98, Windows 95 and previous versions of non-NT Windows only operated on the FAT filesystem, did not support filesystem permissions<a class="footnote-ref" id="fnref:4" href="#fn:4">4</a> and therefore privileges are effectively defeated on Windows NT-based systems that do not use the <a href="/facts/NTFS/dryNM3BK">NTFS</a> file system.

<h3>Nomenclature</h3>
The names used in the Windows source code end in either "privilege" or "logonright". This has led to some confusion about what the full set of all these "rights" and "privileges" should be called.
Microsoft currently uses the term "user rights".<a class="footnote-ref" id="fnref:5" href="#fn:5">5</a>
In the past some other terms have also been used by Microsoft, such as "privilege rights"<a class="footnote-ref" id="fnref:6" href="#fn:6">6</a>
, "logon user rights"<a class="footnote-ref" id="fnref:7" href="#fn:7">7</a>
and "nt-rights".<a class="footnote-ref" id="fnref:8" href="#fn:8">8</a>

<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/File-system_permissions/DHq5SwI4">File-system permissions</a></li>
<li><a href="/facts/Kernel_(operating_system)/uEj4U3Rz">Kernel (operating system)</a></li>
<li><a href="/facts/Principle_of_least_privilege/sqsT4tln">Principle of least privilege</a></li>
<li><a href="/facts/Superuser/0Brr6ol7">Superuser</a></li>
<li><a href="/facts/Privilege_escalation/STzSAaf5">Privilege escalation</a></li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1">"Glossary". CSRC. NIST. Archived from the original on 13 February 2019. Retrieved 12 February 2019. <a href="https://web.archive.org/web/20190213005620/https://csrc.nist.gov/glossary/term/privileged-user" target="_blank">https://web.archive.org/web/20190213005620/https://csrc.nist.gov/glossary/term/privileged-user</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></li>
<li id="fn:2">Miller, Mark (2006). Robust Composition: Towards a Unified Approach to Access Control and Concurrency Control. PhD Theses. Johns Hopkins University. <a href="http://www.erights.org/talks/thesis/" target="_blank">http://www.erights.org/talks/thesis/</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></li>
<li id="fn:3">"Privilege constants". Microsoft. 7 April 2022. <a href="http://msdn.microsoft.com/en-us/library/bb530716.aspx" target="_blank">http://msdn.microsoft.com/en-us/library/bb530716.aspx</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></li>
<li id="fn:4">"How permissions work". Microsoft. 3 July 2013. You can set permissions at the file level only if the files are stored on an NTFS volume. <a href="https://technet.microsoft.com/en-us/library/cc783530(WS.10).aspx" target="_blank">https://technet.microsoft.com/en-us/library/cc783530(WS.10).aspx</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></li>
<li id="fn:5">"User rights". Microsoft TechNet library. 18 June 2014. Userrights include logon rights and privileges. <a href="https://technet.microsoft.com/en-us/library/dd349804(v=ws.10).aspx" target="_blank">https://technet.microsoft.com/en-us/library/dd349804(v=ws.10).aspx</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></li>
<li id="fn:6">"Privilege rights". Microsoft MSDN library. 23 April 2024. <a href="http://msdn.microsoft.com/en-us/library/cc232779(prot.20).aspx" target="_blank">http://msdn.microsoft.com/en-us/library/cc232779(prot.20).aspx</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></li>
<li id="fn:7">"How to set logon user rights by using the ntrights utility". Microsoft support. <a href="http://support.microsoft.com/kb/315276" target="_blank">http://support.microsoft.com/kb/315276</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></li>
<li id="fn:8">"How to set logon user rights by using the ntrights utility". Microsoft support. <a href="http://support.microsoft.com/kb/315276" target="_blank">http://support.microsoft.com/kb/315276</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></li>
</ol>

Privilege (computing) open-in-new

Privilege (computing)