home/glossary/information flow control policy

information flow control policy

nounid 163545·updated Aug 30, 2026
verified

A security or privacy policy construct that specifies the authorized paths and directions along which data may move—within a system, between systems, or across security/privacy domains—based on the characteristics of the information itself or its path rather than on who holds access rights to it. It is distinct from access control policy in that it governs *where* information may travel rather than *who* may read it, and it is typically enforced at boundary devices (firewalls, guards, proxies, data-loss-prevention tools) through rule sets keyed to data classification labels, content, or network attributes. In practice, organizations define organization-specific information flow control policies and then implement enforcement mechanisms—such as one-way data diodes, content filters, or export restrictions—to ensure transfers never violate those policies.

MWE

Source

document
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systems
found in
proposed during MWE review
element
e0181
proposed by
dorianc@moxywolf.com
discovery
ManualCuration
information flowthe 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 rule set or named security requirement that specifies which subjects, information objects, and operations are permitted to move data between security domains, classification levels, or trust boundaries — governing *where* information may travel rather than merely *who* may access a container. It 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 the Common Criteria framework, an information flow control policy controls access to the information, independent of its container, and its scope of control is characterised by three sets: the subjects under control of the policy, the information under control of the policy, and the operations which cause controlled information to flow to and from controlled subjects. In practice, organizations use such policies as the basis for enforcement mechanisms — firewalls, content filters, cross-domain guards, and label-based routing rules — to control the flow of information between designated sources and destinations within systems and between connected systems, with flow control based on the characteristics of the information and/or the information path.

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 Systems2 citations · 2 confirmed by a reviewer · observed 2026-10-20 under anchor/0.9/36554/2026-10-20/set-r11, anchor/0.9/36451/2026-09-01
03.01.03 ¶ 403.01.03 ¶ 4

Classifications

Entity Type

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

Sensitivity

unclassified

Information Class

unclassified

Variants

plural
information flow control policies
possessive
information flow control policy's
pluralpossessive
information flow control policies'

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 security or privacy policy construct that specifies the authorized paths and directions along which data may move—within a system, between systems, or across security/privacy domains—based on the characteristics of the information itself or its path rather than on who holds access rights to it. It is distinct from access control policy in that it governs *where* information may travel rather than *who* may read it, and it is typically enforced at boundary devices (firewalls, guards, proxies, data-loss-prevention tools) through rule sets keyed to data classification labels, content, or network attributes. In practice, organizations define organization-specific information flow control policies and then implement enforcement mechanisms—such as one-way data diodes, content filters, or export restrictions—to ensure transfers never violate those policies.
DR-088 backfill from the noun definition column
Web lookup drafts1 senseview framework →
§1 · web_lookup_draft
A rule set or named security requirement that specifies which subjects, information objects, and operations are permitted to move data between security domains, classification levels, or trust boundaries — governing *where* information may travel rather than merely *who* may access a container. It 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 the Common Criteria framework, an information flow control policy controls access to the information, independent of its container, and its scope of control is characterised by three sets: the subjects under control of the policy, the information under control of the policy, and the operations which cause controlled information to flow to and from controlled subjects. In practice, organizations use such policies as the basis for enforcement mechanisms — firewalls, content filters, cross-domain guards, and label-based routing rules — to control the flow of information between designated sources and destinations within systems and between connected systems, with flow control based on the characteristics of the information and/or the information path.
Drafted by the propose-term web lookup (PD-018); a curator confirms or replaces it.

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.