home/glossary/non-security function

non-security function

nounid 163580·updated Sep 1, 2026
verified

A category of system capability or task — specifically, any operation, feature, or process whose purpose is ordinary business, user-productivity, or operational activity rather than the administration, enforcement, or configuration of security controls. In NIST SP 800-171 and related least-privilege frameworks, it serves as the contrast class to "security functions" (privileged operations such as modifying access policies, managing accounts, or configuring audit mechanisms), and the distinction drives the rule that elevated privileges must not be active during routine work. Practitioners use it to draw the boundary at which a privileged account or role must step down to a non-privileged one, limiting the blast radius of credential compromise or user error during everyday tasks.

MWE

Source

document
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systems
found in
proposed during MWE review
element
e0204
proposed by
dorianc@moxywolf.com
discovery
ManualCuration
when accessing non-the sentence this term was read in
Where the definition came fromawaiting curator confirmation

generalized from a web lookup of the quoted expression at proposal time Verdict: term of art.

A definition generalized from search results is a draft to react to, not provenance. Confirm it against an authority document before this term is verified.

A web lookup ran when this term was proposed

A category of system or application capability whose purpose is the delivery of business, operational, or user productivity outcomes — email, file editing, data entry, reporting — as distinct from capabilities that enforce, configure, audit, or administer the security posture of the system itself. Standards such as NIST SP 800-171 contrast it with "security functions," which include the elevated capabilities that privileged accounts are granted to access resources otherwise restricted to non-privileged users. The expression is used operationally to require that users holding privileged accounts drop to non-privileged accounts when doing work that does not involve those security capabilities, thereby limiting unauthorized access to and manipulation of security functions or security-relevant information. The distinction is the basis for enforcing least-privilege and separation-of-duties controls: users may only have access to the minimum level of information and resources necessary to perform their job functions.

Advisory only. A term this product ships is defined by an authority document, not by a search result.

Proposed during multiword review of this document in the CKI mapping queue.

Attested in

NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systems1 citation · 1 confirmed by a reviewer · observed 2026-09-01 under anchor/0.9/36451/2026-09-01
03.01.06.b

Classifications

Entity Type

Unknown75%llm-generatedmulti_axis_classifier_queued.v1

Sensitivity

Regulated80%manual reviewllm:claude-haiku-4-5

Information Class

unclassified

Variants

plural
non-security functions
possessive
non-security function's
pluralpossessive
non-security functions'

Framework definitions

NIST SP 800-171r31 senseview framework →
§1 · attested_usage_reviewer_confirmed
No definition is given in NIST SP 800-171r3. The term is attested in use at 1 citation in that document; a definition is pending curation.
Increment 2: attested in 800-171r3 without a glossary definition.
Legacy lexicon import1 senseview framework →
§1 · web_lookup_draft
A category of system capability or task — specifically, any operation, feature, or process whose purpose is ordinary business, user-productivity, or operational activity rather than the administration, enforcement, or configuration of security controls. In NIST SP 800-171 and related least-privilege frameworks, it serves as the contrast class to "security functions" (privileged operations such as modifying access policies, managing accounts, or configuring audit mechanisms), and the distinction drives the rule that elevated privileges must not be active during routine work. Practitioners use it to draw the boundary at which a privileged account or role must step down to a non-privileged one, limiting the blast radius of credential compromise or user error during everyday tasks.
DR-088 backfill from the noun definition column

Outgoing relationships

No outgoing triples
This term is not the subject of any RDF-style relationship yet.

Incoming relationships

No incoming triples
No other term currently asserts a relationship to this one.