Privilege (computing)
computing term; delegation of authority to perform security-relevant functions on a computer system
In computing, privilege is defined as the delegation of authority to perform security-relevant functions on a computer system. A privilege allows a user to perform an action with security consequences. Examples of various privileges include the ability to create a new user, install software, or change kernel functions.
Users who have been delegated extra levels of control are called privileged. Users who lack most privileges are defined as unprivileged, regular, or normal users.
Theory
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 MS-DOS - 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.
The public source identifies “Privilege (computing)” as computing term; delegation of authority to perform security-relevant functions on a computer system. This brief keeps that definition visible, then builds a research path around Privilege, computing and term.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Privilege (computing)”, the useful work is to connect “computing term; delegation of authority to perform security-relevant functions on a computer system” to the records capable of establishing context and consequence.
Datasets, specimens, observations and peer-reviewed methods provide the appropriate test for the technical claims summarized here. The source revision retrieved here is dated Jun 26, 2026. The linked authority identifier is Q3404265. None of the 0 selected statements returned an explicit reference.
Current terminology should not be projected backward without checking the classification used when the underlying evidence was created. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Check terminology, classification and the date of the cited evidence. Scientific names and technical consensus can change while older records retain historical value.
- Current terminology
- Classification context
- Finding cited technical literature
Primary datasets, specimen catalogues, standards bodies and the most recent peer-reviewed literature.
Three-step research path
- Establish the record: confirm the title “Privilege (computing)”, its source revision and the description used here.
- Expand the search: follow Privilege (computing) primary sources, Privilege (computing) archive and Privilege research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Privilege (computing)”?
- Has classification or technical consensus changed since the cited source?
- Which observation, specimen, dataset or publication supports the account?
Search terms from this dossier
This entry incorporates text from “Privilege (computing)” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.