home/glossary/flow control restrictions include

flow control restrictions include

nounid 163533·updated Aug 30, 2026
verified

The specific policy-derived constraints — such as blocking spoofed traffic, preventing unencrypted transmission of export-controlled data, or limiting cross-organizational data transfers by content type — that an organization imposes under an information flow control regime. They are distinguished from access control (which governs *who* may reach information) by governing instead *where* information may travel within or between systems, irrespective of who subsequently accesses it. In practice, security architects and compliance teams invoke the concept when specifying, auditing, or implementing the enforceable rules that make an information flow control policy (e.g., NIST AC-4) operational.

MWE

Source

document
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systems
found in
proposed during MWE review
element
e0179
proposed by
dorianc@moxywolf.com
discovery
ManualCuration
can transit within a system and between systems (in contrast to who is allowed to access the information) and without regard to subsequent accesses to that information. Flow control restrictions include keepingthe 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

The set of policy-derived rules and enforcement mechanisms that constrain how information may move across paths, boundaries, or domains within and between systems — distinguished from access control in that they govern *where* data may travel rather than *who* may read it, and operate independently of what a recipient subsequently does with the information. Information flow control regulates where information can travel within a system and between systems, in contrast to who is allowed to access the information, and without regard to subsequent accesses to that information. In practice the restrictions are implemented at boundary-enforcement points (firewalls, guards, proxies, routers) through rule sets keyed to the characteristics of the information or the information path; flow control is based on the characteristics of the information and/or the information path, and enforcement occurs in boundary protection devices that employ rule sets or configuration settings that restrict system services, provide packet-filtering based on header information, or message-filtering based on message content. Concrete instances span a wide range: they include blocking external traffic that claim

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.03 ¶ 2

Classifications

Entity Type

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

Sensitivity

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

Information Class

unclassified

Variants

plural
flow control restrictions includes
possessive
flow control restrictions include's
pluralpossessive
flow control restrictions includes'

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
The specific policy-derived constraints — such as blocking spoofed traffic, preventing unencrypted transmission of export-controlled data, or limiting cross-organizational data transfers by content type — that an organization imposes under an information flow control regime. They are distinguished from access control (which governs *who* may reach information) by governing instead *where* information may travel within or between systems, irrespective of who subsequently accesses it. In practice, security architects and compliance teams invoke the concept when specifying, auditing, or implementing the enforceable rules that make an information flow control policy (e.g., NIST AC-4) operational.
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.