03.01.07 — Least Privilege – Privileged Functions

Official NIST requirement content

Security requirement

a.Prevent non-privileged users from executing privileged functions.
b.Log the execution of privileged functions.

Official NIST discussion

Discussion

Privileged functions include establishing system accounts, performing system integrity checks, conducting patching operations, changing system configuration settings, or administering cryptographic key management activities. Non-privileged users do not possess the authorizations to execute privileged functions. Bypassing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users. This requirement represents a condition achieved by the definition of authorized privileges in 03.01.01 and privilege enforcement in 03.01.02. The misuse of privileged functions — whether intentionally or unintentionally by authorized users or by unauthorized external entities that have compromised system accounts — is a serious and ongoing concern that can have significant adverse impacts on organizations. Logging the use of privileged functions is one way to detect such misuse and mitigate risks from advanced persistent threats and insider threats.

Bare Metal Cyber interpretation

Implementation perspective

Treat Least Privilege – Privileged Functions as a CUI protection outcome that must be reflected in the system boundary, documented implementation, operational behavior, and assessment evidence. Pay particular attention to approved identities, least privilege, remote access, information flow, and the full account lifecycle.

Confirm the requirement is in scope for the CUI system components, services, users, and external connections being assessed.
Resolve every organization-defined parameter through an approved governance and tailoring process.
Map each clause of the requirement to an accountable owner, implementation mechanism, and evidence source.
Verify that inherited and shared implementations are supported by current provider evidence and responsibility boundaries.
Collect evidence during normal operation and review changes, exceptions, and deficiencies on a risk-based cadence.

Questions to ask

Which CUI assets, data flows, users, and services are protected by this requirement?
Which portions are implemented locally, inherited, shared, or not applicable, and what evidence supports that determination?
Do the system security plan, deployed configuration, operating process, and assessment evidence tell the same story?
What change, incident, or threshold should trigger reassessment?

Evidence and validation

access authorization and approval records
account inventories and entitlement exports
access review results
authentication and authorization logs

Common failure patterns

CUI access that exceeds mission need
shared or orphaned accounts
remote access paths outside the approved boundary
access reviews that cannot be reconciled to deployed permissions

Official NIST SP 800-171A content

Assessment objectives and methods

Assessment objectives (2)

b.
the execution of privileged functions is logged.
a.
non-privileged users are prevented from executing privileged functions.

Examine

access control policy and procedures
procedures for least privilege
system design documentation
system configuration settings
system audit records
list of audited events
list of privileged functions to be audited and associated user account assignments
system security plan
other relevant documents or records

Interview

personnel with responsibilities for reviewing least privileges
personnel with information security responsibilities
system developers
system administrators

Test

mechanisms for auditing the execution of least privilege functions
mechanisms for implementing least privilege functions for non-privileged users

Official source-control relationships

Source NIST SP 800-53 controls

These controls are referenced by the official SP 800-171 Rev. 3 OSCAL record. Open the corresponding control pages for complete control text, enhancements, D3FEND mappings, and related learning.

Source controlAC-6(9)Open SP 800-53 control →Source controlAC-6(10)Open SP 800-53 control →

Source record

Authoritative sources

Bare Metal Cyber is an independent educational publisher and is not affiliated with or endorsed by NIST. The official publications, the responsible federal agency, and the governing contract or agreement determine applicability, tailoring, assessment depth, and required implementation.