Least Privilege
LOW ✓ MODERATE ✓ HIGHRequirements NIST SOURCE
Employ the principle of least privilege, allowing only authorized accesses for users (or processes acting on behalf of users) that are necessary to accomplish assigned organizational tasks.
Discussion (NIST Supplemental Guidance)
Organizations employ least privilege for specific duties and systems. The principle of least privilege is also applied to system processes, ensuring that the processes have access to systems and operate at privilege levels no higher than necessary to accomplish organizational missions or business functions. Organizations consider the creation of additional processes, roles, and accounts as necessary to achieve least privilege. Organizations apply least privilege to the development, implementation, and operation of organizational systems.
Enhancements NIST SOURCE
AC-6(1) Authorize Access to Security Functions LOW ✓ MODERATE ✓ HIGH
Authorize access for [individuals and roles] to:
- (a) [organization-defined security functions (deployed in hardware, software, and firmware)] ; and
- (b) [security-relevant information].
Discussion
Security functions include establishing system accounts, configuring access authorizations (i.e., permissions, privileges), configuring settings for events to be audited, and establishing intrusion detection parameters. Security-relevant information includes filtering rules for routers or firewalls, configuration parameters for security services, cryptographic key management information, and access control lists. Authorized personnel include security administrators, system administrators, system security officers, system programmers, and other privileged users.
AC-6(2) Non-privileged Access for Nonsecurity Functions LOW ✓ MODERATE ✓ HIGH
Require that users of system accounts (or roles) with access to [security functions or security-relevant information] use non-privileged accounts or roles, when accessing nonsecurity functions.
Discussion
Requiring the use of non-privileged accounts when accessing nonsecurity functions limits exposure when operating from within privileged accounts or roles. The inclusion of roles addresses situations where organizations implement access control policies, such as role-based access control, and where a change of role provides the same degree of assurance in the change of access authorizations for the user and the processes acting on behalf of the user as would be provided by a change between a privileged and non-privileged account.
AC-6(3) Network Access to Privileged Commands LOW MODERATE ✓ HIGH
Authorize network access to [privileged commands] only for [compelling operational needs] and document the rationale for such access in the security plan for the system.
Discussion
Network access is any access across a network connection in lieu of local access (i.e., user being physically present at the device).
AC-6(4) Separate Processing Domains LOW MODERATE HIGH
Provide separate processing domains to enable finer-grained allocation of user privileges.
Discussion
Providing separate processing domains for finer-grained allocation of user privileges includes using virtualization techniques to permit additional user privileges within a virtual machine while restricting privileges to other virtual machines or to the underlying physical machine, implementing separate physical domains, and employing hardware or software domain separation mechanisms.
AC-6(5) Privileged Accounts LOW ✓ MODERATE ✓ HIGH
Restrict privileged accounts on the system to [personnel or roles].
Discussion
Privileged accounts, including super user accounts, are typically described as system administrator for various types of commercial off-the-shelf operating systems. Restricting privileged accounts to specific personnel or roles prevents day-to-day users from accessing privileged information or privileged functions. Organizations may differentiate in the application of restricting privileged accounts between allowed privileges for local accounts and for domain accounts provided that they retain the ability to control system configurations for key parameters and as otherwise necessary to sufficiently mitigate risk.
AC-6(6) Privileged Access by Non-organizational Users LOW MODERATE HIGH
Prohibit privileged access to the system by non-organizational users.
Discussion
An organizational user is an employee or an individual considered by the organization to have the equivalent status of an employee. Organizational users include contractors, guest researchers, or individuals detailed from other organizations. A non-organizational user is a user who is not an organizational user. Policies and procedures for granting equivalent status of employees to individuals include a need-to-know, citizenship, and the relationship to the organization.
AC-6(7) Review of User Privileges LOW ✓ MODERATE ✓ HIGH
- (a) Review [frequency] the privileges assigned to [roles and classes] to validate the need for such privileges; and
- (b) Reassign or remove privileges, if necessary, to correctly reflect organizational mission and business needs.
Discussion
The need for certain assigned user privileges may change over time to reflect changes in organizational mission and business functions, environments of operation, technologies, or threats. A periodic review of assigned user privileges is necessary to determine if the rationale for assigning such privileges remains valid. If the need cannot be revalidated, organizations take appropriate corrective actions.
AC-6(8) Privilege Levels for Code Execution LOW MODERATE HIGH
Prevent the following software from executing at higher privilege levels than users executing the software: [software].
Discussion
In certain situations, software applications or programs need to execute with elevated privileges to perform required functions. However, depending on the software functionality and configuration, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking such applications or programs, those users may indirectly be provided with greater privileges than assigned.
AC-6(9) Log Use of Privileged Functions LOW ✓ MODERATE ✓ HIGH
Log the execution of privileged functions.
Discussion
The misuse of privileged functions, either intentionally or unintentionally by authorized users or by unauthorized external entities that have compromised system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Logging and analyzing the use of privileged functions is one way to detect such misuse and, in doing so, help mitigate the risk from insider threats and the advanced persistent threat.
AC-6(10) Prohibit Non-privileged Users from Executing Privileged Functions LOW ✓ MODERATE ✓ HIGH
Prevent non-privileged users from executing privileged functions.
Discussion
Privileged functions include disabling, circumventing, or altering implemented security or privacy controls, establishing system accounts, performing system integrity checks, and administering cryptographic key management activities. Non-privileged users are individuals who do not possess appropriate authorizations. Privileged functions that require protection from non-privileged users include circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms. Preventing non-privileged users from executing privileged functions is enforced by AC-3.
Implementation Guidance
Original engineering commentary written for this explorer — not NIST source text and not authoritative guidance.
No engineering interpretation has been authored for AC-6 yet. This section is architected to receive it — see the Requirements and Assessment sections above for the authoritative NIST source content in the meantime.
Assessment
Assessment Objectives
- the principle of least privilege is employed, allowing only authorized accesses for users (or processes acting on behalf of users) that are necessary to accomplish assigned organizational tasks.
Examine
[SELECT FROM: Access control policy; procedures addressing least privilege; list of assigned access authorizations (user privileges); system configuration settings and associated documentation; system audit records; system security plan; other relevant documents or records].
Interview
[SELECT FROM: Organizational personnel with responsibilities for defining least privileges necessary to accomplish specified tasks; organizational personnel with information security responsibilities; system/network administrators].
Test
[SELECT FROM: Mechanisms implementing least privilege functions].
Overlays
STIGs & CCIs
No STIG checks or CCI mappings are currently loaded for AC-6. This section is architected to display, per product: STIG ID, Finding ID, Severity, Title, Description, Check, Fix, CCI, and NIST control mapping — but nothing is populated here until a real DISA STIG/CCI dataset is ingested.
Learn more about STIG/CCI integration →Evidence
Categorized from the SP 800-53A "Examine"/"Test" artifact list above by keyword — not an authoritative NIST evidence list.
Policy
- Access control policy
- system security plan
Configuration
- system configuration settings and associated documentation
Testing
- Mechanisms implementing least privilege functions
Other Records
- procedures addressing least privilege
- list of assigned access authorizations (user privileges)
- system audit records
- other relevant documents or records