home/glossary/travel requirement

travel requirement

nounid 163513·updated Aug 30, 2026
verified

This is a compositional phrase, not a term of art. In authority documents such as NIST SP 800-53, it appears in supplemental guidance as an ordinary English description of an operational circumstance — specifically, a practical need arising from an employee or user traveling — used to justify or explain a particular account attribute, access permission, or system configuration (for example, enabling a temporary account or remote-access credential). NIST SP 800-53 Rev. 4 notes that account attributes and conditions of use reflect both "system-related requirements" and "mission/business" considerations, within which physical travel situations fall as one illustrative case. The phrase carries no standardized technical definition of its own; its meaning in any given passage is fully determined by its ordinary constituent words in context.

MWE

Source

document
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systems
found in
proposed during MWE review
element
e0163
proposed by
dorianc@moxywolf.com
discovery
ManualCuration
to facilitate travel requirements).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: compositional.

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 business/operational condition — specifically, the need for personnel to access systems or data remotely while physically away from a primary work location — that must be factored into the design of account attributes and access-control configurations. It distinguishes itself from general access requirements by being bound to mobility: the condition that the user is geographically displaced (e.g., on a business trip or working from a remote site) rather than working in a fixed environment. In the field it appears as one of several mission/business justifications that authorize non-default account attributes such as extended remote-access windows, modified time-of-day restrictions, or adjusted point-of-origin permissions.

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.01.h ¶ 2

Classifications

Entity Type

Requirement85%llm-generatedllm:claude-haiku-4-5

Sensitivity

unclassified

Information Class

unclassified

Variants

plural
travel requirements
possessive
travel requirement's
pluralpossessive
travel requirements'

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
This is a compositional phrase, not a term of art. In authority documents such as NIST SP 800-53, it appears in supplemental guidance as an ordinary English description of an operational circumstance — specifically, a practical need arising from an employee or user traveling — used to justify or explain a particular account attribute, access permission, or system configuration (for example, enabling a temporary account or remote-access credential). NIST SP 800-53 Rev. 4 notes that account attributes and conditions of use reflect both "system-related requirements" and "mission/business" considerations, within which physical travel situations fall as one illustrative case. The phrase carries no standardized technical definition of its own; its meaning in any given passage is fully determined by its ordinary constituent words in context.
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.